Messages

1

Angstrom & OpenZaurus / OpenEmbedded builds, flashes but doesn't boot

« on: June 27, 2004, 05:40:00 pm »

Even on the danger of continously talking to myself:

It was an initrd problem, so changing around with the kernel didn't help. Using the openzaurus 3.3.5 initrd.bin did help.

But why is build/tmp/deploy/images/opie-image-collie-20040624231113.rootfs.jffs2 not a valid initrd.bin?

2

Angstrom & OpenZaurus / OpenEmbedded builds, flashes but doesn't boot

« on: June 25, 2004, 07:05:22 pm »

OK, found it myself when 'diff'ing around. In CMDLINE_CONFIG (or similar) console=ttyS0 has to be removed.

Error output is "RAMDISK: Couldn't find valid RAM disk image starting at 0 [or maybe the 'unprintable character' symbol]".

Any suggestions welcome, otherwise I'll have to go through the kernel config tomorrow again.

Regards
   Markus

3

Angstrom & OpenZaurus / OpenEmbedded builds, flashes but doesn't boot

« on: June 25, 2004, 06:11:51 pm »

After some problems (with conflicting/missing instructions) OpenEmbedded built, I got it flashed (the boot logo changed, so it must have flashed), but afterwards not much happens. Alas, the Zaurus has the unfortunate tendency to be quiet during boot, so I don't know why.

Is there a way to get 'normal' (i.e. like with a desktop) output during kernel boot?

Also,  when looking through the kernel configuration file (at least I assume the .config base/openzaurus-sa-2.4.18..../linux is the configuration file even though it differs from defconfig-collie) I saw that the Minix filesystem is enabled. Is really someone expecting to have a use for that on the Zaurus?

Thanks
    Markus