UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I recently upgraded to Kubuntu Gutsy from Feisty and CPU scaling no longer works. I have a Pentium M 1.60 gHz processor on a Dell 9300 laptop and it's currently stuck at 800 mHz at all times. Speedstep is enabled in the BIOS and I've tried manually editing the scaling files, following numerous CPU scaling HOWTOS, loading/unloading modules by hand, and cpufrequtils... nada. The min and max freq are the same, no matter what I do.
This seems to be an often posted problem, but I've yet to find anything that works to solve it. I know this is a known bug in the Gutsy kernel, but has anyone found a workaround? Some people ound a temporary solution which only works until the next reboot, but even I haven't had that much success.
Will rolling back to an older kernel fix this until a solution is found, or just muck me up further?
$ cpufreq-info:
Code:
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
/etc/modules:
Code:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
fuse
lp
sbp2
i8k
acpi-cpufreq
cpufreq_conservative
cpufreq_ondemand
cpufreq_powersave
cpufreq_stats
cpufreq_userspace
NOTE: Never needed anything after i8k in Feisty, but I added those just in case.
UPDATE: Nothing's fixed, but I found that it's not a kernel bug like I had thought. I rolled back to 2.6.20-15, the one I used prior to upgrade, and still no scaling.
I'm running Gutsy 2.6.22-14 kernel. This works for me (at least temporarily) - it won't normally let me write to anything in the /sys/devices/system/cpu/cpu0/cpufreq path unless I'm *actually* root, not just 'sudo'. I have a 2GHz T7300 Centrino Duo, which 'ondemand' likes to run at 800MHz most of the time!
The CPU Frequency Monitor widget in my Application Panel under Gnome now tells me I'm running at a constant 2GHz, and obviously checking the scaling_cur_freq tells me that as well.
This is really useful when running Virtual Machines, because if I run under 'ondemand' scaling, I get a very fast clock in the host VM due to difference in expected and actual CPU clock speed.
Hi, I've a turion X2 , when I set "conservative" governor my cpu runs at 800 Mhz (forever) and when I set "ondemand" it runs at 1600 Mhz (forever). I simply I don't know why..(noob :-) )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.