> > That is not one of the VME crates.  I think it is different.  I once ran
> > a 3/80 on NetBSD, but I don't remember how the drives were set on it.
> > On the VME scsi things and on my 3/60, it has to have the motor on at
> > power on jumpers set, in my hands for NetBSD 1.4.2 to work.  Conversely,
> > sunos doesn't need them.  If there is something I am  missing or some other
> > explanation for the stalling attempts to read the scsi at bootup, do holler.
> 
> There are two different ways I've seen some disks work.  First is the
> mode where they'll spin up on the first command of any sort (or on a bus
> reset), and second are those drives that require an explicit SCSI "START
> UNIT" (1B) command before they'll spin up.
> 
> It would appear that NetBSD will send a "START UNIT" command *unless*
> the disks have a "quirk" table entry that sets the SDEV_NOSTARTUNIT
> flag.  From what I can see though the only listed fixed drives are two
> specific revisions of the Hitachi DK515C (CP15 & CP16).

OK, is there anything about DEC drives that anyone knows about on
sun3 hardware with NetBSD.  Whatever sunos is doing, it is spinning
the drives up.  Whatever NetBSD is doing, it is not spinning up my'
drives in question.  I have to attribute that to software and not
hardware.  Where in the code were you looking?

> With drives any older than about 4-5 years it's always safest to jumper
> them 100% correctly in all cases, and that includes having them spin up
> and go ready on power up.  I've seen drives which SunOS-4.1.4 couldn't
> command to spin up, so you just never know....

OK, this still has me curious, though.  It is occurring when the bootup
does the first scsi probing.  Sunos spins up the drives then.  NetBSD
does not.  Apparently NetBSD is sending some code down the bus, but
not what is spinning the drives.  After about 10-15 minutes, it times
out and returns a REQ not found or something like that error to the
console, and then abruptly halts.  I don't have my notes handy, so
can't report the exact error.

Should NetBSD be sending something like a bus reset to force all
drives to spin up, then do the probing?  Maybe sunos is doing that
sort of thing, and thus, can spin up the drives where NetBSD does not?

I recall that when sunos boots, you can hear the tape resetting, several
times, possibly indicative of a bus reset.  I don't recall NetBSD doing
that, but I will have to check that to be sure.

Now, maybe, we are getting somewhere.  Where in the code is this found?

Thanks

Bob