K3b will only use one or the other of both drives.

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

Did a google search and could really only find issues with not detecting any burners. The few I found with not detecting both, are old and things have changed a lot since this: ie udev, udisks,...

Anyway, here is the issue: Two Optical Drives, both same: Lite-ON LH-20A1S drives (dev/sr0 & dev/sr1) . K3b will only use /dev/sr1 for some reason. It doesn't even see /dev/sr0.

It will see if if I trick it:
1) removed power from /dev/sr1, then it saw and used /dev/sr0, hooked /dev/sr1 power back and refreshed in K3b devices, didn't see /dev/sr1.
2) Thought, okay stuck with just /dev/sr0 then. No, restarted K3b and only /dev/sr1 showing up again.

Other info:
1) Made some home videos to DVD using DVDStyler, I used /dev/sr0 on that just fine.
2) I've also played back DVD's on both devices using Xine.
3) Dmesg sees them both the same.
4) Even removed entries for them in /etc/fstab, cause read it could possible cause confusion with new programs using /run/media/... Still works and works the same in K3b.

So there isn't a problem with the drives. Just can't seem to get K3b to see and use both them. Would be nice to have source DVD in one and burn the copy to the other. Plus it's annoying that
it isn't working the way I want. But maybe that is how K3b works now.

Any good ideas?

Thanks
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright

Roman_Gruber · Posted: Mon Jun 01, 2015 4:38 am Post subject:

AFAIK k3b is just a gui for commad line "cd-burner" commands.

1) check if k3b has any tweakable config files
2) bother with the command line "cd / dvd / whatever" commands to get the job done.

I have not bothered in ages with that stuff but i think one of the things used is

VoidMage · Watchman Joined: 14 Oct 2006 Posts: 6196

Well, 'udevadm info' on both nodes might be interesting, but lets go one level deeper - any chance the controller in BIOS is set to IDE instead of AHCI ?

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

I think it might be UDISKS. The reason I say this is cause it is acting like K3b. 1st post I mention a trick. Well same thing happening with UDISKS.
I will save you from all the other test outputs at first and post just this:
Permissions and user is in cdrom group and plugdev....
brw-rw---- 1 root cdrom 11, 0 Jun 1 20:03 sr0
brw-rw---- 1 root cdrom 11, 1 Jun 1 19:58 sr1

1) Both burners plugged in:
# solid-hardware list details | grep sr1

-> Block.device = '/dev/sr1' (string)

# solid-hardware list details | grep sr0
'NOTHING shows"

2) Just /dev/sr0 plugged in:
# solid-hardware list details | grep sr0

-> Block.device = '/dev/sr0' (string)

# solid-hardware list details | grep sr1
'NOTHING shows"

I'm going to look more into UDISKS on this. I might be barking up same tree, but only thing displaying the same exact behavior.
In fact, had K3b up while doing this. Still showed /dev/sr1, hit refresh and said no optical drives at all. Closed and restarted and now says /dev/sr0 only.

FYI: I might note here that in /dev folder /dev/cdrom is symlinked to /dev/sr0 and /dev/cdrom1 symlinked to /dev/sr1
Put that info in /etc/default/cdrecord and didn't change anything.

***Here is other stuff that doesn't show anything useful that I can tell:

VoidMage

VoidMage · Watchman Joined: 14 Oct 2006 Posts: 6196

I didn't say ''udevadm info'', I've said ''udevadm info' on both nodes'.

They can't show the same info, as at very least DEVPATH will differ.

As for udisks, what does 'udisksctl info' print for the nodes ?

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

Sorry about that, I misunderstood you. Yes the DEVPATH and few other things just to make them 'I guess' unique enough. I assumed that would be implied, but maybe you'll catch something I didn't, so should have posted it. Here is the sdiff.

udevadm info -a -n for /dev/sr0 & /dev/sr1

VoidMage · Watchman Joined: 14 Oct 2006 Posts: 6196

...

for the time being, I don't care that much about attribute walk, I wanted to see udev markings.
Also, for completeness sake, post 'lspci -k' too.

...and just my personal opinion, but those sdiffs make thing less readable, at least on this forum.

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

Here you go:

xaviermiller · Posted: Wed Jun 03, 2015 5:32 am Post subject:

https://bugs.kde.org/show_bug.cgi?id=337553
_________________
Kind regards,
Xavier Miller

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

That's the Ticket!

Did look at K3b bugs, even searched for multiple I think. Thanks!

Thanks, to everyone that contributed to this problem.
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.

I added to the bug report. Noticed how udisks is behaving and reporting. So added my results:
Udisks reports two ways:

a) udi = '/org/freedesktop/UDisks2/drives/LITE_ON_DVDRW_LH_20A1S_LITE_ON_DVDRW_LH_20A1S
1) where it only report /dev/sr1 (maybe just the last drive it sees if both the same)
2) this way only looks at 'drives'

b) '/org/freedesktop/UDisks2/block_devices/sr0' AND udi = '/org/freedesktop/UDisks2/block_devices/sr1'
1) where it reports both devices /dev/sr0 & /dev/sr1
2) this way looks at 'block_devices'

c) Looks like K3b is only looking at udi = '/org/freedesktop/UDisks2/drives/
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright