Repository navigation
Enable nvidia-powerd so laptop GPUs get Dynamic Boost - #10592
onelegdave wants to merge 8 commits into
Conversation
Arch ships nvidia-powerd.service with preset: disabled. Without it, laptop NVIDIA GPUs stay at base TGP with no Dynamic Boost. On an RTX 5060 Laptop this meant a hard 50W ceiling against 100W with the daemon running - 49.7W sustained versus 85-93W under identical load. Reproduced in both directions on the same hardware. Harmless on desktop cards, where the daemon finds nothing to manage.
|
Confirming on a third vendor. Lenovo Legion Pro 5 16ARX8, Ryzen 7 7745HX, RTX 4060 Laptop GPU, Omarchy 4.0.3, nvidia-open-dkms 615.71.09, kernel 7.2.3. Fresh Omarchy install had Under a sustained VR load (SteamVR + Half-Life: Alyx) it sat at 97-99 % utilization, throttling from 2220 MHz to about 1600 MHz. After One note on the "harmless on desktop cards" point. The unit ships with |
|
Thanks for confirming this on the Lenovo and for catching the desktop failure behavior. I've added the ACPI guard in a3633d9 and corrected the description's "harmless on desktop cards" claim. The installer now checks for an exact Bash syntax, whitespace checks, and the existing NVIDIA hardware-detection and KMS-hook tests passed. Eight mocked installer scenarios also passed, covering absent/unrelated devices, instances This detects the platform-controller device; it does not guarantee working Dynamic Boost on every firmware/driver combination. The guard revision has not been tested across other physical laptops or in a fresh ISO installation. |
|
Reviewed at a3633d9 against What was checked, on a disposable Omarchy VM:
A second opinion from Codex Medium read the diff and the base branch's rules and found no defect. It agreed on the guard, the unit being in both packages, and #3079. It also notes that Two things are left, and both belong to the maintainer:
Waiting on the maintainer. |
|
Confirming on an Intel hybrid laptop: ASUS ROG Zephyrus G16 GU605MI (Core Ultra 9 185H, RTX 4070 Laptop GPU), Omarchy 4.0.4, kernel 7.2.5-3-omarchy, nvidia-open-dkms 610.57.04. MUX in Hybrid mode, so the Intel iGPU drives the internal panel and the NVIDIA GPU renders through PRIME. On a fresh install (2026-10-03) Under a game load (Overwatch through DXVK) it was at 100% utilization, ~55 W and 1450–1650 MHz, with After I enabled the service by hand rather than running the PR's install script. One thing I couldn't check here: whether the daemon keeps the dGPU from runtime-suspending. On this machine the dGPU never suspends anyway, because Firefox's media process (RDD) holds it, presumably through |
|
Tested the change in a3633d9 on an ASUS ROG Zephyrus G16 GU605CP (DMI
On ROG, asusd also starts |
|
Two new hardware reports since the last review, read at a3633d9. The head hasn't moved and What the new reports add:
Neither reporter ran this PR's install script. Both enabled the unit by hand, which ends in the same service state but doesn't exercise the guard. The GU605CP also added a A second opinion from Codex Medium read both reports and came to the same conclusions. It also raised the battery point, which this review had not. It found no new defect. Its independence from this review is not guaranteed. This still isn't marked verified. Hardware confirmation has to come from the issue's reporter (here the PR's author, who can't confirm their own fix) or a maintainer, naming the full commit. The open questions are unchanged: confirming on a laptop at this commit, possibly including battery behaviour, and whether existing installs should get a migration. The GU605CP report shows an updated machine still has the unit disabled. Waiting on the maintainer. |
|
Battery test on the same ASUS Zephyrus G16 GU605MI (Core Ultra 9 185H + RTX 4070 Laptop, hybrid mode), at a3633d9. Same caveat as before: the unit is enabled by hand ( Booted on battery: the enabled unit came up at boot and logged Idle on battery, 2 min settle + 60 s measured, screen on at fixed brightness (idle inhibited), no game or browser on the dGPU:
(Default 55 W, Max 115 W in both.) So with the daemon running on battery the dGPU still runtime-suspends at idle, and the 0.4 W difference is within noise. AC transitions with the daemon running: plugging in raised Current Power Limit 47 -> 105 W; unplugging dropped it to 42 W because asusd stopped the service. |
The GB10 desktops (DGX Spark, Ascent GX10) reach this branch and expose the same NVDA0820 platform controller, but NVIDIA documents Dynamic Boost for Intel and AMD notebooks only, so the guard alone would enable the daemon on an unsupported desktop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com>
|
Re-reviewed because
What was checked, on a disposable Omarchy VM at 2c6f70a:
The battery report on the GU605MI answers the question raised last time, for that machine: the daemon came up on battery, kept running after the firmware turned off the DC controller, and the dGPU still runtime-suspended at idle. On ROG laptops asusd stops the service on unplug anyway. This was tested on one ASUS model with the unit enabled by hand, not through this script. Codex Medium found the GB10 case in its review of the merged tree. It then reviewed the fix and found no defect. This still isn't marked verified. A Dynamic Boost fix can only be confirmed on a laptop, and it needs a maintainer, testing the full commit 2c6f70a. Whether existing installs should get a migration is still open. Waiting on the maintainer. |
[Medium impact] The PR appears safe to merge. SummaryEnables
Reviews (3) · Last reviewed commit: "Reset the sandboxed /etc between test ca..." · Reviewed by Greptile |
The section says Codex helped with tests "in this fork", which stops being true once it lands in Omarchy's README, and it is unrelated to enabling nvidia-powerd. The PR description is where that disclosure belongs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AGENTS.md requires the exact platform names in tests; `arm` is not one of them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Muse Wonder High <noreply@omarchy.org>
The files the first case wrote let every later case pass the "completes setup after the guard" check without the script reaching those writes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> Co-Authored-By: Muse Wonder High <noreply@omarchy.org>
|
Re-reviewed because the branch gained 6619015, which adds The new test runs the whole setup script against a fake ACPI tree and a sandboxed What I pushed, @onelegdave:
Codex Medium and muse-wonder (via pi, thinking high) reviewed the new commits. Both found the stale This still isn't marked verified. Dynamic Boost only shows up on an NVIDIA laptop, and #9678 was opened by the author of this PR, so the confirmation has to come from a maintainer, testing the full commit e6c48d7. Whether existing installs should get a migration is also still open. Waiting on the maintainer. |
Fixes #9678
What
Enables
nvidia-powerdininstall/hardware/nvidia.shafter driver installation, only when an ACPI device exposes NVIDIA's platform-controller hardware ID (NVDA0820).Why
Arch ships
nvidia-powerd.servicewithpreset: disabled. Nothing in the install enables it, so on laptops the GPU stays at its base TGP with no Dynamic Boost.On an ASUS ROG Strix G16 with an RTX 5060 Laptop GPU:
Without the daemon:
Pinned at 49.5–50W at 65–69°C under sustained 99% load.
With it:
85–93W at 78–80°C under the same load.
Reproduced in both directions on the same hardware — masking the daemon on a working install drops the ceiling straight back to 50W, and enabling it on a fresh Omarchy install raises it immediately.
Notes
enablerather thanenable --now, since the install runs before the graphical session and the daemon is only useful from next boot.NVDA0820match in/sys/bus/acpi/devices/*/hid, without assuming instance:00. Systems without a match skip enablement.