NO CD/DVD's detected

[Mike Chambers]

I don't know about after an initial f8t2 install, but at least since the
updates, k3b nor xcdroast can detect a cdrom nor dvd drive.  It wasn't
detected on my last updated system before I did a reinstall yesterday.
I can see the devices in the kernel messages.  Would this have to do
with cdrecord or something about that, as I thought there were license
problems with that program and therefore is maybe screwing things up?

[Till Maas]

On Fr September 28 2007, Mike Chambers wrote:
> I can see the devices in the kernel messages.  Would this have to do
> with cdrecord or something about that, as I thought there were license
> problems with that program and therefore is maybe screwing things up?

Since Fedora 7, Fedora contains cdrkit instead of cdrecord, the application is 
now called wodim (cdrecord is a symlink to wodim) and does not have this 
license problems.

Regards,
Till

[Mike Chambers]

On Fri, 2007-09-28 at 08:10 +0200, Till Maas wrote:
> On Fr September 28 2007, Mike Chambers wrote:
> > I can see the devices in the kernel messages.  Would this have to do
> > with cdrecord or something about that, as I thought there were license
> > problems with that program and therefore is maybe screwing things up?
>
> Since Fedora 7, Fedora contains cdrkit instead of cdrecord, the application is 
> now called wodim (cdrecord is a symlink to wodim) and does not have this 
> license problems.

Yes I can see that wodim is installed and the symlinks.  But not sure if
this is related to my problem or not though.  If it's been this way a
while, then guess it's something else.  I don't know why k3b won't pick
up neither of my drives.

[Denis Leroy]

Mike Chambers wrote:
> On Fri, 2007-09-28 at 08:10 +0200, Till Maas wrote:
> > On Fr September 28 2007, Mike Chambers wrote:
> > > I can see the devices in the kernel messages.  Would this have to do
> > > with cdrecord or something about that, as I thought there were license
> > > problems with that program and therefore is maybe screwing things up?
> >
> > Since Fedora 7, Fedora contains cdrkit instead of cdrecord, the application is 
> > now called wodim (cdrecord is a symlink to wodim) and does not have this 
> > license problems.
>
> Yes I can see that wodim is installed and the symlinks.  But not sure if
> this is related to my problem or not though.  If it's been this way a
> while, then guess it's something else.  I don't know why k3b won't pick
> up neither of my drives.

What if you run as root ? Do you see a difference between "wodim 
--scanbus" and  "sudo wodim --scanbus" ?

[Ralf Ertzinger]

Hi.

On Fri, 28 Sep 2007 13:07:52 +0200, Denis Leroy wrote:
> What if you run as root ? Do you see a difference between "wodim 
> --scanbus" and  "sudo wodim --scanbus" ?

As far as I know (which may well be wrong) k3b does not use wodim
to scan for drives, but uses internal code for that.

The actual burning is another story.

[Mike Chambers]

On Fri, 2007-09-28 at 13:07 +0200, Denis Leroy wrote:
> What if you run as root ? Do you see a difference between "wodim 
> --scanbus" and  "sudo wodim --scanbus" ?

[mike@scrappy ~]$ sudo wodim --scanbus
Password:
scsibus1:
        1,0,0   100) 'LITE-ON ' 'LTR-52327S      ' 'QS58' Removable
CD-ROM
        1,1,0   101) 'LITE-ON ' 'DVDRW SHW-160P6S' 'PS09' Removable
CD-ROM
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
[mike@scrappy ~]$ su -
Password: 
[root@scrappy ~]# wodim --scanbus
scsibus1:
        1,0,0   100) 'LITE-ON ' 'LTR-52327S      ' 'QS58' Removable
CD-ROM
        1,1,0   101) 'LITE-ON ' 'DVDRW SHW-160P6S' 'PS09' Removable
CD-ROM
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *

[Harald Hoyer]

Mike Chambers schrieb:
> I don't know about after an initial f8t2 install, but at least since the
> updates, k3b nor xcdroast can detect a cdrom nor dvd drive.  It wasn't
> detected on my last updated system before I did a reinstall yesterday.
> I can see the devices in the kernel messages.  Would this have to do
> with cdrecord or something about that, as I thought there were license
> problems with that program and therefore is maybe screwing things up?

Hmm, k3b WORKSFORME.. Is ConsoleKit running?

$ k3b
 (K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_DVD_RAM_UJ_850S to device /dev/sr0
/dev/sr0 resolved to /dev/sr0
/dev/sr0 is block device (0)
/dev/sr0 seems to be cdrom
bus: 0, id: 0, lun: 0
(K3bDevice::Device) /dev/sr0: init()
(K3bDevice::Device) /dev/sr0 feature: CD Mastering
(K3bDevice::Device) /dev/sr0 feature: CD Track At Once
(K3bDevice::Device) /dev/sr0 feature: CD-RW Media Write Support
(K3bDevice::Device) /dev/sr0 feature: DVD Read (MMC5)
(K3bDevice::Device) /dev/sr0 feature: DVD+R
(K3bDevice::Device) /dev/sr0 feature: DVD+RW
(K3bDevice::Device) /dev/sr0 feature: DVD+R Double Layer
(K3bDevice::Device) /dev/sr0 feature: DVD-R/-RW Write
(K3bDevice::Device) /dev/sr0 feature: Rigid Restricted Overwrite
(K3bDevice::Device) /dev/sr0 feature: Layer Jump Recording
(K3bDevice::Device) /dev/sr0 unknown profile: 2
(K3bDevice::Device) /dev/sr0: dataLen: 60
(K3bDevice::Device) /dev/sr0: checking for TAO
(K3bDevice::Device) /dev/sr0: checking for SAO
(K3bDevice::Device) /dev/sr0: checking for SAO_R96P