Talk:Suspend and hibernate

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 10:54, 5 November 2024 (UTC)
:: Your reply ~~~~

EFI stub kernel support

Talk status

This discussion is done as of 2024-06-03.

TODO: suspend/hibernate with EFI stub kernel, see https://forums.gentoo.org/viewtopic-t-1068222.html Fcl (talk) 19:06, 27 August 2017 (UTC)

That forum post refers to CONFIG_PM_STD_PARTITION, but the page now uses {{{1}}} and {{{1}}}. I think that's fine, so I'm closing this.

— Waldo Lemmer 03:34, 3 June 2024 (UTC)

Security

Talk status

This discussion needs help as of 2024-06-03.
Tip: To get this fixed sooner, use {{Proposal}}.

Everybody having physical access to a suspended or hibernated computer could wake it up and proceed in any open session. A section about security telling how to integrate locking with suspend/hibernate would be very helpful.--Charles17 (talk) 13:09, 4 September 2017 (UTC)

alternatives

Talk status

This discussion is done as of 2024-06-03.

sys-power/suspend is marked for deletion and sys-power/hibernate-script only exist in the DISTFILES because the upstream is dead as well. Besides rolling your own and using the manual methods and/or forking the two mentioned applications, is there anything else which could be recommended? For example ACPI resp. acpid is relevant enough. ng0 (talk) 08:48, 12 November 2018 (UTC)

sys-power/suspend removal has been reversed. If you still need alternatives, please find and add them. Our mirror network will ensure the files of both packages will continue without issues. --Grknight (talk) 13:46, 12 November 2018 (UTC)

This has become a problem again. There is currently no way to run the usual hooks on suspend/hibernate/thaw/resume for Linux. There is one for Microsoft SystemD and separated taken from that (logind). Since this is such an easy thing to implement on Unix-likes, I might aswell put it in my (self-written) system event manager. But the problem is having a good set of scripts. Of course, SystemD being from the business programmer world, it makes it intentionally hard and uncomfortable to interoperate with any god besides it, so automating the taking of scripts from that feels like a massive hassle with a topping of cultist hostility when you even dare ask such a thing. … Yes, I’m grumpy, after just having been asked, *again*, “Why don’t you love systemd?”, like it was “Why don’t you love Jesus?”. XD … Come on! … WAT?? … I don’t hate SystemD. But it seems to hate non-believers like me, and back then my dad didn’t flee Taliban country for nothing! — Evi1m4chine (talk)

TuxOnIce

Talk status

This discussion is done as of 2024-06-03.

It seems dead, any mention of it in the article should be removed I think --Niyumard (talk) 12:25, 24 April 2022 (UTC)

If you think so, sounds good... Have you done it already ? -- Ris (talk) 05:06, 2 May 2022 (UTC)

Yes: Special:Diff/1059994.

— Waldo Lemmer 03:38, 3 June 2024 (UTC)

Suggestion: Adding a section for the Linux way.

Mainly, during boot, /sys/power/resume has to be set (otherwise e.g. elogind will report that hibernate won’t work, and KDE won’t offer the button).

#! /bin/bash
swap="$( swapon --noheadings --show | awk '{ print $1 }' )"
if [[ "$swap" =~ ^/dev/ ]]; then echo "$swap" > /sys/power/resume; fi

seems to work fine, if swap is enabled before, and the power management tooling is not used before that (e.g. powerdevil (for KDE) is started later). Thing is, I currently don’t know the idiomatic/correct place to put this in Gentoo.

Additionally, of course people without and SystemD proselytization will want some hooks and scripts to e.g. re-enable wifi or the like. But every god besides SystemD has been eradicated due to Microsoft Eternal Septembering Linux, so somebody has to step up and maintain at least one package. (I’m writing my own userspace currently, which involves an event manager that would be up for the job, but I don’t see me dealing with the hostility of wanting to auto-convert any scripts from SystemD, if they aren’t a hard-coded part of some binary “service” anyway. ;)

Currently, I’m just echo shutdown > /sys/power/disk and then echo disk > /sys/power/state. After that, wpa_supplicant re-connects the wifi. So it’s manual, without hooks, which is of course not a permanent solution.

For me, there currently is another problem too, where the system doesn’t come up when it went to sleep with KDE, but does, when I use loginctl directly. But that may be unrelated. I have to check.

I hope this helps any graybeard out there.

— Evi1m4chine (talk) 13:59, 17 October 2024 (UTC)