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

Fix an external monitor that ignores the brightness slider while the OSD says it changed

omarchyomarchy-4hyprlandddcutildesktoplaptopamd
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The 4.0.4-1 helper still writes with ddcutil --skip-ddc-checks --noverify setvcp 10, and omarchy-brightness-display passes the helper's printed target straight to omarchy-osd, so the false OSD holds. Issue #8931 (open) has the LG UltraGear transcript quoted in the symptom, and its comment from the PA32QCV reporter has DDCRC_VERIFY on every path, the firmware-lock reading, the untested HDR note and cm = hdredid. PR #9876 is open and says it targets ddcutil 3.0.1+. archlinux.org reports ddcutil 3.0.2-1 in extra, and the stable-mirror.omarchy.org extra.db (last-modified 2026-09-08) still lists ddcutil-2.2.7-1, matching the record. ddcutil --help confirms the setvcp <code> [+|-] <value> relative syntax. o.bind with { locked = true } matches default/hypr/bindings/media.lua, and CTRL + XF86MonBrightnessUp/Down are not bound by default. Not exercised: no DDC write was made on this machine.

Symptom

The Display panel finds my external monitor and shows a brightness slider. Dragging it, or pressing the brightness keys with that monitor focused, moves the OSD, but the screen's brightness never changes. The helper even claims success:


$ omarchy-brightness-display --no-osd --monitor DP-1 70%
$ echo $?
0
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100

Reported with an LG UltraGear evo 27GM950B-B and an ASUS ProArt PA32QCV, both on amdgpu.

Cause

omarchy-brightness-display-ddc writes brightness on ddcutil's fast path, ddcutil --bus "$bus" --skip-ddc-checks --noverify setvcp 10 "$raw_target". Two kinds of monitor fail behind that one symptom. Some, the LG in the report, accept the fast-path write with no error but ignore it, while a normal ddcutil --bus 9 setvcp 10 70 with checks enabled works. Others, the ASUS, reject every write on every path with Verification failed for feature 10 / DDCRC_VERIFY, which points at a firmware lock. In both cases the MCCS Set VCP command carries no acknowledgement and --noverify turns off the read-back, so the helper exits 0 and omarchy-brightness-display hands the requested value to the OSD. The proposed fix, PR #9876, is open and depends on ddcutil 3.0.1 or later. Arch extra has ddcutil 3.0.2, but the Omarchy stable mirror still serves 2.2.7-1 as of 2026-10-04, and the 4.0.4-1 helper still uses the fast path.

Fix

**Find the monitor's bus and test both write paths:**


ddcutil detect --brief
# then, with the bus number it printed:
ddcutil --bus 9 --skip-ddc-checks --noverify setvcp 10 70
ddcutil --bus 9 getvcp 10 --brief      # unchanged means the fast path is ignored
ddcutil --bus 9 setvcp 10 70
ddcutil --bus 9 getvcp 10 --brief      # changed means the full-check path works

**If the full-check write works**, add your own bindings that use it. Put them in ~/.config/hypr/bindings.lua, on a modifier so the stock keys keep driving the laptop panel. ddcutil takes a relative change when + or - stands alone between spaces:


o.bind("CTRL + XF86MonBrightnessUp", "External brightness up", "ddcutil --bus 9 setvcp 10 + 10", { locked = true })
o.bind("CTRL + XF86MonBrightnessDown", "External brightness down", "ddcutil --bus 9 setvcp 10 - 10", { locked = true })

Saving the file reloads Hyprland. I2C bus numbers can change after a kernel update or a different port, so re-run ddcutil detect --brief if the binding stops working.

**If both writes fail with DDCRC_VERIFY**, the monitor refuses DDC/CI brightness writes and only its own OSD buttons will change it. Check that DDC/CI is turned on in the monitor's menu. One reporter's panel was in HDR mode (cm = "hdredid"), and whether HDR causes the refusal was not tested.

Verify

Press the new binding and run ddcutil --bus 9 getvcp 10 --brief. The current value moves by 10 each time and the screen visibly changes.

Sources

ddc-brightness-slider-moves-monitor-unchanged