Asus eeepc 900 intel celeron m can support powernowd by manually loading p4-clockmod module. Jaunty Alpha 6 Ubuntu 9.04

Bug #343101 reported by Jean Roberto Souza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
powernowd (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Intrepid by Jean Roberto Souza
Nominated for Jaunty by Jean Roberto Souza

Bug Description

Revision history for this message
Jean Roberto Souza (sjeanr) wrote :

I'm testing the Jaunty Alpha 6 releases and I can see there have been big changes in powernow and/or cpufreq. Namely no cpufreq modules are loaded anymore, powernowd is not present, and yet the kernel still scales the CPU frequency if I use the command sudo modprobe p4_clockmod on terminal.

Revision history for this message
Don Newell (ducky12432) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in powernowd (Ubuntu):
status: New → Invalid
Revision history for this message
Jean Roberto Souza (sjeanr) wrote :

Hello Don Newell! Thank you for your reply! The issue persists unchanged and also affects Lucid.

As requested, the command apport-collect 343101 was applied. The result was:

"Updating problem report"

"No additional information collected"

I suspect I may need to include something else to this command. Could you help me to determine what should I include on this command line?

The following lines are an attempt to provide a clue to what's going on. See attached image, please!

CPU Frequency Scaling Monitor 2.29.5

The problem persists today and it also affects Ubuntu Lucid
Release 10.04 Kernel Linux 2.6.32-17-generic-pae
Gnome 2.29.92

Trying to add CPU Frequency Scaling Monitor to Panel will result on an error message that states as follow:

"You will not be able to modify the frequency of your machine. Your machine may be *misconfigured* or not have hardware support for CPU frequency scaling."

A print screen image of the message is attached to this report.

There are ways to activate this ability by following instructions reported on 2009-03-15. On lucid it will partially allow CPU scaling but the scaling profiles will be messed up. i.e on demand scaling profile will cause it switch to the lowest frequency and keep it there instead of increasing CPU frequency as required.

The problem/Bug

Frequency Scaling Monitor 2.29.5 does not work after it has been added to Panel. It shows an error message and is unable to manage CPU.

How it is supposed to work? How it is expected to work?

Frequency Scaling Monitor 2.29.5 should identify and allow CPU management upon activation. CPU management can greatly improve battery life if enabled.

Thank you for your attention. I will be waiting for any other information request.

Revision history for this message
Jean Roberto Souza (sjeanr) wrote :
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.