/etc/auto-cpufreq.conf working only in --live mode, not if auto-cpufreq runs as service (OpenSuse) about auto-cpufreq

[Animeshz]

Well it turns out after updating the whole system and everything installing from latest commit last week, it somehow started working. I'm not sure what happened, and what caused it earlier to misbehave. Since I can't reproduce the behavior I'll say this may have been fixed in between the releases and latest commit.

[dgrat]

# settings for when connected to a power source
[charger]
governor = schedutil
scaling_min_freq = 400000
scaling_max_freq = 2000000
turbo = auto

# settings for when using battery power
[battery]
governor = powersave
scaling_min_freq = 400000
scaling_max_freq = 2000000
turbo = never

[AdnanHodzic]

Have you tried restarting after creating the config file? I remember that for changes to be picked up auto-cpufreq process had to be stopped (an improvement could be made regarding this of course).

[dgrat]

Hi there
Restarting the service is not helping. It applies the config only in live mode.
I think it would be helpful to add some error output to --debug, regarding if and which settings really have been applied.
On the first glance everything looks like it should work :D

[Animeshz]

I recently noticed this, after update to nixos-23.11 channel at v1.9.9, (prior nixos-23.05 at v1.7.1 was working fine). I'll bisect and see if I can find anything.

[dgrat]

I tested a little more with current snap image.. When I run
sudo auto-cpufreq --live
sudo auto-cpufreq --install
It works till restart. After reboot, the settings are not applied anymore.

It will work again with
sudo auto-cpufreq --remove
sudo auto-cpufreq --live

I think it is pretty reproducible at least on my system

[AdnanHodzic]

Please make sure to use the latest version and preferably use auto-cpufreq-installer.

[dgrat]

I tested 2.1 and installed from git repo (not snap). Seems to work again ..
So 2.0 via snap has the issue ..

[AdnanHodzic]

Great, closing the issue then.