Wake a USB4 monitor that stays dark on hotplug by setting a lower mode first
Read drm/amd 5011 in full (open): Framework 13 Ryzen AI 300 (Strix Point), BenQ RD320UA, DM_MST: DP14, 2-lane link detected, 12.96 versus 14.25 Gbps, ENOSPC on every commit, and 4K@30 then a 3-second wait then 4K@60 succeeds with eDP-1 at 2880x1920@120. Three statements go beyond it. The symptom presents Hyprland behaviour (0x0 in hyprctl, a Hyprland log line) as observed, but the report is GNOME only, where Mutter logged Page flip failed: drmModeAtomicCommit: No space left on device. The cause states as fact that the driver neither waits nor retries, which is the reporter's analysis under a heading that says 'appears'. And the fix claims hyprctl keyword does nothing under a Lua config, which no source here supports: the Lua-era hyprctl wiki page documents eval and dispatch and is silent on keyword, and hyprctl --help on 0.56.2 still lists keyword. Confirmed on this machine: hyprctl eval exists on 0.56.2, the Hyprland wiki documents the hl.monitor fields used, o.bind in /usr/share/omarchy/default/hypr/helpers.lua wraps a string in hl.dsp.exec_cmd, and SUPER + CTRL + ALT + M is not bound by any Omarchy default. Nothing was exercised on USB4 hardware, and hyprctl eval was not run.
Symptom
AMD Ryzen AI 300 (Strix Point) laptop with USB4, a Framework Laptop 13 in the report. Plug a 4K monitor into the USB4 port: it is detected, the EDID is read and modes are listed, but the screen never lights. Windows lights the same monitor at 4K@60 immediately. The report was made under GNOME, where Mutter logged Page flip failed: drmModeAtomicCommit: No space left on device over a thousand times. Under Hyprland the same failure should show the output at 0x0 in hyprctl monitors all and failed commits ending in No space left on device in the Hyprland log, but no Hyprland report has confirmed that.
Cause
On hotplug the USB4 DisplayPort tunnel first comes up as a 2-lane DP 1.4 link, about 12.96 Gbps, and 3840x2160@60 at 8 bits needs about 14.25 Gbps, so the kernel's atomic check fails with ENOSPC. The kernel log shows DM_MST: DP14, 2-lane link detected. The bandwidth is there once the tunnel settles: in drm/amd 5011 (open) setting 4K@30 first, waiting 3 seconds and then switching to 4K@60 succeeds, with the laptop panel at 2880x1920@120 alongside. The reporter's reading is that the driver neither waits for the full tunnel allocation before the first modeset nor retries after it grows. That is an analysis in the report, not a confirmed driver diagnosis. The workaround was demonstrated under GNOME. On Hyprland the same two-step modeset is done with hyprctl eval, which the report did not test.
Fix
**1. Confirm the signature:**
journalctl -k -b | grep -E 'DM_MST: DP14, [0-9]-lane'
grep -c 'No space left on device' "$XDG_RUNTIME_DIR/hypr/$HYPRLAND_INSTANCE_SIGNATURE/hyprland.log"
hyprctl monitors all -j | jq -r '.[] | "\(.name) \(.width)x\(.height)"'
**2. Step the mode up by hand.** Replace DP-9 with the name from step 1. A rule set with eval lasts until the next config reload:
hyprctl eval 'hl.monitor({ output = "DP-9", mode = "3840x2160@30", position = "auto", scale = 1.5 })'
sleep 3
hyprctl eval 'hl.monitor({ output = "DP-9", mode = "3840x2160@60", position = "auto", scale = 1.5 })'
**3. Keep it one keypress away.** Save it as a script:
mkdir -p ~/.local/bin
cat > ~/.local/bin/usb4-monitor-kick <<'EOF'
#!/bin/bash
out="${1:-DP-9}"
hyprctl eval "hl.monitor({ output = \"$out\", mode = \"3840x2160@30\", position = \"auto\", scale = 1.5 })"
sleep 3
hyprctl eval "hl.monitor({ output = \"$out\", mode = \"3840x2160@60\", position = \"auto\", scale = 1.5 })"
EOF
chmod +x ~/.local/bin/usb4-monitor-kick
and bind it in ~/.config/hypr/bindings.lua:
o.bind("SUPER + CTRL + ALT + M", "Kick USB4 monitor", "~/.local/bin/usb4-monitor-kick DP-9")
Check the key combination is free first with omarchy menu keybindings --print.
**Plain Arch with a hyprlang config (Hyprland 0.54 or older):** hyprctl keyword monitor DP-9,3840x2160@30,auto,1.5, wait 3 seconds, then the same with @60. Omarchy 4 ships a Lua config, so use the hyprctl eval form above there.
Verify
hyprctl monitors shows the output at 3840x2160@60 and the monitor is lit. grep -c 'No space left on device' on the log stops growing.