Hi Folks! I’ve got a question about the L1 KVMs and use with dp-alt over usb-c on linux.
The target setup is the following:
Minisforum UM790Pro → usb-c dp-alt (or usb-c to display adaptor to DP) → L1 KVM → samsung odyssey G9 neo
Everything suggests this chain should be capable of the full 5120x1440 at 240Hz but I can not for the life of me get this to yield anything but a blank screen.
I’ve read many things, reviewed all the L1 KVM forum posts, and gone through every resource I could find and have just been hitting the most baffling wall. I’d like to describe the scenarios that work and describe what doesn’t and would be so grateful for guidance in how to troubleshoot.
The pieces of the setup are the following:
- Quad host dual monitor DP 1.4 L1 KVM
- Samsung Odyssey G9 Neo (firmware up-to date as of Oct. 19 2023 1015.0)
- Minisforum UM790Pro (BIOS up-to date as of Oct. 19 2023 1.07)
- OS: Fedora 38 Sericea (Silverblue sway spin, kernel 6.5.7)
- Club3d 6ft DP1.4++ cable
- one of the following:
- Club3d usb-c DP1.4 bidirectional cable
- Club3d usb-c to DP 1.4 adaptor
- Anker 556 USB4 hub with DP output
- monoprice bidirectional usb-c to DP 1.4 cable
Here are the different setups i’ve tried and their outcomes:
- UM790 → Anker hub → DP 1.4 → L1 KVM → G9 Neo
- max output 5120x1440 @ 120Hz
- UM790 → club 3d usb-c to DP adaptor → DP 1.4 → L1 KVM → G9 Neo
- black screen, but querying sway for available outputs correctly lists DP with up to 5120x1440@240Hz
- UM790 → club 3d bidirectional usb-c to DP → L1 KVM → G9 Neo
- black screen, but querying sway for available outputs correctly lists DP with up to 5120x1440@240Hz
- UM790 → club 3d bidirectional usb-c to DP → G9 Neo
- solid 5120x1440@240Hz connection
Now the whackier thing that I came across that is adding to my confusion is that if I start with an HDMI cable plugged in to the UM790 and put the G9 into PIP mode, the usb-c DP connection via the L1 KVM works perfectly well! To boot, if i then turn off the PIP mode, and use the already active usb-c DP connection, then the system works, albeit at 2560x1440@120Hz. If i then switch the output to be 5120x1440@any freq. the connection fails back to just a black screen.
It happened exactly once that following the PIP → to single output → correct display settings succeeded at giving me a stable connections at the max resolution and frequency, but it then failed once I changed the connection and I could never get it to replicate.
It almost seems as though the computer is failing to allocate the correct bandwidth to the cable but I’m not sure if thats how that works and at this point I my efforts feel more like divination than actual troubleshooting. I’d be immensely grateful for any input on possible ways to troubleshoot this further, or what I could look for, or try. While I’ve been using linux as my daily driver and am pretty comfortable with the commandline, I’m not sure what to look for in dmesg, journalctl, or other logging utilities for hints as to the issue.
I’ve tried journalctl -k and dmesg -k at different log levels but none of the messages seem to be related to the display (though im pretty unsure as to what i’m even looking for). I’ve also queried lsusb for the usb-c dp-alt cables and as far as I can tell, they report correctly but even that i’m not totally sure I understand how to interpret what I’m seeing.
If anyone has any thoughts on next steps I could try, whether configurations, or system commands to query for states or logs I would really appreciate any kind of input
Addendum:
- UM790 → club 3d bidirectional usb-c to DP → L1 KVM → G9 Neo
- This actually now works if I force the resolution to [email protected]. Curiously though, additional frequencies listed are
60.001Hz
72.010Hz
96.020Hz
120.001Hz
239.761Hz
But selecting anything else 60.001 and above) results in a black screen with the system struggling. I’ve tried with both adaptive sync on and off. Confusing…
- This actually now works if I force the resolution to [email protected]. Curiously though, additional frequencies listed are