Ubuntu
powersave package

No Speedstepping module can be loaded

Bug #74274 reported by Sebastian Schulze
8
Affects Status Importance Assigned to Milestone
powersave (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Neither the speedstep_centrino
"FATAL: Error inserting speedstep_centrino (/lib/modules/2.6.17-10-386/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko): No such device"

nor the acpi-cpufreq
"FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.17-10-386/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): Unknown symbol in module, or unknown parameter (see dmesg)"

can be loaded. So the Process always runs at full speed.
Laptop is an Acer Travelmate 4150, with an 1,5 GHz Pentium M.

I am not sure if this is the right place to report this bug,
please tell me, if I should supply more information!

Revision history for this message
Sebastian Schulze (bascht) wrote :

The errormessage, found in dmesg:

[17180549.376000] acpi_cpufreq: Unknown symbol cpu_online_map

Revision history for this message
mathew (meta23) wrote :

Same problem here. Edgy. VIA Nehemiah (C3) processor. Can't load acpi_cpufreq, dmesg shows

[24125816.832000] acpi_cpufreq: Unknown symbol cpu_online_map

Revision history for this message
Rolf Leggewie (r0lf) wrote :

mathew, I believe you may be experiencing bug 45747

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Sebastian, do you still experience this issue?

Changed in powersave:
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

are you guys sure that acpi-cpufreq is the right module? For the C3 processor, I don't think it is. It should be the longhaul module (which unfortunately, does not work for me, either)

Revision history for this message
Sebastian Schulze (bascht) wrote :

Rolf: I can't reproduce it - the Laptop is already sold... :)
And I think the problem was with feisty (2006?) - so maybe this can be closed.

Revision history for this message
Connor Imes (ckimes) wrote :

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!

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

Other bug subscribers

Remote bug watches

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