Timo Juhani Lindfors a écrit , Le 05/11/2011 00:46: > Gilles Filippini <p...@debian.org> writes: >>> My guess is this is due to the kernel change related to device names >>> reported by linux-base during its configuration. > > Yeah but since linux-base does not pass device names to qi or linux it > should not be able to cause any of this.
You're right. It was a wrong guess. Read below. >>> mmcblk0: mmc1:b368 USD 7.51 GiB >>> mmcblk0: detected capacity change from 0 to 8067743744 >>> mmcblk0: unknown partition table >> >> What could be missing to recognize the partition table? > > Good question. My guess is that the SD card read is returning only > zeroes for some reason. \o/ It has eventually booted after I played with boot parameters in /boot/append-GTA02. I've ended up with: rootwait glamo_mci.sd_max_clk=5000000 glamo_mci.sd_drive=3 And I removed the root=UUID part which didn't work after the successful mmcblk0 initialization. > Can you try booting with an initramfs? I tested that if I generate it with > > sudo mkinitramfs -o /boot/initrd-GTA02.bin > > it is able to boot using qi patches that enable initramfs support (I > sent those to openmoko-kernel just today). If you use qi-bootmenu you > probably can specify initramfs to the kexec call? I don't know how to do that. Any pointers? gn, _g.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
