On Wednesday 21 November 2007 16:52:39 tk23 wrote:
> A quick-and-dirty fix is reloading the kernel module "acpi_cpufreq":
> $ modprobe -rv acpi_cpufreq
> $ modprobe -v acpi_cpufreq
That doesn't seem to help in my case:
root@buznote:~# modprobe -r acpi_cpufreq && modprobe -v acpi_cpufreq
root@buznote:~# cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 800 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand,
performance
current policy: frequency should be within 800 MHz and 2.00 GHz. The governor "ondemand" may decide which speed to use within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
On Wednesday 21 November 2007 16:52:39 tk23 wrote:
> A quick-and-dirty fix is reloading the kernel module "acpi_cpufreq":
> $ modprobe -rv acpi_cpufreq
> $ modprobe -v acpi_cpufreq
That doesn't seem to help in my case:
root@buznote:~# modprobe -r acpi_cpufreq && modprobe -v acpi_cpufreq
The governor "ondemand" may decide which speed to use
within this range.
root@buznote:~# cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 800 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand,
performance
current policy: frequency should be within 800 MHz and 2.00 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU