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

Get DisplayLink dock monitors redetected after a replug

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

The problem and root cause are well sourced: hyprwm/Hyprland#14538 ('DRM devices from evdi (DisplayLink) not re-detected after dock reconnect without full compositor restart') and #7292 both exist, and uwsm stop is the documented Arch/Omarchy logout. But two of the diagnostic/fix commands are simply wrong. The AUR displaylink package installs /usr/lib/systemd/system/displaylink.service. There is no displaylink-driver.service, so both systemctl status displaylink-driver.service and sudo systemctl enable --now displaylink-driver.service fail outright (that unit name is the Ubuntu vendor installer's, not Arch's). Separately, ls -la /proc/$(pgrep -x Hyprland)/fd | grep -i evdi can never match: those fds are symlinks to /dev/dri/cardN, and the string 'evdi' appears nowhere in the listing, so the check reports the bug for everyone including healthy systems.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

Boot with the DisplayLink dock attached and all screens work. Unplug the dock, plug it back in, and hyprctl monitors shows only the laptop display. The kernel is happy. evdi: [I] (card3) Connector state: connected and /dev/dri/card2..card5 all exist, but Hyprland ignores them. hyprctl reload, hyprctl dispatch dpms off/on and explicit desc: monitor rules all do nothing.

Cause

Hyprland/aquamarine enumerate DRM devices once at startup and do not rescan for DRM *devices* (as opposed to connectors) that appear at runtime. When a DisplayLink dock is replugged, evdi creates brand-new card nodes. Hyprland never opens them, and ls -la /proc/$(pgrep Hyprland)/fd | grep -i evdi is empty.

Fix

There is no runtime fix in the compositor today. Practical options:

  1. Restart the session with the dock already attached:

uwsm stop        # Omarchy / Arch with uwsm; then log back in
  1. Confirm the driver side is actually healthy before blaming it. The Arch AUR displaylink package's unit is displaylink.service (there is no displaylink-driver.service on Arch: that name comes from the vendor's Ubuntu installer):

systemctl status displaylink.service
lsmod | grep evdi
ls /dev/dri/

Compare the card nodes evdi created against the ones Hyprland actually holds open. The fds are symlinks to /dev/dri/cardN, so match the numbers by hand:


ls -l /sys/class/drm/*/device/driver | grep evdi   # which cardN are evdi's
ls -l /proc/$(pgrep -x Hyprland)/fd | grep /dev/dri  # which cardN Hyprland opened

An evdi card that never appears in the second list is one Hyprland never opened.

  1. Have the driver running before login so the card nodes exist when Hyprland starts:

sudo systemctl enable --now displaylink.service

This is necessary but not sufficient: the dock must also be attached before the session starts, since Hyprland enumerates DRM devices once.

  1. If you dock and undock all day, prefer a DisplayPort-Alt-Mode/Thunderbolt dock over a DisplayLink one, because those drive real connectors on your GPU and are hotplugged normally.

Verify

After re-login with the dock attached, hyprctl monitors | grep ^Monitor lists every panel, and ls -la /proc/$(pgrep -x Hyprland)/fd | grep -c evdi is non-zero.

Sources

displaylink-dock-monitors-not-redetected