* [U-Boot-Users] ML300 NFS rfs mount problem
@ 2004-03-12 18:18 Mike Wellington
2004-03-12 22:01 ` himbA
0 siblings, 1 reply; 2+ messages in thread
From: Mike Wellington @ 2004-03-12 18:18 UTC (permalink / raw)
To: u-boot
My kernel command line is set as follows in
include/configs/ml300.h
> #define CONFIG_BOOTARGS "console=ttyS0,9600 root=/dev/nfs rw \
> nfsroot=135.4.21.60:/opt2/timesys/linux/4.0/amxap100/rfs \
> rootpath=/opt2/timesys/linux/4.0/amxap100/rfs \
> ip=135.4.21.155:135.4.21.60:135.4.21.254:255.255.254.0:prolab6::off"
However when the kernel outputs its command line
during the boot process I see:
"Kernel command line: console=ttyS0,9600
root=/dev/nfs rw
nfsroot=135.4.21.60:/opt2/timesys/linux/4.0/amxap100/rfs
rootpath=/opt2/timesys/linux/4.0/amxap100/rfs
ip=135.4.21.155:135.4.21.60:135.4.21.254:255.255.254.0:prolab6::off"
Then, later I see:
"IP-Config: Complete: device=eth0,
addr=135.4.21.155, mask=255.255.254.0,
gw=135.4.21.254, host=prolab6, domain=,
nis-domain=(none)
bootserver=135.4.21.60 rootserver=135.4.21.60
rootpath="
Note that rootpath is now empty, even though I
set it on the command line.
Can somebody give me a clue?
--
=mike wellington
wellington at lucent.com
303.920.6412 Desk
720.434.7559 Cell
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] ML300 NFS rfs mount problem
2004-03-12 18:18 [U-Boot-Users] ML300 NFS rfs mount problem Mike Wellington
@ 2004-03-12 22:01 ` himbA
0 siblings, 0 replies; 2+ messages in thread
From: himbA @ 2004-03-12 22:01 UTC (permalink / raw)
To: u-boot
Mike Wellington wrote:
>
> My kernel command line is set as follows in
> include/configs/ml300.h
>
>> #define CONFIG_BOOTARGS "console=ttyS0,9600 root=/dev/nfs rw \
>> nfsroot=135.4.21.60:/opt2/timesys/linux/4.0/amxap100/rfs \
>> rootpath=/opt2/timesys/linux/4.0/amxap100/rfs \
>> ip=135.4.21.155:135.4.21.60:135.4.21.254:255.255.254.0:prolab6::off"
>
>
> However when the kernel outputs its command line
> during the boot process I see:
>
> "Kernel command line: console=ttyS0,9600 root=/dev/nfs rw
> nfsroot=135.4.21.60:/opt2/timesys/linux/4.0/amxap100/rfs
> rootpath=/opt2/timesys/linux/4.0/amxap100/rfs
> ip=135.4.21.155:135.4.21.60:135.4.21.254:255.255.254.0:prolab6::off"
>
> Then, later I see:
>
> "IP-Config: Complete: device=eth0, addr=135.4.21.155,
> mask=255.255.254.0, gw=135.4.21.254, host=prolab6, domain=,
> nis-domain=(none)
> bootserver=135.4.21.60 rootserver=135.4.21.60
> rootpath="
>
>
> Note that rootpath is now empty, even though I
> set it on the command line.
>
> Can somebody give me a clue?
>
my config
IP-Config: Complete:
device=eth0, addr=10.10.10.2, mask=255.255.255.0, gw=10.10.10.1,
host=xcep, domain=, nis-domain=(none),
bootserver=10.10.10.1, rootserver=10.10.10.1, rootpath=
my rootpath is also empty but i have 'xcep' dir that matches my target
name under /tftpboot like:
/tftpboot/xcep/<root fs>
I previously had different dir on tftp server but using this config
saved some issues with booting linux...
IMHO, if your fs does not get mounted this is not the issue.
rgds,himba
--
..because under Linux "if something is possible in principle,
then it is already implemented or somebody is working on it".
--LKI
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-03-12 22:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-12 18:18 [U-Boot-Users] ML300 NFS rfs mount problem Mike Wellington
2004-03-12 22:01 ` himbA
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox