Date: Fri, 16 Feb 2001 08:21:16 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: kent@tfd.com (Kent Hauser) Cc: current@FreeBSD.ORG Subject: Re: HEADSUP! change to atapi-cd driver and burncd Message-ID: <200102160721.IAA70241@freebsd.dk> In-Reply-To: <200102160658.f1G6whU00835@chapel-hill.tfd.com> from Kent Hauser at "Feb 16, 2001 01:58:44 am"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Kent Hauser wrote: > Hi all, > > I've been getting errors with "burncd" that I've not seen before. > Specifically, I'm seeing the following: > > chapel-hill# burncd -f /dev/acd1c -s 4 blank data *1.iso fixate > blanking CD - 100 % done > burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Device busy > chapel-hill# > > Trace messages from /var/log/messages: > > Feb 16 00:52:00 chapel-hill /boot/kernel/kernel: acd1: CD-RW <R/RW 4x4x24> at ata1-slave using PIO4 > Feb 16 00:53:30 chapel-hill /boot/kernel/kernel: acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00 This is because some sloppy firmware coders hasn't implemented the "test unit ready" command proberly, it return ready no matter what state the drive is in :( I've gotten ahold of one burner that has this problem and I'm trying to come up with a fix for it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102160721.IAA70241>