Laptop 16 HDMI expansion module not working

Hi all,

I’m on a Framework Laptop 16 (AMD 7840HS) running Ubuntu 24.04.2 and I’m struggling to get the HDMI expansion card working.

The HDMI expansion card is FRACCHBZ01-3 (3rd Gen)

I’ve been trying to connect to my Samsung TV through HDMI.

What I’ve tried:

  • Plugging the HDMI card into expansion slots 1, 2, and 4 which are documented here as supporting external displays
  • plugging it in with the HDMI cable already connected, and with the HDMI cable not connected
  • Turning it off and on again :slight_smile:
  • A 3rd party USB-C to HDMI adapter in the same ports – this works!

Observable symptoms:

When the cable is connected to the TV, the HDMI card appears to disconnect from USB after 3-4 seconds, then it comes back, and the whole disconnect/reconnect loop goes on forever. Here’s an example of 2 cycles from /var/log/syslog:

2025-05-24T13:11:00.519474-04:00 jframework kernel: ucsi_acpi USBC000:00: unknown error 0
2025-05-24T13:11:00.519501-04:00 jframework kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
2025-05-24T13:11:01.368063-04:00 jframework boltd[1502]: probing: timeout, done: [2995902] (2000000)
2025-05-24T13:11:01.581502-04:00 jframework kernel: usb 5-1: new full-speed USB device number 4 using xhci_hcd
2025-05-24T13:11:01.742447-04:00 jframework kernel: usb 5-1: New USB device found, idVendor=32ac, idProduct=0002, bcdDevice= 0.00
2025-05-24T13:11:01.742468-04:00 jframework kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-05-24T13:11:01.742470-04:00 jframework kernel: usb 5-1: Product: HDMI Expansion Card
2025-05-24T13:11:01.742472-04:00 jframework kernel: usb 5-1: Manufacturer: Framework
2025-05-24T13:11:01.742474-04:00 jframework kernel: usb 5-1: SerialNumber: 11AD1D00D7CE40161E260B00
2025-05-24T13:11:01.814488-04:00 jframework kernel: hid-generic 0003:32AC:0002.008C: hiddev0,hidraw2: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c3:00.3-1/input1
2025-05-24T13:11:01.819132-04:00 jframework mtp-probe: checking bus 5, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1"
2025-05-24T13:11:01.819243-04:00 jframework mtp-probe: bus: 5, device: 4 was not an MTP device
2025-05-24T13:11:01.820646-04:00 jframework boltd[1502]: probing: started [1000]
2025-05-24T13:11:01.833576-04:00 jframework mtp-probe: checking bus 5, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1"
2025-05-24T13:11:01.833635-04:00 jframework mtp-probe: bus: 5, device: 4 was not an MTP device
2025-05-24T13:11:02.551419-04:00 jframework kernel: usb 5-1: USB disconnect, device number 4
2025-05-24T13:11:03.974557-04:00 jframework kernel: ucsi_acpi USBC000:00: unknown error 0
2025-05-24T13:11:03.974580-04:00 jframework kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
2025-05-24T13:11:04.001032-04:00 jframework systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
2025-05-24T13:11:04.026931-04:00 jframework systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
2025-05-24T13:11:04.027160-04:00 jframework systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
2025-05-24T13:11:04.823592-04:00 jframework boltd[1502]: probing: timeout, done: [2994430] (2000000)
2025-05-24T13:11:05.045475-04:00 jframework kernel: usb 5-1: new full-speed USB device number 5 using xhci_hcd
2025-05-24T13:11:05.206454-04:00 jframework kernel: usb 5-1: New USB device found, idVendor=32ac, idProduct=0002, bcdDevice= 0.00
2025-05-24T13:11:05.206470-04:00 jframework kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-05-24T13:11:05.206471-04:00 jframework kernel: usb 5-1: Product: HDMI Expansion Card
2025-05-24T13:11:05.206473-04:00 jframework kernel: usb 5-1: Manufacturer: Framework
2025-05-24T13:11:05.206473-04:00 jframework kernel: usb 5-1: SerialNumber: 11AD1D00D7CE40161E260B00
2025-05-24T13:11:05.276475-04:00 jframework kernel: hid-generic 0003:32AC:0002.008D: hiddev0,hidraw2: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c3:00.3-1/input1
2025-05-24T13:11:05.281094-04:00 jframework mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1"
2025-05-24T13:11:05.281903-04:00 jframework mtp-probe: bus: 5, device: 5 was not an MTP device
2025-05-24T13:11:05.283685-04:00 jframework boltd[1502]: probing: started [1000]
2025-05-24T13:11:05.294863-04:00 jframework mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1"
2025-05-24T13:11:05.294936-04:00 jframework mtp-probe: bus: 5, device: 5 was not an MTP device
2025-05-24T13:11:06.012445-04:00 jframework kernel: usb 5-1: USB disconnect, device number 5

This appears to be the same issue as described in this thread from 2023. That thread didn’t come to a final resolution.

Has anyone else run into this? Any solutions?

1 Like

Just a note from the guy who started the other thread. I’m using external USB-C to HDMI adapters for a while now, without problems. The internal HDMI cards simply do not work in most of the setups at my work. Checked that yesterday again: HDMI card does not work, external adapter works.

1 Like

I’m experiencing the same issue as of this evening. The HDMI adapter has worked for over a year until today–and it still works on my Framework 13. Any chance you found a resolution?

Turns out port 4 isn’t working but port 1 is.

Does anyone have a solid fix for this? On my Laptop 16 the HDMI module was working, but now isn’t. I have a USB C to hdmi and this won’t work either…

Thanks,

Dave

So after some testing, the hdmi module only works in the port closest to the screen on either side…

Is that intentional?

Thanks,

Dave

Yes, only three of the six ports can output video. See this reference for the full story on port compatibility: Expansion Card Slot functionality on Framework Laptop 16 (AMD Ryzen™ 7040 Series)

My issue was/is that the HDMI adapter doesn’t work on several displays I own. I did find an older 1080p display that it works with, so I’m guessing it’s a compatibility issue and the adapter itself isn’t completely broken.