Fix washed-out, dim colours on an AMD laptop panel
The single cited source resolves and does support the claim. I fetched https://wiki.archlinux.org/title/AMDGPU as raw wikitext and its section "Colors appear washed out and dim on laptops" says that power-profiles-daemon and tuned have started to enable Panel Power Savings, that PPS makes the GPU lower colour accuracy to save power on more aggressive profiles, and that the fix is amdgpu.abmlevel=0. The record's cause and symptom are close to verbatim from it, so the source stays and nothing is removed. I then checked the parameter in the kernel rather than trusting the wiki: in drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c it is module_param_named(abmlevel, amdgpu_dm_abm_level, int, 0444) with the description ABM level (0 = off, 1-4 = backlight reduction level, -1 auto (default)), and the kerneldoc above it adds that userspace can only override this level after boot if it is set to auto. That is a real fact the record misses in both directions. It explains why a power profile can change your colours at all, and it means amdgpu.abmlevel=0 is not auto, but off: it pins the level and stops power-profiles-daemon managing panel power savings afterwards. It also gives a reversible fix the record never offered.
What was wrong is the apply step, the same shape as the other AMD kernel-parameter records. The record told an Omarchy reader to edit cmdline: in /boot/limine.conf or /etc/default/grub, and carries omarchy in applies_to. On this workstation (omarchy 4.0.2-1, kernel 7.1.9) there is no /etc/default/grub, the boot is a UKI, and /boot/limine.conf is regenerated. I read /etc/limine-entry-tool.d/omarchy-defaults.conf and omarchy-uki.conf directly, and the packaged template /etc/limine-entry-tool.conf from limine-mkinitcpio-hook 1.37.1-1 states the += versus = rule. The fix now matches the existing record limine-kernel-parameters-not-applying-omarchy instead of contradicting it, and keeps the systemd-boot and GRUB branches labelled for other distributions.
I also checked what Omarchy manages itself before leaving the reader to set anything by hand. Omarchy 4 ships power-profiles-daemon 0.30-1 (pacman -Q), tuned is not installed, and /usr/share/omarchy/bin carries omarchy-powerprofiles-set, -list and -init. I read omarchy-powerprofiles-set: it detects AC or battery from UPower, calls powerprofilesctl set, and remembers a profile per state under $XDG_STATE_HOME/omarchy/powerprofiles. omarchy-powerprofiles-list on this machine prints power-saver, balanced, performance. Omarchy's brightness tooling (omarchy-brightness-display and friends) drives brightnessctl and DDC and does not touch ABM, so there is no conflict with a theme refresh here. NOT EXERCISED: this workstation has an NVIDIA RTX 3090 and amdgpu is not loaded, so no ABM or colour behaviour was tested here and no profile was switched. The Omarchy boot and power-profile mechanisms were confirmed on this machine. Severity low and frequency common are left alone: the symptom is cosmetic and now has a one-command reversible fix, and it is common on AMD laptop panels.
Option 1 carries no risk worth naming. You can undo it with one command and nothing is written to the bootloader.
Option 2 has two costs. The panel draws slightly more power on battery in every profile. More importantly, the kernel says userspace can only override the ABM level after boot while the parameter is left at auto, so pinning it to 0 stops power-profiles-daemon managing panel power savings at all, which is not obvious from the parameter name. On Omarchy 4 the drop-in itself is the larger risk. Writing KERNEL_CMDLINE[default]= instead of +=, or naming your file so it sorts before omarchy-defaults.conf, silently drops Omarchy's initramfs_async=0, and the packaged comment in that file says that is what keeps Plymouth alive at the LUKS prompt, so an encrypted machine falls back to an unthemed text prompt or hangs. limine-mkinitcpio rewrites the UKI on the ESP, so run df -h /boot first, because a full ESP produces a truncated image that will not boot. A bad kernel parameter is a failure to boot. Recovery is the Limine boot menu editor or a Limine snapshot entry, and both are bypassed if you have enabled Omarchy's Direct Boot, in which case pick Limine from the firmware boot menu (usually F12, F8 or Esc). On a GRUB system the equivalent recovery is GRUB's own e editor at the menu.
Symptom
Colours on the internal laptop display look grey and washed out, and get worse when the machine switches to a power-saving profile or goes on battery. External monitors look normal.
Cause
Adaptive Backlight Management, which the AMD driver exposes as Panel Power Savings, tells the GPU to reduce colour accuracy on the laptop's internal panel to save power. power-profiles-daemon has enabled it in its more aggressive power modes since version 0.20, and tuned does the same, which is why the colours track the power profile and the charger. External monitors are unaffected because ABM is an internal panel feature.
The kernel describes the parameter as ABM level (0 = off, 1-4 = backlight reduction level, -1 auto (default)), and adds that userspace can only override the level after boot while the parameter is left at auto. That is what lets a power profile change it at runtime, and it is also why pinning the parameter to 0 takes the setting away from the power daemon for good.
On Omarchy 4 the daemon in play is power-profiles-daemon (0.30-1 as of 2026-09-11). tuned is not installed. Omarchy drives the daemon through omarchy-powerprofiles-set, which detects AC or battery from UPower and remembers a separate profile for each under ~/.local/state/omarchy/powerprofiles/.
Fix
**Option 1, reversible and no reboot: stop using the most aggressive power profile.** The kernel parameter defaults to -1 (auto), and only at auto can userspace change ABM after boot, so the power profile is what is actually moving your colours.
powerprofilesctl get
# Omarchy 4: sets it now and remembers it for the next time you are on battery
omarchy-powerprofiles-set battery balanced
# plain Arch, EndeavourOS, CachyOS, Manjaro
powerprofilesctl set balanced
Colours come back within a second or two. Try this first, because it costs nothing to undo.
**Option 2, permanent: turn ABM off with a kernel parameter.**
amdgpu.abmlevel=0
abmlevel is a 0444 module parameter, so this only takes effect at boot. Read the danger note first: 0 is not auto, but off. It pins the level, so power-profiles-daemon can no longer manage panel power savings on any profile.
**Omarchy 4** has no /etc/default/grub, and /boot/limine.conf is regenerated on every kernel or limine transaction, so an edit there is discarded. Omarchy boots a Unified Kernel Image, which bakes the command line into the .efi image. Kernel parameters go in your own drop-in under /etc/limine-entry-tool.d/ whose filename sorts after Omarchy's omarchy-defaults.conf, and always with +=:
sudo tee -a /etc/limine-entry-tool.d/zz-local.conf >/dev/null <<'EOF'
# `+=` appends. A bare `=` would wipe Omarchy's own defaults.
KERNEL_CMDLINE[default]+=" amdgpu.abmlevel=0"
EOF
sudo limine-mkinitcpio && sudo limine-update && sudo reboot
Use tee -a rather than tee. A bare tee truncates the file and would drop any parameter you added earlier from another record. The full mechanism, including how to test a parameter from the Limine boot menu editor without writing anything to disk, is in the record limine-kernel-parameters-not-applying-omarchy.
**Other bootloaders:**
- systemd-boot: append to
optionsin/boot/loader/entries/*.conf - GRUB:
GRUB_CMDLINE_LINUX_DEFAULTin/etc/default/grub, thensudo grub-mkconfig -o /boot/grub/grub.cfg
Reboot in every case.
Verify
For option 1:
powerprofilesctl get
reports the profile you chose, and the colours follow it when you switch profiles or unplug the charger.
For option 2:
cat /sys/module/amdgpu/parameters/abmlevel # 0 once applied, -1 is the default
cat /proc/cmdline
/proc/cmdline contains amdgpu.abmlevel=0. On Omarchy 4 it must also still contain Omarchy's own defaults (quiet splash loglevel=0 systemd.show_status=false rd.udev.log_level=0 vt.global_cursor_default=0 and initramfs_async=0). If those have gone, your drop-in used = where it needed +=. Then switch to power-saver and unplug the charger: the colours must not change.