Does USB-C docking now require a firmware package, or is there a known regression?

General system Kernel, boot, graphics & hardware
1

So, updated this morning, and after updating, when docked on my USB-C dock, all the hardware works EXCEPT the alt-mode display port. Was working as of when I ran the update, so definitely something in the update. I know recently a bunch of the wireless firmware is now tied to packages (YAY!!) instead of just installed, so was wondering if anyone knows if this is a kernel regression in the latest kernel or if it’s I’m missing a firmware package that’s required for it to work?

The laptop in question is a HP Elitebook X G1A, and the dock is a Kensington SD4600P. The dock is definitely seen when connected

[tim@kyton ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 30c9:00e4 Luxvisions Innotech Limited HP 5MP Camera
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0e8d:8c38 MediaTek Inc. Wireless_Device
Bus 003 Device 003: ID 06cb:0106 Synaptics, Inc. 
Bus 003 Device 004: ID 047d:8021 Kensington K38231_01
Bus 003 Device 005: ID 04b4:5217 Cypress Semiconductor Corp. Billboard Device
Bus 003 Device 006: ID 047d:8023 Kensington K38231_02
Bus 003 Device 007: ID 04b4:3610 Cypress Semiconductor Corp. K38231_03
Bus 003 Device 008: ID 08bb:2912 Texas Instruments PCM2912A Audio Codec
Bus 003 Device 009: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 003 Device 010: ID 1a2c:99f4 China Resource Semico Co., Ltd USB Gaming Keyboard 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
2

Can you boot the laptop with dock under MS Windows? Maybe a reinitialization from the Windows driver could sort things out again.

3

I’d have to wipe Endeavour to put windows back on.

4

Do you know what update caused the issue? If so then just downgrade that package for now. You can check what the updates were by looking at /var/log/pacman.log

5

No idea, I ASSUME it was the kernel, but it hadn’t been updated in a several weeks actually so it was quite a lengthy list of updates. And if this ISN’T a regression, and is instead that the firmware for this feature is no longer just installed as part of the kernel, then it’s not necessarily going to fix it downgrading the kernel.

6

How do you know unless you try that. Downgrading the kernel is a simple step. I don’t know what individual updates you had or what might have caused it but looking through them from the log is sometimes helpful. Was there any firmware updates? Try the downgrade then you’ll know if it’s kernel possibly or not.

7

IT was firmware. I upgraded my Elitebook 845 G11, same kernel version, and similar enough builds (Xen 4 vs. Xen 5, but RDNA3 & RDNA3.5) that it worked still on the 845 that I figured it wasn’t the kernel. So I did a ‘pacman -Ss firmware | grep -i installed’, and somehow on the last upgrade, the Elitebook X removed the linux-firmware-amdgpu package. Reinstalled and restarted, and everything working as it should again.

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.