nfs: server xxx.xxx.xxx.xxx not responding, still trying

To add to this,  I have also seen this when using wireless networks.  Also, to add to Bernie's comments on duplicate MAC addresses, this is very common when you have multiple virtual machines (say VMWare images for Host) in the same local network unless you take steps to ensure that each virtual machine has a unique MAC address.

I just wanted to share our experience with the DM6467 EVM.

We had similar messages, and at other times u-boot wouldn't load the kernel over NFS (we boot the entire board from an NFS server). The intermittent trouble occurred while we were connected to a gigabit switch. Moving to a 10/100 Mbps switch seems to have resolved the issue.

This is a very good point.  I believe there is a u-boot patch that will allow u-boot to work with GBit Ethernet.

I also came across the site below when looking at this, which hints at a faster ethernet card causing trouble with NFS, they suggest another fix by using smaller block sizes on the client, something like this may allow you to use the gigabit switch again. 

http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding

would you not need to enable the option in the kernel configuration about allowing the RFS to be as the NFS?

can anyone confirm?

If there is such an option for RFS as NFS than you probably would need to enable it, I have not seen the option myself, it must be enabled by default in the TI builds.

I tried it out...it seems that there would have been some issue in the custom HW I was trying my kernel with. My custom PHY It seems to work fine with the default DVEVM configuration; but still its a mystery if we need it or not. TI default kernel doesnt need that option to be enabled!

Sorry to have lost out the path

Device Drivers -> FileSystems -> Network File Systems -> Root File System on NFS.

Hi,
i am trying to make a NFS mount but i obtain this same error

IP-Config: Guessing netmask 255.0.0.0
IP-Config: Complete:
      device=eth0, addr=10.0.0.2, mask=255.0.0.0, gw=255.255.255.255,
     host=10.0.0.2, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath=
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
VFS: Mounted root (nfs filesystem).
Freeing init memory: 184K
Warning: unable to open an initial console.
CSL: Module install successful, device major num = 253
CSL: Module version 0.10.00, built on Jul 21 2010 11:47:15
I2C: Module install successful, device major num = 252
DMA: Module install successful, device major num = 251
DRV: Module install successful
DRV: Module built on Jul 21 2010 11:47:18
DRV: EDMACC.QUEPRI  = 00000777
DRV: SYSTEM.MSTPRI0 = 00550011
DRV: SYSTEM.MSTPRI1 = 00000444
DRV: ISP.BCR        = 00000002
CMEMK module: built on Jul 21 2010 at 11:46:36
  Reference Linux version 2.6.18
  File /home/software/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
allocated heap buffer 0xc5000000 of size 0x4800000
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x83800000)
cmemk initialized
EDMAK module: built on Jul 21 2010 at 11:46:39
  Reference Linux version 2.6.18
  File /home/software/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/edma/src/module/edmak.c
IRQK module: built on Jul 21 2010 at 11:46:40
  Reference Linux version 2.6.18
  File /home/software/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/irq/src/module/irqk.c
irqk initialized
DavinciDisplay DavinciDisplay.1: Before finishing with S_FMT:
layer.pix_fmt.bytesperline = 640,
 layer.pix_fmt.width = 640,
 layer.pix_fmt.height = 480,
 layer.pix_fmt.sizeimage =460800
DavinciDisplay DavinciDisplay.1: pixfmt->width = 640,
 layer->layer_info.config.line_length= 640
io scheduler deadline registered
io scheduler cfq registered
 sbulla: unknown partition table
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
loop: loaded (max 8 devices)
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
Loading iSCSI transport class v1.1-646.<5>iscsi: registered transport (tcp)
 sbulla: unknown partition table
nfs: RPC call returned error 101
nfs: RPC call returned error 101
nfs: server 10.0.0.1 not responding, still trying
nfs: server 10.0.0.1 not responding, still trying


in this case i have connect my DM365IPNC-MT5 to host directly (but i obtain the same error connecting them in main lan with DHCP server)
what could happen? what can i try to do to solve this?

best regards

ADC said:

in this case i have connect my DM365IPNC-MT5 to host directly (but i obtain the same error connecting them in main lan with DHCP server)
what could happen? what can i try to do to solve this?

As suggested by the prior posts, this would normally be some kind of network connection failure, I would probably start by going into the U-Boot prompt and trying to ping the host PC you are attempting to NFS mount from, and/or boot the board into Linux through an alternate root file system (flash, SD, etc) and try pinging from there. If you cannot ping than you would need to look further into how you have your network setup. It may also be worth trying to mount through another PC or another network (i.e. different switch, router, etc), it could be that you just happen to be getting blocked with the two setups you have tried.

Unfortunately I don't have one of these DM365IPNC kits so I am not sure if there is anything special you have to do to get the networking going on them, you may want to ask the manufacturer of the kit.

Hi Bernie,
i have tried with another filesystem on the same host and in this way i can boot correctly. The first was the one provided by appro DM365IPNC kit and the last is the one installed with downloaded DaVinci DVSDK. I haven't understand the cause .... anyway now i can work

thanks,
regards