On Thu, Mar 03, 2011 at 01:22:41PM +0100, Vanalme Filip wrote: > In the current phase, I can boot the kernel, but it panics when trying to mount the root filesystem. > I downloaded a root filesystem from the server into the dedicated NAND partition : tftp rootfs.jffs2 /dev/nand0.root.bb > This seems to be OK. > > However, I have doubts about the bootargs I'm passing to the kernel : > > commandline: console=ttymxc0,115200 ip=dhcp root=/dev/mtdblock3 rootfstype=jffs2 earlyprintk mtdparts=mxc_nand:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root) > > Does this look OK ? Yes, looks good. > > These are the last lines of the console output when booting the kernel : > > IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.0.49.70 > IP-Config: Complete: > device=eth0, addr=10.0.49.70, mask=255.255.0.0, gw=10.0.127.254, > host=10.0.49.70, domain=televic.com, nis-domain=(none), > bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath= > VFS: Unable to mount root fs via NFS, trying floppy. > List of all partitions: > No filesystem could mount root, tried: jffs2 > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) Do you have enabled the mxc_nand driver in the kernel and also mtd command line partitioning (CONFIG_MTD_CMDLINE_PARTS)? Sascha -- 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
