I just applied the latest updates via the Fedora update manager. After reboot, my HDMI module is no longer functioning. I see the following in dmesg
[ 136.186841] usb 1-1: USB disconnect, device number 2
[ 145.699363] ucsi_acpi USBC000:00: unknown error 0
[ 145.699376] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 146.706968] usb 1-1: new full-speed USB device number 5 using xhci_hcd
[ 146.872406] usb 1-1: New USB device found, idVendor=32ac, idProduct=0002, bcdDevice= 0.00
[ 146.872421] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 146.872427] usb 1-1: Product: HDMI Expansion Card
[ 146.872431] usb 1-1: Manufacturer: Framework
[ 146.872435] usb 1-1: SerialNumber: 11AD1D00A49C401422040B00
[ 146.950299] hid-generic 0003:32AC:0002.0006: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[ 153.374277] ucsi_acpi USBC000:00: unknown error 256
[ 153.374289] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 179.023331] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 179.287988] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 652.679872] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 652.946927] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
Here is the output of lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 001 Device 004: ID 0e8d:e616 MediaTek Inc. Wireless_Device
Bus 001 Device 005: ID 32ac:0002 Framework HDMI Expansion Card
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 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
Do you see those messages when you connect a HDMI cable or even with a non-used HDMI port?
I think I got a quite similiar or even the same problem: AMD Framework, latest USB-HDMI adapter and latest firmware (3.05) but Arch Linux as OS (Kernel 6.10.0-1-mainline). My adapter keeps disconnecting and reconnecting when I plug in a HDMI cable from one of my projectors and there will be no connection established. Same error (“GET_CABLE_PROPERTY failed (-5)”) for me, will try to fetch a longer log next time. I tried a basic Anker USB-C hub with a integrated HDMI port and that one works fine for me with that projector and same cables. Other laptops don’t got any problems with that projector and same cables, too.
What I can see is that the non-working projector is detected every few seconds in my system settings and then disappears right away. Will try to get a video from that, too.
Currently I have no clue why my other projector works totally fine and without any problems with the same Framework HDMI adapter (same port, no updates in between, …).
I now tried to reproduce the error and get some logs.
Hardware used:
Framework HDMI adapter (third gen)
Framework 13 DIY AMD 7840U (BIOS 3.05)
Arch Linux with Kernel 6.10.8-arch1-1
Projectors:
BenQ W2700 (direct HDMI connection, working with Framework adapter)
Optoma ZU607T (direct HDMI connection, not working with Framework adapter)
Macbook Air M1 (2022) for cross testing the Framework HDMI adapter (did not work with Optoma projector, too - same re-connects every few seconds)
I also tested a random mini USB-C dock with integrated HDMI-adapter from Anker, which works fine with my Framework Laptop and the Optoma projector using the same ports. There seem to be a problem with some combination of projector and Frameworks adapter but I’m not sure how to debug this any further. I will try to use a Ubuntu live image but this take some days.
There are some hdmi options in that projector’s input settings to change EDID version, turn on CEC, set a hdmi port to be an output, etc. Do changing any of these effect the issue?
It appears that this issue has disappeared after subsequent updates. I no longer experience any connection problems with the HDMI module or with the USB-C module via my Anker PowerExpand dock.
Thanks for continuing to research the problem, even when I lost track of the issue.
I just noticed that using a Ubuntu 24.04 live image my HDMI works fine using the same adapter and same projector. When I boot my Arch Linux it does not work. Now I can at least exclude a hardware problem. Will do some more tests in the next weeks, maybe I can find the piece of software which is not working (any more).
Ubuntu worked using Linux 6.8.0-41-generic, my Arch Linux using 6.11.2-arch1-1 does not work. I will try to use some older kernels using Arch soon to eliminate other software packages
Update: This success seems to be a onetime experience I cannot get it working anymore using a Ubuntu Live image. I will open a support ticket now and reference this topic here.
This is how it looks without touching a cable or the HDMI adapter at all:
The HDMI adapter started working again after I unpluged every extension module except HDMI and a type-C. It works fine. So I thought, I will plug them back one by one to find the faulty one. The above error showed up again after I pluged in USB-A module, but the HDMI still works fine. Then, I pluged in two more type-C and one SD card module, so I have all six populated, HDMI still works – in other words, I can no longer reproduce the problem…
I’m in contact with Framework support and we’re testing a lot of different things. We already found a workaround: When I avoid using the Framework HDMI adapter and use the DisplayPort adapter instead (and then a cheap random DP->HDMI adapter) my projector works fine using the same cables.
Another interesting finding: using a 1st gen HDMI expansion card solves the connection problem with that Optoma ZU607T projector. Using a 3rd gen HDMI expansion card connected to the same devices and using the same cables does not work.
No final result yet but we’re getting closer to a solution At least there are two workarounds now available.