This is a tricky bug, as it has to do with several modules interacting. It is also related somehow to the old bug report number 49074. Cdrecord (Cdrecord-ProDVD-Clone 2.01.01a20) Graveman (0.3.12-5) Gentoo-sources kernel (2.6.18) The issue is really simple to understand: -I don't have scsi cdrom support enabled in the kernel. I'm using ATA, as imho it seems stupid to use an emulation when I don't need one. -A bit related to the bug report mentioned earlyer, "cdrecord -scanbus" errors out. I need to use "cdrecord -dev=ATA -scanbus" to scan for devices. -Graveman finds its devices by calling "cdrecord -scanbus", which for the reason above doesn't work. So it just hangs.. So I'm not sure where this bug fits. I'm inclined to say it's graveman's fault, but not sure.. As for workarounds, there are lots of them, but I would prefer to see the issue fixed. And I don't want to use scsi, because I don't need to ;)
Kindly review https://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity
I thought "blocking" was for a bug which impeded the use of an application, not gentoo.. I appologise.
gravenan scans "dev=ATA:" and "dev=ATAPI:", plus usual IDE devices if IDE is available and SCSI devices if SCSI is available. I couldn't reproduce this bug neither with stable cdrtools nor the latest testing cdrtools on several boxes. Please post the output of "cdrecord -scanbus -dev=ATAPI".
Cdrecord-ProDVD-Clone 2.01.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling scsidev: 'ATAPI' devname: 'ATAPI' scsibus: -2 target: -2 lun: -2 Warning: dev=ATA: is preferred over dev=ATAPI:. Warning: Using ATA Packet interface. Warning: The related Linux kernel interface code seems to be unmaintained. Warning: There is absolutely NO DMA, operations thus are slow. Using libscg version 'schily-0.8'. scsibus0: 0,0,0 0) '_NEC ' 'DVD_RW ND-1300A ' '1.0B' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) *
Strangely graveman is working now. I'll check my emerge logs to see if anything changed. Thanks
I guess it was the kernel. I'm using 2.6.19-r4 now. Other than that everything is the same. Should I change the report to FIXED or INVALID?
Kinda INVALID then.