Comment 58 for bug 132271

Revision history for this message
samnmax (aleixmercader) wrote : Re: [Bug 132271] Re: [GUTSY] cpu freq scaling not working anymore

Hi, I'm trying the Hardy Heron LiveCD now. The problem is still the same,
Pentium M 1.6 GHz stuck at 1600 and it won't go down. Same problem in
Windows, so in my case it is a BIOS bug of the laptop, a Quanta ZW9 (Ahtec
X-9600M).

I tried this too:
ubuntu@ubuntu:~$ sudo modprobe speedstep-centrino
FATAL: Error inserting speedstep_centrino
(/lib/modules/2.6.24-2-generic/kernel/arch/x86/kernel/cpu/cpufreq/speedstep-
centrino.ko): No such device
ubuntu@ubuntu:~$ sudo modprobe speedstep-smi
FATAL: Error inserting speedstep_smi
(/lib/modules/2.6.24-2-generic/kernel/arch/x86/kernel/cpu/cpufreq/speedstep-
smi.ko): No such device
ubuntu@ubuntu:~$ sudo modprobe speedstep-ich
FATAL: Error inserting speedstep_ich
(/lib/modules/2.6.24-2-generic/kernel/arch/x86/kernel/cpu/cpufreq/speedstep-
ich.ko): No such device
ubuntu@ubuntu:~$ sudo modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.24-2-generic/kernel/arch/x86/kernel/cpu/cpufreq/acpi-
cpufreq.ko): No such device
ubuntu@ubuntu:~$

So I guess the only solution is the phc patch... :(

2008/1/4, Leann Ogasawara <email address hidden>:
>
> Hardy Heron Alpha2 was recently released. It contains an updated
> version of the kernel. You can download and try the new Hardy Heron
> Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ .
> You should be able to then test the new kernel via the LiveCD. If you
> can, please verify if this bug still exists or not and report back your
> results. General information regarding the release can also be found
> here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!
>
> ** Also affects: linux (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> ** Tags removed: hardy-kernel-candidate
>
> --
> [GUTSY] cpu freq scaling not working anymore
> https://bugs.launchpad.net/bugs/132271
> You received this bug notification because you are a direct subscriber
> of the bug.
>