You are not logged in.
I have an ASUS TUF F15 with an rtx4070 gpu. When I'm dual booting windows and arch with hyprland.
When i put the laptop to suspend mode only the enter key from an external keyboard wakes the laptop. The builtin power button, keyboard, touchpad, external mouse does not do anything.
I tried
cat /proc/acpi/wakeupto see if the power button is disabled
Device S-state Status Sysfs node
PEG1 S4 *enabled pci:0000:00:01.0
PEGP S4 *disabled pci:0000:01:00.0
PEG2 S4 *disabled
PEGP S4 *disabled
PEG0 S4 *disabled pci:0000:00:06.0
PEGP S4 *disabled
RP09 S4 *disabled
PXSX S4 *disabled
RP10 S4 *disabled
PXSX S4 *disabled
RP11 S4 *disabled
PXSX S4 *disabled
RP12 S4 *disabled
PXSX S4 *disabled
RP13 S4 *disabled
PXSX S4 *disabled
RP14 S4 *disabled
PXSX S4 *disabled
RP15 S4 *disabled
PXSX S4 *disabled
RP16 S4 *disabled
PXSX S4 *disabled
RP01 S4 *disabled
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *disabled
PXSX S4 *disabled
RP06 S4 *disabled
PXSX S4 *disabled
RP07 S4 *enabled pci:0000:00:1c.0
PXSX S4 *disabled pci:0000:37:00.0
RP08 S4 *disabled
PXSX S4 *disabled
RP17 S4 *disabled
PXSX S4 *disabled
RP18 S4 *disabled
PXSX S4 *disabled
RP19 S4 *disabled
PXSX S4 *disabled
RP20 S4 *disabled
PXSX S4 *disabled
RP21 S4 *disabled
PXSX S4 *disabled
RP22 S4 *disabled
PXSX S4 *disabled
RP23 S4 *disabled
PXSX S4 *disabled
RP24 S4 *disabled
PXSX S4 *disabled
XHCI S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
CNVW S4 *disabled pci:0000:00:14.3
TXHC S3 *enabled pci:0000:00:0d.0
TDM0 S4 *enabled pci:0000:00:0d.2
TDM1 S4 *disabled
TRP0 S4 *enabled pci:0000:00:07.0
PXSX S4 *disabled
TRP1 S4 *disabled
PXSX S4 *disabled
TRP2 S4 *disabled
PXSX S4 *disabled
TRP3 S4 *disabled
PXSX S4 *disabled
AWAC S4 *enabled platform:ACPI000E:00It doesn't show any devices like PWRB, LID...
I've also tried a lot of other things with nvidia power management before realizing the external keyboard works.
I would highly appreciate any help and am happy to provide any additional information.
Thanks in advance.
Last edited by ravenousByte (2025-12-06 08:06:23)
Offline
I have an ASUS TUF A15 and is also experiencing the same problem. i don't have an external keyboard to test that though
cat /proc/acpi/wakeupDevice S-state Status Sysfs node
GPP1 S4 *disabled
GPP2 S4 *disabled
GPP0 S4 *enabled pci:0000:00:01.1
GPP5 S4 *enabled pci:0000:00:02.1
GPP6 S4 *enabled pci:0000:00:02.2
GPP7 S4 *disabled
GP11 S0 *disabled
SWUS S4 *disabled
GP12 S0 *disabled
SWUS S4 *disabled
XHC0 S4 *enabled pci:0000:05:00.3
XHC1 S4 *enabled pci:0000:05:00.4
XHC2 S4 *enabled pci:0000:06:00.0
XHC3 S4 *enabled pci:0000:06:00.3
XHC4 S4 *enabled pci:0000:06:00.4
NHI0 S0 *disabled
NHI1 S0 *disabledLast edited by hisham shefeekh (2025-12-02 21:16:18)
Offline
oh wait, they are in
/sys/class/wakeup/see https://wiki.archlinux.org/title/Power_ … s/wakeup/*
even though they are shown to be enabled there, the issue still persists
Last edited by hisham shefeekh (2025-12-02 21:14:46)
Offline
yes i found the wakeup trigger in
/sys/class/wakeup/ Its enabled for me too. I tried switching to deep suspend state from s2idle. But that just performs a clean boot.
I did manage to get hibernation working though. I guess I'll use that instead for now.
Offline
mine only supports s2idle
Offline
When I'm dual booting windows and arch with hyprland.
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Do you have any BIOS/UEFI settings for the wakeup behavior?
Offline
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
I don't think it's a fast startup issue. I had both fast startup and the BIOS setting fastboot disabled from the start.
Offline
To add info, I am on CachyOS with KDE and is having the issue. Since OP is on Arch with Hyprland, the issue is probably unrelated to DEs. The one thing we have in common is that we are on an ASUS TUF series laptop. So I think this is a device specific issue.
Offline
It is most certainly related to the HW (more specifically the ACPI) and most certainly not some DE.
Make absolutely sure that windows fast-start is *still* disabled (it frequently gets re-enabled w/ udpdates)
The BIOS setting is irrelevant, it controls some initial self-tests - the concern is that windows might be hibernating while you're running arch.
Otherwise you might lie to the firmware and convince it that this is actually windows and it can enable certain features:
acpi_osi=! acpi_osi="Windows 2015"Offline
Make absolutely sure that windows fast-start is *still* disabled (it frequently gets re-enabled w/ udpdates)
I checked just now. Since I disabled hibernation recently, fast startup is not even an option in control panel anymore. I presume hibernation is necessary for fast startup.
Otherwise you might lie to the firmware and convince it that this is actually windows and it can enable certain features:
acpi_osi=! acpi_osi="Windows 2015"
I did this and it didn't go well. The system was not booting with
acpi_osi=! acpi_osi="Windows 2015"So I tried it with just
acpi_osi="Windows 2015"This time it booted, but the 'not waking' issue was not resolved.
Offline
I did this and it didn't go well. The system was not booting with
acpi_osi=! acpi_osi="Windows 2015"
It booted with
acpi_osi=! acpi_osi="Windows 2013"Didn't solve the problem though
Last edited by hisham shefeekh (2025-12-04 00:33:29)
Offline
W/o "acpi_osi=!" the subsequent acpi_osi won't do much and apparently the system doesn't like Win10 and doesn't change w/ Win8
Are there any BIOS/UEFI updates available for the system?
I presume hibernation is necessary for fast startup.
Fast-start /is/ hibernation (in disguise)
Offline
Are there any BIOS/UEFI updates available for the system?
Just checked. It is indeed on the latest BIOS.
Offline
https://bbs.archlinux.org/viewtopic.php … 3#p2102563
This issue seems familiar. But I tried the solution and didn't work
Offline
When I press on my keyboard or click on my mouse, the LEDs on my keyboard and PC turn on as expected, and my monitors appears as if it will display something
There're countless "failed to wake-up" threads but most (like the one you linked) don't revolve around dysfunctional specific triggers but failures to initialize the system (that thread seemed to revolve around nvidias VRAM preservation mechanisms)
Offline
This one actually might be the same issue.
https://www.reddit.com/r/AMDLaptops/com … are_button
They also have an ASUS TUF laptop but a different model. They seem to solve it by downgrading their BIOS. The version that worked for them is 307 or 309. But that won't work for me because the latest BIOS version on my model (FA506NCR) is 304.
Only if there was a way to know which BIOS version for my exact model will work correctly
. Also I am a little hesitant to downgrade the BIOS since on ASUS's website, the latest BIOS update has a severity rating of "critical"
Last edited by hisham shefeekh (2025-12-05 02:56:49)
Offline
Finally! I found the fix
. I don't know how it managed to go under my radar all this time, but the arch wiki had a section specifically for this issue.
https://wiki.archlinux.org/title/Laptop … h_no_iGPU)
Basically u just set this nvidia kernel module parameter
NVreg_EnableS0ixPowerManagement=1I wonder why it is disabled by default.
ravenousByte's problem might be different, since his/her work with an external keyboard. As I previously said, I don't have an external keyboard to try. Anyway, give this a try ravenousByte.
Offline
Finally! I found the fix
. I don't know how it managed to go under my radar all this time, but the arch wiki had a section specifically for this issue.
https://wiki.archlinux.org/title/Laptop … h_no_iGPU)Basically u just set this nvidia kernel module parameter
NVreg_EnableS0ixPowerManagement=1I wonder why it is disabled by default.
ravenousByte's problem might be different, since his/her work with an external keyboard. As I previously said, I don't have an external keyboard to try. Anyway, give this a try ravenousByte.
I actually tried changing these options in nvidia.conf file before. But nothing changed. I have this option set to 1 already. Does your laptop not have an iGPU. The article https://wiki.archlinux.org/title/Laptop … h_no_iGPU) is for laptops with no iGPU.
Last edited by ravenousByte (2025-12-05 18:00:08)
Offline
Does your laptop not have an iGPU
Yea, mine does not have an iGPU. So it is a different problem after all.
I actually tried changing these options in nvidia.conf file before. But nothing changed.
Just to make sure, you regenerated the intramfs after setting the parmeter, right?
Offline
Just to make sure, you regenerated the intramfs after setting the parmeter, right?
Yes I did.
Offline
When I'm dual booting windows and arch with hyprland.
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.Do you have any BIOS/UEFI settings for the wakeup behavior?
…
Make absolutely sure that windows fast-start is *still* disabled (it frequently gets re-enabled w/ udpdates)
The BIOS setting is irrelevant, it controls some initial self-tests - the concern is that windows might be hibernating while you're running arch.Otherwise you might lie to the firmware and convince it that this is actually windows and it can enable certain features:
acpi_osi=! acpi_osi="Windows 2015"
Offline
I checked again to see if fast boot and hibernation is off in windows.
I also tried adding this to grub.
acpi_osi=! acpi_osi="Windows 2015"I just found out something. When i suspend the laptop just after i do a hibernation, suspending works normally and power button works one time. If i try to suspend again, power button doesnt work again. If i do hibernation again, suspending works again one time.
This only happens after hibernation. Shutting down and booting again does not do this.
This is starting to sound ridiculous now. ![]()
Offline
UPDATE! : I FIXED THE ERROR
using
journalctl -b -1 | grep -iE 'suspend|nvidia|acpi|pci'i found the error
Dec 06 12:41:42 archlinux kernel: ACPI Error: No installed handler for fixed event - PowerButton (2), disabling (20250404/evevent-255)then i found this https://github.com/linux-surface/linux- … issues/316
which had a link to this article https://sylence.cc/posts/power-button-surface-go-2/
After asking gemini i found a fix.
The fix is to perform an ACPI table override to tell the kernel to always expect the "Fixed Power Button" mechanism, which forces the kernel to install the correct handler, or simply correct the invalid flag set by the BIOS.
==================================================
Prerequisites
sudo pacman -S acpica cpioSteps:
# Dump the binary table
cat /sys/firmware/acpi/tables/FACP > facp.dat
# Decompile the binary data into human-readable ASL code
iasl -d facp.dat
# open facp.dsl
nvim facp.dslIn the facp.dsl file you have to change two things.
1. increase the Oem Revision number to ensure the kernel uses your patched table.
2. change 'Control Method Power Button (V1)' value from 1 to 0
...
[018h 0024 4] Oem Revision : 00000001 # <--- Change this to a higher number
...
... Control Method Power Button (V1) : 0 # <--- Change this to 0then
# Recompile the patched table
iasl -tc facp.dsl
# Create the directory structure and CPIO archive
mkdir -p kernel/firmware/acpi
cp facp.aml kernel/firmware/acpi
find kernel | cpio -H newc --create > acpi_override
# Move the override file to your boot partition
sudo cp acpi_override /bootadd the line
GRUB_EARLY_INITRD_LINUX_CUSTOM="acpi_override"to /etc/default/grub file.
Finally update grub
sudo grub-mkconfig -o /boot/grub/grub.cfgReboot.
=================================================
Thanks for the help.
Last edited by ravenousByte (2025-12-06 08:02:36)
Offline