From mboxrd@z Thu Jan 1 00:00:00 1970 From: himbA Date: Fri, 12 Mar 2004 23:01:52 +0100 Subject: [U-Boot-Users] ML300 NFS rfs mount problem In-Reply-To: <4051FF11.6080902@lucent.com> References: <4051FF11.6080902@lucent.com> Message-ID: <40523350.1070707@email.si> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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/ 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