From: Baruch Siach <baruch@tkos.co.il>
To: Vanalme Filip <F.Vanalme@TELEVIC.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: bootargs
Date: Fri, 4 Mar 2011 15:13:29 +0200 [thread overview]
Message-ID: <20110304131329.GD3143@tarshish> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B0109C@SRV-VS06.TELEVIC.COM>
Hi Vanalme,
On Fri, Mar 04, 2011 at 01:54:38PM +0100, Vanalme Filip wrote:
> barebox 2010.12.0-00073-gfad11e8-dirty (Mar 3 2011 - 09:28:01)
>
> Board: Freescale i.MX27 PDK 3Stack
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xaa (Samsung NAND 256MiB 1,8V 8-bit)
> Bad block table found at page 131008, version 0x01
> Bad block table found at page 130944, version 0x01
> PMIC Power
> Enable FEC
> Reset FEC
> Malloc space: 0xa7b00000 -> 0xa7f00000 (size 4 MB)
> Stack space : 0xa7af8000 -> 0xa7b00000 (size 32 kB)
> running /env/bin/init...
>
> Hit any key to stop autoboot: 3\b\b 2\b\b 1\b\b 0
> loaded zImage from /dev/nand0.kernel.bb with size 1996604
> commandline: console=ttymxc0,115200 ip=dhcp rootfstype=jffs2 root=/dev/nfs nfsroot=10.0.48.80:/tftpboot/rootfs earlyprintk mtdparts=mxc_nand:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root)
[snip]
Removing "rootfstype=jffs2" might help. Just a guess.
baruch
> 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=10.0.48.80, rootpath=
> VFS: Unable to mount root fs via NFS, trying floppy. <======== ??
> List of all partitions:
> 1f00 256 mtdblock0 (driver?)
> 1f01 128 mtdblock1 (driver?)
> 1f02 2048 mtdblock2 (driver?)
> 1f03 259712 mtdblock3 (driver?)
> No filesystem could mount root, tried: jffs2
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
>
>
> I checked the kernel's configuration and I think I have all NFS related items included.
> A showmount -e 10.0.48.80 gives me :
> /tftpboot/rootfs 10.0.0.0/255.255.0.0
> /home/user1/i.MX27/ltib/rootfs 10.0.0.0/255.255.0.0
>
> So, I guess the mounting point is correct.
> The bootargs also look OK to me. However, there's still something I miss here.
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-03-04 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Baruch Siach [this message]
2011-03-04 13:24 ` bootargs Vanalme Filip
2011-03-04 13:49 ` bootargs Vanalme Filip
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 12:22 bootargs Vanalme Filip
2011-03-03 12:33 ` bootargs Sascha Hauer
2011-03-03 14:00 ` bootargs Vanalme Filip
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
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=20110304131329.GD3143@tarshish \
--to=baruch@tkos.co.il \
--cc=F.Vanalme@TELEVIC.com \
--cc=barebox@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.