On Sat, Nov 22, 2025 at 2:22 PM home user via users <
[email protected]> wrote:

>
> On 11/22/25 8:40 AM, George N. White III wrote:
> > On Fri, Nov 21, 2025 at 1:13 PM home user via users
> > <[email protected]> wrote:
> > [snip]
> >
> > [...] try starting `journalctl --follow` in a
> > terminal,
> > then connect the data cable and watch for useful messages in the journal.
> -bash: journalctl --follow
> [...]

Nov 22 11:16:40 [sysname] kernel: usb 1-5: new high-speed USB device
> number 4 using xhci_hcd
> Nov 22 11:16:40 [sysname] kernel: usb 1-5: New USB device found,
> idVendor=2571, idProduct=152e, bcdDevice= 1.00
> Nov 22 11:16:40 [sysname] kernel: usb 1-5: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> Nov 22 11:16:40 [sysname] kernel: usb 1-5: Product: Slim Ext Blu-ray
> Nov 22 11:16:40 [sysname] kernel: usb 1-5: Manufacturer: HLDS Inc
> Nov 22 11:16:40 [sysname] kernel: usb 1-5: SerialNumber: BP52E25512102417
> Nov 22 11:16:40 [sysname] kernel: usb-storage 1-5:1.0: USB Mass Storage
> device detected
> Nov 22 11:16:40 [sysname] kernel: scsi host6: usb-storage 1-5:1.0
> Nov 22 11:16:40 [sysname] mtp-probe[6171]: checking bus 1, device 4:
>
> "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-5"
> Nov 22 11:16:40 [sysname] mtp-probe[6171]: bus: 1, device: 4 was not an
> MTP device
> Nov 22 11:16:40 [sysname] mtp-probe[6172]: checking bus 1, device 4:
>
> "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-5"
> Nov 22 11:16:40 [sysname] mtp-probe[6172]: bus: 1, device: 4 was not an
> MTP device
> Nov 22 11:16:42 [sysname] kernel: scsi 6:0:0:0: CD-ROM HL-DT-ST BD-RE
> BP60NB10   1.02 PQ: 0 ANSI: 0
> Nov 22 11:16:42 [sysname] kernel: sr 6:0:0:0: Power-on or device reset
> occurred
>
Nov 22 11:16:42 [sysname] kernel: sr 6:0:0:0: [sr0] scsi3-mmc drive:
> 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
> Nov 22 11:16:42 [sysname] kernel: sr 6:0:0:0: Attached scsi CD-ROM sr0
> Nov 22 11:16:42 [sysname] kernel: sr 6:0:0:0: Attached scsi generic sg1
> type 5
> Nov 22 11:16:42 [sysname] (udev-worker)[6166]: sr0: Process
> '/usr/sbin/pktsetup -i -d 11:0' failed with exit code 1.
> Nov 22 11:16:42 [sysname] fwupd[3292]: 18:16:42.100 FuEngine      failed
> to add device
> /sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-5/1-5:1.0/host6/target6:0:0/6:0:0:0/block/sr0:
>
> failed to subclass open: failed to open /dev/sr0: Operation not permitted
> Nov 22 11:16:42 [sysname] fwupd[3292]: 18:16:42.104 FuEngine      failed
> to add device
> /sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-5/1-5:1.0/host6/target6:0:0/6:0:0:0/block/sr0:
>
> failed to subclass open: failed to open /dev/sr0: Operation not permitted
> Nov 22 11:16:42 [sysname] (udev-worker)[6179]: sr0: Process
> '/usr/sbin/pktsetup -i -d 11:0' failed with exit code 1.


Good.  Now we have "idVendor=2571, idProduct=152e,", which you can use to
search on the LHDB
<https://linux-hardwar.org> to see reports from other linux users.

This looks like a power management problem, possibly the USB cable that
provides power is being
turned off because there is no active data.  <
https://www.baeldung.com/linux/control-usb-power-supply>
may give you some ideas, but not everything may be correct for Fedora 43.
If you have an external
powered USB hub I would try moving the data cable to the hub.

Some linux kernel changes related to power management need vendor (system
and or external drive)
firmware updates.

"Nov 22 11:16:42 [sysname] fwupd[3292]: 18:16:42.100 FuEngine      failed
to add device" indicates the
vendor doesn't participate in the vendor firmware update program, so you
would have to check for updates
in Windows or the vendor's site.

-- 
George N. White III
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to