[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: R4x00 and R5000 issues



* Krzysztof Krzyzaniak (eloy@transilvania.eu.org) wrote:
> On Tue, Aug 07, 2001 at 05:44:49PM +0200, Krzysztof Krzyzaniak wrote:
> [..]
> > > > > > Might it be that your indy/mips kernel tries to mount the nfs root
> > > > > > as NFS V3 and you only have an NFS V2 server ?
> > > > > 
> > > > > Maybe (I'll compile new 2.4.7 kernel with NFSv3 support).
> > > > 
> > > > It still doesn't work:
> > > > 
> > > > big@root:~{19}# rpcinfo -u localhost nfs 3
> > > > program 100003 version 3 ready and waiting
> > > Hmm...I'm I think version 2 should do. Since the Indy seems to query for
> > > version 2 anyway:
> > > > looking up port of RPC 100003/2 on 192.168.101.3
> > > > Looking up port of RPC 100005/2 on 192.168.101.3
> > > 				`-- this is very likely the prot. version
> > > Can you make sure your portmapper is answering the requests(tcpdump).
> > 
> > I'll se tommorow.
> 
> tcpdump port 111
> 
> (booting Indy)
> 
> ... and tcdpump doesn't seek any transmission :(

	Ran into this myself.  The kernel isn't compiled with bootp
	support so it can't find it's IP address to use so it's not
	bringing the networking up, thus the sendmsg error.  The way to
	fix this is to specify nfsaddrs=xx.xx.xx.xx where xx.xx.xx.xx is
	the IP address of the client.

	ie:

boot -f bootp():linuxr4k-ip22 nfsaddrs=192.168.1.2 nfsroot=192.168.1.1:/sgi-linux

	At the prom prompt.

		Stephen

Attachment: pgpU8prtmEGv0.pgp
Description: PGP signature


Reply to: