OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors medium common DISPUTE

Find out why a USB-C dock or MST hub hides your monitor's high refresh rate

omarchyarchendeavouroscachyoshyprlandwaylandintelamdlaptopdock
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Read i915 16640, 17207 and 17228 and omarchy 13119. All four are open as of 2026-10-05. The lane counts, port_clock=810000, lane_count=2, compressed-bpp:16.0000, the 1056.75 MHz 240 Hz timing, the 17207 direct-cable result and the 17228 CLOCK_HIGH pruning of 144/165/180 Hz all match. Two specifics are not supported. The symptom says the dock path tops out at 100 or 120 Hz, but 16640 exposes 144 Hz for its 240 Hz panel, and nothing cited shows a 60 Hz only case. The cause says Windows uses 8 bpp, but no source reports what Windows picks: 16640's reporter calculated that 8 bpp would fit and observed Windows running 240 Hz. omarchy 13119 is a different bug (a 7.2.5 amdgpu MST regression) and supports only the 2-lane dock negotiation it is cited for. The fix commands were checked for shape only: amdgpu debugfs link_settings exists in amdgpu_dm_debugfs.c and its Current: 4 0x1e 16 format is shown in drm/amd 5033. The debugfs reads were not run here because they need root. Symptom and cause rewritten, fix kept.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

My 3440x1440 165 Hz (or 2560x1440 240 Hz) monitor runs at full rate plugged straight into the laptop, but through my USB-C dock or MST hub hyprctl monitors all tops out lower: 100 Hz for the 3440x1440 165 Hz panel in i915 17207, 120 Hz for a 3440x1440 panel in i915 17228, and 144 Hz for the 2560x1440 240 Hz panel in i915 16640. Windows on the same dock and cable does the full rate. Editing the mode line does nothing, because the fast mode is not in availableModes at all.

Cause

The kernel removes the mode before Hyprland ever sees it, and two limits stack on a dock path.

  1. **Two lanes.** Many USB-C docks and hubs that also carry USB 3 data run DisplayPort Alt Mode on two of the four high-speed lanes. Two HBR3 lanes carry about 12.96 Gbps of payload, half of a direct 4-lane link. The Lenovo dock in omarchy 13119 and the hub in i915 16640 both negotiate 2 lanes.
  1. **Conservative DSC behind MST.** The mode must then fit after Display Stream Compression, and the Intel driver reports a compressed rate of 16 bits per pixel in i915_display_info. In i915 16640 (Raptor Lake) 2560x1440@240 needs about 1056.75 MHz × 16 bpp, roughly 16.9 Gbps, which exceeds the 2-lane budget, so the mode is pruned. The reporter calculates that it would fit at 8 bpp, and the same laptop, hub and monitor run 240 Hz on Windows. i915 17207 (Meteor Lake, Lenovo 40AY dock) shows port_clock=810000, lane_count=2 and compressed-bpp:16.0000 with 3440x1440@165 missing, while a direct USB-C to DP cable offers it. i915 17228 (Tiger Lake, Dell WD19) logs the 144, 165 and 180 Hz modes as pruned with CLOCK_HIGH. All three are open as of 2026-10-05.

The Omarchy record monitor-stuck-at-60hz-high-refresh covers the general case of a missing mode. This record is the dock and MST case, where the cable is fine and the same monitor works direct.

Fix

**1. Confirm the mode is missing, not misconfigured:**


hyprctl monitors all -j | jq -r '.[] | .name, (.availableModes | join(" "))'

If the fast rate is listed, this is not your record. Go to monitor-stuck-at-60hz-high-refresh.

**2. Read the link the dock negotiated** (root needed):

Intel (i915 or xe):


sudo sh -c 'grep -E "port_clock|lane_count|dsc-dss|compressed-bpp" /sys/kernel/debug/dri/*/i915_display_info'

AMD:


journalctl -k -b | grep 'DM_MST'          # e.g. "DM_MST: DP14, 2-lane link detected"
sudo sh -c 'for f in /sys/kernel/debug/dri/*/DP-*/link_settings; do echo "== $f"; cat "$f"; done'

In link_settings the first number after Current: is the lane count and the second is the link rate code (0x14 is 5.4 Gbps per lane, 0x1e is 8.1 Gbps per lane).

**3. Pick a remedy.** No monitor rule can bring back a mode the kernel pruned.

  • Connect the monitor directly with a USB-C to DisplayPort cable. That uses all four lanes, and it is how the i915 17207 reporter got 165 Hz on the same laptop.
  • Put fewer monitors on the hub. MST splits one link's bandwidth across every display behind it.
  • Run the highest rate the dock does offer, copied verbatim from availableModes, in ~/.config/hypr/monitors.lua:

hl.monitor({ output = "desc:<description from hyprctl monitors>", mode = "3440x1440@99.98", position = "auto", scale = 1 })

On Intel, follow i915 16640 and 17207 for a driver change to the compressed bpp choice.

Verify

On a direct cable the fast rate appears in availableModes and hyprctl monitors runs it. On the dock, the pinned rate holds after a replug.

Sources

mst-dock-high-refresh-mode-pruned-dsc