Xref: utzoo comp.sys.sgi:10058 comp.periphs.scsi:2590
Newsgroups: comp.sys.sgi,comp.periphs.scsi
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!stanford.edu!neon.Stanford.EDU!kaufman
From: kaufman@neon.Stanford.EDU (Marc T. Kaufman)
Subject: Re: < Connecting Fujitsu M2266SA to SGI SCSI (SOLVED) >
Message-ID: <1991May13.160731.6804@neon.Stanford.EDU>
Organization: Computer Science Department, Stanford University, Ca , USA
References: <41530@unlisys.in-berlin.de> <41691@unlisys.in-berlin.de>
Date: Mon, 13 May 1991 16:07:31 GMT
Lines: 13

In article <41691@unlisys.in-berlin.de> rot@unlisys.in-berlin.de (Robert Rothe) writes:

>the drive runs fine so far..
>but i wonder why i have to slow down the device soo much to get it running
>with the sgi-machine ? is it the fault of the disk, the scsi-driver or the 
>scsi-adapter ?

Well, I don't know about SGI's drivers, but I was absolutely appalled to see
that there was essentially no code to recover from errors in a driver that is
supposed to be the boot driver for SUN Sparc Stations.  I mean, the code
could not even handle a Unit Busy response.

Marc Kaufman (kaufman@Neon.stanford.edu)