cdrecord hangs with kernel >= 2.6.10 and cyberdrive cdrw
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
linux-2.6 (Debian) |
Fix Released
|
Unknown
|
Bug Description
cdrecord hangs at every attempt to write a CD with at CyberDrive CDRW drive when
using a kernel >= 2.6.10 and cdrecord version > 2.0+a30. IOW, this applies to
several Ubuntu distributions. Downgrading cdrecord to 2.0+a30 is an acceptable
short-term fix, but not in the long run. Downgrading to kernel 2.4 or 2.6 <= .9
would also work.
I am not a hardware or kernel expert, but I own a CyberDrive CDRW drive. I can
aid in testing, if that is necessary.
The bug is discussed several places. Schily and the cdrecord people won't touch
it with a pole (claiming it's the kernel's fault), the kernel people discuss it
at http://
the debian people discuss it at
http://
to what change in cdrecord is causing the problem (from the a33 changelog):
"- cdrecord now tries to check the DMA speed if the drive supports to read the
drive buffer. If the DMA speed is not sufficient, then cdrecord requires
that burnfree is activated. If the environment variable "CDR_FORCESPEED"
is set or -force has been specified, then cdrecord does not try to enforce
that the available DMA speed is 2x the expected write speed."
This becomes problematic because the CyberDrive units are inherently brain-dead
and non-standardized, and it sends spurious interrupts when polling DMA speed (I
think).
In the long run, Schily and the kernel people should sort out their differences.
But maybe Ubuntu should consider rolling out a fixed version of cdrecord, which
for instance could disable this check with a command-line flag or something
similar. This bug has annoyed me for more than a year (since 2.6.10), and
neither the kernel or cdrecord people seem to {want|be able} to fix it.
Changed in cdrtools: | |
status: | Unconfirmed → Confirmed |
Changed in cdrtools: | |
status: | New → Fix Released |
Changed in linux-2.6 (Debian): | |
status: | Unknown → Fix Released |
I suggested in the duplicate bug #16791 that whatever change was made in the last working build of cdrecord be undone as an Ubuntu patch - hopefully that way we can get cdrecord working for those of us with CyberDrive devices. (I also have a CW058D and am happy to test if necessary.) The current recommendation is "get new hardware" which is never an acceptable solution in my book.