From owner-freebsd-scsi Thu Jan 25 13:59:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09935 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 13:59:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA09788 for ; Thu, 25 Jan 1996 13:57:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA15749; Thu, 25 Jan 1996 22:55:34 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA19491; Thu, 25 Jan 1996 22:55:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id WAA15751; Thu, 25 Jan 1996 22:40:31 +0100 (MET) From: J Wunsch Message-Id: <199601252140.WAA15751@uriah.heep.sax.de> Subject: Re: HP CD Writer To: freebsd-scsi@freebsd.org Date: Thu, 25 Jan 1996 22:40:30 +0100 (MET) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org, fcawth@jjarray.umd.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601251340.IAA00931@jjarray.umd.edu> from "Fred Cawthorne" at Jan 25, 96 08:40:35 am X-Phone: +49-351-2012 669 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-freebsd-scsi@freebsd.org Precedence: bulk As Fred Cawthorne wrote: > > > You need an ``override entry'' in scsiconf.c. Most likely: > > > > { > > T_WORM, T_WORM, T_REMOV, "HP", "C4324/C4325", "*", > > "worm", SC_ONE_LU > > }, > > > I assume there are only supposed to be one of the T_WORM above? At least No, really two of them. Well, actually, the first one must be a T_CDROM, since this is what the INQUIRY string is matched for. The second one is the driver assigned. > that is what the other entries look like. Also, what exactly is the > format of this thing and how does it work? I can't seem to get it to > work. Does it compare the ID strings for every device type, then > make it type T_WORM and attach it to the worm driver no matter what > device type the drive actually returns? Something that way. Alas, i've just checked out the 2.1R code and had to see that these changes to scsiconf.c didn't make it into 2.1. So i'm afraid you will either have to upgrade to some -current system, or to hand-fiddle these changes into your code. > > As it stands: a unit attention. These drives tend to generate a lot > > of them. > > > The unit attention seems to be the result of the ncr driver resetting the > bus when the handshake timeout occurs. I have disabled the handshake > timeout (like it is in the -current driver) and I don't see these problems > any more. Aha, i haven't been using an NCR for this kind of work yet. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)