TDE Powersave offers 4 states according to the source (factually 3 on my system): * Suspend2RAM -- this is obvious * Suspend2Disk -- obvious, too * Freeze -- hmm, anybody knowing what this actually is? (in the code it uses the Suspend2RAM icons but calls it's own method) * Standby -- according help this is either a DPMS screen standby with the system otherwise running on power or combined with a Suspend2RAM??? What is it really?
And I'm wondering where my most favourite suspend mode is hidden:
"Suspend2Both" aka "Hybrid Suspend"
This mode sets up the swap area as for Suspend2Disk AND then does a Suspend2RAM. The net effect is, that you normally have quick resume from RAM, but should power fail, nothing is lost as you can resume from disk. Essentially a failsafe suspend ... Its the only suspend-mode I you for desktop systems, and my prefered mode for laptop lid-close action as it always does "the right thing" (at little cost).
So, is "Freeze"="Suspend2Both" or can we introduce "Suspend2Both" (if the machine and swap configs allows)?
ciao, ThoMaus
state: Suspend-To-Idle ACPI state: S0 Label: "freeze"
This state is a generic, pure software, light-weight, system sleep state. It allows more energy to be saved relative to runtime idle by freezing user space and putting all I/O devices into low-power states (possibly lower-power than available at run time), such that the processors can spend more time in their idle states.
This state can be used for platforms without Power-On Suspend/Suspend-to-RAM support, or it can be used in addition to Suspend-to-RAM (memory sleep) to provide reduced resume latency. It is always supported.
On 25 February 2016 at 09:23, Thomas Maus thomas.maus@gmx.de wrote:
TDE Powersave offers 4 states according to the source (factually 3 on my system):
- Suspend2RAM -- this is obvious
- Suspend2Disk -- obvious, too
- Freeze -- hmm, anybody knowing what this actually is? (in the code it uses
the Suspend2RAM icons but calls it's own method)
- Standby -- according help this is either a DPMS screen standby with the
system otherwise running on power or combined with a Suspend2RAM??? What is it really?
And I'm wondering where my most favourite suspend mode is hidden:
"Suspend2Both" aka "Hybrid Suspend"
This mode sets up the swap area as for Suspend2Disk AND then does a Suspend2RAM. The net effect is, that you normally have quick resume from RAM, but should power fail, nothing is lost as you can resume from disk. Essentially a failsafe suspend ... Its the only suspend-mode I you for desktop systems, and my prefered mode for laptop lid-close action as it always does "the right thing" (at little cost).
So, is "Freeze"="Suspend2Both" or can we introduce "Suspend2Both" (if the machine and swap configs allows)?
ciao, ThoMaus
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Donnerstag, 25. Februar 2016, 10:22:22 wrote Calvin Morrison:
state: Suspend-To-Idle ACPI state: S0 Label: "freeze"
This state is a generic, pure software, light-weight, system sleep state. It allows more energy to be saved relative to runtime idle by freezing user space and putting all I/O devices into low-power states (possibly lower-power than available at run time), such that the processors can spend more time in their idle states.
This state can be used for platforms without Power-On Suspend/Suspend-to-RAM support, or it can be used in addition to Suspend-to-RAM (memory sleep) to provide reduced resume latency. It is always supported.
Thanks for this clarification!
Where in the source (and how) could I've found that (trying to learn to find my way around myself, at least a little bit ...)
To avoid a possible misunderstanding by the flurry of bug reports I produce at the moment: I'm just making the "Grand Tour" through TDE, taking note of all rough edges. Please take the flood of critic reports as sign of care and appreciation of the project.
I will then raise a bug report concerning the documentation (which I could perform in english and german, given some guidance) and an improvement request concerning Suspend2Both ...
ciao,
ThoMaus
On Thursday 25 of February 2016 19:35:24 Thomas Maus wrote:
I will then raise a bug report concerning the documentation (which I could perform in english and german, given some guidance) and an improvement request concerning Suspend2Both ...
ciao,
ThoMaus
Yes currently modes are identical to those offered by /sys/power/state. Therefore Suspend2both is not between them. But surely it would be useful provide even such a mode.
Please fill bug report for feature request :)
This state is a generic, pure software, light-weight, system sleep state. It allows more energy to be saved relative to runtime idle by freezing user space and putting all I/O devices into low-power states (possibly lower-power than available at run time), such that the processors can spend more time in their idle states.
Where in the source (and how) could I've found that (trying to learn to find my way around myself, at least a little bit ...)
Thanks to my "Google Ph.D" ( :-) ): https://www.kernel.org/doc/Documentation/power/states.txt
To avoid a possible misunderstanding by the flurry of bug reports I produce at the moment: I'm just making the "Grand Tour" through TDE, taking note of all rough edges. Please take the flood of critic reports as sign of care and appreciation of the project.
I assure you that your comments are more than welcomed and taken exactly in the way you described. Please continue in your scrupulous TDE dissection, that is exactly what we need! Just keep in mind what I already said and do not grow tired if some of the bugs are not look after for months. We do what we can.
I will then raise a bug report concerning the documentation (which I could perform in english and german, given some guidance) and an improvement request concerning Suspend2Both ...
Suspend2Both sounds very interesting. Honestly I did not know about that. Slavek, I think we should look at adding this for R14.1.x, I hate failed suspend-to-ram sessions.
Thomas, please fill as many bug reports about issues as you see fit. That is the only way to constantly improve! Thanks for your effort.
Just wondering, have you recently moved from Suse KDE 3 to Trinity?
Cheers Michele
On Friday 26 February 2016, 22:37 wrote Michele Calgaro:
...
Where in the source (and how) could I've found that (trying to learn to find my way around myself, at least a little bit ...)
Thanks to my "Google Ph.D" ( :-) ): https://www.kernel.org/doc/Documentation/power/states.txt
;-)
Well, I meant of course TDE sources, because I do not take for granted -- occupational habit ;-) -- that the use of identical terms in TDE and the kernel gurantees, that TDE actually triggers the corresponding kernel functionality. So I always sleep better, when I've seen it in the source. (Use the Source, Luke! ;-)
To avoid a possible misunderstanding by the flurry of bug reports I produce at the moment: I'm just making the "Grand Tour" through TDE, taking note of all rough edges. Please take the flood of critic reports as sign of care and appreciation of the project.
I assure you that your comments are more than welcomed and taken exactly in the way you described. Please continue in your scrupulous TDE dissection, that is exactly what we need!
Glad to hear this.
Just keep in mind what I already said and do not grow tired if some of the bugs are not look after for months. We do what we can.
I've survived nigh on 4 decades as computer scientist and professional not by being impatient.
The same will be true for my icon drafts ;-)
I will then raise a bug report concerning the documentation (which I could perform in english and german, given some guidance) and an improvement request concerning Suspend2Both ...
Suspend2Both sounds very interesting. Honestly I did not know about that. Slavek, I think we should look at adding this for R14.1.x, I hate failed suspend-to-ram sessions.
Cast an eye on 'systemd', 'logind' and especially '/etc/systemd/logind.conf' ...
Thomas, please fill as many bug reports about issues as you see fit. That is the only way to constantly improve! Thanks for your effort.
You're welcome.
Just wondering, have you recently moved from Suse KDE 3 to Trinity?
That is a little bit more complicated: Not counting touch-screen devices, I herd a score of systems -- 4 alone for professional use ...
In the wake of the KDE3->KDE4 transition disaster a few systems stayed on recent Evergreen versions still supporting KDE3, while my professional systems moved to KDE4 when it became stable and usable again around 4.5. Recently, with the advent of new machines, end-of-support and staleness of some Evergreens, I decided to consolidate the herd on Tumbleweed -- just to find myself in the KDE4->KDE5 transition disaster ...
I have always done subliminal Linux promotion in my customer base by sporting tools and desktops showing innovative functionality, missing in M$.
With Plasma5 crashing several times a day, and the only positive I have to say about "Plasma5 Breeze" is, that they managed to finally bring the "Leaning Toothpick Syndrome" to the desktop, KDE5 is definitely not suited for this subliminal Linux promotion anymore ... And, -- having learned that KDE has not learned from the KDE3->KDE4 fracas -- I will definitely not give KDE opportunity to wreak havoc with my working environment anymore ...
Having done a Grand Tour through all current Linux desktops, I was devastated: Only 2 really useful, flexible, and powerful options remained -- XFCE and Trinity TDE. I'm strongly in favor of dual-source concepts, so I will support the survival of TDE, and hopefully its rise to an official "distro desktop" ...
What is the state of code sharing or cooperation between Trinity and the (in my perception former and stale?) OpenSuSE KDE3.5 efforts? Hopefully no ill feelings?
ciao,
ThoMaus
In the wake of the KDE3->KDE4 transition disaster a few systems stayed on recent Evergreen versions still supporting KDE3, while my professional systems moved to KDE4 when it became stable and usable again around 4.5.
<snip> Having done a Grand Tour through all current Linux desktops, I was devastated: Only 2 really useful, flexible, and powerful options remained -- XFCE and Trinity TDE. I'm strongly in favor of dual-source concepts, so I will support the survival of TDE, and hopefully its rise to an official "distro desktop" ...
I was on Debian but I also went through a similar path in the past. KDE 3.5 was great, KDE4 was not even worth being called a DE when it was first released (although around 4.6 or 4.7 it was again usable), switched to Gnome 2 until the even more disastrous Gnome 2->Gnome 3 transition. Then XFCE for a couple of years but I always felt somehow limited by its small footprint (but I consider it a great DE). Then by chance I discovered TDE and never looked back anymore :-)
Cheers Michele
-
Calvin Morrison -
Michele Calgaro -
Slávek Banko -
Thomas Maus