atapicam and cd-rw problem, no cd0 but acd0 some error

eculp at argosteve.com eculp at argosteve.com
Thu Jun 14 13:56:20 UTC 2007


Quoting Tom Evans <tevans.uk at googlemail.com>:

> On Thu, 2007-06-14 at 07:35 -0500, eculp at argosteve.com wrote:
>> Quoting Tom Evans <tevans.uk at googlemail.com>:
>>
>> > On Wed, 2007-06-13 at 20:34 +0200, Momchil Ivanov wrote:
>> >> Hi guys,
>> >>
>> >> I am running  6-STABLE as of today and I cannot use the CD-RW on my
>> >> IBM T40 to
>> >> burn CDs. When I put atapicam_load="YES" in loader.conf or
>> compile it in the
>> >> kernel I see the following error
>> >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40
>> >> 0x00 0x01
>> >> and no /dev/cd0 is created. I don`t see the above error without atapicam
>> >> loaded or in kernel. This is not something new, I haven`t been able to
>> >> get /dev/cd0 since more than a month following 6-STABLE, don`t know if it
>> >> ever worked on 6 or 6.x, but I certainly cannot get it to work on
>> 6-STABLE.
>> >> Any help would be appreciated :) I would be happy ot be able to burn CDs.
>> >>
>> >> I have acd0: CDRW <TOSHIBA DVD-ROM SD-R9012/1121> at ata1-master UDMA33
>> >> and camcontrol shows:
>> >> <TOSHIBA DVD-ROM SD-R9012 1121>    at scbus2 target 0 lun 0 (pass1)
>> >>
>> >> Thanks
>> >>
>> >
>> > The error message is benign - the controller tries to send a command to
>> > the device, the device doesn't support it, so you get the error message.
>> > That's all, everything else should work.
>> >
>> > Do you load or compile into your kernel
>> > 	device scbus
>> > 	device cd
>> > 	device atapicam
>> >
>> > atapicam allows you to access ATAPI devices through the SCSI subsystem,
>> > so you must ensure that you have a SCSI subsystem to access them
>> > through.
>> >
>> > Cheers
>> >
>> > Tom
>>
>> Hi Tom,
>>
>> I am getting a very similar error with my sony cdrom:
>>
>> Jun 14 07:12:36 HOME kernel: acd0: FAILURE - INQUIRY ILLEGAL REQUEST
>> asc=0x24 ascq=0x00
>> Jun 14 07:12:36 HOME kernel: (probe0:ata1:0:1:0): error 22
>> Jun 14 07:12:36 HOME kernel: (probe0:ata1:0:1:0): Unretryable Error
>> Jun 14 07:12:36 HOME kernel: pass0 at ata1 bus 0 target 1 lun 0
>> Jun 14 07:12:36 HOME kernel: pass0: <SONY CD-RW  CRX230ED 4YS1>
>> Removable CD-ROM SCSI-0 device
>> Jun 14 07:12:36 HOME kernel: pass0: 33.000MB/s transfers
>> Jun 14 07:12:36 HOME kernel: GEOM: new disk cd0
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error
>> Jun 14 07:12:36 HOME kernel: cd0 at ata1 bus 0 target 1 lun 0
>> Jun 14 07:12:36 HOME kernel: cd0: <SONY CD-RW  CRX230ED 4YS1>
>> Removable CD-ROM SCSI-0 device
>> Jun 14 07:12:36 HOME kernel: cd0: 33.000MB/s transfers
>> Jun 14 07:12:36 HOME kernel: cd0: Attempt to query device size failed:
>> NOT READY, Medium not present
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6
>> Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error
>>
>> There was a good cd in the burner when booting.
>>
>> the unfortunate part is that in this case, it doesn't seem to be
>> benign because I can't mount any cd nor can I use burncd or k3b.
>>
>> Any suggestions appreciated.  IIRC, I can use burncd if I remove
>> scsi support.
>>
>> Thanks,
>>
>> ed
>>
>
> Hey ed
>
> Those errors look different to what was described (I only get one such
> error in my dmesg), and different to what the OP reported (he didnt get
> a cd0).
>
> I don't run STABLE, just CURRENT, so I don't know what to suggest. There
> was a lot of talk about problems burning in k3b on freebsd-stable@ a few
> months ago, I suggest searching the archives for k3b and see what the
> resolution was to that.
>
> If you haven't already (and don't have a good reason to not), I'd ensure
> your kernel + userland are up to date, perhaps track RELENG_6 rather
> than RELENG_6_[12] and see if that helps.
>
> Tom
>

Thanks a lot, Tom.  I am running RELENG6 from this morning.
6.2-STABLE FreeBSD 6.2-STABLE #279: Thu Jun 14 07:50:36 CDT 2007

I've had some really weird problems with RELENG_6 since the end of  
May.  My kernel from May 21 has fewer problems.  Actually my CURRENT  
machines are giving me no grief and I'm considering upgrading this one  
to current.

Thanks again,

ed


More information about the freebsd-stable mailing list