From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Mark E Mason <mason@broadcom.com>
Cc: LMO <linux-mips@linux-mips.org>,
"mmason@upwardaccess.com" <mmason@upwardaccess.com>
Subject: Re: Booting top-of-tree bcm47xx as nfs-root with cfe only (no sibyl)
Date: Wed, 26 Nov 2008 23:10:54 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0811262304510.23566@ftp.linux-mips.org> (raw)
In-Reply-To: <BD3F7F1EFBA6D54DB056C4FFA45140080348EC801C@SJEXCHCCR01.corp.ad.broadcom.com>
On Wed, 26 Nov 2008, Mark E Mason wrote:
> Linux version 2.6.28-rc6 (mason@hawaii) (gcc version 3.4.4) #4 Wed Nov 26 13:59:54 PST 2008
> arcs_cmdline='root=/dev/nfs rw nfsroot=10.0.1.184:/home/mason/debian-root-el console=ttyS0,115200'<6>console [early0] enabled
[...]
> VFS: Cannot open root device "nfs" or unknown-block(0,255)
> Please append a correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)
For NFS root to work you have to specify an "ip=" option too, so that a
network interface gets assigned an address somehow. The default for this
option was changed to "off" at some point with no respective update to
documentation apparently.
Maciej
next prev parent reply other threads:[~2008-11-26 23:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 22:56 Booting top-of-tree bcm47xx as nfs-root with cfe only (no sibyl) Mark E Mason
2008-11-26 23:10 ` Maciej W. Rozycki [this message]
2008-11-26 23:21 ` Mark E Mason
2008-11-26 23:31 ` Andrew Sharp
2008-11-26 23:57 ` Mark E Mason
2008-11-27 11:09 ` Maciej W. Rozycki
2008-11-27 16:20 ` David Pelton
2008-11-27 16:20 ` David Pelton
2008-11-26 23:52 ` Maciej W. Rozycki
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=alpine.LFD.1.10.0811262304510.23566@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mason@broadcom.com \
--cc=mmason@upwardaccess.com \
/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.