Revert "base-defaults: disable system suspend and hibernation"

This reverts commit 697a7420 that disabled system sleep like "systemctl suspend" via systemd since the kernel had not supported it (The system would in most cases suspend, but never be able to resume). Since kernel version 5.16.3pureos1 the kernel supports resuming from suspend so people can at least start to do tests. So this simply *allows* to test system sleep via systemd. It doesn't change any default behaviour. Keep in mind that * there can still be bugs around suspend and resume in general. Let's find them together. * System suspend means that no data connection is kept alive: No receiving of email, xmpp and so on. * While the goal is that cellular calls and SMS would wake up the system and work normally, that is currently disabled on many of the shipped modems. We're working on it and Linux supports it already. * All policies how to "transparently" use suspend in the future are open questions, see for example Librem5/OS-issues#237 * Compared to "display off standby" we currently have (using runtime pm), we can say that system suspend will always save power. How much though is highly dependent on what is running and enabled on the system: - If the modem is enabled, it stays enabled and can use quite some power depending on signal strength. That would *reduce* the amount of power saved. - If there are applications running, they will be freezed during system suspend, so more open applications would *increase* power saved.

Revert "base-defaults: disable system suspend and hibernation"
This reverts commit 697a7420 that disabled system sleep like "systemctl suspend" via systemd since the kernel had not supported it (The system would in most cases suspend, but never be able to resume). Since kernel version 5.16.3pureos1 the kernel supports resuming from suspend so people can at least start to do tests. So this simply *allows* to test system sleep via systemd. It doesn't change any default behaviour. Keep in mind that * there can still be bugs around suspend and resume in general. Let's find them together. * System suspend means that no data connection is kept alive: No receiving of email, xmpp and so on. * While the goal is that cellular calls and SMS would wake up the system and work normally, that is currently disabled on many of the shipped modems. We're working on it and Linux supports it already. * All policies how to "transparently" use suspend in the future are open questions, see for example Librem5/OS-issues#237 * Compared to "display off standby" we currently have (using runtime pm), we can say that system suspend will always save power. How much though is highly dependent on what is running and enabled on the system: - If the modem is enabled, it stays enabled and can use quite some power depending on signal strength. That would *reduce* the amount of power saved. - If there are applications running, they will be freezed during system suspend, so more open applications would *increase* power saved.
d920f08d · Martin Kepplinger · e4e98ecb · d920f08d · e4e98ecb
Commit d920f08d authored 3 years ago by Martin Kepplinger
--- a/debian/librem5-base-defaults.install
+++ b/debian/librem5-base-defaults.install
@@ -49,6 +49,3 @@ default/systemd/stop-timeout.conf	etc/systemd/user.conf.d/

 # initramfs modules
 default/initramfs-tools/modules.d/*	usr/share/initramfs-tools/modules.d/
-
-# systemd system suspend configuration
-default/systemd/l5-suspend.conf		/usr/lib/systemd/sleep.conf.d/
--- a/default/systemd/l5-suspend.conf
+++ b/default/systemd/l5-suspend.conf
-[Sleep]
-AllowSuspend=no
-AllowHibernation=no
-
-# once the kernel is fixed, we allow suspend by removing the above and
-# enable the freeze state.
-#SuspendState=freeze