A bit more info... why do I always figure these things out right after I
send a message?

It appears that the problem lies in the negotation of wide SCSI transfers
with the drive (which should support them):

----
# insmod ncr53c8xx ncr53c8xx="wide:n"
ncr53c8xx: at PCI bus 0, device 13, function 0
ncr53c8xx: 53c876 detected 
ncr53c8xx: at PCI bus 0, device 13, function 1
ncr53c8xx: 53c876 detected 
ncr53c876-0: rev=0x37, base=0xfa103000, io_port=0x1400, irq=11
ncr53c876-0: ID 7, Fast-20, Parity Checking
ncr53c876-0: on-chip RAM at 0xfa100000
ncr53c876-0: restart (scsi reset).
ncr53c876-0: Downloading SCSI SCRIPTS.
ncr53c876-1: rev=0x37, base=0xfa103400, io_port=0x1800, irq=10
ncr53c876-1: ID 7, Fast-20, Parity Checking
ncr53c876-1: on-chip RAM at 0xfa101000
ncr53c876-1: restart (scsi reset).
ncr53c876-1: Downloading SCSI SCRIPTS.
scsi0 : ncr53c8xx - revision 3.1f
scsi1 : ncr53c8xx - revision 3.1f
scsi : 2 hosts.
  Vendor: SEAGATE   Model: ST39173WC         Rev: 6244
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: ESG-SHV   Model: SCA HSBP M5       Rev: 1.65
  Type:   Processor                          ANSI SCSI revision: 02
Detected scsi generic sgb at scsi0, channel 0, id 6, lun 0
ncr53c876-0-<0,0>: tagged command queue depth set to 4
ncr53c876-0-<0,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7
GB]
 sda: sda1
----

Things appear to work fine in this configuration. The question is, why
does the wide transfer negotation fail? The drives use SCA connectors to
attach to the HSB, I don't know if that's relevant or not.

Thanks again,

        Tim

On Tue, 16 Feb 1999, Tim Buller wrote:

> I'm having a problem with Seagate ST39173WC drives mounted in the Hot Swap
> Bay (HSB) of an Intel Astor Chasis. The mainboard is a Intel N440BX, with
> an on-board Symbios SYM53C876 SCSI controller. I'm using ncr53c8xx
> ver. 3.1f driver in a Linux 2.2.1 kernel (Debian distro). 
> 
> I upgraded the firmware on the HSB controller to ver. 1.65, on the advice
> of Gerard Roudier, who forwarded a message posted to linux-scsi about a
> similar problem from Pekka Pietikainen.
> 
> I am now able to boot the SCSI drive if I pass 'ncr53c8xx=safe:y' at the
> LILO prompt. I then loaded the system onto an IDE drive, so I could do
> some testing by loading the SCSI driver as a module. I append the results
> of those tests below.

====
Tim Buller                                       [EMAIL PROTECTED]
Systems Specialist                               Office: Snow Hall 643
Department of Mathematics                          Voice: 785-864-7311
University of Kansas, Lawrence, KS 66045             Fax: 785-864-5255

#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

Please visit http://online.offshore.com.ai/arms-trafficker/


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to