You are not logged in.
Hi to all,
I've just bought an Ugreen usb-c hub with Pd functionality
It is connected to one usb-c port and it has connected the hdmi out, an externa hdd 2,5", an usb audio card and an usb kvm with connected keyboard and mouse.
The usb-c hub is powered by my laptop charger.
When I turn on the laptop with the hub connected, the hdmi works, but all USB devices are not recognized with the "unable to enumerate USB device"
If I unplug and replug it, it works perfectly.
Is there something I can do to solve this issue?
sudo dmesg | grep "usb 3-4"
[ 2.133681] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[ 2.278623] usb 3-4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=57.01
[ 2.278627] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.278628] usb 3-4: Product: USB2.1 Hub
[ 2.278630] usb 3-4: Manufacturer: GenesysLogic
[ 4.474790] usb 3-4-port1: attempt power cycle
[ 6.794252] usb 3-4-port1: unable to enumerate USB device
[ 8.724774] usb 3-4-port2: attempt power cycle
[ 11.027966] usb 3-4-port2: unable to enumerate USB device
[ 12.947924] usb 3-4-port3: attempt power cycle
[ 15.265450] usb 3-4-port3: unable to enumerate USB device
[ 17.192218] usb 3-4-port4: attempt power cycle
[ 19.508796] usb 3-4-port4: unable to enumerate USB device
[ 101.111755] usb 3-4: USB disconnect, device number 3
[ 112.405641] usb 3-4: new high-speed USB device number 22 using xhci_hcd
[ 112.550461] usb 3-4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=57.01
[ 112.550471] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 112.550474] usb 3-4: Product: USB2.1 Hub
[ 112.550476] usb 3-4: Manufacturer: GenesysLogic
[ 112.886060] usb 3-4.4: new high-speed USB device number 23 using xhci_hcd
[ 112.999852] usb 3-4.4: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 112.999864] usb 3-4.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 112.999868] usb 3-4.4: Product: USB 2.0 Hub
[ 113.379730] usb 3-4.4.2: new low-speed USB device number 24 using xhci_hcd
[ 113.576730] usb 3-4.4.2: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=49.20
[ 113.576750] usb 3-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 113.576756] usb 3-4.4.2: Product: USB Keyboard
[ 113.576760] usb 3-4.4.2: Manufacturer: Logitech
[ 113.759670] usb 3-4.4.3: new low-speed USB device number 25 using xhci_hcd
[ 113.952992] usb 3-4.4.3: New USB device found, idVendor=1bcf, idProduct=08a0, bcdDevice= 1.02
[ 113.953003] usb 3-4.4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 115.049186] usb 3-4.3: new full-speed USB device number 26 using xhci_hcd
[ 115.164690] usb 3-4.3: New USB device found, idVendor=12d1, idProduct=0010, bcdDevice= 1.00
[ 115.164698] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 115.164700] usb 3-4.3: Product: KT USB Audio
[ 115.164701] usb 3-4.3: Manufacturer: KTMicro
[ 115.164702] usb 3-4.3: SerialNumber: 2021-06-07-0000-0000-0000-
[ 115.569084] usb 3-4.2: new high-speed USB device number 27 using xhci_hcd
[ 115.683609] usb 3-4.2: New USB device found, idVendor=152d, idProduct=2339, bcdDevice= 1.00
[ 115.683615] usb 3-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 115.683617] usb 3-4.2: Product: USB to ATA/ATAPI Bridge
[ 115.683618] usb 3-4.2: Manufacturer: JMicron
[ 115.683619] usb 3-4.2: SerialNumber: 152D203380B6Offline
try unbind and bind the usb device,
https://stackoverflow.com/questions/187 … vice-again
1st answer.
For me this worked for a usb 3.0 hdd case, which did not work until re-plug or the unbind/bind workaround.
If this is working, you can build a small script around this workaround to run it automatically on reboot or suspend/resume.
Offline
try unbind and bind the usb device,
https://stackoverflow.com/questions/187 … vice-again
1st answer.For me this worked for a usb 3.0 hdd case, which did not work until re-plug or the unbind/bind workaround.
If this is working, you can build a small script around this workaround to run it automatically on reboot or suspend/resume.
I've tried, but it didn't solve the issue.
Offline
I've done other tests and the behaviour is always reproducible both in linux and in windows the first boot after power on and only if the hub is powered before the pc is turned on.
EDIT
The issue is the same with another usb hub, same brand and model.
Can it be fixed or is better if I buy a different brand and model?
However adding fwupdmgr get-devices to autostart seems to solve the issue.
Is it possible to execute it during the boot process and not later when I login in the desktop environment?
Last edited by Xwang (2024-09-02 22:17:18)
Offline