Hello Maciej!
Do you mean something like this?
setenv LINUX_CMDLINE "root=/dev/nfs rw ip=dhcp
nfsroot=10.0.1.184:/home/mason/debian-root-el"
ifconfig eth1 -auto
boot -elf 10.0.1.184:vmlinux.47xx
[which ... Unfortunatetly doesn't work... :(]
What about CONIFG_ROOT_NFS? Some of the HOWTOs on the net mention it, and it's
still in some (most) of the default config files except for the bcm47xx (but I
added it to mine manually as I couldn't find it in the menuconfig). So it
shouldn't matter... Except that I'm paraniod... Is this a left over 2.4-ism?
I'm thinking this board, plus a USB disk and I should be able to build a
portable mips system that I can actually take with me to hack on... Unlike the
sibyte stuff which usually needs a handtruck to move...
Thanks!
Mark
-----Original Message-----
From: Maciej W. Rozycki [mailto:macro@linux-mips.org]
Sent: Wednesday, November 26, 2008 3:11 PM
To: Mark E Mason
Cc: LMO; mmason@upwardaccess.com
Subject: Re: Booting top-of-tree bcm47xx as nfs-root with cfe only (no sibyl)
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
|