> Could you confirm it is 100NS (should be 50 ns).
You are right, it says 50ns.
> 0x18 -> bit 8 in SIST --> SCSI GROSS ERROR
> Such a error just after FAST-20 data transfer negotiation is likely
> due to a broken SCSI BUS. You may want to:
>
> 1) Check your SCSI BUS (cables, device position, terminators)
> 2) Give a try with a conservative settings, for example 8 bit SCSI,
> 5 MB/s.
Ok; I'll check the scsi bus and try playing around with reduced transfer
rates and such, as soon as I'm done with this.
But you might find this curious. I've both a DC-390F and a Fireport 40
which use the same driver. I've tried both, and both report the same
error messages that I posted earlier. Does this work towards
eliminating what could be the culprit? I mean since the SCSI GROSS
ERROR occurs on two different controllers (same driver and same SCSI
BUS), does this eliminate the controller and the disk as the culprit?
> Could you give a brief description of your SCSI BUS.
My current scsi bus is made up of the internal ribbon cable that came
with the controller, and I've it plugged into 80pin-to-68pin adapter
which then plugs into the drive. You mentioned position of the drive;
does that matter? The drive's electronics are facing the sky when the
mid-tower case is standing normally.
Has anybody had bad experiences with the SCA 80pin-to-68pin adapters?
Are they reliable? Are they capable of breaking the scsi bus?
> For driver upgrade, you may want to have a look at:
> ftp://ftp.tux.org/pub/roudier/drivers/linux/sym53c8xx/
Gerard, I've just downloaded kernel 2.2.6; is your driver included?
Robert
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
