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
<<attachment: smime.p7s>>
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
