-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Not detecting correct CPU Max frequency and ignoring config file #737
Comments
I've made a fork and edited |
This is unfortunately true, and something I was aware of. As like you I would prefer to have I'd like to have
So I'd have to set it to
But even then I might see them go to 800Mhz instead when 1800 should be the I never had the problem you had, as my max frequencies were always reached. I will even get same values for both:
Where in my case these values are the same:
But I also see you're limiting the
I would encourage you to contribute to the project and you will be credited for your work as part of future release, as if it fixes an issue it's def worth having. But can you share are you values before and after the changes? Because for me they are all the same between max & min:
And finally just wanted to add that both my min & max frequency are correctly identified in both
|
Also some potentially related EPP changes to this issue were merged with #738 |
Interesting. Maybe when the CPU enter turbo state it's exposing these frequencies to the system? That would explain why setting to "always" it would never go down 1800, as this frequency is always available. I will try this and report back.
Mainly because of temps and fan noise. When gaming it would almost always reach 3.4GHz and increase the temperature to the thermal limit of 100°, to then throttle down to 400mhz because of these high temps, even tough I'm not playing heavy or CPU intensive games. . Even on desktop it reaches 85° on normal use, along with the noisy fans. I found that between 2.1 - 2.7Ghz is the sweet spot, where I can get stable FPS, frametime and good temps.
That would be super cool! I can make a PR with these changes I've made if you want, as it should get a ""more accurate"" info.From what I've seen shouldn't be a problem as for most systems these values are the same, and it would now cover these weird cases(like mine) where they aren't.
Sure, here you go:
After
|
I'm no expert with GUI's,but I can try giving it a look into this problem when the value(s) is not within the allowed frequencies, maybe auto-setting the |
That would be great, @shadeyg56 is the one who originally introduced GUI, so if you have some questions he might be able to help. We're also all hanging around in auto-cpufreq Discord community. |
Fill out information requested in this template, without doing so issue will be ignored & closed!
Have you tried?
Error output:
System information:
Add/paste output of:
Also please be descriptive about the issue you're reporting, i.e: what you tried & what's the expected behaviour.
The output of
auto-cpufreq --debug
reports that the max CPU frequency is 3400Mhz, but the output ofauto-cpufreq --stats
says that it's 1600Mhz( The max frequency without turbo boost). Ifscaling_max_freq
orscaling_min_freq
value in the config file is greater than the CPU max frequency ofauto-cpufreq --stats
, the config file is ignored, and the GUI App only shows "Battery is: Charging".Expected Behaviour
It should use the real CPU Max frequency(3400Mhz) as the limit and not the max without turbo
Proof
auto-cpufreq.conf
Additional Information
Output of
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
:1600000
Output of
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
:3400000
I'm using msr-tools to edit the CPU registers to enable turbo boost, since the option is not present in my Bios. Without it the turbo would be permanently disabled, and if I use the
acpi-cpufreq
driver the turbo works, but it doesn't expose the real max frequency of the CPU, and therefore I can't limit it.Also I'm using a notebook, but I removed the battery since it died
The text was updated successfully, but these errors were encountered: