I was referring to governor tweaks. I'm using currently 2 sets of tweaks, but they might be outdated.
Originally Posted by Baconmon
Second set (battery only)
/sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor = 6
/sys/devices/system/cpu/cpufreq/ondemand/up_threshold = 35
/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load = 1
/sys/devices/system/cpu/cpufreq/ondemand/powersave_bias = 200
/sys/devices/system/cpu/cpufreq/conservative/up_threshold = 98
/sys/devices/system/cpu/cpufreq/conservative/down_threshold = 95
/sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor = 7
/sys/devices/system/cpu/cpufreq/conservative/ignore_nice_load = 1
Control Theory uses a feedback loop (thus hysteresis), according to the link you provided.
Originally Posted by rdnetto
Nice, a change (and an article) I can understand :).
… And I just noticed I don’t have a /sys/devices/system/cpu/cpufreq/ anymore… acpi_cpufreq refuses to load, and /proc/cpuinfo says my Core i3 550 (3.2GHz) is running at 3840.242 MHz. Meh.
Start the driver manually (i.e.: using modprobe) if you have to. And IIRC, it's
Originally Posted by stqn
Thanks Sonadow, I found out today that I had to set EIST to Enabled instead of Auto in my BIOS to make cpufreq work.
Originally Posted by Sonadow
In module names, - and _ are interchangeable (which is confusing, but true).