-
-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service keeps enabling discrete GPU, causing higher power drain instead of saving it #278
Comments
What if you don't use Also please make sure to have the latest 1.7.2 release. |
okay, I've updated to 1.7.2 and the same behaviour persists. some additional details that I've noticed:
|
Just released v1.9.2 which adds ability to change power governor used by default with auto-cpufreq from |
Sorry to comment on this after more than a year, but I am having the same issue, and I wanted to know if OP ever found a fix for this. |
Can you confirm if this is related to: #398 |
I didn't notice problem #398. However, the problem of the active GPU is also present on my ASUS G14 2022 with the Ryzen 6800HS and RX 6700S. No idea if this info helps, but if the auto-cpufreq is off and the CPU-X graphics card page is open, the GPU will also be activated. As a small idea from a user with no programming experience. Does the auto-cpufreq service access the graphics card info somewhere? If you still need information, please write what and how I can retrieve it. |
I just checked my laptop for problem #398. it doesn't look that bad but the battery performance is greatly reduced. On battery:
On power adapter:
In the first second on the power adapter:
|
Was this mentioned in #216 as it could simply be mentioned as part of documentation? If there are any changes that could be made please give it a try and contribute to the project and you will be credited for your work as part of future release. In meantime closing the issue due to inactivity. |
hello there,
I've started using using
auto-cpufreq
on my laptop (MSI Bravo 15 B5DD) and I've noticed that whenever it's enabled and doing its thing, the LED that indicates which GPU is currently used is constantly switching between orange (discrete GPU) and white (integrated GPU), with the former being active for the majority of time. it reflects on the battery life when unplugged, with Plasma's battery widget actually estimating shorter remaining battery life when runningauto-cpufreq
in the--live
option, and significantly extending the estimation when stopping it. I've observed the same behaviour with it running as a daemon.the laptop model is MSI Bravo 15 B5DD with AMD Ryzen 5600H CPU and AMD Radeon RX 5500M dGPU, running EndeavourOS (Arch-based) with KDE Plasma.
I've attached my
auto-cpufreq.conf
below the system information, although the only thing I've changed compared to the example file from the readme is the governor when plugged in (schedutil
instead ofperformance
), which as far as I understand shouldn't have any effect on the behaviour when unplugged, anyway. I've also tried changingturbo
tonever
and restarting the service, and the same issue persisted.I'll be happy to provide any other required information, just might need a little bit of hand holding here and there :)
System information:
/etc/auto-cpufreq.conf:
The text was updated successfully, but these errors were encountered: