Subject: Re: netbooting a blade 100
To: Andrey Petrov <petrov@netbsd.org>
From: Brian A. Seklecki <lavalamp@spiritual-machines.org>
List: port-sparc64
Date: 06/05/2002 17:29:39
Yea let's see the dmesg (serial console?).  I'm curious.  Those are nice
boxes.

-lava

On Wed, 5 Jun 2002 @ 1:06pm (-0700), Andrey Petrov wrote:

AP> On Wed, Jun 05, 2002 at 03:48:57PM -0400, IvanK. wrote:
AP> > Hi all,
AP> >
AP> > I followed the instructions in diskless(8) and setup a linux server with a
AP> > sparc (blade 100) client for a net install.  The problem is that at some
AP> > point after booting, the kernel asks for the root device and the only
AP> > available choices are raid[0-9][a-h] (I believe).
AP> >
AP> > Btw, I'm booting with ofwboot.net.
AP> >
AP> > When I get back home tonight, I'll try with the server running NetBSD and see
AP> > if that helps, even though I don't think that matters much.  I guess I
AP> > didin't configure my bootparams.  Here's what I have in my /etc/bootparams:
AP> >
AP> > vazov root=192.168.0.3:/export/vazov/root gateway=192.168.0.1:255.255.255.0
AP> >
AP> > vazov is the name of the client that needs to be netbooted.  I've exported
AP> > /export/vazov/root, I'm running tftpd, rarpd and rpc.bootparamd.  My
AP> > /etc/ethers is also correct.
AP> >
AP> > Any ideas?
AP>
AP> Network interface were not configured. dmesg would show it.
AP>
AP> 	Andrey