[8306] in linux-scsi channel archive
Re: SYNC madness - is it Tekram (SYMBIOS) or Tandberg?
daemon@ATHENA.MIT.EDU (Matthias Andree)
Mon Mar 6 23:04:20 2000
To: linux-scsi@vger.rutgers.edu
In-Reply-To: Kurt Garloff's message of "Mon, 6 Mar 2000 18:59:10 +0100"
From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Date: 07 Mar 2000 00:12:04 +0100
Message-ID: <m366uzd77f.fsf@emma1.emma.line.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Kurt Garloff <garloff@suse.de> writes:
[Tandberg SLR4DC "TDC 4222" does not negotiate SYNC with Tekram DC-390U]
> Gérard 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 drive inquiry data was wrong. A firmware update fixed the problem.
> * 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).
I have no clue, since I haven't tried to write to the drive's buffer
aggressively (is there a tool to check transfer speeds if the buffer
size is known, 256 kB in this drive?).
I somehow recalled drive specifications of 3 MB/s async and 5 MB/s sync,
but this may well be related to sluggish Adaptec ISA stuff such as ISA
AHA1542CF along with crappy Yamaha CD writers (CDR-200/400 series) and
not be up-to-date information.
Anyways, since the firmware update the driver negotiates 4 MB/s,
8-byte-per-handshake transfers.
See my reply to Gérard's posting for further details.
--
Matthias Andree
Hi! I'm the infamous .signature virus!
Copy me into your ~/.signature to help me spread!
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
