>> 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" ( :-) ):
> 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?