From owner-freebsd-hackers Sun Sep 26 1:24:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D0C9C14C97 for ; Sun, 26 Sep 1999 01:24:49 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA65733; Sun, 26 Sep 1999 10:24:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909260824.KAA65733@freebsd.dk> Subject: Re: wormcontrol write speed In-Reply-To: <19990926020604.A21048@netmonger.net> from Christopher Masto at "Sep 26, 1999 02:06:04 am" To: chris@netmonger.net (Christopher Masto) Date: Sun, 26 Sep 1999 10:24:03 +0200 (CEST) Cc: doconnor@gsoft.com.au (Daniel O'Connor), freebsd-hackers@FreeBSD.ORG, paulo@nlink.com.br X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher Masto wrote: > On Wed, Sep 22, 1999 at 09:27:37AM +0200, Soren Schmidt wrote: > > Anyhow, I have some changes to the worm stuff, it needs to be dealt with > > to handle modern HW, and to deal with all the possible block formats > > thats possible on a CD nowadays. It will probably mean the death of > > the worm stuff as is now, but I'm the last user anyways so.... > > Any chance of getting a passthrough or "SCSI emulation" so that > cdrecord could be used instead? (Then you won't have to worry about > different CD-R quirks) If somebody writes it there is a chance. I dont have this on my TODO list. I could maybe be talked into providing a generic ATAPI interface that would give you a method of injecting ATAPI commands directly into the systemi, cdrecord etc could use that then. > I have an Acer CRW 6202A which doesn't seem to work with FreeBSD > (current as of five minutes ago, including the rev 1.19 of > atapi-cd.c). "wormcontrol blank" (with a CD-RW of course) runs for a > little while, then aborts with an I/O error. Also, all IDE devices > are completely locked up while it's running. What I/O error ?? its impossible to diagnose on no data... > The dd also sort of works for a while, then gets an I/O error. Same > with fixate (which also locks up the IDE busses). What I/O error ?? its impossible to diagnose on no data... > I'm currently recompiling with ATAPI_DEBUG and ACD_DEBUG in the hopes > that I'll be able to produce a better bug report. Any suggestions? Provide data, the system spits out lots of sensekey things and the like on errors, those are invaluable data to diagnose this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message