CPU at maximum speed when connected to AC

[Eagle2]

Binary package hint: kernel-image-2.6.20-8-386-di

Hello, here's the problem. I've an ASUS A6VA laptop with an Intel Centrino to 1,73 GHz. When the laptop is connected to the AC, the CPU works ONLY and ALWAYS at 1,73 GHz, even with the "Ondemand" option on. It should jump between 4 steps, but it doesn't do that. The only solution I've found is to compile my own kernel leaving only my CPU as supported. The point is that it always worked with other distros without compile another kernel. So...maybe it's possible, could you make something to resolve this or, is it a kernel bug?

Best Regards.

[Cristian Aravena Romero (caravena)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

[Eagle2 (davide-barbuto)]

Hello, sorry I didn't know about the DebuggingKernelProblems wiki.

Here're my outputs:

1) uname -a:

Linux ubuntux-laptop 2.6.20-custom #1 Sun Feb 11 02:01:48 CET 2007 i686 GNU/Linux

As I wrote you, this "2.6.20-custom" is my customized kernel, and if you need it, I can send you the kernel.config

2-3) logs attached

[Eagle2 (davide-barbuto)]

Second log...

Thanks again for your answer.

Best Regards

[Ben Collins (ben-collins)]

dmesg shows this was using the old speedstep cpufreq driver. Your system should now be using the acpi-cpufreq driver due to a fix that went in since this bug was reported.

[Eagle2 (davide-barbuto)]

Sorry to say this, but I still have the same problem, I've Feisty up to date with the latest updates and kernel... I don't know what it can be...

[Eagle2 (davide-barbuto)]

I'm sorry but it still doesn't work...updated again this night...

[Ben Collins (ben-collins)]

I've made some commits in the past few days that will be uploaded and available some time early next week that should fix this.

[Eagle2 (davide-barbuto)]

I don't know if the fix has been already released, but until now (with ubuntu all updated, of course), it still doesn't work...just to let you know...

Thanks

[Djembe (djemberob)]

It looks like bug 99059 https://bugs.launchpad.net/bugs/99059 is the same as this.

[Strash (strash)]

Feisty is out and the problem still remain...

Is there any solution ??

[Strash (strash)]

I finally find a way to solve this problem !

I now use the kernel -i386 instead of the -generic ! And CPU scaling works now both on AC and battery.

If devel can find what was wrong with the generic kernel...

[Eagle2 (davide-barbuto)]

With Gutsy all work for me...