Timo Juhani Lindfors a écrit , Le 05/11/2011 00:08: > Gilles Filippini <p...@debian.org> writes: >> Same error here. My guess is is that's due to linux-base which warns >> during (re-)configuration: > > But linux-base is userland? The error is printed before linux even > mounts the rootfs so nothing there can possibly cause this?
Well. I should have written: > My guess is this is due to the kernel change related to device names > reported by linux-base during its configuration. >> I'm using qi-menu to handle multi-boot. There must be a way to change >> its configuration so that it uses UUIDs. > > qi-menu? So you use initramfs + kexec? Have you thought about uploading > qi-menu to debian? ;-) Please read: qi-bootmenu. I'm not that at ease with the kernel/bootloader world :/ Anyway, I've managed to go a bit further using a /boot/append-GTA02 file specifying: > root=UUID=<uuid-for-/dev/mmcblk0p2> rootwait But then the boot process stops with: > 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? (which is correct from the 2.6.34 kernel side). Thanks, _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
