Me, too, on a Latitude D620 with Duo 2 CPU (2GHz), running 9.10 Karmic (2.6.31-17-generic).
But with a twist.
After booting, cpufreq-info shows that all is well: the ondemand governor is managing steps between 1GHz and 2GHz, the machine is humming along, moving to higher or lower steps as needed.
But after a certain amount of time, something (acpi-cpufreq?) automatically changes those settings and I am stuck on the lowest setting on both CPU 0 and CPU 1:
política atual: a frequência deveria estar entre 1000 MHz e 1000 MHz. O governor "userspace" deve decidir qual velocidade usar dentro desse limite.
(My machine speaks Portuguese, but you can see that the interval is between 1GHz and 1GHz. I changed the governor to userspace in a bid to manually set freq to 2GHz with echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
or cpufreq-selector -f 2000000)
I have seen many similar complaints in the forums.
BIOS has no settings like the ones mentioned by everflux (note #23).
I have uninstalled all cpufreq demons (kpowersave, cpudyn, cpufreqd, powernowd).
Me, too, on a Latitude D620 with Duo 2 CPU (2GHz), running 9.10 Karmic (2.6.31- 17-generic) .
But with a twist.
After booting, cpufreq-info shows that all is well: the ondemand governor is managing steps between 1GHz and 2GHz, the machine is humming along, moving to higher or lower steps as needed.
But after a certain amount of time, something (acpi-cpufreq?) automatically changes those settings and I am stuck on the lowest setting on both CPU 0 and CPU 1:
política atual: a frequência deveria estar entre 1000 MHz e 1000 MHz. O governor "userspace" deve decidir qual velocidade usar dentro desse limite.
(My machine speaks Portuguese, but you can see that the interval is between 1GHz and 1GHz. I changed the governor to userspace in a bid to manually set freq to 2GHz with echo 2000000 > /sys/devices/ system/ cpu/cpu0/ cpufreq/ scaling_ cur_freq
or cpufreq-selector -f 2000000)
I have seen many similar complaints in the forums.
BIOS has no settings like the ones mentioned by everflux (note #23).
I have uninstalled all cpufreq demons (kpowersave, cpudyn, cpufreqd, powernowd).
Canonical Kernel Team, ride to the rescue!