cdrdao doesn't support burning using ATAPI even though ATAPI support can be added easilly. Could I change the ebuild to add ATAPI support and if so, should I have it disable/enable based on a local USE flag (since it would add cdrtools sources to the SRC_URI)? Reproducible: Always Steps to Reproduce:
Actually, this was supposedly fixed (a better way) for bug 23384... But it still doesn't work for some reason.
I had to update to cdrdao 1.1.8pre2 (http://fenrir.infoiasi.ro/~xcyborg/k3b/) to enable atapi burning under kernel 2.6.0-testX. Making the ebuild was a simple process of copying, en rebuilding the digest.
http://bugs.gentoo.org/show_bug.cgi?id=34085 Ebuild for cdrdao-1.1.8-pre2 (CVS) supporting atapi!
*** Bug 34085 has been marked as a duplicate of this bug. ***
cdrdao 1.1.7-r2 which uses the lib from cdrtools (which supports atapi burning) has been in portage for ages, any reason why it hasnt been marked stable yet ?
Have you had any luck using 1.1.7-r2 with ATAPI burner? My attempts with K3b and cdrdao command line haven't been too successful. Keeps trying to talk to it as a SCSI device.
It works with 1.1.7-r3. Could you verify it?
Nope: arumekun bin # cdrdao scanbus Cdrdao version 1.1.7-gentoo - (C) Andreas Mueller <andreas@daneb.de> SCSI interface library - (C) Joerg Schilling Paranoia DAE library - (C) Monty Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables. arumekun bin # K3b also reports cdrdao's lack of ATAPI support.
k3b tells everytime it's error-message, but that doesn't matter. It still works. You should check out the thread in the forums at: http://forums.gentoo.org/viewtopic.php?t=126036 I can access my two ATAPI burners with cdrdao disk-info --device ATAPI:0,1,0 --driver toshiba (for the TOSHIBA DVD-ROM SD-R2002 in my iBook) and cdrdao disk-info --device ATAPI:0,0,0 --driver generic-mmc-raw (for the TEAC DV-W58G in my x86). Which driver you have to set is listed on http://cdrdao.sourceforge.net/drives.html#dt Please check again ;)
I was basing the fact that it didn't work also on scanbus, which really should be scanning ATAPI devices as well... Manually specifying the ATAPI stuff did work, though.
Closing this bug.