Subject: Re: netbooting problems with Mr.Coffee javastation
To: Michael Parson <mparson@bl.org>
From: Jasper Lievisse Adriaanse <jasper@nedbsd.nl>
List: port-sparc
Date: 11/21/2005 07:59:07
On Sun, 20 Nov 2005 15:50:11 -0600
Michael Parson <mparson@bl.org> wrote:

> On Sun, Nov 20, 2005 at 08:24:13PM +0100, Jasper Lievisse Adriaanse wrote:
> 
> > Ok, now I'm stuck again :( I managed to make my Krups boot of my laptop. But
> > that's not very desireble so I wanted to make my Javastation boot of my gateway
> > (with IP 192.168.1.1), this is also my DHCP and NFS-server.
> > In my logs I see that an IP is given to my Krups and I notice a BOOTREQUEST and
> > a BOOTREPLY, but when booting my Javastation with 'boot net' I get the
> > following error:
> >
> > ------8<-----------
> > Booting netbsd
> > Trying BOOTP protocol... net_open: client addr: 192.168.1.10
> > net_open: subnet mask: 255.255.255.0
> > net_open: net gateway: 192.168.1.1
> > net_open: server addr: 192.168.1.1
> > ip address: 192.168.1.10, netmask: 255.255.255.0 gateway: 192.168.1.1
> > root addr=192.168.1.1 path=
> 
> Looks like it's not getting the path to the root filesystem on the nfs
> server.
> 
> > Can't open NFS network connection on `/pci@0,300c0000/network@0,1'
> > Cannot load netbsd: error=13
> >
> > device[/pci@0,300c0000/network@0,1] ("halt" to halt);
> > ------8<-----------
> > The empty 'path=' bothers me.
> 
> Yeah.
> 
> > Here is my /etc/exports (the server is an OpenBSD-box):
[...]
> >
> > And here's the relevant /etc/dhcpd.conf part:
[...]
> 
> Here's how I boot my sun xterminal-1 off my FC-3 Linux box:
> 
>         host one {
>                 hardware ethernet 08:00:20:7a:ed:4c;
>                 fixed-address 192.168.15.15;
>                 option root-path "/home/netboot";
>                 server-name "gold.bl";
>                 option host-name "one";
>         }
> 
> The "filename" part is handled by the rarp process, you shouldn't need
> that line.
Well, I got the whole setup working some weeks ago when the files were on my
laptop (192.168.1.241) and without rarpd, but now that I have them on my
gateway it won't work. I'll try it all when I come back from school later this
day.
And I'll try if it works if I put another NIC in the server with IP 192.168.1.2.

Cheers,
Jasper
> 
> -- 
> Michael Parson
> mparson@bl.org
> 


-- 
"Security is decided by quality" -- Theo de Raadt