Currently, cpufrequtils blindly attempts to set the governor specified in /etc/conf.d/cpufrequtils GOVERNOR. Many other init scripts try to be have nicer by modprobing required modules before exploiting them, the following patch does exactly that. I use modprobe --quiet to ensure that users with cpufreq governors built-in see no error messages. Reproducible: Always
Created attachment 139878 [details, diff] quietly probe for user specified governor in /etc/init.d/cpufrequtils
a better idea might be to have cpufreq-set itself do the modprobe ... if the set fails, it will execve modprobe on the specified governor ...
ive written a patch and added it to 006 such that cpufreq-set will run `modprobe` if the initial gov write fails
actually, ive dropped my patch. recent kernels will automatically do the same thing (issue a module request when given an unknown gov).