Keep Activity from waking a runtime-suspended NVIDIA GPU - #11675
Open
anant1811 wants to merge 1 commit into
Open
Keep Activity from waking a runtime-suspended NVIDIA GPU#11675anant1811 wants to merge 1 commit into
anant1811 wants to merge 1 commit into
Conversation
btop initialises NVML at startup whenever shown_gpus lists nvidia, whether or not a GPU box is on screen. On a hybrid laptop whose iGPU drives every output, opening Activity therefore resumed the discrete GPU and held it awake for as long as btop ran, on battery included. Route the Activity binding through omarchy-launch-activity, which drops nvidia from shown_gpus while every NVIDIA GPU is runtime suspended and puts it back once the card is awake. The check reads the cached sysfs power state, which unlike lspci or NVML does not itself wake the card. Fixes omacom#11184 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LKJ7WaM8LCBtL91KJe3wQT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
btop initialises NVML at startup whenever
shown_gpuslistsnvidia, whether or not a GPU box is on screen. On a hybrid laptop whose iGPU drives every output, opening Activity therefore resumed the discrete GPU and held it awake for as long as btop ran, on battery included.Route the Activity binding through
omarchy-launch-activity, which dropsnvidiafromshown_gpuswhile every NVIDIA GPU is runtime-suspended and puts it back once the card is awake. The check (omarchy-hw-nvidia-suspended) reads the cached sysfspower/runtime_status, which unlike lspci or NVML does not itself wake the card — the same criterion the report measured against.Fixes #11184
Testing
New
hw-nvidia-suspended-test.sh(5 cases) andlaunch-activity-test.sh(4 cases). Also exercised the launcher end-to-end with the real detector and the shippedbtop.conf: no NVIDIA → file untouched; simulated suspended NVIDIA → onlyshown_gpuschanges; awake again → file restored exactly. Fulltest/shellrun shows only the pre-existing environmental failures.🤖 Generated with Claude Code
https://claude.ai/code/session_01LKJ7WaM8LCBtL91KJe3wQT