k3b can't find optical drive

Message

curmudgeon · Post by **curmudgeon** » Sun May 12, 2013 12:11 am

I don't think this is a hardware problem, so it goes here.

No idea why this isn't working.

Kernel sees the (ordinary - not something unusual) drive:

Code: Select all

May 11 22:55:52 system kernel: [    0.604754] scsi 1:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-H653G  LW02 PQ: 0 ANSI: 5
May 11 22:55:52 system kernel: [    0.610559] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
May 11 22:55:52 system kernel: [    0.610560] cdrom: Uniform CD-ROM driver Revision: 3.20
May 11 22:55:52 system kernel: [    0.610635] sr 1:0:0:0: Attached scsi CD-ROM sr0
May 11 22:55:52 system kernel: [    0.610678] sr 1:0:0:0: Attached scsi generic sg1 type 5

User is in the cdrom group ("mplayer cdda://" works fine).

Dbus and consolekit are running.

But k3b says it can't find any optical drives.

VoidMage · Post by **VoidMage** » Sun May 12, 2013 8:29 am

I don't use KDE, but on the odd chance k3b uses udev markings, check if 'udevadm info' shows the drive as properly marked as such.

curmudgeon · Post by **curmudgeon** » Sun May 12, 2013 9:13 am

Everything that I can see looks normal:

Code: Select all

# hdparm -I /dev/sr0 

/dev/sr0:

ATAPI CD-ROM, with removable media
        Model Number:       TSSTcorp CDDVDW TS-H653G                
        Serial Number:      xxxxxxxxxxxxxx      
        Firmware Revision:  LW02    
Standards:
        Supported: CD-ROM ATAPI-3 -4 -5 -6 -7 
Configuration:
        DRQ response: 50us.
        Packet size: 12 bytes
        cache/buffer size  = unknown
Capabilities:
        LBA, IORDY(can be disabled)
        DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns


# udevadm info --query=property --name=/dev/sr0
DEVLINKS=/dev/cdrom /dev/disk/by-id/ata-TSSTcorp_CDDVDW_TS-H653G_xxxxxxxxxxxxxx
DEVNAME=/dev/sr0
DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0
DEVTYPE=disk
ID_ATA=1
ID_ATA_SATA=1
ID_ATA_SATA_SIGNAL_RATE_GEN1=1
ID_BUS=ata
ID_CDROM=1
ID_CDROM_CD=1
ID_CDROM_CD_R=1
ID_CDROM_CD_RW=1
ID_CDROM_DVD=1
ID_CDROM_DVD_PLUS_R=1
ID_CDROM_DVD_PLUS_RW=1
ID_CDROM_DVD_PLUS_R_DL=1
ID_CDROM_DVD_R=1
ID_CDROM_DVD_RAM=1
ID_CDROM_DVD_RW=1
ID_CDROM_MRW=1
ID_CDROM_MRW_W=1
ID_MODEL=TSSTcorp_CDDVDW_TS-H653G
ID_MODEL_ENC=TSSTcorp\x20CDDVDW\x20TS-H653G\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
ID_REVISION=LW02
ID_SERIAL=TSSTcorp_CDDVDW_TS-H653G_xxxxxxxxxxxxxx
ID_SERIAL_SHORT=xxxxxxxxxxxxxx
ID_TYPE=cd
MAJOR=11
MINOR=0
SUBSYSTEM=block
UDISKS_PRESENTATION_NOPOLICY=0
USEC_INITIALIZED=43389


# ls -al /dev/sr*
brw-rw---- 1 root cdrom 11, 0 2013-05-12 05:12:45 /dev/sr0

ulenrich · Post by **ulenrich** » Sun May 12, 2013 10:36 am

I have the new linux-3.9, and did for to be sure disable this new feature:
"SATA Zero Power Optical Disc Drive (ZPODD) support"

# zcat /proc/config.gz |grep SATA_ZPODD
# CONFIG_SATA_ZPODD is not set

curmudgeon · Post by **curmudgeon** » Sun May 12, 2013 2:18 pm

ulenrich wrote:I have the new linux-3.9, and did for to be sure disable this new feature:
"SATA Zero Power Optical Disc Drive (ZPODD) support"t

Still using the default stable (3.7.10-r1 for amd64). I will look out for that option when I encounter it.

Vorlon · Post by **Vorlon** » Mon May 13, 2013 2:08 pm

I'm using the same kernel with my burner on /dev/sr0 and have no problems with k3b.

Did you custom compile your kernel, or is it a genkernel? If manually compiled, you may very well have missed a setting to enable this. If a genkernel, then I'm stumped too.

Have you tried other burner programs to see if it is unique to k3b?

curmudgeon · Post by **curmudgeon** » Tue May 14, 2013 9:21 am

Vorlon wrote:Did you custom compile your kernel, or is it a genkernel? If manually compiled, you may very well have missed a setting to enable this. If a genkernel, then I'm stumped too.

Yes, it is a custom kernel, but given that other programs have no problem accessing the optical drive, I doubt it is a kernel configuration problem.

Vorlon wrote:Have you tried other burner programs to see if it is unique to k3b?

No, but I just tried plugging in a usb flash drive, and I get the same behavior - kde refuses to acknowledge its existence, but the system sees it fine, and I have no problem mounting it as root and accessing it.

JumboAg · Post by **JumboAg** » Sat Jul 20, 2013 1:11 am

I'm running into the same problem. CD/DVDs mount fine but k3b doesnt see optical drive. My optical is a SATA. I'm running 3.8.13. Anybody ever figure this one out?

piewie · Post by **piewie** » Sat Aug 17, 2013 7:31 pm

same here. All optical drives have gone in k3b. cdrecord can still see the drives:

Code: Select all

udo cdrecord --scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a16 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2013 Joerg Schilling
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
scsibus1:
        1,0,0   100) 'Optiarc ' 'DVD RW AD-7280S ' '1.01' Removable CD-ROM
        1,1,0   101) *
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
scsibus2:
        2,0,0   200) 'ATAPI   ' 'iHAS324   B     ' 'AL18' Removable CD-ROM
        2,1,0   201) *
        2,2,0   202) *
        2,3,0   203) *
        2,4,0   204) *
        2,5,0   205) *
        2,6,0   206) *
        2,7,0   207) *
scsibus3:
        3,0,0   300) 'PIONEER ' 'BD-RW   BDR-206D' '1.06' Removable CD-ROM
        3,1,0   301) *
        3,2,0   302) *
        3,3,0   303) *
        3,4,0   304) *
        3,5,0   305) *
        3,6,0   306) *
        3,7,0   307) *
scsibus13:
        13,0,0  1300) 'PLEXTOR ' 'CD-R   PREMIUM2 ' '1.03' Removable CD-ROM
        13,1,0  1301) *
        13,2,0  1302) *
        13,3,0  1303) *
        13,4,0  1304) *
        13,5,0  1305) *
        13,6,0  1306) *
        13,7,0  1307) *

piewie · Post by **piewie** » Tue Aug 20, 2013 9:53 pm

so, got my devices back. I took a look here:
http://forum.kde.org/viewtopic.php?f=15 ... 07c2eebace
https://forums.gentoo.org/viewtopic-t-8 ... ight-.html

Code: Select all

$ solid-hardware list
$ udisks --enumerate

did not show my devices / threw errors

Code: Select all

* added consolekit to use flags in make.conf
* emerge --update --newuse @system / @world
* emerge udisks (added "sys-fs/udisks cryptsetup" to packages.use - don't think this use flag is really necessary, but since I use encrypted devices ...) 
* emerge dbus
* restarted dbus
* done

Elv13 · Post by **Elv13** » Sun Dec 15, 2013 8:17 pm

This solved the issue for me

Code: Select all

 sudo chmod u+s /usr/libexec/dbus-daemon-launch-helper

No idea why it wasn't u+s in the first place, it has to be.

NuclearPeon · Post by **NuclearPeon** » Sat Feb 08, 2014 8:31 pm

I experienced this issue, but it wasn't due to dbus or consolekit/polkit.

I had compiled myself a new kernel and when I went to burn a dvd, it said it couldn't find optical drive.
The problem was one of two things:

- I had enabled apparmor in the kernel without installing the apparmor packages.
- I had enabled the "Restrict unprivileged access to the kernel syslog" option

I removed both options from my kernel, recompiled, and my drive was found again. Noob-ish mistake on my part.