• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 ... 7 8 [9] 10
 81 
 on: September 20, 2013, 03:04:07 PM 
Started by cbxbiker61 - Last post by birdman
If someone can point me to a suitable cross-compiling toolchain for an Intel x86_64 host, I'm happy to try building some kernels to find out what change makes the difference.
I have the while thing set up for my Plug by using qemu in a VirtualBox host running Debian (which is all on my Linux Mint workstation, so I can run with multiple cores, and lots of memory, if I wish...).
That's quite simple to set-up.  (I have qemu setups there for my Raspberry Pi and Asus66 also..)

 82 
 on: September 20, 2013, 03:59:23 AM 
Started by cbxbiker61 - Last post by pqa
Regarding the console problem, I have identified the following so far:

The Fedora 3.10.10 kernel with device tree, with the working console, reports the following in dmesg at boot time:
[   19.249385] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[   19.250677] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   19.775383] console [ttyS0] enabled

The Cbxbiker 3.10.10 kernel reports:
[   12.563947] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
and then a few lines later:
[   12.691809] Warning: unable to open an initial console.

so it's clearly not finding the serial port.
The obvious difference here, other than not reporting the hardward, is that the Fedora kernel has interrupt sharing enabled.

Looking at the device trees, the main differences are:
Cbxbiker:
clocks = <0x03, 0xn>          # throughout the device tree
phandle for core-clocks = 0x02
phandle for clock-gating-control = 0x03

Fedora:
clocks = <0x02, 0xn>
phandle for core-clocks = 0x03
phandle for clock-gating-control = 0x02

The clocks value is specified in the source file as &gate_clk, and I haven't found how the device tree compiler translates that to 0x02 or 0x03.
The phandle entries are generated by the DT compiler.

Also, Cbxbiker has applied the following patches:
Added cpus section
patched address of crypto engine
but neither of these would appear to affect the console.

There are lots of differences in the kernel configuration, but I've tried to pick out the ones relevant to the UART:
Cbxbiker:
CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=2
# CONFIG_SERIAL_8250_EXTENDED is not set
CONFIG_USB_SERIAL=m

Fedora:
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y

Since the working console output is referencing MMIO, I have also had a look at the kernel config relating to that.

Cbxbiker:
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
# CONFIG_VIRTIO_MMIO is not set

Fedora:
CONFIG_REGMAP_MMIO=y
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_TULIP_MMIO=y
CONFIG_VIA_RHINE_MMIO=y
CONFIG_MDIO_BUS_MUX_MMIOREG=m
CONFIG_RT2X00_LIB_MMIO=m
CONFIG_SPI_DW_MMIO=m
CONFIG_VIRTIO_MMIO=m

I'm guessing here, but I wonder if CONFIG_REGMAP_MMIO=y needs to be set for the serial port hardware to be found.

If someone can point me to a suitable cross-compiling toolchain for an Intel x86_64 host, I'm happy to try building some kernels to find out what change makes the difference.

 83 
 on: September 19, 2013, 04:22:35 PM 
Started by PeniWize - Last post by PeniWize
I have an old dreamplug (0101 is on the sticker on the back).  The model number is 003-DS2001.  It was running Debian and I ran an update via apt-get, which failed half way through, and now the OS is corrupt so I need to rebuild.  I have an SD card reader/writer so I don't have to mess with updating via UBoot.  I've tried the old (v1, v2) Debian and Ubuntu distributions on https://code.google.com/p/dreamplug/downloads/list and both seem to be out of date.  The debian version also sometimes hangs after reboot.  I haven't diagnosed why.  Neither is able to successfully 'apt-get update' and neither appears to be exactly what I received from the factory.  I also downloaded and tried v9 and v10, but neither worked properly.

Question 1: Is dreamplug compatible with other plug computers?  Should I be looking for content for sheevaplpug or guruplug or something else?

Question 2: Is is possible to get a newer or more current Linux distribution running on my dreamplug?  I don't care which distro it is as long as it works.  I'm also willing to update UBoot, if necessary.

Any instruction is grealy appreciated.

Thanks!

 84 
 on: September 18, 2013, 07:11:58 AM 
Started by cbxbiker61 - Last post by pqa
Thanks for the update re read-only rootfs. After booting the rootfs is definitely mounted read-only, so it looks like my systemd scripts aren't running properly then when using the Cbxbiker kernels. I dig into this a bit more. It's probably due to Fedora using an initrd, and I am now suspecting that some scripts are run on that before switching to the permanent rootfs.

 85 
 on: September 18, 2013, 02:07:23 AM 
Started by cbxbiker61 - Last post by apemberton
I confirm that I find the same as Birdman on the disk thing. Also because my /etc/fstab requires it, my disks are unmounted, a fs check performed and then remounted. This is normal and a bit of a lifesaver as the i-node count get corrupted in service.

 86 
 on: September 17, 2013, 06:20:12 PM 
Started by cbxbiker61 - Last post by birdman
I am having one other problem with the Cbxbiker kernels, which I don't get with a Fedora kernel (my root filesystem is on sdb3).

Part way through the boot process, I get the following messages in the log:
[    9.821912] EXT3-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.823149] EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.840065] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[    9.840113] VFS: Mounted root (ext4 filesystem) readonly on device 8:19.

and I end up with the root filesystem mounted read only.

Can anyone give me some suggestions about what is causing this problem..
Are you sure it's an actual problem?
Mine does the same (it tries ext3, ext2, ext4 in that order, hence the error messages).
But shortly after mounting the root readonly (which is always does at start with) it then reports:
Quote
Sep 16 00:23:46 plug kernel: EXT4-fs (sda1): re-mounted. Opts: (null)
Sep 16 00:23:46 plug kernel: EXT4-fs (sda1): re-mounted. Opts: (null)
and it is then mounted read/write.

 87 
 on: September 17, 2013, 04:43:49 PM 
Started by cbxbiker61 - Last post by pqa
I am having one other problem with the Cbxbiker kernels, which I don't get with a Fedora kernel (my root filesystem is on sdb3).

Part way through the boot process, I get the following messages in the log:
[    9.821912] EXT3-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.823149] EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.840065] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[    9.840113] VFS: Mounted root (ext4 filesystem) readonly on device 8:19.

and I end up with the root filesystem mounted read only.

Can anyone give me some suggestions about what is causing this problem.

Many thanks.

 88 
 on: September 17, 2013, 01:11:29 PM 
Started by cbxbiker61 - Last post by pqa
Tony,

The Fedora kernels are downloadable from http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=3547 . The fc18 series are the last ones being built for armv5tel. If  you click on a kernel you are interested in, there is an option to download the source RPM. Alternatively all the source files for the build, except the kernel itself, are available from http://pkgs.fedoraproject.org/cgit/kernel.git/log/?h=f18

Quentin

 89 
 on: September 17, 2013, 12:23:52 PM 
Started by cbxbiker61 - Last post by apemberton
Thanks for your info and update. I think you are on to it. Is there a link for the Fedora kernel DT source? More minds the better especially to aid my old, worn out grey cells! Tony.

 90 
 on: September 17, 2013, 12:12:19 PM 
Started by Daniel Ng - Last post by trampjuice
IT WAS THE PSU!!!

It has taken me this long to connect a regulated bench PSU. INSANE. My old PSU was a cheap  220V in 5v 2a out dc, so at UK 240v it gradually must have failed over about 2 years. 

Have replaced and hopefully trouble free from now.

Pages: 1 ... 7 8 [9] 10