From owner-freebsd-current  Thu Feb 15 23:21:25 2001
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 87F4037B491
	for <current@FreeBSD.ORG>; Thu, 15 Feb 2001 23:21:22 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id IAA70241;
	Fri, 16 Feb 2001 08:21:17 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200102160721.IAA70241@freebsd.dk>
Subject: Re: HEADSUP! change to atapi-cd driver and burncd
In-Reply-To: <200102160658.f1G6whU00835@chapel-hill.tfd.com> from Kent Hauser at "Feb 16, 2001 01:58:44 am"
To: kent@tfd.com (Kent Hauser)
Date: Fri, 16 Feb 2001 08:21:16 +0100 (CET)
Cc: current@FreeBSD.ORG
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-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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