Power Management - Revision history

Sandro: /* Hibernation */

2026-01-18T10:00:18Z

Hibernation

← Older revision		Revision as of 10:00, 18 January 2026
Line 48:		Line 48:

	Therefore, an example configuration could look like this:<syntaxhighlight lang="nix">		Therefore, an example configuration could look like this:<syntaxhighlight lang="nix">
	/*		// I'm hibernating into a logical volume that's also under LUKS. Pretty cool, right?
	I'm hibernating into a logical volume that's also under LUKS. Pretty cool, right?
	*/

	swapDevices = [		swapDevices = [

Sandro: /* Suspend hooks */

2026-01-18T10:00:01Z

Suspend hooks

← Older revision		Revision as of 10:00, 18 January 2026
Line 30:		Line 30:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	systemd.services.your-service-name = {		systemd.services.your-service-name = {
	description = "Service description here";		description = "Service description here";
	wantedBy = [ "post-resume.target" ];		wantedBy = [ "post-resume.target" ];
	after = [ "post-resume.target" ];		after = [ "post-resume.target" ];
	script = ''		script = ''
	echo "This should show up in the journal after resuming."		echo "This should show up in the journal after resuming."
	'';		'';
	serviceConfig.Type = "oneshot";		serviceConfig.Type = "oneshot";
	};		};
	</syntaxhighlight>		</syntaxhighlight>

LordXerus: Clarified that solutions may vary when troubleshooting a blocked pre-sleep.service

2026-01-16T23:06:03Z

Clarified that solutions may vary when troubleshooting a blocked pre-sleep.service

← Older revision		Revision as of 23:06, 16 January 2026
Line 200:		Line 200:
	</syntaxhighlight>		</syntaxhighlight>

	~~The~~ <code>pre-sleep-start</code> script referenced by <code>ExecStart</code> contained directives installed by the [[Displaylink]] package, that contained a flush operation which hung the suspend action. Starting <code>dlm.service</code> or running <code>sudo DisplayLinkManager</code> unblocks the script and made suspend work normally.		In this case, the <code>pre-sleep-start</code> script referenced by <code>ExecStart</code> contained directives installed by the [[Displaylink]] package, that contained a flush operation which hung the suspend action. Starting <code>dlm.service</code> or running <code>sudo DisplayLinkManager</code> unblocks the script and made suspend work normally.

	==== Cancelling an existing suspend action ====		==== Cancelling an existing suspend action ====

LordXerus: Added a header to highlight systemctl cancel

2026-01-16T22:53:58Z

Added a header to highlight systemctl cancel

← Older revision		Revision as of 22:53, 16 January 2026
Line 202:		Line 202:
	The <code>pre-sleep-start</code> script referenced by <code>ExecStart</code> contained directives installed by the [[Displaylink]] package, that contained a flush operation which hung the suspend action. Starting <code>dlm.service</code> or running <code>sudo DisplayLinkManager</code> unblocks the script and made suspend work normally.		The <code>pre-sleep-start</code> script referenced by <code>ExecStart</code> contained directives installed by the [[Displaylink]] package, that contained a flush operation which hung the suspend action. Starting <code>dlm.service</code> or running <code>sudo DisplayLinkManager</code> unblocks the script and made suspend work normally.

			==== Cancelling an existing suspend action ====
	An existing suspend operation that is hung may be interrupted using <code>'''systemctl cancel'''</code> in case reboots or internet access is needed.		An existing suspend operation that is hung may be interrupted using <code>'''systemctl cancel'''</code> in case reboots or internet access is needed.

LordXerus: Added a lang="text" to syntaxhighlight

2026-01-16T22:51:55Z

Added a lang="text" to syntaxhighlight

← Older revision		Revision as of 22:51, 16 January 2026
Line 59:		Line 59:

	boot.resumeDevice = "/dev/dm-7";		boot.resumeDevice = "/dev/dm-7";
	</syntaxhighlight>Derived from a system with the following output from <code>swapon -s</code> :<syntaxhighlight>		</syntaxhighlight>Derived from a system with the following output from <code>swapon -s</code> :<syntaxhighlight lang="text">Filename Type Size Used Priority
	Filename Type Size Used Priority
	/dev/dm-7 partition 67108860 00		/dev/dm-7 partition 67108860 00
	/dev/zram0 partition 32881148 032767		/dev/zram0 partition 32881148 032767</syntaxhighlight>

	</syntaxhighlight>

	Test and use hibernation with the following command:<syntaxhighlight lang="nix">		Test and use hibernation with the following command:<syntaxhighlight lang="nix">

LordXerus: change lang=sh to shell session to fix syntax highlighting error

2026-01-16T22:50:01Z

change lang=sh to shell session to fix syntax highlighting error

← Older revision		Revision as of 22:50, 16 January 2026
Line 141:		Line 141:
	After finding out which component is causing unwanted wakeups you can use the sysfs id to find out the "vendor" and "device" fields:		After finding out which component is causing unwanted wakeups you can use the sysfs id to find out the "vendor" and "device" fields:

	<syntaxhighlight lang="sh">		<syntaxhighlight lang="console">
	$ cat /sys/class/pci_bus/0000:04/device/0000:04:00.0/vendor		$ cat /sys/class/pci_bus/0000:04/device/0000:04:00.0/vendor
	0x1987		0x1987

LordXerus: Added a section to troubleshoot userspace suspend issues.

2026-01-16T22:48:45Z

Added a section to troubleshoot userspace suspend issues.

@@ Line 155: / Line 155: @@
 '';
 </syntaxhighlight>
 == See also ==

LordXerus: change lang=sh to shell session to fix syntax highlighting error

2026-01-16T22:05:52Z

change lang=sh to shell session to fix syntax highlighting error

← Older revision		Revision as of 22:05, 16 January 2026
Line 120:		Line 120:

	First, list all components and their current wakeup status:		First, list all components and their current wakeup status:
	<syntaxhighlight lang="sh">		<syntaxhighlight lang="shell-session">
	$ cat /proc/acpi/wakeup		$ cat /proc/acpi/wakeup
	Device S-state Status Sysfs node		Device S-state Status Sysfs node

LordXerus: /* Troubleshooting: bumped header level to increase readability*/

2026-01-16T22:04:14Z

Troubleshooting: bumped header level to increase readability

← Older revision		Revision as of 22:04, 16 January 2026
Line 91:		Line 91:
	== Troubleshooting ==		== Troubleshooting ==

	==== System immediately wakes up from suspend ====		=== System immediately wakes up from suspend ===

	Particularly in some Gigabyte motherboards with NVMe drives, the system may immediately wake up from being suspended.		Particularly in some Gigabyte motherboards with NVMe drives, the system may immediately wake up from being suspended.
	This can be worked around by disabling the wakeup triggers for the offending components:		This can be worked around by disabling the wakeup triggers for the offending components:

	===== Solution 1: Disabling wakeup triggers for all PCIe devices =====		==== Solution 1: Disabling wakeup triggers for all PCIe devices ====

	If you don't need your system to wakeup via PCIe components you can simply disable it for all without needing to determine which component is causing problems.		If you don't need your system to wakeup via PCIe components you can simply disable it for all without needing to determine which component is causing problems.
Line 106:		Line 106:
	</syntaxhighlight>		</syntaxhighlight>

	===== Solution 2: Disable a common NVMe interface =====		==== Solution 2: Disable a common NVMe interface ====

	Specifically on Gigabyte motherboards you can try targetting only the NVMe ports.		Specifically on Gigabyte motherboards you can try targetting only the NVMe ports.
Line 116:		Line 116:
	</syntaxhighlight>		</syntaxhighlight>

	===== Solution 3: Disable a single device's wakeup triggers =====		==== Solution 3: Disable a single device's wakeup triggers ====
	If you wish to be more granular in what components should no longer be able to wakeup your system, you can find out which component is causing the wakeup events.		If you wish to be more granular in what components should no longer be able to wakeup your system, you can find out which component is causing the wakeup events.

Hustlerone: remove some whitespace and fix typo

2025-07-31T10:18:55Z

remove some whitespace and fix typo

← Older revision		Revision as of 10:18, 31 July 2025
Line 45:		Line 45:
	Hibernation requires a configured swap device. See [https://nixos.org/manual/nixos/stable/#ch-installation installation instructions] on how to create a swap partition.		Hibernation requires a configured swap device. See [https://nixos.org/manual/nixos/stable/#ch-installation installation instructions] on how to create a swap partition.

	Please note that <code>resumeDevice</code> must match the output of <code>swapon -s</code> especially if you're dealing with mapped volumes (LUKS, logical volumes, logical volumes under LUKS, etc.). If you're using a swapfile, you must also [https://search.nixos.org/options?channel=unstable&show=boot.resumeDevice&from=0&size=50&sort=relevance&type=packages&query=resume+offset specify the offset to it].		Please note that <code>resumeDevice</code> must match the output of <code>swapon -s</code> especially if you're dealing with mapped volumes (LUKS, logical volumes, logical volumes under LUKS, etc.). If you're using a swapfile, you must also [https://search.nixos.org/options?channel=unstable&show=boot.resumeDevice&from=0&size=50&sort=relevance&type=packages&query=resume+offset specify the offset to it.]


	Therefore, an example configuration could look like this:<syntaxhighlight lang="nix">		Therefore, an example configuration could look like this:<syntaxhighlight lang="nix">
Line 67:		Line 66:
	</syntaxhighlight>		</syntaxhighlight>

			Test and use hibernation with the following command:<syntaxhighlight lang="nix">
	Test and use hibernation with following command:<syntaxhighlight lang="nix">
	systemctl hibernate		systemctl hibernate
	</syntaxhighlight>		</syntaxhighlight>