Skip to content
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

SteamOS 3.7 is missing Schedutil Governor #1781

Open
deathblade201243 opened this issue Jan 17, 2025 · 2 comments
Open

SteamOS 3.7 is missing Schedutil Governor #1781

deathblade201243 opened this issue Jan 17, 2025 · 2 comments

Comments

@deathblade201243
Copy link

I updated to the "Main" channel recently and I noticed that Schedutil is missing.

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors performance powersave

by default it is set to the performance governor

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
performance
performance
performance
performance
performance
performance
performance
performance
@FanOfABT
Copy link

Finally and good riddance to the SchedUtil CPU governor!

There are probably very good reasons why A.B.T.'s SteamOS tweaks always defaulted to the performance governor, looks like Valve finally had the time to read that article. ;-)

Anyhow, the reason why the awful schedutil governor is missing is because SteamOS 3.7 must be activating the AMD-PSTATE CPU driver by default.

You can confirm that's indeed the case by running the following command and looking at the driver column:

sudo cpupower frequency-info

Personally, ever since I've read A.B.T.'s excellent article I always defaulted to the performance CPU governor and never had any problems whatsoever.

Good times ahead for all SteamOS users, thanks VALVe!

@deathblade201243
Copy link
Author

deathblade201243 commented Jan 17, 2025

never heard of AMD-PSTATE before now and just thought it was an error but it looks like it is indeed active

driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 400 MHz - 3.50 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 1.70 GHz and 3.50 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 3.50 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 3.50 GHz.
    AMD PSTATE Nominal Performance: 204. Nominal Frequency: 2.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 124. Lowest Non-linear Frequency: 1.70 GHz.
    AMD PSTATE Lowest Performance: 30. Lowest Frequency: 400 MHz.

originally just using performance governor would waste a huge chunk of battery so that guide was bad for telling people to do that at that point

Edit: after further testing it looks like powersave is the intended default governor. idk why it defaulted to performance for me since I never use that governor could have been something like powertools getting confused after the update or something else. either way I'm sure its meant to be powersave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants