OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend medium occasional DISPUTE

Fix power profiles failing with 'Error writing .../boost: Invalid argument' on AMD

omarchyarchcachyosamdlaptopdesktoppower-profiles-daemon
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Read omacom/omarchy #12805 (5600G desktop, ppd 0.30-1, every boot, no platform_profile) and #6898 (Lenovo LOQ, later closed by its reporter as no longer reproducible after a reboot, which does not contradict the record). Read ppd #189 (Strix Halo, CPPC firmware owns boost, code excerpt showing the boost write is fatal before EPP, now closed), #172 (ThinkPad E16, still open) and MR !235 (open, checks global cpufreq/boost and stops aborting, fixes #172/#188/#189). Arch package JSON shows power-profiles-daemon 0.30-1 and the GitLab releases API shows 0.30 released 2025-02-18 as the latest. On this workstation: pacman -Ql confirms the binary is /usr/lib/power-profiles-daemon, the stock unit's ExecStart is that path, and --help-all lists --block-driver. The upstream README documents the systemctl edit override with the /usr/libexec path, so the record's path correction is right. Omarchy 4 enables power-profiles-daemon in install/config/enable-services.sh and drives it from omarchy-powerprofiles-set, so the warning against masking holds, and the cross-referenced slug exists. The cpufreq/boost write and the drop-in were not exercised: this workstation is intel_pstate and has no global boost file.

Symptom

Power profile switching does nothing on my AMD machine. The Omarchy menu shows the profiles, but picking Performance or Power Saver has no effect. powerprofilesctl set performance and the journal show:


Failed to activate CPU driver 'amd_pstate': Error writing '/sys/devices/system/cpu/cpufreq/policy11/boost': Invalid argument

It fails at every boot (Failed to activate initial profile). Reported on Ryzen 5 5600G desktop, Ryzen 7 250 Lenovo LOQ, ThinkPad E16 and Strix Halo.

Cause

power-profiles-daemon 0.30's amd_pstate driver writes each policy's boost file before it writes energy_performance_preference, and treats a failed boost write as fatal. The kernel rejects any write to a per-policy boost with EINVAL while core performance boost is disabled driver-wide, and on some CPPC platforms where the firmware owns boost. The switch aborts before the EPP is written. Fixed upstream in principle (ppd issues #172 and #189, merge request !235, still open on 2026-10-04). Arch still ships 0.30, the last release (2025-02-18).

Fix

**1. Check the global boost state:**


cat /sys/devices/system/cpu/cpufreq/boost
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver

If boost reads 0, boost is off driver-wide. Turn Core Performance Boost (CPB) back on in the firmware setup, or enable it for this boot and retry:


echo 1 | sudo tee /sys/devices/system/cpu/cpufreq/boost
powerprofilesctl set performance && powerprofilesctl get

**2. If boost must stay off, or the write still fails,** stop power-profiles-daemon loading its amd_pstate driver. This uses the daemon's documented --block-driver option. On Arch the binary is /usr/lib/power-profiles-daemon, not the /usr/libexec path the upstream README shows:


sudo systemctl edit power-profiles-daemon.service

[Service]
ExecStart=
ExecStart=/usr/lib/power-profiles-daemon --block-driver=amd_pstate

sudo systemctl try-restart power-profiles-daemon.service
powerprofilesctl list

On a laptop that has /sys/firmware/acpi/platform_profile, the profiles then drive the firmware profile only. On a desktop with no platform profile, the profiles become placeholders that change nothing, and the EPP stays at its kernel default, so this only removes the errors.

Do not mask power-profiles-daemon on Omarchy 4: the power menu calls powerprofilesctl, which crashes when the daemon is masked (record omarchy-powerprofilesctl-crash-ppd-masked).

Verify

journalctl -b -u power-profiles-daemon has no Failed to activate line after a reboot, and powerprofilesctl set power-saver && powerprofilesctl get prints power-saver.

Sources

ppd-amd-pstate-boost-write-invalid-argument