This package is obsolete and has been removed from the archive. Closing
associated bugs.
** Changed in: powernowd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This is not an appropriate way to declare a package "obsolete". If you
think a package should not be used, file a bug to get it removed from
the archive and *then* invalidate the bugs.
** Changed in: powernowd (Ubuntu)
Status: Invalid => New
--
powernowd doesn't start with init script
htt
The powernowd package is obsolete, please do not use it. CPU frequency
scaling is now handled by the kernel, so if you still have issues on a
modern release, file a bug against the linux package.
** Changed in: powernowd (Ubuntu)
Status: New => Invalid
--
powernowd doesn't start with ini
See also bug 637845.
--
powernowd doesn't start with init script
https://bugs.launchpad.net/bugs/153186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported should be reproducible with
the live environment of the Desktop CD development release - Maverick
Meerkat. It would help us greatly if you could test with it so we can
work on getting it
Try using kernel cpu stepping instead of powernowd:
http://ubuntuforums.org/showthread.php?t=248867
--
powernowd doesn't start with init script
https://bugs.launchpad.net/bugs/153186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
I agree with Ilya, I was wondering why the init script would not start
powernowd, and if the kernel is supposed to be stepping my CPU by itself
it is not doing it aggressively enough.
--
powernowd doesn't start with init script
https://bugs.launchpad.net/bugs/153186
You received this bug notifica
I noticed that powernowd init script is not doing what the documentation
says it will do. I can't see it load the powernowd daemon with the
default configuration. I tried "ps -e|grep powernowd" and was puzzled
why it won't start. Skimmed all logs for errors and found none.
As written the default b
** Changed in: powernowd (Ubuntu)
Status: Invalid => New
--
powernowd doesn't start with init script
https://bugs.launchpad.net/bugs/153186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
This bug is still marked as Incomplete so we are now going to close this
bug report. Please upgrade to the latest release Karmic 9.10 - If this
bug is still reproducible please reopen the bug by setting the status to
New. Thanks
** Changed in: powernowd (Ubuntu)
Status: Incomplete => Invali
I'm changing it to incomplete because I want to know why only when
variable OPTIONS is equal to '-q' the use_ondemand if verified?
powernowd starts (in intrepid) if OPTIONS='' or OPTIONS='-v', but not when
OPTIONS='-q'
I think that a better method is to do somenthing like set a new var
PREFER_ON
I'm closing this as invalid, because it seems to be the expected behaviour (at
least that powernowd is not used).
I'll provide a patch/debdiff for the other issues mentioned here
(ignore_nice_load and not using the ondemand scheduler if OPTIONS are given for
powernowd).
Please re-open, if I misu
I guess that powernowd does not start, because "use_ondemand" in the
init script is successful.
Matthew said in another bug's comment:
"The ondemand governor can react to load changes more quickly than powernowd
can, so powernowd exits on machines which support ondemand."
(https://bugs.launchpad
13 matches
Mail list logo
