Power Management: Difference between revisions
Hustlerone (talk | contribs) m remove some whitespace and fix typo |
|||
| Line 91: | Line 91: | ||
== Troubleshooting == | == Troubleshooting == | ||
=== 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 ==== | |||
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 ==== | |||
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 ==== | |||
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. | ||