Op 29 jan. 2012, om 22:43 heeft Kövesdi György het volgende geschreven: > Hi, > > I reported some days ago a problem with kernel boot: > > [ 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) > > It is caused by the kernel module OMAP_MUX. I tried it on 2.6.39 and 3.0.17: > the same result, but if it is turned off, the kernel boots correctly. > Is it known to work on Beagleborad-C4? Or do i something wrong?
Which u-boot version? I've booted the latest u-boot+ 3.0.17 with rootfs on SD on a B6, C3, C5, xM A and xM C this weekend without problems. _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
