Building cpufreq modules into F16 kernel is it right or wrong?
Marcos Felipe Rasia de Mello
marcosfrm at gmail.com
Tue Oct 18 16:16:41 UTC 2011
2011/10/18 <alekcejk at googlemail.com>:
> Changing governor can't help me, I need frequency scaling completely disabled.
> cpupower.service starts cpupower which can't set frequency
> which I set in BIOS (slightly overclocked).
> This is cpufreq modules problem because frequency which
> I set is not in range which can be detected by
> cpufreq modules and cpupower.
> I have no such problems only when cpufreq modules not loaded.
> Loading module immediately sets wrong frequency in /proc/cpuinfo
> while real frequency shown by 'cpupower monitor' is equal
> to what I set in BIOS.
> That's why forcing cpufreq module loading by building them
> into kernel is unacceptable for me.
> Loading modules by starting service was more flexible.
> Alexey Kurov <nucleo at fedoraproject.org>
https://bugzilla.redhat.com/show_bug.cgi?id=713572 (you already posted there)
Let's hope the CPU modaliases stuff get done some day.
More information about the devel