NFS can not mount (linuxppc2.2.4 mpc5200 lxt971)

3 messages, 3 authors, 2005-10-31 · open the first message on its own page

NFS can not mount (linuxppc2.2.4 mpc5200 lxt971)

From: ÏÄÓê <hidden>
Date: 2005-10-28 02:42:08

I have ported linuxppc2.2.4 to my board based on ICECUBE.
One board can not mount NFS(eth0 = lxt971), Message as follow:

eth0: config: auto-negotiation on, 100HDX, 10HDX.
IP-Config: Complete:
      device=eth0, addr=198.87.102.211, mask=255.255.255.0, gw=198.87.102.140,
     host=oops, domain=, nis-domain=(none),
     bootserver=198.87.102.140, rootserver=198.98.102.140, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 198.98.102.140
eth0: status: link up, Unknown speed/duplex, auto-negotiation complete, remote f
ault.
portmap: server 198.98.102.140 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 198.98.102.140
portmap: server 198.98.102.140 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 198.98.102.140 not responding, timed out
Root-NFS: Server returned error -5 while mounting /opt/eldk/ppc_82xx
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00

But i can ping the board from my PC:

Pinging 198.87.102.211 with 32 bytes of data:

Reply from 198.87.102.211: bytes=32 time<10ms TTL=64
Reply from 198.87.102.211: bytes=32 time<10ms TTL=64
Reply from 198.87.102.211: bytes=32 time<10ms TTL=64
Reply from 198.87.102.211: bytes=32 time<10ms TTL=64


The other boards using the same program can mount NFS on the same server.

What part of this board might be wrong? 

Thanks!

Re: NFS can not mount (linuxppc2.2.4 mpc5200 lxt971)

From: Esben Nielsen <hidden>
Date: 2005-10-28 08:03:37


On Fri, 28 Oct 2005, =CF=C4=D3=EA  wrote:
I have ported linuxppc2.2.4 to my board based on ICECUBE.
One board can not mount NFS(eth0 =3D lxt971), Message as follow:
=20
eth0: config: auto-negotiation on, 100HDX, 10HDX.
IP-Config: Complete:
      device=3Deth0, addr=3D198.87.102.211, mask=3D255.255.255.0, gw=3D19=
8.87.102.140,
     host=3Doops, domain=3D, nis-domain=3D(none),
     bootserver=3D198.87.102.140, rootserver=3D198.98.102.140, rootpath=
=3D
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 198.98.102.140
eth0: status: link up, Unknown speed/duplex, auto-negotiation complete, r=
emote f
ault.
portmap: server 198.98.102.140 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 198.98.102.140
portmap: server 198.98.102.140 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 198.98.102.140 not responding, timed out
Root-NFS: Server returned error -5 while mounting /opt/eldk/ppc_82xx
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=3D" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
=20
But i can ping the board from my PC:
=20
Pinging 198.87.102.211 with 32 bytes of data:
=20
Reply from 198.87.102.211: bytes=3D32 time<10ms TTL=3D64
Reply from 198.87.102.211: bytes=3D32 time<10ms TTL=3D64
Reply from 198.87.102.211: bytes=3D32 time<10ms TTL=3D64
Reply from 198.87.102.211: bytes=3D32 time<10ms TTL=3D64
=20
=20
The other boards using the same program can mount NFS on the same server.
=20
What part of this board might be wrong?=20
=20
I can't tell you what is wrong, but I have seen the same error:
It works fine on the Lite5200 proto board but not on our custom board :-(

Esben

Thanks!
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
=20

Re: NFS can not mount (linuxppc2.2.4 mpc5200 lxt971)

From: Tore Martin Hagen <hidden>
Date: 2005-10-31 14:29:41

ÏÄÓê wrote:
eth0: config: auto-negotiation on, 100HDX, 10HDX.
IP-Config: Complete:
     device=eth0, addr=198.87.102.211, mask=255.255.255.0, gw=198.87.102.140,
    host=oops, domain=, nis-domain=(none),
    bootserver=198.87.102.140, rootserver=198.98.102.140, rootpath=
 
Hi

Check out your DHCP server.  You don't get the rootpath from it.

/etc/dhcpd.conf should contain
option root-path "/local/Mpc8266ads/Box0/root";  
or something similar.
also take a look in /var/log/messages to pinpoint the problem.

/Tore Hagen
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help