On Monday 23 August 2010 13:28:35 Sebastian Kügler wrote:
On Friday 20 August 2010 10:10:42 Nico Kruber wrote:
On Friday 20 August 2010 08:58:59 Sven Burmeister wrote:
Am Freitag, 20. August 2010, 07:39:58 schrieb Divan Santana:
On Thursday 19 August 2010 23:45:00 Markus Slopianka wrote:
AFAIK this was a concious decision and if I'm not mistaken, this is the
reason:
I actually wasn't trying to clock down the cpu but rather set the cpu from ondemand(default on plugged in mode) to performance so it's always at full throttle since that is best for me. Like I said I could easily do this before, however with 4.5.0 packages the option is missing. Would be great if that could be fixed...
That won't happen because it is not a bug. You will have to search the kde (not opensuse-kde) mailinglists archives for the explanation but the setting did not make sense, neither for increasing cpu performance nor for saving battery.
Indeed, it's a red herring, even the kernel devs advised removing it, so we did. Use ondemand.
actually it makes sense for bugs like this: http://bugs.winehq.org/show_bug.cgi?id=13486
also in regard to rogue processes consuming 100%CPU (if you notice that within a minute, having the CPU on low power will probably have consumed much less energy)
Applications that rely on the CPU frequency being constantare so eighties. Ask their developers to fix them.
I'm not willing to optimize the UI for applications that hang, either.
Notice that I'm not saying it's impossible to set the CPU to a specific governor, the power management KCM still support that. We only removed misleading options from the UI, users that want them can still emulate it using scripts triggered by powerdevil.
but ideally I'd agree with this setting being removed (having to execute a possibly unknown (to the user) command for this is also not ideal - especially if the feature has been around before)
Not feature, but *misfeature*, judging by contemporary Linux kernel and CPU characteristics.
Cheers,
well, I can live with it (and work around if needed) - just wanted to add some of my experience with this "feature" and how (possibly not only I) was using it... Possibly someone could wrap this up into a plasmoid - that way it's still accessible but not by default... Remember, there are a lot of such "battery optimisation tools" around in the Windows-world, too - a user might look out for it... Nico