I actually have both boot-file and boot-device on my environment variables.
I had changed around some of the alias's and confirmed that "disk1" refers
to the scsi id 1.  So I enter the command "boot disk1"  and I get a message
"Illegal Instruction"  Nothing more...  Where is this coming from???
-andy

-----Original Message-----
From: port-sparc-owner@netbsd.org [mailto:port-sparc-owner@netbsd.org]On
Behalf Of Greywolf
Sent: Friday, March 14, 2003 2:59 PM
To: Andrew Obusek
Cc: port-sparc@netbsd.org
Subject: RE: Problems with booting up in general


Thus spake Andrew Obusek ("AO> ") sometime Yesterday...

AO> Date: Thu, 13 Mar 2003 22:06:17 -0500
AO> From: Andrew Obusek <obusek@UDel.Edu>
AO> To: port-sparc@netbsd.org
AO> Subject: RE: Problems with booting up in general
AO>
AO> So I tried:
AO> ok> setenv boot-device sd(0,1,0)netbsd
AO> ok> boot
AO> and I got a message saying can't open device sd(0,1,0) or somethign of
the
AO> like.  And if I try simply "boot disk"  it says somethign along the
lines of
AO> sd 3,0 not responding.
AO> Just to confirm that I'm reading the probe-scsi right it is telling me
that
AO> the hard disk is at
AO> Target 1 Unit 0
AO> and the cd rom (which worked fine for the installation
AO> Target 6

I seem to remember it needing

boot sd(0,8,0) netbsd

i.e. controller 0 lun 8 (target 1, lun 0) partition 0.

Since the targets have up to 8 luns, even though in practice we
*KNOW* nothing really uses multiple luns anymore, the middle parameter
is specified as (target * 8) + lun -- in hex, no less.  Yes,
that means that booting from target 1 lun 4 would be

boot sd(0,c,0)

I think boot-from is the envariable you want to set; boot-device and
boot-file are on later versions of the PROM.

Hope this helps!



AO>
AO> Any other ideas of what could be the problem?
AO> -andy
AO>
AO> -----Original Message-----
AO> From: Greg Earle [mailto:earle@isolar.DynDNS.ORG]
AO> Sent: Thursday, March 13, 2003 9:55 PM
AO> To: Andrew Obusek
AO> Cc: port-sparc@netbsd.org
AO> Subject: Re: Problems with booting up in general
AO>
AO>
AO> > I was able to install netBSD onto my Sparc1+ but after the
installation
AO> I'm
AO> > not able to boot into netBSD.  Here are a couple of the things I've
tried
AO> > 1) both boot sd(0,1,0)
AO> > 	and boot sd()
AO> > 	but I get a message that both of those commands are outdated.
AO> > 2) so I try "boot disk" but for some reason it says "can't open
device" at
AO> > target sd3,0
AO> > If I probe-scsi the hard disk I want to boot off is at scsi 1
AO> > I think that if you "boot disk" it looks at scsi port 3.  I have the
env
AO> > argument boot-file set to netbsd.
AO> > I apologize if this seems to ramble, but any ideas on where to go from
AO> here?
AO>
AO> Your EEPROM is probably too old to have the common "devalias" NVRAM
device
AO> aliases like "disk1" to boot from the disk at SCSI target id 1, etc.
AO> Those aliases are available in newer EEPROM'ed machines.
AO>
AO> Try "setenv boot-from sd(0,1,0)netbsd" from the "ok " prompt and see if
AO> that works for you.
AO>
AO> 	- Greg
AO>
AO>
AO>


				--*greywolf;
--
NetBSD: I Wanna Be Sedated!