On Fri, 28 Oct 2005, ???? wrote:
> 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? > 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 at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded >
