Hi, On 2010-06-27, Martin Jansa wrote: > After hopefully lucky incident we have finally switched to new kernel. > It's based on 2.6.32.13 and has DRM/KMS enabled.
> * With slower uSD you can see unknown-block-device while booting. Flash newer > Qi from SHR [3] it is using rootwait instead of rootdelay=1. For u-boot > increase rootdelay or use rootwait. this is somehow not working for me (latest u-boot) - even a rootdelay of 60s will not get me past "Cannot open root device mmcblk0p7 or unknown-block(179,7)". The available partition list includes all NAND partitions and then just "mmcblk0 driver: mmcblk". rootwait anywhere in uboot_env seems to mess up partition selection (it always boots the 2.6.32 kernel on p7, even for other partitions??), but anyway I don't understand how a slow uSD should be an issue with one kernel if it isn't with another - and in any case uboot has already loaded the uImage from that very partition just fine? Is it possible this is more an issue with the driver / initrd (do we have something like that inside the uImage?) not actually providing the device nodes or the like? Does anyone have useful pointers on how to investigate this? I'd also like to do some u-boot debugging (booting always works the *second* time, the first time ends in a quick reset for some opaque reason) but don't know where to start not understanding the hardware in substantial detail.. Florian _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
