LizardMan wrote:
It seems to work fine until a power state
change occurs. Unplugging the AC adapter or plugging it in causes the
CPU scaling to lock in 100% mode again.
This is because gnome-power-manager kicks in and activates its profile
for AC power / battery mode and sets the governor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
LizardMan wrote:
My Thinkpad A22p (1GHzP3 440BX chipset) laptop has the same problem.
While running 7.10 the CPU freq throttling worked correctly without
requiring any configuration changes. However, when I upgraded to 8.04
the CPU began to run
You CANNOT use a blacklist for this! On PowerPC, there is a scaling
driver that both supports and doesn't support ondemand, depending on the
specific hardware. The ONLY correct solution is the first idea you had,
but with a better patch. Combine the gconf stuff from your patch with
the patch in
Hanno Stock,
After a fresh system start cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver returns speedstep-
smi.
Running /etc/init.d/powernowd stop; cpufreq-selector -g userspace;
powernowd -q (as root) returns the laptop to 7.10 style CPU freq scaling
(two steps 700/1000 MHz). It seems
This problem isn't limited to nforce chipsets.
My Thinkpad A22p (1GHzP3 440BX chipset) laptop has the same problem.
While running 7.10 the CPU freq throttling worked correctly without
requiring any configuration changes. However, when I upgraded to 8.04
the CPU began to run at full speed
The command sequence in the comment above works, until the laptop
changes power states due to disconnecting the AC adapter. All power
state changes seem to trigger this problem, until the cpufreq-selector
and powernowd -q commands are re-run.
--
[hardy] Regression: powernowd no longer works
Dmitry,
sorry, this patch didn't make it into 8.04.1.
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Sorry, can't understand from this discussion if this patch was committed
to 8.04.1 or not?
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here is a debdiff for intrepid.
** Attachment added: patch for intrepid
http://launchpadlibrarian.net/15763875/powernowd_1.00-1ubuntu2.debdiff
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this bug
Here is an updated patch with the dependency on gconf removed.
Thanks for the input and also sorry for replying so late.
** Attachment added: Updated patch with dependency on gconf removed
http://launchpadlibrarian.net/15567277/powernowd_0.97-2ubuntu5.debdiff
--
[hardy] Regression:
gconf is not present on Kubuntu machines. Can you remove the strict
dependency on gconf and rework the patch to use type to check for the
presence of gconftool-2 instead?
Thanks and sorry for being horrendously late in replying.
--
[hardy] Regression: powernowd no longer works with nforce2
Joel,
it seems that your setup is not using the nforce2 cpufreq driver, but
the powernow-k8 driver - which is correct, I think, since the Athlon64
X2 supports PowerNow. (My Athlon XP does not)
So I guess your problem is a different one with similar symptoms only. I
noticed that I also have the
Sorry, for some reason the important stuff was cut of the end of
/var/log/dmesg and only shows up in dmesg itself.. (Is this normal?)
** Attachment added: dmesg continued
http://launchpadlibrarian.net/14453362/dmesg.cont
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq
I can report the same problem. I used to cat /proc/sys/cpuinfo and see
1000MHz on both cores unless I ran burnK7... Then it would jump to 2200
like it was supposed to. Setting in gnome to Based on processor load
is the same as Always maximum speed
Setting it at Max power saving keeps it at 1000
Here is an updated debdiff:
* In the init script I changed the code so that it specifically checks for the
nforce2 driver. This makes it less generic (in case other drivers have a
similar issue), but more reliable against timing issues.
* In post{inst,rm} I added code that installs mandatory
My results so far:
I suspect the gnome-power-manager of changing the cpufreq governor.
I had the ac power cpufreq governor setting set to nothing, while another
user had it set to ondemand. The change of cpufreq governor seemed related to
the other user using the computer.
I have now set the
Update:
From syslog:
May 9 13:26:21 HANNO kernel: [ 3355.797659] ondemand governor failed, too long
transition latency of HW, fallback to performance governor
Finger:
Login NameTty Idle Login Time Office Office Phone
xxx xxx tty9 18 May 9 13:26 (:20)
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:
No such file or directory
I get the error message mentioned above, too. But powernowd works
regardless of this message. Could you please verify via the cpu speed
applet (don't know the correct english name) that it is actually
I checked it, and whenever I select Ondemand governor with the applet,
it does not work. Instead, the applet switches to performance mode.
Yes, that's right. The ondemand governor does not work with the nforce2
driver. Actually, when ondemand is used, powernowd (the daemon) is not
used at all.
Hanno, great work so far. Let me know via a comment on this bug when
you've got an updated debdiff, should you fix the other issues, and I'll
sponsor the upload.
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: No
such file or directory
I get the error message mentioned above, too. But powernowd works
regardless of this message. Could you please verify via the cpu speed
applet (don't know the correct english name) that it is actually
Evan: can you please take a look at it?
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Similar problem here, but Hanno's solution does not work:
$ sudo powernowd -q
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: No such
file or directory
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You
I think I found a solution...
** Changed in: powernowd (Ubuntu)
Assignee: (unassigned) = Hanno Stock (hefe_bia) (hanno-stock)
Status: New = In Progress
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received
Here is a debdiff that fixes the above issue by testing whether the
ondemand governor has really been loaded and else switching back to
powernowd.
Please test on a system where ondemand would usually work, since I don't
own such a system and therefore cannot test this setup.
** Attachment added:
Subscribing ubuntu-main-sponsors, since I'm not sure whether this is worth a
SRU.
But I think this should be fixed in 8.04.1.
--
[hardy] Regression: powernowd no longer works with nforce2 cpufreq driver
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a
26 matches
Mail list logo
