RE: [Ltib] Cannot NFS/Network Delpoy

[Stuart Hughes]

Hi Frank,

This indicates you've got network problems (maybe hardware/cable/hub).
It could also indicate that you have more that one device with the same
IP addr.

Regards, Stuart

On Fri, 2008-05-16 at 14:57 +1200, Frank Wei wrote:
> Hi Stuart,
> 
>  
> 
> It now works now by doing /etc/init.d/nfs restart
> and /etc/init.d/portmap restart on the host but after that the target
> seems keeps talking to the NFS server. Here are the message after
> rebooting:
> 
>  
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 OK
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
>  
> 
>  
> 
> The reason I have two networks is because the host and target in
> different networks.
> 
>  
> 
> Cheers,
> 
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden 
> Sent: Thursday, 15 May 2008 8:39 p.m.
> To: Frank Wei
> Cc: ltibext
> Subject: RE: [Ltib] Cannot NFS/Network Delpoy
> 
>  
> 
> Hi Frank,
> 
> The IP address you assign to the target must be on the same network
> and free as the NFS server.
> 
> It looks to me like when the network is starting on the target it's
> changing the IP address to something that is not compatible with the
> network address of the NFS server.
> 
> Regards, Stuart
> 
> On Thu, 2008-05-15 at 10:23 +1200, Frank Wei wrote: 
> 
> Hi Stuart,
> 
>  
> 
> After de-select and manually setup the IP address network parameters,
> the NFS server is still not responding. Pleas see some of the
> captures:
> 
>  
> 
> ##############################################################################################
> 
> CP cubic registered
> 
> NET: Registered protocol family 1
> 
> NET: Registered protocol family 17
> 
> NET: Registered protocol family 15
> 
> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> 
> IP-Config: Complete:
> 
>       device=eth0, addr=172.16.10.220, mask=255.255.0.0,
> gw=172.16.0.4,
> 
>      host=172.16.10.220, domain=, nis-domain=(none),
> 
>      bootserver=192.168.0.158, rootserver=192.168.0.158, rootpath=
> 
> Looking up port of RPC 100003/2 on 192.168.0.158
> 
> Looking up port of RPC 100005/1 on 192.168.0.158
> 
> VFS: Mounted root (nfs filesystem).
> 
> free_initmem: __init_begin = 0xc02d8000  __init_end = 0xc02ec000
> 
> Setting the hostname to freescale
> 
> Mounting /proc and /sys
> 
> mount: Mounting proc on /proc failed: No such file or directory
> 
> mount: Mounting sys on /sys failed: No such file or directory
> 
> Mounting filesystems
> 
> cp: /tmp: No such file or directory
> 
> mount: Mounting /mnt/rwfs//tmp on /tmp failed: No such file or
> directory
> 
> ln: /etc/mtab: File exists
> 
> mount: Mounting usbfs on /proc/bus/usb failed: No such file or
> directory
> 
> Starting syslogd and klogd
> 
> Setting up networking on loopback device:
> 
> Setting up networking on eth0:
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
> ##############################################################################################
> 
>  
> 
> However the TFTP works OK in the IP setup. Any other ideas?\
> 
>  
> 
> Cheers,
> 
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden 
> Sent: Tuesday, 13 May 2008 8:11 p.m.
> To: Frank Wei
> Cc: 'address@hidden'
> Subject: Re: [Ltib] Cannot NFS/Network Delpoy
> 
>  
> 
> Hi Frank,
> 
> You can't use dhcp and NFS root deployment. Run ./ltib --configure and
> go to 
> 
> --- Target System Configuration
>     Options  --->
>       Network setup  --->
> 
> And de-select 
> [ ]   get network parameters using dhcp
> and enter suitable fixed IP address network parameters for your
> network.
> 
> Regards, Stuart
> 
> On Tue, 2008-05-13 at 10:38 +1200, Frank Wei wrote: 
> 
> Hello,
> 
>  
> 
> I’
> m new to LTIB. I was using LTIB try to NFS/Network deploy the
> Freescale M54455EVB following every instruction provided by Freescale
> but I always see the error
> 
>  
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> 
> IP-Config: Complete:
> 
>       device=eth0, addr=172.16.10.221, mask=255.255.0.0,
> gw=172.16.0.4,
> 
>      host=172.16.10.221, domain=, nis-domain=(none),
> 
>      bootserver=192.168.0.158, rootserver=192.168.0.158, rootpath=
> 
> Looking up port of RPC 100003/2 on 192.168.0.158
> 
> Looking up port of RPC 100005/1 on 192.168.0.158
> 
> VFS: Mounted root (nfs filesystem).
> 
> free_initmem: __init_begin = 0xc02d8000  __init_end = 0xc02ec000
> 
> Setting the hostname to freescale
> 
> Mounting /proc and /sys
> 
> Mounting filesystems
> 
> mount: Mounting  on swap        swap    defaults          0       0
> failed: No such file or directory
> 
> Starting syslogd and klogd
> 
> Setting up networking on loopback device:
> 
> Setting up networking on eth0:
> 
> udhcpc (v0.9.9-pre) started
> 
> nfs: server 192.168.0.158 not responding, still trying
> 
>  
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
>  
> 
> As you can see the last line captured indicating the NFS server is not
> responding(?) Does it mean the NFS is not set up well? (I’ve followed
> up every instruction Freescale provided).
> 
> Has anybody ever experienced this issue?
> 
>  
> 
> Many thanks.
> 
> 
> 
> 
> 
> 
>  
>  
> _______________________________________________
> LTIB home page: http://bitshrine.org
>  
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib