>  > On Thu, 22 May 1997, Ole Myren R|hne wrote:
>  > 
>  > > I have tried booting NetBSD on a VS3100 over the network using the
>  > > description found at:
>  > 
>  > ...
>  > 
>  > > 1. This particular VS3100 is diskless, with some internal scsi bus
>  > > left unconnected/unterminated. When booting, I get a some 10
>  > > minutes worth of messages like
>  > > 
>  > > ncr0 at vsbus0: scsi-id 7
>  > > scsibus0 at ncr0: 8 targets
>  > > ncr0: reselect, BSY stuck, bus=0xff
>  > > ncr0: reselect, BSY stuck, bus=0xff
>  > > ncr0: select found SCSI bus busy, resetting
>  > > ncr0: reselect, BSY stuck, bus=0xff
>  > > ncr0: reselect, BSY stuck, bus=0xff
>  > > ncr0: select found SCSI bus busy, resetting

Okay, I think I've figured out the nature of your problem a little bit
better.  This will probably be of interest to anyone netbooting a VS3100
and to anyone doing the VS3100 kernel support development. <nudge nudge,
wink wink>.

Tonight I was booting up a new VS3100/30 which I recently acquired. This
one however has a SCSI/ST506 controller in it.  The original one I'm
having great success with has a SCSI/SCSI controller.  Anyway, when I
booted NetBSD/vax on the new VS3100 with SCSI/ST506, NetBSD returned the
same types of error messages you see above only with reference to "ncr1".

VS3100/30 with SCSI/ST506:
--------------------------

 -ESA0
 Nboot
 : /netbsd
 le_softc.sc_r2 = 0x3a0000
 device: le0 attached to 08:00:2b:0e:c4:58
 boot: client IP address: 10.3.250.5
 boot: client name: atari-vax
 root addr=10.3.250.2 path=/mp/d1/diskless/atari-vax
 675840+35840+70136 start 0x98bbe
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 NetBSD 1.2D (VS) #9: Thu Apr 24 07:42:40 MEST 1997
     bertram@:/v/vax/src/sys/arch/vax/compile/VS

 realmem = 16580608
 avail mem = 12670976
 Using 809 buffers containing 828416 bytes of memory.
 backplane0 (root)
 cpu0 at backplane0: MicroVAX 3100 (KA41)
 vsbus0 at backplane0
 le0 at vsbus0: address 08:00:2b:0e:c4:58
 le0: 32 receive buffers, 8 transmit buffers
 ncr0 at vsbus0: scsi-id 7
 scsibus0 at ncr0: 8 targets
 ncr1 at vsbus0: scsi-id 7
 scsibus1 at ncr1: 8 targets
 ncr1: reselect, BSY stuck, bus=0xff
 ncr1: reselect, BSY stuck, bus=0xff
 ncr1: select found SCSI bus busy, resetting...
 ncr1: reselect, BSY stuck, bus=0xff
 ncr1: reselect, BSY stuck, bus=0xff
 ncr1: select found SCSI bus busy, resetting...

---

Remembering that your difficulties were on a system which had no disk
controller at all, I unplugged the controller board from the main board.
When booting with this configuration I ended up getting the same results
you had.

VS3100/30 with no disk controller
---------------------------------
 -ESA0
 Nboot
 : /netbsd
 le_softc.sc_r2 = 0x3a0000
 device: le0 attached to 08:00:2b:0e:c4:58
 boot: client IP address: 10.3.250.5
 boot: client name: atari-vax
 root addr=10.3.250.2 path=/mp/d1/diskless/atari-vax
 675840+35840+70136 start 0x98bbe
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 NetBSD 1.2D (VS) #9: Thu Apr 24 07:42:40 MEST 1997
     bertram@:/v/vax/src/sys/arch/vax/compile/VS

 realmem = 16580608
 avail mem = 12670976
 Using 809 buffers containing 828416 bytes of memory.
 backplane0 (root)
 cpu0 at backplane0: MicroVAX 3100 (KA41)
 vsbus0 at backplane0
 le0 at vsbus0: address 08:00:2b:0e:c4:58
 le0: 32 receive buffers, 8 transmit buffers       
 ncr0 at vsbus0: scsi-id 7                         
 scsibus0 at ncr0: 8 targets                       
 ncr0: reselect, BSY stuck, bus=0xff               
 ncr0: reselect, BSY stuck, bus=0xff               
 ncr0: select found SCSI bus busy, resetting...
 ncr0: reselect, BSY stuck, bus=0xff
 ncr0: reselect, BSY stuck, bus=0xff
 ncr0: select found SCSI bus busy, resetting...

---

When I first starting inquiring about the VS3100 support for NetBSD, I had
some discussions with Bertram about the SCSI/ST506 controllers since he
didn't have access to one.  All the machines he's working with apparently
have SCSI/SCSI controllers.  Sooooo it sort of looks like the present
version of the VS3100 SCSI driver is expecting the dual SCSI controller 
configuration -- if it sees one or none, it gets lost.

Calling upon the assitance of Bertram... How difficult would it be to
modify the SCSI driver to allow for configurations with one or zero SCSI
controllers?  I'd be happy to assist in the testing process.

-brian.
---------------------------------------------------------------------------
Brian D. Chase         Systems Coordinator        brian.chase@carpediem.com
-- Compression, Inc. - 13765 Alton Pkwy, Suite B - Irvine, CA 92618, USA --