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

Quiet fans stuck at full speed on AC after a fresh Omarchy install

omarchylaptopdellalienwarepower-profiles-daemon
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Cause matches issue #7516 and the installed omarchy-powerprofiles-set (identical on quattro). With no ac state file it picks performance when available, and autostart.lua runs omarchy-powerprofiles-init on hyprland.start. omarchy-powerprofiles-set ac balanced writes ~/.local/state/omarchy/powerprofiles/ac and applies it. Init (autodetect) and the battery service's omarchy-powerprofiles-set ac on plug-in both read it back. The menu (autodetect <profile>) and the power panel (ac while not discharging) save it too. Defects: (1) the firmware-file paragraph says a direct quiet write 'resets at the next profile change'. The G15 comment in #7516 reports the opposite: power-profiles-daemon kept and saved the quieter firmware mode across restarts. On Omarchy, init and plug-in re-apply the saved profile, which can replace it. Neither outcome is confirmed, so the fix now says what the source supports and adds the persistent route (ac power-saver) with a check of the resulting firmware mode. (2) Frequency: three reporters on specific vendor drivers (Alienware, Dell G15, one Yoga 'same issue') is occasional, not common. Not exercised: no profile changed.

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

Symptom

On a fresh Omarchy 4 install, with the laptop plugged in and doing nothing, both fans run at or near maximum. CPU is 40-55 °C and the GPU is cool. powerprofilesctl get prints performance and cat /sys/firmware/acpi/platform_profile prints performance. Seen on Alienware 16 Aurora, Dell G15 5510, and a Lenovo Yoga Pro 14.

Cause

At session start Omarchy runs omarchy-powerprofiles-init, which calls omarchy-powerprofiles-set autodetect. With no profile saved for AC, the script picks performance whenever that profile exists. power-profiles-daemon passes this to the firmware platform profile, and on several vendor platform drivers performance is a turbo mode that pins the fans. On Alienware it is G-Mode (thermal profile 0xAB), which ignores temperature.

Fix

**Omarchy 4:** save a quieter AC profile. It is remembered in ~/.local/state/omarchy/powerprofiles/ac and restored at every login and AC plug-in:


omarchy-powerprofiles-set ac balanced
powerprofilesctl get
cat /sys/firmware/acpi/platform_profile

The same choice is in the Super+Space menu and the battery panel while you are on AC.

If the fans are still loud on balanced, list what the firmware offers:


cat /sys/firmware/acpi/platform_profile_choices

power-profiles-daemon exposes only power-saver, balanced and performance. To keep a quieter mode persistently, save power-saver for AC and check which firmware mode the daemon chose for it:


omarchy-powerprofiles-set ac power-saver
cat /sys/firmware/acpi/platform_profile

A vendor mode such as quiet or cool can also be written to the firmware directly. Omarchy re-applies the saved profile at every login and AC plug-in, which can replace it, so use this to find which mode is quiet on your machine rather than as a permanent setting:


echo quiet | sudo tee /sys/firmware/acpi/platform_profile

**Plain Arch with power-profiles-daemon:** powerprofilesctl set balanced. The daemon saves its own choice in /var/lib/power-profiles-daemon/state.ini.

Verify

cat ~/.local/state/omarchy/powerprofiles/ac prints balanced. After a reboot on AC, powerprofilesctl get prints balanced and sensors shows fan RPM following temperature instead of sitting at maximum.

Sources

omarchy-performance-profile-fans-max-on-ac