ok, lets look at the devices probed...


   mainbus0 (root)

always exists, on the sparc.  bit of glue ...

   cpu0 at mainbus0: SUN-4/200 series (MB86910 or WTL1164/5 FPU)
   cpu0: 131072 byte write-back, 16 bytes/line, sw flush cache enabled

...

   obio0 at mainbus0

this is a bus.

   oclock0 at obio0 addr 0xf3000000 delay constant 6
   eeprom0 at obio0 addr 0xf2000000
   memreg0 at obio0 addr 0xf4000000

clock, eeprom, and something i'm not entirely sure about, but, is
probably realted to memory, not, scsi.  :-)

   zs0 at obio0 addr 0xf1000000 pri 12, softpri 6
   zs0a: console i/o
   zs1 at obio0 addr 0xf0000000 pri 12, softpri 6

serial ports.

   bwtwo0 at obio0 addr 0xfd000000: bwtwo, 1600 x 1280
   bwtwo0: attached to /dev/fb

graphics card.

   ie0 at obio0 addr 0xf6000000 pri 6 address 08:00:20:00:2e:b8, type onboard

intel ethernet card.

   vmel0 at mainbus0
   vmes0 at mainbus0

more busses, i believe.  someone may correct me here.

   xyc0 at vmes0 addr 0xffffee40 vec 0x48 pri 3: Xylogics 450/451

the xy (SMD) controller.

   xy0 at xyc0 drive 0: off-line
   xy1 at xyc0 drive 1: off-line

... and disks.

and that's it.  the restof the messages aren't devices.
   
   the SCSI card... Perhaps NetBSD doesn't know how to cope with the card that I
   have? I'd hate to learn that I need to somehow find myself a copy of SunOS
   after I've spent all this time working on getting NetBSD working. :) 

well, netbsd *is* changing, and, we can probably get it working.

what sort of card do you think it is ?  if you can find a sunos
kernel to boot, it would be useful to get the output of it, to
help diagnose the problem, and hopefully fix it.