Jump to content

Power Management: Difference between revisions

Add notes on hibernation
imported>Samueldr
(Created page with "{{expansion}} == Suspend == === Suspend hooks === NixOS provides the {{nixos:option|powerManagement.resumeCommands}} option which defines commands that are added to a globa...")
 
(Add notes on hibernation)
 
(2 intermediate revisions by 2 users not shown)
Line 13: Line 13:
</syntaxhighlight>
</syntaxhighlight>


It is also possible, to use the <code>post-resume</code> target directly to make a service.
It is also possible to use the <code>post-resume</code> target directly to make a service.
Refer to the [[Systemd Services]] article for details about writing systemd services for NixOS.


<syntaxhighlight lang="nix">
<syntaxhighlight lang="nix">
Line 28: Line 27:
</syntaxhighlight>
</syntaxhighlight>


== Hibernation ==
Hibernation requires a configured swap device. See [https://nixos.org/manual/nixos/stable/#ch-installation installation instructions] on how to create a swap partition. An example configuration could look like this:<syntaxhighlight lang="nix">
swapDevices = [
  {
    device = "/dev/hda7";
  }
];
boot.resumeDevice = "/dev/hda7";
</syntaxhighlight>Please note that encrypted swap devices or swap files are not yet supported for hibernation.
Test and use hibernation with following command:<syntaxhighlight lang="nix">
systemctl hibernate
</syntaxhighlight>
== Tips and tricks ==
=== Go into hibernate after specific suspend time ===
Using following configuration, your system will go from suspend into hibernate after 1 hour:<syntaxhighlight lang="nix">
systemd.sleep.extraConfig = ''
  HibernateDelaySec=1h
'';
</syntaxhighlight>
== Troubleshooting ==
==== System immediately wakes up from suspend ====
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:
===== 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.
<syntaxhighlight lang="nix">
services.udev.extraRules = ''
  ACTION=="add", SUBSYSTEM=="pci", DRIVER=="pcieport", ATTR{power/wakeup}="disabled"
'';
</syntaxhighlight>
===== Solution 2: Disable a common NVMe interface =====
Specifically on Gigabyte motherboards you can try targetting only the NVMe ports.
<syntaxhighlight lang="nix">
services.udev.extraRules = ''
  ACTION=="add" SUBSYSTEM=="pci" ATTR{vendor}=="0x1022" ATTR{device}=="0x1483" ATTR{power/wakeup}="disabled"
'';
</syntaxhighlight>
===== 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.
First, list all components and their current wakeup status:
<syntaxhighlight lang="sh">
$ cat /proc/acpi/wakeup
Device S-state   Status  Sysfs node
GP12   S4 *enabled  pci:0000:00:07.1
GP13   S4 *disabled  pci:0000:00:08.1
XHC0   S4 *enabled  pci:0000:0a:00.3
GP30   S4 *disabled
....
PT27   S4 *disabled
PT28   S4 *disabled
PT29   S4 *disabled  pci:0000:03:09.0
</syntaxhighlight>
You can temporarily toggle a device by writing its "Device" name back into <code>/proc/acpi/wakeup</code>
<syntaxhighlight lang="sh">
echo GPP0 | sudo tee /proc/acpi/wakeup
</syntaxhighlight>
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">
$ cat /sys/class/pci_bus/0000:04/device/0000:04:00.0/vendor
0x1987
$ cat /sys/class/pci_bus/0000:04/device/0000:04:00.0/device
0x5013
</syntaxhighlight>
And finally use those values in a <code>udev</code> rule:
<syntaxhighlight lang="nix">
services.udev.extraRules = ''
  ACTION=="add" SUBSYSTEM=="pci" ATTR{vendor}=="0x1987" ATTR{device}=="0x5013" ATTR{power/wakeup}="disabled"
'';
</syntaxhighlight>
== See also ==
* [[Laptop]]


== External resources ==
== External resources ==


* {{manual:nixos|sec=#sec-rebooting|chapter=Chapter 23. Rebooting and Shutting Down}}
* {{manual:nixos|sec=#sec-rebooting|chapter=Chapter 23. Rebooting and Shutting Down}}
62

edits