2012/1/22 Kövesdi György <kg...@freemail.hu>: > Hi, > > I tried to compile the current (jan 21 2012) version of Angstrom, with > the kernel 3.0.17+ for my Beagleboard, but the currently generated MLO > and u-boot does not boot at all, just hangs immediately after reset.
Are you using 'u-boot.img' and not 'u-boot.bin' ? > Using older versions of MLO and u-boot (from an older image generated by > Narcissus), the kernel starts boot but fails this way: > > [ 4.182769] VFS: Cannot open root device "mmcblk0p2" or > unknown-block(179,2) > [ 4.190246] Please append a correct "root=" boot option; here are the > available partitions: > [ 4.199127] 1f00 512 mtdblock0 (driver?) > [ 4.204437] 1f01 1920 mtdblock1 (driver?) > [ 4.209838] 1f02 128 mtdblock2 (driver?) > [ 4.215209] 1f03 4096 mtdblock3 (driver?) > [ 4.220550] 1f04 255488 mtdblock4 (driver?) > [ 4.225952] b300 3813376 mmcblk0 driver: mmcblk > [ 4.231628] b301 72261 mmcblk0p1 > 00000000-0000-0000-0000-000000000mmcblk0p1 > [ 4.240142] b302 907672 mmcblk0p2 > 00000000-0000-0000-0000-000000000mmcblk0p2 > [ 4.248626] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(179,2) Without seeing the full command line that the kernel saw, is 'rootwait' making it through? -- Tom _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
