On Friday 07 May 2004 3:12 pm, Giuseppe Pesce wrote:

> The board gets some informations from the server and then stops, the
> is the output:
[snip]
> device: ie0 attached to 08:00:3e:22:17:aa
> net_open: client addr: 10.0.0.3
> net_open: subnet mask: 255.255.255.0
> net_open: server addr: 192.167.203.159
> net_open: server path: 192.167.203.159:/tftpboot/10.0.0.3/
> net_open: file name: /tftpboot/netbsd-VME167
> 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 don't believe the standalone bootloader can deal with the NFS server 
being on a different subnet, as is apparently the case with your setup.

In addition, you need to set the 'option root-path ...' in your 
dhcpd.conf to point to the *NFS root* for your mvme board, *not* the 
tftp directory. The standalone bootloader expects to be able to grab 
the kernel from that root directory. (Ignore me if your /tftpboot 
directory really *is* the NFS root ;-).

Cheers, Steve