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

Can't mount nfsroot Re: sunlance.c - network driver for sun4m



Hi,

Ok so you've got tftp running and your bootpd (which gives your client 
computer
its name and network address), your nfs server is running and the
name or ip of your client is listed in the /etc/exports file.

The nfs server appears to be set up correctly and if it works from a third
box thats fine.

Your kernel boots, but when the portmapper tries to convert the RPC
program number to a port is tries the wrong program numbers and doesn't
recieve a port so it can't talk to the NFS server and there it stops.

N.B. You mentioned earlier that you weren't able to compile a kernel image
on an intel machine, which kernel are you running and are your all your
options compilled in (ie no modules).

Regards,

Peter Firmstone.  

On Wed, 22 Nov 2000, m.nine.six wrote:

> > 
> > mv vmlinuz vmlinux-elf.gz
> > gzip -d vmlinux-elf.gz
> > elf2out -o vmlinux vmlinux-elf
> 
> thanks a lot.
> finally i heared that i have to do it this way. really tricky...
> 
> now finally it boots but it can't find the nfs server. it get's me the
> following error:
>  
> Looking up port of RPC 100002/2 on 192.168.10.1
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> portmap: server 192.168.10.1 not responding, timed out
> Root-NFS: unable to get nfsd port number from server using default
> Looking up port of RPC 100005/1 on 192.168.10.1
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> portmap: server 192.168.10.1 not responding, timed out
> Root-NFS: unable to get nfsd port number from server using default
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> RPC: sendmsg returned error 51
> mount: server 192.168.10.1 not responding, timed out
> Root-NFS: Server returned error -5 while mounting /sun4m
> 
> 
> the boot parameter is: "boot net nfsroot=192.168.10.1:/sun4m"
> 
> and if i do without the boot parameter it writes the following error:
> 
> Root-NFS: No NFS server avaible, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> 
> the portmap is running:
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100003    2   udp   2049  nfs
>     100005    1   udp   1039  mountd
>     100005    1   tcp   1066  mountd
>     100005    2   udp   1039  mountd
>     100005    2   tcp   1066  mountd
>     100005    3   udp   1039  mountd
>     100005    3   tcp   1066  mountd
> 
> as it should till the mountd. shouldn't it run below the port 1024? if
> so how can i put it back to the right port? but on the other side i can
> mount this nfs part. from a 3th box. that means nfs works correct. or
> not?
> 
> 
> to install a sun box is much more complicated then i ever imagined it.
> and i always drive to a dead end... 
> 
> 
> 
> ps: i still tried to link to silo and it doesn't worked as expected.
> silo starts but is not able to start any kernel images.
> 
> 
> thanks a lot for your help,
> 
> regards,
> alias m.nine.six.
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 



Reply to: