ACPI Wake-up Triggers

will41 · 10-14-2022, 11:32 AM

I'm running Fedora 36 with Cinnamon. If I run

Code:

cat /proc/acpi/wakeup

I get a list of devices that are triggers apparently for waking the system. Some are enabled, but most are disabled. Are these enabled triggers used for anything else other than waking a sleeping (suspended) system? Are there any side effects to disabling any or all of them?

I'm asking because, at some point, my Dell xps became unable to stay suspended. Something is causing the system to re-wake almost immediately. I have found that if I disable one of the triggers I can, at least, suspend the system from the command line using

Code:

systemctl suspend

If it is OK to keep it that way, I need to figure out how to make it persist (it goes back to the original enabled setting after re-boot).

Jason_25 · 10-15-2022, 08:11 PM

/etc/rc.local would be the standard place for something like that. This runs at system startup. It can be created if needed. If it does not work right off the bat you can make sure it is executable and add a "shebang" up top and an exit 0 at the end.

You can put it in bashrc to have it run at login instead. You can put it in xsessionrc to have it run with a display manager session or put it in xinitrc to have it run with a scripted or manual xorg session. In the old days or with a sysvinit setup like I use you could put it in a script in /etc/init.d and use update-rc.d or something like that. Finally, you could hijack an existing script you know that runs and put your code in there.

This is how you how change those kinds of variables with sudo without having to become root by the way. But /etc/rc.local runs by default as root so you can just write it as normal.

Code:

sudo sh -c "echo '1' >> /proc/sys/net/ipv4/ip_forward"

edit: I forgot to add the scripting option of having the DE start your script for you. For KDE it is in system settings > startup and shutdown > autostart.

will41 · 10-15-2022, 11:09 PM

I am unsure of what changes to make without screwing something up.
Are these enabled triggers used for anything else other than waking a sleeping (suspended) system?
Are there any side effects to disabling any or all of them?
When I run

Code:

dmesg -k

I get the following, printed largely in red, repeated several times within a long list of other information

Code:

[221670.943313] nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend+0x0/0x20 [nvidia] returns -5
[221670.944067] nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -5
[221670.944082] nvidia 0000:01:00.0: PM: failed to suspend async: error -5
[221671.216668] PM: Some devices failed to suspend, or early wake event detected

I assume that this gives a clue to my problem, but I have no idea on what to do to fix it. I think I have all of the Nvidia drivers installed properly.