Make brightness keys control an external monitor over DDC/CI
Read /usr/share/omarchy/bin/omarchy-brightness-display-ddc and omarchy-brightness-display on this machine: the ddcutil detect bus mapping, VCP 0x10, the 60-second unavailable cache under $XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/ and the silent exit 1 all match. PR 6490 'Support external monitor brightness in Quattro' merged 2026-08-01 into quattro. Migration 1785608251.sh runs omarchy-pkg-add ddcutil. 'FIXED BRIGHTNESS' is in shell/plugins/panels/monitor/Panel.qml. omarchy 14005 is open and matches the MST description exactly. ddcutil.com/nvidia gives the same options nvidia NVreg_RegistryDwords=RMUseSwI2c=0x01;RMI2cSpeed=100 line and the /proc check. /etc/mkinitcpio.conf.d here has modconf in HOOKS and the nvidia modules in MODULES, so the UKI rebuild with limine-mkinitcpio is the right step. One misattribution: /usr/lib/modules-load.d/ddcutil.conf (i2c-dev) and the udev rule are owned by the ddcutil 2.2.7-1 package (pacman -Qo), not by Omarchy, so plain Arch with ddcutil gets them too. The cause is corrected for that. The fix holds as written. Not exercised: no ddcutil command or module load was run.
The NVIDIA RegistryDwords option is undocumented by NVIDIA. If the display misbehaves after it, delete /etc/modprobe.d/nvidia-i2c.conf and rebuild the initramfs again.
Symptom
On Omarchy 4 the brightness keys and the Display panel slider work on the laptop panel but do nothing on my external monitor, or the panel shows FIXED BRIGHTNESS for it. omarchy-brightness-display --monitor DP-1 exits 1 with no output.
Cause
Omarchy 4 controls external monitor brightness over DDC/CI with ddcutil (omarchy-brightness-display-ddc, added in Quattro by omarchy pull request 6490, with ddcutil installed by a migration). The script maps the Hyprland connector to an I2C bus through ddcutil detect, then reads and writes VCP feature 0x10. Any of these breaks it:
- DDC/CI is switched off in the monitor's on-screen menu, or a monitor feature such as dynamic contrast or an eye-care mode is holding brightness.
i2c-devis not loaded or the user cannot open/dev/i2c-*. The ddcutil package loads it at boot through/usr/lib/modules-load.d/ddcutil.conf, and its udev rule/usr/lib/udev/rules.d/60-ddcutil-i2c.rulestags video-adapter I2C busesuaccess.- NVIDIA's proprietary driver fails I2C on some cards.
- The monitor sits behind an MST dock or hub. It appears on a virtual connector with no I2C bus of its own, and ddcutil refuses the physical port's bus because the kernel reports that port disconnected (omarchy 14005, open, no fix in 4.0.4).
- A failed lookup is cached as
unavailablefor 60 seconds in$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/, so fixing the monitor and retrying immediately still fails.
Apple displays use a different path, and all-in-one built-in panels are wrongly sent down this one. Both have their own records.
Fix
**1. Run the pieces by hand:**
pacman -Q ddcutil
hyprctl monitors -j | jq -r '.[].name'
omarchy-brightness-display-ddc DP-1; echo "exit $?"
ddcutil detect
**2. Act on what ddcutil detect shows.**
- **Monitor listed with an I2C bus:** test it directly with
ddcutil --bus N getvcp 10. If that fails, enable DDC/CI in the monitor's menu and turn off dynamic contrast or eye-care modes. Then clear Omarchy's cache and retry:
rm -rf "$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc"
omarchy-brightness-display --monitor DP-1 50%
- **No
/dev/i2c-*devices or permission errors:**
lsmod | grep i2c_dev || sudo modprobe i2c-dev
ddcutil environment # prints what it thinks is wrong
- **NVIDIA proprietary driver and no monitor detected:** ddcutil's documented workaround is an undocumented driver option. Omarchy bakes
/etc/modprobe.dinto the UKI, so rebuild it:
echo 'options nvidia NVreg_RegistryDwords=RMUseSwI2c=0x01;RMI2cSpeed=100' | sudo tee /etc/modprobe.d/nvidia-i2c.conf
# Omarchy 4
sudo limine-mkinitcpio && sudo reboot
# plain Arch
sudo mkinitcpio -P && sudo reboot
# after reboot
grep RegistryDwords /proc/driver/nvidia/params
- **Monitor behind an MST dock or hub, not listed at all:** no Omarchy fix as of 4.0.4. Use the monitor's own buttons, or connect it directly, where
ddcutil detectwill list it.
**Plain Arch:** sudo pacman -S ddcutil, then ddcutil --bus N setvcp 10 70 sets an absolute value and ddcutil --bus N setvcp 10 + 10 a relative one. Bind those to your brightness keys.
Verify
omarchy-brightness-display --monitor DP-1 prints a percentage, the keys move it with the external monitor focused, and the Display panel shows a slider for that monitor.
Sources
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-brightness-display-ddc
- https://github.com/omacom/omarchy/pull/6490
- https://github.com/omacom/omarchy/issues/14005
- https://www.ddcutil.com/faq/
- https://www.ddcutil.com/nvidia/
- https://www.ddcutil.com/kernel_module/
- https://www.ddcutil.com/i2c_permissions/
- https://wiki.archlinux.org/title/Backlight