Stop an HDMI monitor waking and blanking over and over while the session is locked
The cause and the AMD branch hold. shell/plugins/lock/Service.qml on 4.0.4-1 has idleBlankTimer at 5000 ms running omarchy-brightness-keyboard off and omarchy-brightness-display off. Issues #13812 and #8863 (both open) give the log pairs, the pointer-enter wake path, the HDMI audio SW_VIDEOOUT_INSERT path and the 4,182 transitions figure. PRs #8896, #10343 and #13129 are all open. modinfo on 7.2.5-3-omarchy lists hdmi_hpd_debounce_delay_ms. amdgpu_dm_connector.c reads it at connector init and clamps it to AMDGPU_DM_MAX_HDMI_HPD_DEBOUNCE_MS, 5000, so the reboot and the stated maximum are right. omarchy_hooks.conf contains modconf and kms. The defect is the mitigation for other GPUs. omarchy toggle idle stay-awake only writes ~/.local/state/omarchy/indicators/stay-awake, which the idle service reads to cancel the idle cycle. beginLock() in the lock service arms the 5 s blank on every lock, with no stay-awake check and no lock-only path in 4.0.4-1. So a lock started by hand, or before suspend, still blanks and loops. The record presents the toggle as stopping the lock from blanking. Rewritten to say what it covers. Not exercised: no lock was triggered here.
The initramfs rebuild writes the UKI to the ESP. Run df -h /boot first, because a full ESP produces a truncated image that does not boot. omarchy toggle idle stay-awake turns off automatic locking, so an unattended machine stays unlocked until you lock it by hand.
Symptom
While the session is locked, the display keeps turning on and off. Each time it comes back it shows the password field for a few seconds, then goes dark again, and this repeats for as long as the machine stays locked, all night if you let it. One reporter counted 4,182 display sleep transitions in a single day. The Hyprland log ($XDG_RUNTIME_DIR/hypr/*/hyprland.log) has pairs like this, over and over:
drm: Connector HDMI-A-1 disconnected
ERR from aquamarine ]: drm: Cannot commit a disconnected output
drm: HDMI-A-1 is not connected, clearing stale crtc 67
drm: Connector HDMI-A-1 connected
drm: Modesetting HDMI-A-1 with 3840x2160@60.00Hz
Mostly reported on AMD (APUs and discrete Radeon) with HDMI monitors. GTK4 apps may crash during the loop (see gtk4-apps-crash-on-monitor-hotplug).
Cause
Five seconds after the session locks, Omarchy's lock blanks the screens with omarchy-brightness-display off (DPMS off). Many HDMI monitors drop their hotplug-detect (HPD) line when they go into standby, then raise it again a few seconds later. The kernel reports that as a disconnect and a reconnect. Hyprland removes the output and adds it back with DPMS on, the lock surface is rebuilt for the new output, and the pointer entering that surface counts as activity. The lock wakes, re-arms its 5-second blank, and the loop starts again. On some AMD machines the HDMI audio codec's SW_VIDEOOUT_INSERT switch events also count as activity. The Omarchy-side fixes (PRs #8896, #10343 and #13129) are open and not in 4.0.4. amdgpu has an HDMI HPD filter that is off by default. When it is on, a disconnect followed by the same EDID returning within the window never reaches the compositor. The parameter hdmi_hpd_debounce_delay_ms was confirmed with modinfo on kernel 7.2.5-3-omarchy.
Fix
**AMD graphics with an HDMI monitor: turn on amdgpu's HPD debounce.**
modinfo -p amdgpu | grep hdmi_hpd # must list hdmi_hpd_debounce_delay_ms
echo 'options amdgpu hdmi_hpd_debounce_delay_ms=1500' | sudo tee /etc/modprobe.d/amdgpu-hdmi-hpd.conf
amdgpu is loaded from the initramfs (the kms and modconf hooks), and the parameter is read only when the module sets up its connectors, so rebuild and reboot:
- **Omarchy 4:**
sudo limine-mkinitcpio && sudo reboot - **Plain Arch:**
sudo mkinitcpio -P && sudo reboot
1500 ms is the value AMD and the Omarchy PR chose (the kernel caps it at 5000). The filter covers HDMI only, not DisplayPort.
**Any other GPU, or a DisplayPort monitor:** there is no packaged fix yet. The mitigation reporters use is to stop the session locking on idle:
omarchy toggle idle stay-awake
That turns off automatic locking and screen-off. It does not change what happens after a lock you start yourself: Omarchy's lock blanks the screens 5 seconds after any lock, so a manual lock on an affected monitor still loops. Until upstream fixes it, leave the machine unlocked only where that is safe, or power the monitor off by its own button while locked. Undo the toggle with omarchy toggle idle allow-idle. One reporter instead pins the connector's EDID and forces the connector on, so the kernel never sees the monitor leave. See the record edid-override-for-bad-or-missing-monitor-edid for that mechanism, which breaks hot-swapping on that port.
Verify
After the reboot, cat /sys/module/amdgpu/parameters/hdmi_hpd_debounce_delay_ms prints 1500. Lock the session and leave it for two minutes. The screen stays dark, and grep -c 'disconnected' "$XDG_RUNTIME_DIR"/hypr/*/hyprland.log does not grow while you wait.
Sources
- https://github.com/omacom/omarchy/issues/13812
- https://github.com/omacom/omarchy/issues/8863
- https://github.com/omacom/omarchy/pull/13129
- https://github.com/omacom/omarchy/pull/8896
- https://github.com/omacom/omarchy/pull/10343
- https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c
- https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c