[8304] in linux-scsi channel archive
Re: SYNC madness - is it Tekram (SYMBIOS) or Tandberg?
daemon@ATHENA.MIT.EDU (=?ISO-8859-1?Q?G=E9rard_Roudier?=)
Mon Mar 6 15:58:16 2000
Date: Mon, 6 Mar 2000 22:00:04 +0100 (CET)
From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
To: linux-scsi@vger.rutgers.edu
In-Reply-To: <m3hfeki8k3.fsf@emma1.emma.line.org>
Message-ID: <Pine.LNX.4.10.10003062133090.1283-100000@linux.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On 6 Mar 2000, Matthias Andree wrote:
> short: Tandberg TDC4222 does not do sync transfers on Tekram DC-390U
> (SYM53C875)
>
>
>
> setup:
> Linux 2.2.14 (openwall, reiserfs, current ide driver patches)
>
> Tekram DC-390U with BIOS 3.20, drives as shown below, Plextor PX-32 is
> terminated at bus cable end, host adaptor is supposed to be terminated
> as well.
[ ... ]
> problem:
>
> Now, during the BIOS bus scan, the Tekram reports the Tandberg tape
> drive as offset 8 Byte/Handshake, 4 MXfers/s synchronous, in conformance
> with the Tandberg documentation. Loading the st module (2.2.14)
[ ... ]
> sym53c875-0-<6,*>: target did not report SYNC.
>
> Why does the Tekram BIOS report the Tandberg drive as 4 MB/s while the
> SYM driver reports the drive as using async? The sym driver is at its
> default settings (or does it read ncr53c8xx=tags:32,debug:0x200,specf:1?)
>
> Is this the driver's or the drive's fault? Is it that the max sync xfer
> rate is only 4 MB/s? How do I track this problem down to is root?
>
> How do I fix this?
A nail and a hammer would not help:), but result from 'scsiinfo -i' can.
Let me know.
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
