[8303] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: SYNC madness - is it Tekram (SYMBIOS) or Tandberg?

daemon@ATHENA.MIT.EDU (Kurt Garloff)
Mon Mar 6 14:24:39 2000

Date:   Mon, 6 Mar 2000 18:59:10 +0100
From: Kurt Garloff <garloff@suse.de>
To: linux-scsi@vger.rutgers.edu
Cc: Gerard Roudier <groudier@club-internet.fr>
Message-ID: <20000306185910.F2966@mobil.tue.nl>
Mail-Followup-To: linux-scsi@vger.rutgers.edu,
	Gerard Roudier <groudier@club-internet.fr>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="SxgehGEc6vB0cZwN"
In-Reply-To: <m3hfeki8k3.fsf@emma1.emma.line.org>; from ma@dt.e-technik.uni-dortmund.de on Mon, Mar 06, 2000 at 01:31:40PM +0100


--SxgehGEc6vB0cZwN
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 06, 2000 at 01:31:40PM +0100, Matthias Andree wrote:
> short: Tandberg TDC4222 does not do sync transfers on Tekram DC-390U
> (SYM53C875)
>=20
>=20
>=20
> setup:=20
> Linux 2.2.14 (openwall, reiserfs, current ide driver patches)
>=20
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
>   Vendor: HP       Model: HP35480A         Rev: 1209
>   Type:   Sequential-Access                ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
>   Vendor: TANDBERG Model:  TDC 4222        Rev: =3D07:
>   Type:   Sequential-Access                ANSI SCSI revision: 02
>=20
> problem:
>=20
> 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)=20
> sym53c875-0-<4,*>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
> sym53c875-0-<6,*>: target did not report SYNC.

G=E9rard has to help you. I don't know about a bug in the DC390 BIOS
misreporting speeds. The reason for the message, that your target does not
report sync might be:
* The device is buggy and does not answer with a corrected SDTR message, but
  refuses it, if more than 4MB/s are suggested by the initiator.
* The driver does not support sync speeds below 5MHz, as they don't make
  sense anyway. With async. transfers, you can get 5MB/s (and a little bit
  more, if your driver uses aggressive timing).

Regards,
--=20
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

--SxgehGEc6vB0cZwN
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1c- (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4w/HuxmLh6hyYd04RAeYwAKDN8fne4bKpLbk/wKcGwiYmxyX76ACg1lRt
aN3oyuqwiIuLLIWRgux83W0=
=qLWn
-----END PGP SIGNATURE-----

--SxgehGEc6vB0cZwN--

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post