@Nils The thing is, the OS doesn’t let me change the resolution, the screen is not even shown in display settings 
@NM64 Shall I try using X11 instead of wayland then ?
I’d say just try it in a live session of a distro that definitely uses X11, such as Linux Mint (protip: Ventoy is your friend for booting ISOs).
One fun thing about Linux Mint is, even in a live session, you can still log out and log back in without actually rebooting which should in theory allow the use of an xorg.conf file if that’s something you want to fiddle with.
nevermind, it was working only with the live version… How weird
Kinda sounds to me like it’s the monitor not the laptop or cable. I have a LG that I connect DP (USB-C), different model than yours, that can be really finicky.
Time to narrow this down. Connect to the monitor with no other power supply and no devices attached to the monitors usb hub. If that works, start adding usb devices to the monitor and see what happens. Do the same with your framework power supply also connected to your laptop.
Also, if you have a friendly computer shop nearby maybe you could try your desired setup with a different monitor. Definitely a pain to drag your stuff to a shop but it would answer certain questions. Especially given that’s an expensive monitor.
Weird about wayland/X11, different kernel in the live image?
Edited to add: Don’t think will have any effect but remove the usb module and connect directly to the laptop carefully and gently. The module is just a couple of connectors and a wire, but it sounds like this is driving you crazy so try everything…
@John_Jacobs I tried all of that sadly… And I also tried on other monitors on which it works great. I really think the monitor is the problem, it already had some weird behavior with my mac previously.
It’s kinda working with linux mint and xorg, but as I plug or unplug an other usb device, it’s suddenly christmas and everything starts to blink.
I’ve rolled back to good ol HDMI but without my shared keyboard and mouse
thanks to all of you for the help either way 
1 Like
Does HDMI 2.0 even have enough bandwidth to drive that monitor at 144Hz? I think it’d only just have enough bandwidth to do it at 120Hz, but only at 8bit rather than 10bit, and presumably without AdaptiveSync as well (if that even works on xorg of course).
Or do you have one of those rare DisplayPort to HDMI 2.1 adapters? (though in that case I’d wonder why you wouldn’t just be using DisplayPort directly…)
Haha no I don’t, it runs at 70hz but I will order a display port module later maybe.
It’s my work computer so I don’t really need this refresh rate for cloud, code and devops tasks. Furthermore, I found that GUI doesn’t benefit high refresh rates on linux, most of the time I see an awful tearing when draging windows on the screen, even in 144hz.
It’s a good monitor for gaming / working tho
Piggybacking on this post because I also had issues with a USB-C hub monitor and Fedora 36. In my case, the laptop saw the monitor, but the monitor reported no signal 
.
I switched to Xorg and it’s working now - Framework is in clamshell mode connected via USB-C to a 32" 4k screen daisy chained to a portrait orientation 22" 1080p. I also have a work-issued desktop connected via DP, and they share keyboard and mouse (wireless via a USB dongle) as well as webcam. I’ve been able to switch back and forth and everything seems to be working as expected.
2 Likes
This sounds a bit like the issue I’m having with my 12th gen laptop on Fedora 36. In particular, I couldn’t get the DisplayPort to work on my Dell TB16 thunderbolt dock even though it worked on an 11th gen Framework laptop I tried. Thankfully, I had a spare USB-C to DisplayPort cable and that seemed to work with the Thunderbolt port on the Dell TB16 dock.
Up: I still have the error on either xorg or wayland. Pluging a thunderbolt cable make the charging led blink on the laptop like if it doesn’t know if it’s for charging or a USB hub
1 Like
I’m not quite sure if this problem has anything to do with the monitor. I have the same problem with the connecting/disconnecting cycle with my thunderbolt 4 docking station even when no other device is attached to the dock.
UP: So after a while, I decided to try again with a new thunderbolt 4 cable and I still have the problem. I will contact the support about this and let you know.
Direct connections “should” work, however, we always recommend using HDMI or DP as the gold standard.
As always:
- Docks are community support only as we cannot duplicate all the docks out there.
- Direct connections to HDMI, DP are recommended to the HDMI, DP expansion cards.
Hey ! Yeah it has been a long time and this issue is still bothering me ! But this time, dmesg is a bit more clearer:
[ 1009.750537] hub 3-5:1.0: USB hub found
[ 1009.750637] hub 3-5:1.0: 4 ports detected
[ 1009.764938] usb 3-5: USB disconnect, device number 17
[ 1010.494872] usb 3-5: new high-speed USB device number 18 using xhci_hcd
[ 1011.473744] usb 3-5: new high-speed USB device number 19 using xhci_hcd
[ 1011.651823] usb 3-5: Device not responding to setup address.
[ 1011.853940] usb 3-5: Device not responding to setup address.
[ 1012.061765] usb 3-5: device not accepting address 19, error -71
[ 1012.062070] usb usb3-port5: attempt power cycle
[ 1012.921697] usb 3-5: new high-speed USB device number 20 using xhci_hcd
[ 1012.921819] usb 3-5: Device not responding to setup address.
[ 1013.125677] usb 3-5: Device not responding to setup address.
[ 1013.333633] usb 3-5: device not accepting address 20, error -71
[ 1013.921903] usb 3-5: new high-speed USB device number 21 using xhci_hcd
[ 1013.934673] usb 3-5: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
[ 1013.934697] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 1013.934705] usb 3-5: SerialNumber: E80000816081
[ 1013.937575] hub 3-5:1.0: USB hub found
[ 1013.937684] hub 3-5:1.0: 4 ports detected
[ 1014.033753] usb 3-5: USB disconnect, device number 21
[ 1015.032910] usb 3-5: new high-speed USB device number 22 using xhci_hcd
[ 1016.010421] usb 3-5: new high-speed USB device number 23 using xhci_hcd
[ 1016.187092] usb 3-5: Device not responding to setup address.
[ 1016.390124] usb 3-5: Device not responding to setup address.
[ 1016.597910] usb 3-5: device not accepting address 23, error -71
[ 1016.598254] usb usb3-port5: attempt power cycle
[ 1019.593831] usb 3-4: new high-speed USB device number 25 using xhci_hcd
[ 1020.919951] usb 3-4: new high-speed USB device number 26 using xhci_hcd
[ 1021.929762] usb 3-4: device descriptor read/64, error -71
[ 1022.834077] usb 3-4: device descriptor read/64, error -71
[ 1023.737951] usb 3-4: new high-speed USB device number 27 using xhci_hcd
[ 1023.926435] usb 3-4: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
[ 1023.926465] usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 1023.926478] usb 3-4: SerialNumber: E80000816081
[ 1023.931618] hub 3-4:1.0: USB hub found
[ 1023.931662] hub 3-4:1.0: 4 ports detected
[ 1023.943251] usb 3-4: USB disconnect, device number 27
[ 1025.357865] usb 3-4: new high-speed USB device number 29 using xhci_hcd
[ 1038.058077] usb 3-5: new high-speed USB device number 30 using xhci_hcd
[ 1038.246646] usb 3-5: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
[ 1038.246656] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 1038.246660] usb 3-5: SerialNumber: E80000816081
[ 1038.248812] hub 3-5:1.0: USB hub found
[ 1038.248866] hub 3-5:1.0: 4 ports detected
[ 1038.281265] usb 3-5: USB disconnect, device number 30
[ 1039.585979] usb 3-5: new high-speed USB device number 31 using xhci_hcd
[ 1040.594147] usb 3-5: device descriptor read/64, error -71
So we can see multiple errors:
Device not responding to setup address.
device not accepting address 23, error -71
device descriptor read/64, error -71
I have yet to find what this error code means, anyone have a wild guess ?
Cheers,
Louis
Hi Louis,
Looking at error -71 specifically, while kinda generic, tells me it is experiencing communication issues. By the book, usually means incompatibility or bad connection. Usually the former - the dock.
Hi Matt, thanks for your response !
Well, it’s directly connected to my screen with a thunderbolt cable, which is a 38WN95C.
Perhaps the screen hosts a kind of « dock » that is not compatible then ?
Thanks,
Louis