On Sun, 13 Jun 2004, Joshua Coombs wrote:

>> So, the idea is, if you get SCSI timeouts or other untoward
> behavior
>> with the ncrscsi driver (GENERIC), you're supposed to try the sbc
>> driver (GENERICSBC). I don't recall any reports from this list of
>> anyone ever have trouble with the sbc driver, or any bug reports
> that
>> were solved by switching to the ncrscsi driver (but I haven't done
> a
>> search). Does anyone have hardware doesn't work with the sbc
> driver?
>> Perhaps we could avoid a lot of questions by making it the
> default?
>>
>> Frederick
>
> My SE30 distinctly dislikes SBC.  Using SBC and trying to access
> anything other than the main HD results in locks, panics, etc.
> Using NCR, just that device hangs.  (Yeah, so either way I loose,
> but I loose more gracefully with NCR. : ) )

And just to muddy the waters, my SE/30 NetBSD system was unusable
(dropping single characters randomly) until I switched to the SBC
driver. This was quite some time ago, with NetBSD 0.9 something.

-- 
Hisashi T Fujinaka - htodd@twofifty.com
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte