Public bug reported:
Summary
=======
On ASUS TUF Gaming F15 FX507VV (BIOS 330), the system enters s2idle correctly
but cannot be resumed by the internal keyboard, power button, or by opening the
lid. Only a USB wireless mouse can wake it. Root cause is a firmware ACPI
defect: the active lid device \_SB.PC00.LPCB.LID0 lacks a _PRW object, so GPE
0x02 used by the embedded controller (EC) for lid/keyboard/power-button wake
events is not armed during s2idle.
Hardware and software
=====================
- Model: ASUS TUF Gaming F15 FX507VV_FX507VV (BIOS FX507VV.330)
- CPU: 13th Gen Intel Core i7-13700H
- GPU: Intel Iris Xe Graphics + NVIDIA GeForce RTX 4060 Max-Q / Mobile
- OS: Ubuntu 26.04.1 LTS (Resolute Raccoon)
- Kernel: 7.0.0-38-generic
- Sleep mode: s2idle (cat /sys/power/mem_sleep -> [s2idle] deep)
- Desktop: GNOME 50.1 / Mutter (Wayland)
Symptoms
========
After `systemctl suspend` or closing the lid, the system appears to sleep
normally:
- power LED “breathes”
- fans and keyboard backlight turn off
- journal ends at `PM: suspend entry (s2idle)` with no `suspend exit`
However, pressing an internal keyboard key, pressing the power button,
or opening the lid does nothing. The only reliable wake source is a USB
wireless mouse that was connected before suspend. This is not a freeze:
the firmware/EC considers the machine asleep, but the wake event never
reaches the CPU.
Root cause
==========
Disassembling the DSDT (`sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat &&
iasl -d dsdt.dat`) shows:
- The active lid device is `\_SB.PC00.LPCB.LID0`. It has no `_PRW` object.
- A second `LID0` exists under `\_SB.PC00.LPCB.H_EC`, but its `_STA` returns
`Zero`, so it is disabled and irrelevant.
- Because no device claims GPE 0x02 for wake, `LID0` does not appear in
`/proc/acpi/wakeup` at all.
- The EC’s wake events for lid, power button and keyboard arrive on GPE 0x02
(`_GPE._L02 -> ECLV()`). Without a `_PRW` claim, Linux does not keep GPE 0x02
enabled during s2idle, so all internal wake sources fail.
This is not an NVIDIA issue: booting with
`module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm` still reproduces
the failure.
This is also not a kernel regression: the DSDT content is independent of the
kernel version, and the same defect is present on this platform regardless of
kernel.
Verified workaround
===================
Injecting `_PRW (0x02, Zero)` into `\_SB.PC00.LPCB.LID0` via a 93-byte SSDT
loaded through `GRUB_EARLY_INITRD_LINUX_CUSTOM="acpi_override.cpio"` fixes the
problem.
After reboot:
- `journalctl -b -k | grep -i "Table Upgrade"` shows:
`ACPI: Table Upgrade: install [SSDT- FIXUP- LIDWAKE]`
- `grep LID0 /proc/acpi/wakeup` shows:
`LID0 S0 *enabled platform:PNP0C0D:01`
With this workaround, the internal keyboard, power button and lid
opening all successfully wake the system.
Sister model confirmation
=========================
The same defect and the same `_PRW` injection fix have been reported for the
ASUS TUF F15 FX507ZI4 with the same BIOS 330. This suggests a BIOS-level
omission across the FX507 series, not a one-off board anomaly.
Upstream status
===============
A Linux kernel Bugzilla report has been filed:
[PASTE_YOUR_KERNEL_BUGZILLA_URL_HERE]
Request to Ubuntu kernel team
=============================
Please consider carrying/backporting a DMI-based ACPI quirk for affected ASUS
TUF FX507 series boards that lack `_PRW` on the active `LID0`, so that GPE 0x02
is armed during s2idle without requiring a user-space SSDT override. If an
upstream quirk is accepted, this report can track the Ubuntu kernel inclusion.
Attachments
===========
`asus-fx507vv-acpi-data.tar.gz` contains:
- `dmidecode.txt` (DMI/SMBIOS identifiers)
- `acpidump.txt` (raw ACPI tables)
- `dmesg.log` (kernel log after the SSDT workaround)
- `dsdt.dsl` (disassembled DSDT showing the active LID0 without _PRW)
Reproducer
==========
1. Confirm s2idle: `cat /sys/power/mem_sleep` -> `[s2idle] deep`
2. Confirm missing LID0: `grep LID0 /proc/acpi/wakeup` -> no output
3. Suspend: `systemctl suspend`
4. Try to wake with internal keyboard, power button, or by opening the lid.
Observed: no reaction. USB mouse wakes the system.
Additional note
===============
The touchpad also does not wake the system because its `GpioInt` is declared as
`Exclusive` rather than `ExclusiveAndWake`. That is a separate, lower-priority
issue and is not required to fix the lid/keyboard/power-button wake problem
described here.
Tags: acpi, s2idle, suspend, wakeup, asus, fx507vv
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-38-generic 7.0.0-38.38
ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14
Uname: Linux 7.0.0-38-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: rocky 4393 F.... wireplumber
/dev/snd/controlC1: rocky 4393 F.... wireplumber
/dev/snd/seq: rocky 4383 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 23:14:07 2026
InstallationDate: Installed on 2026-09-25 (29 days ago)
InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64
(20260826.1)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507VV_FX507VV
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic
root=UUID=7572780b-94a5-4eab-bf44-0e46804ca061 ro
cryptdevice=UUID=df9cda33-1c7a-4b53-86ee-834eef58528d:luks-df9cda33-1c7a-4b53-86ee-834eef58528d
root=/dev/mapper/luks-df9cda33-1c7a-4b53-86ee-834eef58528d quiet splash
nvidia-drm.modeset=1 mem_sleep_default=s2idle
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2025
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX507VV.332
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX507VV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.96
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX507VV.332:bd10/01/2025:br5.27:efr0.96:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX507VV_FX507VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX507VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFGamingF15:
dmi.product.family: ASUS TUF Gaming F15
dmi.product.name: ASUS TUF Gaming F15 FX507VV_FX507VV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
** Patch added: "ACPI debug data for ASUS TUF F15 FX507VV (BIOS 330):
dmidecode, acpidump, dmesg, and disassembled dsdt.dsl showing active LID0
missing _PRW."
https://bugs.launchpad.net/bugs/2172125/+attachment/6012177/+files/asus-fx507vv-acpi-data.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2172125
Title:
[ASUS TUF F15 FX507VV] Internal wake sources (lid/keyboard/power
button) fail after s2idle suspend due to missing _PRW for LID0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172125/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
