Display Port module does not work

The monitor shows no signal. xrandr result is the same as if it is not plugged in:

xrandr
Screen 0: minimum 8 x 8, current 2256 x 1504, maximum 32767 x 32767
eDP1 connected primary 2256x1504+0+0 (normal left inverted right x axis y axis) 280mm x 190mm
   2256x1504     60.00*+
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
DP4 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

dmesg shows the following when the module is unplugged/replugged

[54001.582143] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[54001.799771] usb 3-3: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
[54001.799780] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[54001.799783] usb 3-3: Product: DisplayPort Expansion Card
[54001.799785] usb 3-3: Manufacturer: Framework
[54001.799788] usb 3-3: SerialNumber: 11AD1D004E6B2E0E273C0B00
[54001.841082] hid-generic 0003:32AC:0003.000A: hiddev96,hidraw2: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:00:14.0-3/input1
[54001.841118] usbcore: registered new interface driver usbhid
[54001.841119] usbhid: USB HID core driver

So it appears to be detected.

Any idea?

@Mathieu_Zhang did you ever resolve this? I ran into the same issue today. My Display Port has worked for months but it just wouldn’t go today and I saw the same behavior. I luckily had a spare DP Module and using that worked for me so not sure if the module itself just went bad.

Also having this same problem; acts as if nothing is plugged in.

Has this issue ever been resolved? Neither hdmi nor dp are picking up external monitors. I tried all the external card ports.

I’ve done some more troubleshooting here. I was usually able to get my DP card working by swapping between two. Both work…some of the time. Until today when I can’t get either to work on my original Framework or my new 12th Gen. When I run lsusb in Linux I don’t see it enumerate which is a problem. But when I’m finally able to get it to enumerate as soon as I connect my monitor dmesg shows a USB disconnect.

[  430.499071] usb 3-6: new full-speed USB device number 18 using xhci_hcd
[  430.659049] usb 3-6: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
[  430.659058] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  430.659061] usb 3-6: Product: DisplayPort Expansion Card
[  430.659063] usb 3-6: Manufacturer: Framework
[  430.659065] usb 3-6: SerialNumber: 11AD1D00C9D73E02220D0B00
[  430.672800] hid-generic 0003:32AC:0003.0010: hiddev0,hidraw2: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:00:14.0-6/input1
[  448.469527] usb 3-6: USB disconnect, device number 18

You can see the disconnect about 18 seconds after plugging in the DP card which is when I connected the monitor.

Then if I run dmesg a bit later it seems like it continues to try to enumerate but fails

403.371130] usb usb2-port4: attempt power cycle
[  407.526991] usb 3-6: new full-speed USB device number 17 using xhci_hcd
[  411.871216] usb usb2-port4: unable to enumerate USB device
[  430.499071] usb 3-6: new full-speed USB device number 18 using xhci_hcd
[  430.659049] usb 3-6: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
[  430.659058] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  430.659061] usb 3-6: Product: DisplayPort Expansion Card
[  430.659063] usb 3-6: Manufacturer: Framework
[  430.659065] usb 3-6: SerialNumber: 11AD1D00C9D73E02220D0B00
[  430.672800] hid-generic 0003:32AC:0003.0010: hiddev0,hidraw2: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:00:14.0-6/input1
[  448.469527] usb 3-6: USB disconnect, device number 18
[  677.345090] usb 3-6: new full-speed USB device number 25 using xhci_hcd
[  756.025923] usb usb2-port4: attempt power cycle
[  764.525912] usb usb2-port4: unable to enumerate USB device

Ok, finally got it to work again by connecting the monitor cable to the DP card before seating the card in the slot. While I was booted into PopOS I used the monitor cable to push the DP expansion card into place. It worked. I haven’t tested this more than once but it worked. Time to get back to work.

I have trouble hooking up a screen to displayport aswell. neither the Framework DP Expansion Card nor my Caldigit Thunderbolt 4 docking station work.

I’ve seen these messages:
[ 673.092908] hid-generic 0003:32AC:0003.0008: hiddev97,hidraw6: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:00:14.0-2/input1 [ 674.517400] thunderbolt 0000:00:0d.3: 3:13: DP tunnel activation failed, aborting

one thing which might or might not be relevant:
if i use the framework HDMI expansion card, plug that into the back of my thunderbolt dock and hook up the screen with HDMI, it works. so this is my current workaround (i’ll get a different dock, one that has built-in HDMI instead of displayport)

would still be great to be able to use the displayport extension though

For anyone that comes across this later I found that both of my Display Port expansion cards were the problem. They would intermittently work and sometimes not at all. I bought a USB C to Display port cable and it works 100% of the time. So at least in my case the issue was bad Display Port expansion cards.

1 Like

Sorry for the necrobump.

I had a similar problem where my DP card stopped working out of the blue, although I had been driving it without problem so far.
Recently did a firmware upgrade from build 5 to build 101 and the card is working again.

An important note is that I left the DP lying around for around a month before coming back to it, and I did not test it immediately before doing the firmware update, so it is not a guarantee that the firmware update helped.
Might have been a problem on the kernel / driver side which was fixed later on (currently running Arch linux-clear 6.3.5-1 on i7 1260P).
Or the card just started working again after “cooling down” or something like that ?

In any case, might be worth a try.
Best regards