speedstep-centrino.ko: missing kernel module in kernel 2.6.20-5.7

Bug #82242 reported by Matej Kenda
4
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned
Declined for Feisty by Henrik Nilsen Omma
Declined for Gutsy by Henrik Nilsen Omma
powernowd (Ubuntu)
Invalid
Undecided
Unassigned
Declined for Feisty by Henrik Nilsen Omma
Declined for Gutsy by Henrik Nilsen Omma

Bug Description

Binary package hint: linux-image-generic

I have upgraded from Edgy to Feisty on a laptop HP Compaq nw8440 and noticed that the kernel module speedstep-centrino was not loaded.

AFAIK, this kernel module should be detected by the /usr/share/powernowd/cpufreq-detect.sh and loaded by the powernowd startup script.

The laptop has processor Intel Centrino Duo. From /proc/cpuinfo

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
stepping : 6
cpu MHz : 1000.000

I have queried installed files on my laptop and packages.ubuntu.com. I have noticed that the kernel package for Edgy contains the driver, however it is missing in the Feisty package.

http://packages.ubuntu.com/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-image-2.6.17-10-generic&version=edgy&arch=i386&page=1&number=all

http://packages.ubuntu.com/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-image-2.6.20-5-generic&version=feisty&arch=i386&page=1&number=all

Revision history for this message
Laurent Bigonville (bigon) wrote :

I think I read somewhere that speedstep-centrino is now deprecated with the kernel version 2.6.20.

acpi_cpufreq now replaces speedstep-centrino

Revision history for this message
Matej Kenda (matejken) wrote :

Laurent, thanks. It's correct that the module is deprecated:

http://kernelnewbies.org/LinuxChanges#head-ca36fd189c53b74e7898a8e4f67fbd82ddd7b664

Revision history for this message
Matej Kenda (matejken) wrote : Shall cpufreq-detect.sh be modified?

The script /usr/share/powernowd/cpufreq-detect.sh would have to be modified to use acpi_cpufreq by default.

I'll take a look at the script.

Changed in linux-meta:
status: Unconfirmed → Rejected
Changed in powernowd:
status: Unconfirmed → Confirmed
Revision history for this message
Cesare Tirabassi (norsetto) wrote :

Quite a lot of people are having problems because of speedstep-centrino being used instead of acpi_cpufreq. Do you think we can make this for Feisty? It looks as a rather important patch.

Revision history for this message
Matej Kenda (matejken) wrote : patched cpufreq-detect.sh

It took a bit longer than I have anticipated to find time to modify cpufreq-detect.sh.

I have tried the following modified script and works for me.

Actually the original script loads acpi_cpufreq also even though it should load speedstep-centrino. I use Intel Centrinu Duo.

Revision history for this message
MaxNegro (maxnegro) wrote :

Hi. I have a Toshiba Satellite SA50-111, with Centrino 1.6GHz. While stepping was working flawlessly in feisty, I tried upgrading to gutsy just to discover that this was no more the case. Tried your patch on cpufreq-detect.sh, but to no avail: it still tries to load cpufreq-speedstep, which fails miserably. Manually loading acpi-cpufreq solves the problem here, but I still think this is a regression bug that needs to be addressed.

From /proc/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 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
bogomips : 1197.96
clflush size : 64

Revision history for this message
MaxNegro (maxnegro) wrote :

Followup on previous comment: I completely forgot checking /etc/default/powernowd. Removing the CPUFREQ option in there, the script works flawlessly. My bad.

Revision history for this message
Matej Kenda (matejken) wrote : Close the bug?

Does this problem still appear in newer releases?
Can this bug be closed?

Revision history for this message
Matej Kenda (matejken) wrote :

It seems that this issue is not present any more. Please reopen the bug if necessary.

Changed in powernowd:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.