You are not logged in.

#1 2023-12-02 03:03:01

Morphior
Member
Registered: 2023-12-02
Posts: 3

HDMI on USB-C Dongle only works when plugged in at boot

I’m on a Lenovo Yoga 920 laptop on i3 and I have a USB-C dongle which has a bunch of USB-A, SD, microSD, ethernet, and display ports (2 HDMI, 1 DisplayPort). Everything works perfectly except the display ports (at least HDMI, I don’t have either a monitor or a cable for DisplayPort so that’s untested). When I have the dongle plugged in at boot and a monitor is connected via HDMI and turned on at boot, the display output gets shown on both the internal laptop display and the external display (as it should be). However, when any of those things is not true, then I can’t get any display output on the external display. xrandr won’t recognize it at all (xrandr --auto) and unplugging and replugging the dongle doesn’t fix it either.
I have tried both USB-C ports on my device and nothing works, I always have to completely reboot the device in order to use an external display.
What can I do to fix this? Does anyone have any ideas? I’m happy to provide command outputs but I don’t really know what could help so if I could get some guidance I’d really appreciate any and all help! Thanks in advance.

Offline

#2 2023-12-02 08:26:12

seth
Member
Registered: 2012-09-03
Posts: 48,752

Re: HDMI on USB-C Dongle only works when plugged in at boot

unplugging and replugging the dongle doesn’t fix it either

Does re-plugging the monitor into the dongle "fix" it?

What's the response at

dmesg -w # run that and then plug the dongle

when plugging the dongle?

Offline

#3 2023-12-02 14:31:27

Morphior
Member
Registered: 2023-12-02
Posts: 3

Re: HDMI on USB-C Dongle only works when plugged in at boot

No, replugging the monitor into the dongle doesn’t fix it either.

Output of

dmesg -w
[37248.261218] usb 1-3: new high-speed USB device number 5 using xhci_hcd
[37248.404709] usb 1-3: New USB device found, idVendor=214b, idProduct=7250, bcdDevice= 1.00
[37248.404726] usb 1-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[37248.404734] usb 1-3: Product: USB2.0 HUB
[37248.406878] hub 1-3:1.0: USB hub found
[37248.406950] hub 1-3:1.0: 4 ports detected
[37248.595385] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:01:00.0
[37248.595478] pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[37248.595487] pcieport 0000:01:00.0:   device [8086:15d3] error status/mask=00002000/00000000
[37248.595507] pcieport 0000:01:00.0:    [13] NonFatalErr           
[37248.595772] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:01:00.0
[37248.595858] pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[37248.595866] pcieport 0000:01:00.0:   device [8086:15d3] error status/mask=00002000/00000000
[37248.595876] pcieport 0000:01:00.0:    [13] NonFatalErr           
[37248.691075] usb 1-3.2: new high-speed USB device number 6 using xhci_hcd
[37248.782053] usb 1-3.2: New USB device found, idVendor=214b, idProduct=7250, bcdDevice= 1.00
[37248.782070] usb 1-3.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[37248.782078] usb 1-3.2: Product: USB2.0 HUB
[37248.785343] hub 1-3.2:1.0: USB hub found
[37248.785405] hub 1-3.2:1.0: 4 ports detected
[37248.837692] pcieport 0000:00:1c.0: PME: Spurious native interrupt!
[37248.857943] usb 1-3.4: new high-speed USB device number 7 using xhci_hcd
[37248.969528] usb 1-3.4: New USB device found, idVendor=2109, idProduct=0102, bcdDevice=17.35
[37248.969544] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37248.969551] usb 1-3.4: Product: USB 2.0 BILLBOARD             
[37248.969557] usb 1-3.4: Manufacturer: VIA Technologies Inc.         
[37248.969563] usb 1-3.4: SerialNumber: 0000000000000001
[37249.098223] usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd
[37249.143843] usb 4-2: New USB device found, idVendor=2109, idProduct=0817, bcdDevice=90.14
[37249.143861] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37249.143868] usb 4-2: Product: USB3.0 Hub             
[37249.143874] usb 4-2: Manufacturer: VIA Labs, Inc.         
[37249.143879] usb 4-2: SerialNumber: 000000000
[37249.146653] hub 4-2:1.0: USB hub found
[37249.146975] hub 4-2:1.0: 4 ports detected
[37249.261030] usb 1-3.3: new high-speed USB device number 8 using xhci_hcd
[37249.352813] usb 1-3.3: New USB device found, idVendor=2109, idProduct=2817, bcdDevice=90.14
[37249.352831] usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37249.352839] usb 1-3.3: Product: USB2.0 Hub             
[37249.352845] usb 1-3.3: Manufacturer: VIA Labs, Inc.         
[37249.352850] usb 1-3.3: SerialNumber: 000000000
[37249.354375] hub 1-3.3:1.0: USB hub found
[37249.354739] hub 1-3.3:1.0: 4 ports detected
[37250.254415] xhci_hcd 0000:37:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[37250.557975] usb 4-2: USB disconnect, device number 3
[37250.814520] usb 4-2: new SuperSpeed USB device number 4 using xhci_hcd
[37250.860060] usb 4-2: New USB device found, idVendor=2109, idProduct=0817, bcdDevice=90.14
[37250.860077] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37250.860085] usb 4-2: Product: USB3.0 Hub             
[37250.860090] usb 4-2: Manufacturer: VIA Labs, Inc.         
[37250.860096] usb 4-2: SerialNumber: 000000000
[37250.864578] hub 4-2:1.0: USB hub found
[37250.864749] hub 4-2:1.0: 4 ports detected
[37251.497941] usb 4-2.3: new SuperSpeed USB device number 5 using xhci_hcd
[37251.515929] usb 4-2.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[37251.515945] usb 4-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[37251.515952] usb 4-2.3: Product: USB 10/100/1000 LAN
[37251.515958] usb 4-2.3: Manufacturer: Realtek
[37251.515963] usb 4-2.3: SerialNumber: 000001
[37251.655554] usbcore: registered new device driver r8152-cfgselector
[37251.731687] r8152-cfgselector 4-2.3: reset SuperSpeed USB device number 5 using xhci_hcd
[37251.773785] r8152 4-2.3:1.0: load rtl8153a-4 v2 02/07/20 successfully
[37251.803375] r8152 4-2.3:1.0 eth0: v1.12.13
[37251.803467] usbcore: registered new interface driver r8152
[37251.843926] usbcore: registered new interface driver cdc_ether
[37251.855307] usbcore: registered new interface driver r8153_ecm
[37251.935041] r8152 4-2.3:1.0 enp55s0u2u3: renamed from eth0

Last edited by Morphior (2023-12-02 14:32:24)

Offline

#4 2023-12-02 15:45:53

seth
Member
Registered: 2012-09-03
Posts: 48,752

Re: HDMI on USB-C Dongle only works when plugged in at boot

Hub showed up on https://bbs.archlinux.org/viewtopic.php?id=288498
"Product: USB-C Multiport Adapter" dorsn't appear for you.

[37250.254415] xhci_hcd 0000:37:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

so it's not just the HDCP.

Lenovo typically has an "always on usb" feature that you can toggle in the BIOS/UEFI - is it enabled and does that have any impact on the relevant usb port?
Does it help to plug/unplug/replug the dongle in a row to "bump" the usb slot?

Offline

#5 2023-12-02 15:55:36

Morphior
Member
Registered: 2023-12-02
Posts: 3

Re: HDMI on USB-C Dongle only works when plugged in at boot

I toggled the UEFI setting and it doesn‘t have any impact. I also tried the same dongle on Windows and it’s exactly the same - when plugging it in at runtime, the USB ports and everything gets recognized but not the HDMI whereas if it’s plugged in at boot, the display output works. So I think it might have something to do with the underlying UEFI or whatever and not with the OS. But I have no idea.

Also, unplugging and replugging it repeatedly also doesn’t help.

Last edited by Morphior (2023-12-02 15:57:04)

Offline

#6 2023-12-02 16:35:35

seth
Member
Registered: 2012-09-03
Posts: 48,752

Re: HDMI on USB-C Dongle only works when plugged in at boot

Just to be sure, 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

The odd part is that the dongle works fine during the usually more busy boot process, it might simply need some head-start for power supply.
Does it help to re-bind the USB? (make sure to use the actual usb nodes for that boot/after attaching the dongle)

echo '1-3' | sudo tee /sys/bus/usb/drivers/usb/unbind
echo '4-2' | sudo tee /sys/bus/usb/drivers/usb/unbind
echo '1-3' | sudo tee /sys/bus/usb/drivers/usb/bind
echo '4-2' | sudo tee /sys/bus/usb/drivers/usb/bind

Offline

Board footer

Powered by FluxBB