• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 3773 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

nfs mounting using static IP on dm812x

Chandar L
Prodigy 130 points

Hi,

I am using static IP for connecting wit ubuntu linux.  Boot without nfs mounting works fine but if I try nfs mounting as per instructions in the Users Guide, I get "timed out" messages.

my bootargs are:

for normal boot (without nfs mounting)

bootargs=mem=80M vram=4M notifyk.vpssm3_sva=0xBFD00000 console=ttyO0 ,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 ip=192.168.1.168 earlyprintk

for boot with nfs mounting:


nfshost=192.168.1.25
rootpath=/home/chandar/workdir/filesys
bootargs=console=ttyO0 ,115200n8 root=/dev/nfs rw mem=80M vram=4M notifyk.vpssm3_sva=0xBFD00000 nfsroot=$(nfshost):$(rootpath) ,nolock ip=192.168.1.168 earlyprintk

The snapshot of the "timed out" messages with NFS mount option is as below:

TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
Power Management for TI81XX.
Detected MACID=40:5f:c2:61:5c:7c
tps65911-rtc tps65911-rtc: setting system clock to 2011-03-17 11:22:13 UTC (1300360933)

CPSW phy found : id is : 0x4dd074
PHY 0:01 not found
Sending DHCP and RARP requests ...... timed out!
IP-Config: Retrying forever (NFS root)...

CPSW phy found : id is : 0x4dd074
PHY 0:01 not found
Sending DHCP and RARP requests ...

Can someone please let me know why this would be happening?  Also why is this trying to send DHCP requests though I have configured for static IP.

thanks,

Chandar

  • 0
    Expert 2030 points

    Please look here for setting up kernel bootargs:

    4.4 Using a bootloader without RARP

    The ip and nfsroot kernel parameters (which can be hardcoded into the kernel, interactively entered at some bootloader prompts, or included in lilo.conf via the append= parameter; see the next subsection) provide all of the information necessary for the client to set up its ethernet interface and to contact the NFS server, respectively. The parameters are fully documented in Documentation/nfsroot.txt, which is included in the kernel sources (usually found under /usr/src/linux). Here's the format for a machine with a static (pre-assigned) IP address:

    • nfsroot=<NFS-server-IP-number>:/path/on/server/to/nfs_root ip=<client-IP-number>::<gateway-IP-number>:<netmask>:<client-hostname>:eth0:off

    DHCP is much simpler:

    • nfsroot=<NFS-server-IP-number>:/path/on/server/to/nfs_root ip=dhcp

    4.5 Sample kernel command lines

    Here's an example of a complete kernel command line such as you might include in lilo.conf or equivalent; only the IP numbers and NFS path are bogus:

    • root=/dev/nfs rw nfsroot=12.345.67.89:/path/on/server/to/nfs_root ip=dhcp console=ttyS1

    That uses DHCP to assign an IP address to the machine and puts its boot messages (console) on the second serial port. The following is the corresponding example using a static IP address; it also explicitly specifies Busybox's (non-standard) location for init:

    • root=/dev/nfs rw nfsroot=12.345.67.89:/path/on/server/to/nfs_root ip=12.345.67.88::12.345.67.1:255.255.255.0:embed-o-matic:eth0:off console=ttyS1 init=/bin/init

    in your bootargs I would try this, off setting will let the kernel know to use static ip.

    ip=192.168.1.168 :192.168.1.25:::::off


    RV