[opensuse] Successor for former powersave package?
In older openSUSE and SLES versions there was a package called "powersave": https://www.suse.com/documentation/sles10/book_sle_reference/data/sec_powers... Especially the schema settings were useful, if an admin wanted to enable some powersaving features without detailed configuration. An example: /etc/sysconfig/powersave/common: AC_SCHEME="performance" BATTERY_SCHEME="powersave" Is there any good alternative for this package, especially for computers without a GUI? The package is gone. I already know the Powertop tool which does a good job, but it's interactive. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 15. April 2015, 23:57:07 schrieb Bjoern Voigt:
[...] Especially the schema settings were useful, if an admin wanted to enable some powersaving features without detailed configuration. [...] Is there any good alternative for this package, especially for computers without a GUI?
So you have got a laptop and without a GUI and want to do some powersaving? What exactly do you need? Because the old powersave package did many different things. And not all of them are still useful today. E.g. cpufreq. And the thermal control settings did not always work. However, without a GUI, the powersave package offered some useful things that are not directly related to powersaving: * executing actions depending on the battery state, e.g., shut down if only 2% battery are left * assigning actions to special buttons, e.g., the power button The latter is now handled by systemd (and not acpid anymore), see "man logind.conf". Furthermore, logind lets you define idle actions like suspend after 5 minutes.
The package is gone. I already know the Powertop tool which does a good job, but it's interactive.
There are the packages tlp and laptop-mode-tools. However, I stopped using them. Most of these powersaving options are not worth the effort. Many powersaving options are already activated by default today. And these that are not, might crash your SSD (SATA Link Power Management) or occasionally slow down your Intel WiFi to 54 Mbps after a suspend/resume cycle (iw dev wlp3s0 set power_save on). Gruß Jan -- Good fences make good neighbors. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/01/2015 07:09 AM, Jan Ritzerfeld wrote:
There are the packages tlp and laptop-mode-tools. However, I stopped using them. Most of these powersaving options are not worth the effort. Many powersaving options are already activated by default today. And these that are not, might crash your SSD (SATA Link Power Management) or occasionally slow down your Intel WiFi to 54 Mbps after a suspend/resume cycle (iw dev wlp3s0 set power_save on).
I wonder. For those of us that never turn off our computers (be they laptops, workstations or tablets) is there 'throttling'? I know when I wake up my tablet there's a slight delay then I get told its connected to my wifi and bluetooth. So when the screen shits down _ some delay those get turned off. Well that makes sense for tablets and phones. Does it make sense for laptops? Workstations? Those might be 'servers' or might need to run cron jobs. So is throttling and 'on-demand' more useful? Throttle back after midnight ... Of course any 'activity', keyboard, mouse, other, will need to wake it up. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Freitag, 1. Mai 2015, 07:52:43 schrieb Anton Aylward:
[...] For those of us that never turn off our computers (be they laptops, workstations or tablets) is there 'throttling'?
I know when I wake up my tablet there's a slight delay then I get told its connected to my wifi and bluetooth. So when the screen shits down _ some delay those get turned off.
Some mobile OS shut down WiFi if there is a cellular connection available. Keeping two connections to the internet while being idle is wasteful and the cellular connection is needed anyway for incoming calls.
Well that makes sense for tablets and phones.
This smartphone and tablet "throttling" needs explicit application support: http://www.kandroid.org/online-pdk/guide/power_management.html When developing a mobile app you have many "new" things to consider in contrast to a desktop application. For example, your app must be ready for being shutdown or swapped out at any time automatically. Or it must deal with frequent loss of WiFi or cellular connectivity. You should use push notifications instead of polling or a permanent TCP connection.
Does it make sense for laptops? Workstations?
It would, but every single applications must support such an aggressive power management.
Those might be 'servers' or might need to run cron jobs.
Android OS has an built-in AlarmManager that is used for running code at a specific time: http://developer.android.com/reference/android/app/AlarmManager.html However, the OS shifts alarms if that would minimize wakeups and battery use.
So is throttling and 'on-demand' more useful? Throttle back after midnight ...
The only way I can think about for normal laptops and workstations is to activate all the runtime power management, suspend on idle, WoL to resume when needed, and rtcwake for regular cron jobs.
Of course any 'activity', keyboard, mouse, other, will need to wake it up.
Well, here, only some keys wakeup my laptop. Gruß Jan -- Life is tough, life is tougher when you're stupid. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
Bjoern Voigt -
Jan Ritzerfeld