Subject: Re: Problem booting Shark from Linux
To: Beng Hui Ong <beong@cisco.com>
From: Mark Hayter <mark.hayter@ieee.org>
List: port-arm32
Date: 03/26/2000 18:37:24
Ignatios Souvatzis wrote:
> 
> On Sun, Mar 26, 2000 at 02:53:12AM -0800, Beng Hui Ong wrote:
> >
> > Please advise what does "error=75" means ? I was looking
> > thru the kernel source of Netbsd but still couldn't figure
> > it out.
> 
> % grep 75 /usr/include/sys/errno.h
> PROGMISMATCH   75              /* Program version wrong */
> %
> 
> Sounds like the Shark is doing NFSv3 and your server is doing v2 only, or
> the other way round.
> 
>         -is

This is almost certainly the case. I can remember running in to this one
once. The following is from memory so the details may be slightly off. I
think it may have only been some versions of NetBSD (possibly the DEC
code), the bootstrap mount code was different and had a bug in detecting
this error (I think the error check was done against the NFS error code
for program version wrong, but it was calling a subroutine that had been
updated to do the error code translation into NetBSD error codes) so
after trying NFSv3 it fails to fall back to NFSv2. 

If you are running an old NetBSD, try grabbing the latest snapshot or
for starters the kernel (netbsd_netboot-SHARK.gz from
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.4.2/arm32/binary/kernel/),
which won't work properly with an old userland but should get past the
root fs mount if it solves the problem. The file in question is
boot_nfs.c in src/sys/nfs

As I said I don't remember which versions of NetBSD were affected. But
if you are using the DEC code now and decide to upgrade, you will need
to change your DHCP parameters since the new (written in the time it
took to release our version) dhcp boot code does not support 
<server ip>:/filesystem/path
for nfs mounts, instead just give the /filesystem/path part.

Mark