F14 cpuspeed / ondemand broken?

["Jóhann B. Guðmundsson"]

On 12/31/2010 04:33 PM, Steven Haigh wrote:
> I reset the BIOS to optimal defaults and fired it up. No real change :(
>

As I mention you might need to turn some knobs in the bios to get this 
working so using the optimal defaults might be causing this ;)

> # modprobe acpi-cpufreq
> FATAL: Error inserting acpi_cpufreq
> (/lib/modules/2.6.35.10-74.fc14.i686/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko):
> No such device
>

File a bug against the kernel any modern Intel CPU should be driven with 
acpi-cpufreq, the reason I asked you to clean out your config is because 
you should not be using "p4-clockmod".

And to hopefully clear up general internet misconception amongst users 
p4-clockmod is a thermal regulation mechanism it is not a speed control 
or power management mechanism the driver does not scale frequency et al 
the only thing it does is thermal throttling.

Why it still exist still beats me p4-clockmod reports are utterly bogus 
they always have been and using it usually result in the computer being 
slower and consuming more power which nobody wants....

> Interesting. Surely this should change to the ondemand governor?!
>

Nope it shouldn't be using any governor which should equal to be using 
the performance governor.

The clockmod code should only be throttling when ACPI indicates that the 
system needs it due to a thermal event.

The only thing you can do since you cant use ondemand is set the cpufreq 
governor to userspace which allows the user, or any userspace 
program running with UID "root", to set the CPU to a specific frequency 
by making a sysfs file "scaling_setspeed" available in the CPU-device 
directory.

>> Check if things work if they dont after bios update and orignal cpuspeed
>> file and after fiddling with power savings, EIST, processor scaling,
>> etc.then boot with cpufreq.debug=7 and test latest kernel .35 .36 .37
>> from koji
> Going to look into this tomorrow.

Great :)

Try the .36 and .37 kernel to see if acpi_cpufreq module loads in those 
kernels then boot with cpufreq.debug=7  and run dmesg > dmesg.txt then 
file a bug report against the kernel attache dmesg.txt along with the 
output from "for x in /sys/devices/system/cpu/cpu0/cpufreq/*;do echo 
$x;cat $x;done && for x in 
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/*;do echo $x;cat $x;done" 
to your report and make note if .36 and .36 work or not

That should provide the maintainer with sufficient info to start working 
on your report.

> It's 3:33am now on 1/Jan/2011 - so
> Happy New Year to all, and lets continue the awesome achievements shown
> in Fedora :

Happy new year!
( still ca three and an half hour to go here on top of the world ) ;)

JBG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/test/attachments/20101231/57ec80c1/attachment.html