Version: (using Devel) OS: Linux Installed from: Compiled sources Hybrid suspend provides the same short resume time as normal STR while protecting against battery drain same as STD does. Tadeoff is slightly longer suspend time which is usually acceptable (you close lid and do not care whether it takes 10 seconds or 2 minutes to complete). Hybrid suspend is fully supported by HAL and pm-utils so integrating is is mostly the matter of extra selection in GUI.
Can you please give me some more pointers to that? I'm definitely interested in implementing that
From lshal: org.freedesktop.Hal.Device.SystemPowerManagement.method_names = {'Suspend', 'SuspendHybrid', 'Hibernate', 'Shutdown', 'Reboot', 'SetPowerSave'} (string list) org.freedesktop.Hal.Device.SystemPowerManagement.method_signatures = {'i', 'i', '', '', '', 'b'} (string list) What it does, is to save image to disk (like Hibernate does) and then suspend. So as long as you have enough power you just resume as usual; if battery is empty, does normal resume from disk.
I'm taking care of this, though I'm changing component since the implementation belongs to solid.
SVN commit 923243 by dafre: BUG: 179303 From now on, solid will check if hybrid suspension is available. If that is the case, it will automatically trigger hybrid instead of standard suspension to ram. So there won't be extra options in PowerDevil and/or Solid: Hybrid will be made default if available M +1 -1 halpower.cpp M +23 -3 halsuspendjob.cpp M +4 -2 halsuspendjob.h WebSVN link: http://websvn.kde.org/?view=rev&revision=923243
SVN commit 923247 by dafre: BUG: 179303 Backporting to 4.2 M +1 -1 halpower.cpp M +23 -3 halsuspendjob.cpp M +4 -2 halsuspendjob.h WebSVN link: http://websvn.kde.org/?view=rev&revision=923247
Hi, I do not agree to this change. My notebook is able to suspend to ram out-of-the-box, but if I try s2both, it will suspend to disk and always resume from disk. As pm-utils, s2ram, s2disk and s2both do not work the same way in all machines, I think it would be nice to at least let the user choose the suspending method. After this change (SVN commit 923247), my powerdevil's gui has two hibernate buttons: the first labeled "suspend" and the other labeled "hibernate" =(
As Danilo Luvizotto commented, I also think the proposed fix is bad: s2both locks my laptop on resume. However, s2ram and s2disk work fine. After this change, I do not have a reliable suspend to ram method in KDE anymore. I think you should at least let the user choose the suspending method.
Does not work for me too... Before this fix, "Suspend" button triggered suspend-to-ram correctly. Now, after the fix, it triggers suspend-to-disk which takes about the same time to hibernate but ages to wake up. Please revert this "fix" or make the suspend-command at least configurable.
Should we open a bug report?
I'll make Hybrid Suspend an option, this will have the counter effect that it won't be available in Powerdevil until 4.3 (new strings)
Ok, after a conversation with Kevin, we decided not to revert the commit in trunk and reverting it in 4.2, since the bug is clearly in pm-utils. From our conversation: <ervin> drf__: I'd say don't make an option for now, and report the pm-utils bug upstream <drf__> ervin, but at least we should comment the commit... this would break many suspensions in 4.2.1 <drf__> I agree with you though <ervin> I'd say revert in 4.2 branch <drf__> ok <ervin> that gives room for pm-utils people to fix until 4.3 is out <ervin> if they don't manage to fix in the meantime we'll reevaluate for an option <ervin> but I'd really prefer avoiding it <drf__> ok, agreed So please, report the bug upstream and tell us what the reaction will be. We'll act accordingly after that.
SVN commit 931528 by dafre: CCBUG: 179303 After some failed attempts, I'm reverting this feature for 4.2, since pm-utils seem not to work on every configuration. M +1 -1 halsuspendjob.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=931528
I consider this an interesting feature but I really suggest to make it configurable. This is not what people will expect. Even if pm-utils work correctly, users will see the suspend to disk that they did not ask for and have no way to change it. So, IMO the kcm module should have an option that enables/disables this.
(In reply to comment #13) > I consider this an interesting feature but I really suggest to make it > configurable. This is not what people will expect. Even if pm-utils work > correctly, users will see the suspend to disk that they did not ask for and > have no way to change it. > > So, IMO the kcm module should have an option that enables/disables this. I agree. Maybe in default settings set to active, but leave choice to deactivate it.
What's the state of the kcm-setting ? Is it available meanwhile?