Subject: Re: Trouble netbooting MVME167B
To: Steve Woodford <scw@NetBSD.org>
From: Henning Kiel <kiel@physik.uni-dortmund.de>
List: port-mvme68k
Date: 08/11/2003 11:42:52
On Mon, 11 Aug 2003, Steve Woodford wrote:

> On Mon, 11 Aug 2003, Henning Kiel wrote:
>
> > My dhcp.conf looks like this:
> > host e4pc11 {
> >    hardware ethernet 08:00:3E:21:48:AE;
> >    fixed-address 129.217.160.211;
> >    option host-name "e4pc11";
> >    option root-path "129.217.160.208:/tftpboot/disk";
> > }
> >
> > And when doing "nbo" I get:
> > ...
> > net_open: server path: 129.217.160.208:/tftpboot/disk
> > net_open: NFS mount error=-1
> > open netbsd: Unknown error: code -1
> > boot: netbsd: Unknown error: code -1
> > boot:
> > netboot: no interfaces left untried
>
> I suspect you need to change the root-path option to point to the real NFS
> root directory of the MVME board. The bootloader loads the 'netbsd' kernel
> directly from there over NFS, not TFTP.

Maybe I expressed myself badly. I have NFS running and exported
/tftpboot/disk for the MVME. And a kernel "netbsd" is also in there.

> For one of my boards, I have:
>
> host maggie {
>         hardware ethernet 08:00:3e:2a:33:38;
>         fixed-address 192.168.2.10;
>         filename "/var/tftpboot/netboot";
>         option root-path "/export/diskless/maggie";
> }

I guess "filename..." is not needed? or is it a typo and should be
.../netbsd?

Chau,
Henning