Here is the updated debdiff for Jaunty.
I removed the g-p-m stuff and updated the package description. Should
apply to intrepid package also, since it is the same version.
Gatopeich: While I agree that it is somewhat misleading to hijack the
powernowd package, changing that is beyond the scope
This bug was fixed in the package powernowd - 1.00-1ubuntu3
---
powernowd (1.00-1ubuntu3) jaunty; urgency=low
* debian/init.d: Don't use ondemand governor if it is not working
for the particular hardware. Thanks to Daniel Gimpelevich for the
improved patch. (LP: #223812,
I see. According to you...
* The fix is wrong (essentially because it makes the package do what
description says).
* Package description is wrong (apparently in order to support your
previous assertion).
* Package name is wrong too, it should be named anything-is-better-
than-powernowd.
*
What you are proposing is hijacking powernowd package for a purpose
which would be better acomplished in other ways.
No, I'm informing you that this is *already* the purpose of the package
in Ubuntu. And ondemand *is* better than powernowd (see what upstream
kernel power management developers
gatopeich's proposed fix is incorrect. The powernowd package in Ubuntu
implements Ubuntu's default power management policy, which
/deliberately/ does not use powernowd+cpufreq_userspace if a better
governor (ondemand) is available. So that init script would be a
definite regression in another
This bug is also reproducible on my ibook: The /etc/init.d/powernowd
script exits gracefully thinking that the ondemand govenrnor has been
loaded when it actually failed.
I fixed the script by not checking the ondemand stuff and just running
powernowd.
--
[hardy] Regression: powernowd no longer
** Changed in: powernowd (Ubuntu)
Importance: Undecided = High
Status: Confirmed = Triaged
--
[hardy] Regression: powernowd no longer works with some chipsets
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Marking as invalid for gnome-power-manager. This doesn't seem to be
related to gnome-power-manager.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
[hardy] Regression: powernowd no longer works with some chipsets
https://bugs.launchpad.net/bugs/223812
You received
** Tags added: regression-release
--
[hardy] Regression: powernowd no longer works with some chipsets
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs
I hit this bug after upgrading an IBM Thinkpad T22, and I can confirm
that gatopeich's fixed /etc/init.d/powernowd file appears to have fixed
it.
--
[hardy] Regression: powernowd no longer works with some chipsets
https://bugs.launchpad.net/bugs/223812
You received this bug notification because
I also confirm that gatopeich's version of the powernowd script works
for me also.
A small secondary effect is that the gnome cpufreq-applet does not allow
to change the governor. Instead of proposing powersave, performance and
so on..., it only shows performance which actually throttles the
Daniel Gimpelevich wrote:
Also, I think the gnome-power-manager package should be changed to
default to nothing instead, because then, it would still be OK to
install after powernowd, [...]
I think that could be an option. But this way g-p-m would do nothing
even if powernowd is not
On Thu, 2008-07-17 at 12:46 +, Hanno Stock (hefe_bia) wrote:
So there are several options:
1) disable all power management in g-p-m.
2) disable power management in g-p-m by default, but let users change
it.
3) disable power management in g-p-m only when powernowd is installed,
which is
Daniel Gimpelevich schrieb:
On Thu, 2008-07-17 at 12:46 +, Hanno Stock (hefe_bia) wrote:
So there are several options:
1) disable all power management in g-p-m.
2) disable power management in g-p-m by default, but let users change
it.
3) disable power management in g-p-m only when
14 matches
Mail list logo
