Bug 357943 - k3b does not recognize second BD burner
Summary: k3b does not recognize second BD burner
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 2.0.80
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-01-13 18:05 UTC by Bugs.kde.org
Modified: 2018-10-27 04:01 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bugs.kde.org 2016-01-13 18:05:22 UTC
When I open k3b it only recognizes my Pioneer BDR-S09 at /dev/sdr1. 
It should see a second Pioneer BDR-S09 at /dev/sdr0 like openSuSE 13.2 does.
All was running well till I changed my /dev/sdr0 (I had another BD-burner inside).

Thanks for your help in advance

Reproducible: Always

Steps to Reproduce:
1.place 2 Pioneer BDR-S09 in a PC
2.boot openSuSE 13.2
3.start k3b

Actual Results:  
it only recognizes my Pioneer BDR-S09 at /dev/sdr1

Expected Results:  
should see a second Pioneer BDR-S09 at /dev/sdr0
Comment 1 Bugs.kde.org 2016-01-13 18:09:11 UTC
dmesg | grep -A8 CD-ROM:

[    2.566008] scsi 2:0:1:0: CD-ROM            PIONEER  BD-RW   BDR-S09  1.20 PQ: 0 ANSI: 5
[    2.566032] sd 2:0:0:0: [sda] Write Protect is off
[    2.566037] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.580674] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.580770] scsi 2:0:1:0: Attached scsi generic sg1 type 5
[    2.580961] scsi 3:0:0:0: Direct-Access     ATA      Maxtor 7V300F0   1630 PQ: 0 ANSI: 5
[    2.581230] sd 3:0:0:0: Attached scsi generic sg2 type 0
[    2.581232] sd 3:0:0:0: [sdb] 586112591 512-byte logical blocks: (300 GB/279 GiB)
[    2.583038] sd 3:0:0:0: [sdb] Write Protect is off
--
[    2.588341] scsi 3:0:1:0: CD-ROM            PIONEER  BD-RW   BDR-S09  1.20 PQ: 0 ANSI: 5
[    2.588367] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.607218] sr0: scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.607221] cdrom: Uniform CD-ROM driver Revision: 3.20
[    2.607416] sr 2:0:1:0: Attached scsi CD-ROM sr0
[    2.611333]  sda: sda1 sda2 sda3
[    2.611991] sd 2:0:0:0: [sda] Attached SCSI disk
[    2.628575] sr1: scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.628878] sr 3:0:1:0: Attached scsi CD-ROM sr1
[    2.629006] sr 3:0:1:0: Attached scsi generic sg3 type 5
[    2.655547]  sdb: sdb1
[    2.656299] sd 3:0:0:0: [sdb] Attached SCSI disk
[    2.694657] raid6: sse2x1    5277 MB/s
[    2.711664] raid6: sse2x2    7695 MB/s
[    2.728683] raid6: sse2x4    9597 MB/s
[    2.728686] raid6: using algorithm sse2x4 (9597 MB/s)
[    2.728687] raid6: using ssse3x2 recovery algorithm
Comment 2 Bugs.kde.org 2016-01-13 20:17:48 UTC
I did a firmware update to the actual revision 1.33, but nothing changed :(
Comment 3 Bugs.kde.org 2016-01-13 21:45:35 UTC
For your information: brasero recognizes both devices and is able to burn a DVD+R DL successfully.
Comment 4 Bugs.kde.org 2016-01-16 22:02:20 UTC
Now brasero recognizes only the other writer :(.

Test with k3b 2.0.3 and openSuSE 13.1 Live showed same result.

Even connecting the writers other SATA Ports didn't changed a thing.

Any idea what to try next?
Comment 5 Johannes Obermayr 2016-03-02 18:03:18 UTC
Please add konsole's output (kdebugdialog --on k3b && k3b).
Comment 6 Leslie Zhai 2016-09-06 03:20:22 UTC
Hi,

Please try k3b master https://github.com/KDE/k3b it is able to recognize MultiDevice: CDEmu Virt. CD/DVD-ROM and ASUS SDRW-08D2S-U https://pbs.twimg.com/media/Cro8t4oUEAAonM2.jpg

Regards,
Leslie Zhai
Comment 7 Andrew Crouthamel 2018-09-26 22:11:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-27 04:01:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!