speedstep-centrino driver not working on Pentium-M with ICH6 chipset - acpi-cpufreq driver used instead

Please paste in the contents of:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

For assessing your speedstep-centrino issue, can you paste in the output of /proc/cpuinfo?

Thanks!
  Kyle

On Wed, 2007-06-27 at 17:12 +0000, Kyle McMartin wrote:
> Please paste in the contents of:
>
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver

acpi-cpufreq

> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

performance

> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

1600000 1400000 1200000 1000000 800000 600000

> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

600000

> For assessing your speedstep-centrino issue, can you paste in the output
> of /proc/cpuinfo?

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.60GHz
stepping : 8
cpu MHz : 600.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up est tm2
bogomips : 1198.73
clflush size : 64

Same thing here

jejem@laptop:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.86GHz
stepping : 8
cpu MHz : 800.046
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up est tm2
bogomips : 1601.69
clflush size : 64

root@laptop:~# modprobe speedstep-centrino
FATAL: Error inserting speedstep_centrino (/lib/modules/2.6.22-7-generic/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko): No such device

My understanding is that speedstep-centrino is deprecated, since acpi-cpufreq now has all the native access that only speedstep-centrino used to give...

root@laptop:~# modprobe speedstep-centrino
FATAL: Error inserting speedstep_centrino (/lib/modules/2.6.22-8-generic/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko): No such device

root@laptop:~# modprobe speedstep-centrino
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.22-8-generic/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device

it returns the same error, so, no, speedstep-centrino isn't deprecated because of acpi-cpufreq...

That's weird... my laptop does this:

jon@nick:~$ sudo modprobe speedstep-centrino
[sudo] password for jon:
FATAL: Error inserting speedstep_centrino (/lib/modules/2.6.22-8-generic/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko): No such device
jon@nick:~$ sudo modprobe acpi-cpufreq
jon@nick:~$

Thanks for the output values. Confirming.

I also have this same problem, even using 2.6.20-16, but acpi-cpufreq solves it. speedstep-centrino doesn't work.

My understanding is, even though acpi-cpufreq may have its own problems (I don't see it here), it seems to work mostly when speedstep-centrino doesn't even work at all.

Computer: Lenovo Y400, 1.73 GHz Core Duo

ceefour@ojalanow:~$ uname -a
Linux ojalanow 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux
ceefour@ojalanow:~$ for i in `cat` ; do cat $i ; done
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

acpi-cpufreq
ondemand
1733000 1333000 1067000 800000
800000

ceefour@ojalanow:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Intel(R) Core(TM) Duo CPU T2250 @ 1.73GHz
stepping : 12
cpu MHz : 800.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr
bogomips : 3462.92
clflush size : 64

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Intel(R) Core(TM) Duo CPU T2250 @ 1.73GHz
stepping : 12
cpu MHz : 800.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr
bogomips : 3458.28
clflush size : 64

I had the same trouble after I upgraded to Gutsy. I did some homework and found out that yes speedstep-centrino is depricated in favor of acpi-cpufreq. One side effect of this, at least on my laptop, was that speedstep-centrino worked without SpeedStep being turned on in the BIOS. So when the new kernel was trying to load acpi-cpufreq it found that SpeedStep was disabled and didn't load it. That's why there weren't any errors.

So I went into the BIOS set SpeedStep to automatic and now it works flawlessly.
Hope this helps.

It could help if i had the "SpeedStep" setting in my BIOS, but i haven't...

Can only change date/time, passwording stuff and things aboot quick/quiet boot, nothing else :(

Still "locked" at 800mhz... damn :(

Found a "Long battery life mode" option, which was enabled...

Disabling it delocks acpi-cpufreq, everything works well now, 1.8Ghz is back again, YEAH! :)

Thanks Roger Wood for your tip ;)

You're welcome, glad to help.

Computer: Gericom Blockbuster Excellent 7000 251A7 with Pentium M Dothan 1,6GHz

#################################
coolplayer@gericom:/proc$ cat cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.60GHz
stepping : 6
cpu MHz : 600.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
bogomips : 1205.01
clflush size : 64
#################################

I did the following to get linux-image-general in version 2.6.22-14.52 to work agaein after an update from an older 2.6.22-14:
- Debugged and replaced my ACPI-DSDT-table according to this how-to: http://wiki.ubuntuusers.de/acpi-fix (it workes without, too)
- tried to load speedstep-centrino and acpi-cpufreq with no success
- went into my BIOS and chosen the option "Load optimized defaults" multiple times and saved the settings
- after a reboot I re-adjusted the settings (boot range and so on) to my preferences

Now, it works again. Maybe, it will help someone here.

Results:
$ cat scaling_driver
acpi-cpufreq

$ cat scaling_governor
ondemand

 cat scaling_available_frequencies
1600000 1400000 1200000 1000000 800000 600000

$ cat scaling_cur_freq
600000

Hi all!

I experienced pretty much the same troubles earlier: my PentiumM 750 1.86GHz was stuck on 800 Mhz and acpi-cpufreq was not able to change frequency in spite of the fact speedstep was enabled in BIOS, but speedstep_centrino module couldn't be loaded due to "No such device" error.
It seemed that BIOS hadn't report valid CPU frequencies correctly or I had had some another issues with ACPI system.

So here is the speedstep-centrino.c patch which is based on linux-phc-0.2.10 and adopted to vanilla 2.6.24 kernel by one friend of mine.
It doesn't use ACPI info in its work, so it can fix the problem with broken ACPI or BIOS functionality. Moreover, it might be useful when you are not able to change speedstep settings from BIOS but want to use speedestep anyway.

Patch also adds some new options to the kernel, which needs to be answered 'Y'.

I hope this might be useful for fixing similar problems.

WBR,
Ivan N. Veselov.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!