From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: bootargs
Date: Thu, 3 Mar 2011 15:00:07 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00FE1@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20110303123324.GK29521@pengutronix.de>
> -----Original Message-----
> From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
> Sent: donderdag 3 maart 2011 13:33
> To: Vanalme Filip
> Cc: barebox@lists.infradead.org
> Subject: Re: bootargs
>
> 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)?
[Filip]
I have CONFIG_MTD_CMDLINE_PARTS=y and CONFIG_MTD_NAND_MXC=y.
>
> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-03-03 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 12:22 bootargs Vanalme Filip
2011-03-03 12:33 ` bootargs Sascha Hauer
2011-03-03 14:00 ` Vanalme Filip [this message]
2011-03-03 14:13 ` bootargs Sascha Hauer
2011-03-03 14:23 ` bootargs Vanalme Filip
2011-03-03 14:34 ` bootargs Jon Ringle
2011-03-03 14:42 ` bootargs Vanalme Filip
2011-03-03 14:43 ` bootargs Sascha Hauer
2011-03-04 8:18 bootargs Vanalme Filip
2011-03-04 8:30 ` bootargs Sascha Hauer
2011-03-04 12:54 ` bootargs Vanalme Filip
2011-03-04 13:13 ` bootargs Baruch Siach
2011-03-04 13:24 ` bootargs Vanalme Filip
2011-03-04 13:49 ` bootargs Vanalme Filip
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00FE1@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox