Closed mstormi closed 3 years ago
No, this is not correct. I have not had issues on my end, it has been persistent on my end, perhaps just your box?
yeah but possibly others, too ? Governor is definitely set to "powersave". It should not do harm to always onforce it to "ondemand", should it ?
Perhaps, but I just don't like the idea of creating another service, I feel like we have so many already and we have had so many issues with them. Let me look into it and see if there is a better solution that persists across reboots for everyone.
ok but it would be a one-time service (no running one), we could even remove the cpufrequtils again
ok the line above is already in openhabian-config so under normal conditions it should run like we want it to if somebody had powersave in effect it must be due to some other (unidentified) reason. If you don't mind I'll re-remove the extra cpufrequtils install there (it's still installed in needed_packages() on unattended install)
re-open if you find any reason why governor is set to powersave
Despite of the 'cpufrequtils' package installed & configured I keep seeing that my Raspi keeps running at minimum frequency "powersave" is probably the default somewhere but I have not found out so far where it's overriding the cpufrequtils setting (which is "ondemand" which is what we want).
Workaround: add another service with a timer "on boot" (or make it part of the start script of zram or openhab?)
echo "ondemand">/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor