OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
gpu-drivers medium common DISPUTE

Raise a laptop NVIDIA GPU stuck at its base power limit by enabling nvidia-powerd

omarchyarchendeavouroscachyosmanjaronvidialaptop
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

AUDITOR BREACH, read first (it concerns this workstation, not this record): while checking linux-omarchy-7-2-5-amdgpu-display-regression I ran limine-update --help to read its usage. limine-update has no help handling and re-execs itself through /usr/lib/limine/auth-helper, which falls back to sudo, and sudo is passwordless here. The journal shows COMMAND=/usr/bin/limine-update --help as root at 12:20:55 on 2026-10-05. It ran limine-install --no-efi-register (printed 'Limine EFI update completed successfully') and then limine-mkinitcpio --help, which printed 'Building UKI for linux (7.2.3-arch1-3)' before the pipe into head -3 closed, so the UKI build for the Arch linux kernel was probably killed partway. The default kernel linux-omarchy had not been reached. I did not repair anything, because that would be another root action. The operator should run sudo limine-update to completion and check sudo limine-entry-tool --tree before the next reboot. The same journal shows other root runs at 12:20:46 (limine-entry-tool --help) and 12:21:06 (limine-snapper-sync --remove --help) that were not mine and came from other auditors. RECORD AUDIT: The core claim holds. omarchy#9678 (open) has the 50 W versus 85 to 93 W A/B with the daemon masked and running, the fresh-install disabled; preset: disabled status and the SuspendThread loop failed note. On this machine pacman -Ql nvidia-utils ships /usr/lib/systemd/system/nvidia-powerd.service, the presets in /usr/lib/systemd/system-preset do not enable it, and grep for powerd in /usr/share/omarchy returns nothing. The quattro install/hardware/nvidia.sh writes modprobe and mkinitcpio files and never enables the unit. The fix PR omarchy#10592 is still open. The Arch wiki CPU frequency scaling page lists the Ampere, Comet Lake / Renoir and firmware requirements as stated. Three defects. First, the record cites omarchy#3079 but ignores what it says: on an Omarchy 3 RTX 5070 Ti laptop, enabling nvidia-powerd stopped the machine reaching the graphical session after reboot, so the danger field was empty when it should carry the TTY recovery. Second, NVIDIA's own Dynamic Boost README says it engages only on AC power with GPU load and never on battery, which the verify step did not say, so a reader testing on battery concludes the fix failed. Third, the ASUS asusctl performance-profile line is not in any cited source and was dropped in favour of the wiki's firmware performance-mode note. Not exercised: no NVIDIA laptop here.

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

omarchy#3079 reports an Omarchy 3 laptop (RTX 5070 Ti, Ryzen 9955HX3D) that stopped reaching the graphical session after nvidia-powerd was enabled and the machine rebooted. The reporter recovered with NVIDIA modprobe options, one of which (options nvidia_drm modeset=1) Omarchy 4 already writes. Know the TTY recovery, sudo systemctl disable --now nvidia-powerd from Ctrl+Alt+F2, before rebooting.

Symptom

Games run far worse than on Windows or CachyOS on the same NVIDIA laptop. nvidia-smi shows the card pinned at its default limit under full load, for example Pwr:Usage/Cap 49W / 50W, while nvidia-smi -q -d POWER lists a higher Max Power Limit it never reaches. Temperatures stay low, which makes it look like a hardware or driver fault. Some Proton games also log SuspendThread loop failed on exit.

Cause

NVIDIA Dynamic Boost, the mechanism that lets a laptop GPU draw more than its base TGP, is not automatic on Linux. It needs the userspace daemon nvidia-powerd, which ships in nvidia-utils as nvidia-powerd.service with preset disabled, so nothing starts it unless the installer or the user enables it. Omarchy 4's install/hardware/nvidia.sh installs the driver and writes the modprobe and mkinitcpio files but never enables the service (confirmed on 4.0.4-1 by grepping /usr/share/omarchy for powerd, which returns nothing). Without the daemon the GPU stays at its Default Power Limit. omarchy#9678 reproduced it both ways on an RTX 5060 Laptop: 50 W with the daemon masked, 85 to 93 W with it running. Requirements per the Arch wiki: Ampere or newer GPU, Intel Comet Lake or AMD Renoir or newer platform, and firmware-level Dynamic Boost support.

Fix

Check whether the platform supports Dynamic Boost and whether the daemon runs:


cat /proc/driver/nvidia/gpus/*/power
systemctl status nvidia-powerd
nvidia-smi -q -d POWER | grep -i 'power limit'

Enable it. The command is the same on Omarchy 4 and plain Arch, since the unit comes from nvidia-utils. Omarchy 4.0.4 does not enable it during install (the one-line fix, omarchy#10592, was still an open PR on 2026-10-05). Machines on the legacy nvidia-580xx-utils branch have pre-Ampere GPUs, which Dynamic Boost does not support, so this does not apply to them.


sudo systemctl enable --now nvidia-powerd

Test on AC power. NVIDIA's README says Dynamic Boost engages only when the laptop is plugged in and the GPU is under load, never on battery.

Some laptops only expose the higher limit in a firmware or vendor performance mode (the Arch wiki names some Lenovo Legion models). If the limit does not rise, select that mode as well.

If the machine no longer reaches the graphical session after the next reboot (reported on an Omarchy 3 install in omarchy#3079), switch to a TTY with Ctrl+Alt+F2, log in and turn the daemon back off:


sudo systemctl disable --now nvidia-powerd

On a desktop card, or a laptop without firmware Dynamic Boost support, the daemon has nothing to manage. Disable it again there with the same command.

Verify

With the laptop on AC power and a GPU load running, nvidia-smi --query-gpu=power.draw,power.limit --format=csv -l 2 shows power.limit above the Default Power Limit and draw climbing past the old cap. systemctl is-enabled nvidia-powerd prints enabled. On battery the limit stays at the default by design.

Sources

nvidia-powerd-not-enabled-laptop-tgp-capped