I have recently upgraded from 2.6.8 to 2.6.10, i haven't changed almost anything, but with the new kernel my CD recorder doesnt work.

When I try to record a CD, my drive start to light the leds, both, reading and writing, but doesn't do anything more, and i cannot do anything with this up to reboot, neither eject the CD. Then the recorder dissapear. The program finish returning error and cdrecord --scanbus doesn't detect my unit.

cdrdao doesn't say anything.

cdrecord says that:

cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Warning: Running on Linux-2.6.10agatha-20041226
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.5.31
SCSI buffer size: 64512
cdrecord: Success. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 00 00 00 00 00 00 00 00
Sense Key: 0xFFFFFFFF [], Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 60.306s timeout 40s
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
....
....
cdrecord: No such device or address. Cannot send SCSI cmd via ioctl



And dmesg says:

hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: drive not ready for command
ide-scsi: No active request in idescsi_eh_reset
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 8 lun 0


I dont know what can be bad, some idea?

assuming these are IDE devices, remove the ide-scsi dependency and use the ATAPI devive directly. this functionality is totally mature now, and suitable for use.

Ok, I have recompilled without ide-scsi, and now i can use cdrecord with --dev=ATAPI:0,0,0 and it works perfectly, thanks a lot.