From owner-freebsd-hackers Mon Jan 1 03:48:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA18663 for hackers-outgoing; Mon, 1 Jan 1996 03:48:07 -0800 (PST) Received: from cls.net (freeside.cls.de [192.129.50.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA18658 for ; Mon, 1 Jan 1996 03:48:04 -0800 (PST) Received: by mail.cls.net (Smail3.1.29.1) from allegro.lemis.de (192.109.197.134) with smtp id ; Mon, 1 Jan 96 11:47 GMT From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Reply-To: grog@lemis.de (Greg Lehey) Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id MAA27704 for hackers@freebsd.org; Mon, 1 Jan 1996 12:34:19 +0100 Message-Id: <199601011134.MAA27704@allegro.lemis.de> Subject: Problems with SCSI DDS driver? To: hackers@freebsd.org (FreeBSD Hackers) Date: Mon, 1 Jan 1996 12:34:18 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org Precedence: bulk I've just found a problem with the SCSI DDS tape driver in -current: it can't read some tapes. It works just fine with 90 meter DDS tapes with the coding 010 (1=hole) on the underside, but with 60 meter tapes or with audio quality tapes (coding 000 in each case), I get the message: Jan 1 12:28:16 freebie /kernel: st0: block wrong size, 20 blocks residual If I try to write, I get Dec 31 19:04:02 freebie /kernel: st0(aha0:2:0): DATA PROTECT asc:30,0 Incompatible medium installed In each case, the tape is readable and writeable on the same hardware running BSD/OS 2.0, so it's not the hardware. Dec 31 18:56:00 freebie /kernel: (aha0:2:0): "HP HP35480A 1109" type 1 removable SCSI 2 Dec 31 18:56:00 freebie /kernel: st0(aha0:2:0): Sequential-Access density code 0x13, drive empty While I'm on the subject, wouldn't it be nice if the tape driver would wait until the drive comes ready rather than rejecting a request if the drive isn't ready? This works on QIC-150 and family, why not on DDS? Greg