Am 31.05.2012 um 20:27 schrieb Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > Hi Peter, > > On Fri, May 25, 2012 at 11:35:36AM +0200, Peter Kuennemann@Crane-Soft wrote: >> >> >> To have kernel in flash and rootfs on MMC i tried bootargs as: >> >> ... root=/dev/mmcblk0p1 rootfstype=ext2 rootflags=noatime rw noinitrd rootwait .. >> >> and it boots the kernel properly from flash up to: >> ... >> mmcblk0: mmc0:a95c SD01G 968 MiB <== Recognized the sd card >> mmcblk0: p1 <== and partion 1 >> ... >> 1f00 256 mtdblock0 (driver?) >> 1f01 128 mtdblock1 (driver?) >> 1f02 2048 mtdblock2 (driver?) >> 1f03 30336 mtdblock3 (driver?) >> 1f04 1048576 mtdblock4 (driver?) >> b300 992000 mmcblk0 driver: mmcblk >> b301 991585 mmcblk0p1 <=== Something missing here? >> No filesystem could mount root, tried: ext2 <=== >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) <=== >> >> The mmc does contain a ext2 filesystem with the proper rootfs copied from >> the jffs2.image that I mounted under Ubuntu as loop device. The kernel has ext2 fs >> support compiled in. >> >> The rootfs on the mmc is properly accessible when booting kernel and flash footfs >> on the very same platform. > > Has this been solved in the mean time? The above looks correct, I have > no idea what's wrong. > > Sascha > Sascha, I am sorry but this issue has not yet been resolved. I am currently out of office but will pick it up after my return. It may well be a Kernel configuration Problem. Peter > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
