Re: HEADSUP! change to atapi-cd driver and burncd
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 Version is current as of 2001/02/07. Any comments welcome. Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP! change to atapi-cd driver and burncd
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... -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP! change to atapi-cd driver and burncd
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... Is this the same problem I was having with my NEC burner? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP! change to atapi-cd driver and burncd
It seems Kenneth Wayne Culver wrote: 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... Is this the same problem I was having with my NEC burner? No, your problem was IIRC that the drive wouldn't accept the setting of the write mode page... -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
