Arch Linux

stuckinvim

Member

Registered: 2024-08-22

Posts: 9

Asus ROG Zephyrus M16 Not Waking From Deep Sleep

For some reason my laptop seems to suddenly be unable to wake from deep sleep. Resuming from hibernation invoked manually from the command line works perfectly, but if I just close the lid to put it to sleep (both on battery and A/C power), it will not wake up, and when I attempt to reboot, it goes to a black screen that forces me to disconnect the battery before I can boot properly again. This has only been going on for about two weeks now, and also happens to be coinciding with DBus errors being thrown in the journal whenever I try to use the Super+L keystroke to lock my screen. Anyone with a similar experience have some insight into what may be going on here?

Edit: I'm not sure how useful this will be but below is the journalctl output for the previous boot from closing my laptop's lid to the end of the journal

Nov 19 19:04:53 GU604 systemd-logind[1556]: Lid closed.
Nov 19 19:04:53 GU604 systemd-logind[1556]: Suspending...
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.5204] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 19 19:04:53 GU604 asusd[1884]: [INFO  asusd::ctrl_platform] RogPlatform reloading panel_od
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.5205] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reas>
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.5210] manager: NetworkManager state is now ASLEEP
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.5211] device (wlan0): state change: activated -> deactivating (reason 'slee>
Nov 19 19:04:53 GU604 systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 19 19:04:53 GU604 gnome-shell[4475]: Screen lock is locked down, not locking
Nov 19 19:04:53 GU604 systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 19 19:04:53 GU604 dhcpcd[1572]: wlan0: carrier lost
Nov 19 19:04:53 GU604 kernel: wlan0: deauthenticating from b0:b8:67:f8:5c:50 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Withdrawing address record for 172.19.97.1 on wlan0.
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: nl80211: send_event_marker failed: Source based routing not supported
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: CTRL-EVENT-DISCONNECTED bssid=b0:b8:67:f8:5c:50 reason=3 locally_generated=1
Nov 19 19:04:53 GU604 dhcpcd[1572]: wlan0: deleting route to 172.19.96.0/20
Nov 19 19:04:53 GU604 dhcpcd[1572]: wlan0: deleting default route via 172.19.96.1
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6222] device (wlan0): state change: deactivating -> disconnected (reason 's>
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6225] dhcp4 (wlan0): canceled DHCP transaction
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6225] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 secon>
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Withdrawing address record for fe80::9746:ae3a:9aa1:5ab4 on wlan0.
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6225] dhcp4 (wlan0): state changed no lease
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::9746:ae3a:9aa1:5ab4.
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Interface wlan0.IPv6 no longer relevant for mDNS.
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:f8:5c:50 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:32:50 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:f8:5c:40 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:32:40 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:94:10 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:95:30 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:94:00 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:95:20 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:91:90 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 48:4a:e9:e0:7c:f0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:93:30 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:95:50 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:f8:8f:b0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:95:40 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 48:4a:e9:e0:7c:e0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:fa:02:b0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 48:4a:e9:df:85:30 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 48:4a:e9:df:85:20 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:91:80 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:f8:8f:a0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED b0:b8:67:fa:02:a0 0
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: PMKSA-CACHE-REMOVED 24:f2:7f:b9:93:20 0
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Withdrawing address record for 172.19.101.227 on wlan0.
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 172.19.101.227.
Nov 19 19:04:53 GU604 avahi-daemon[1538]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 19 19:04:53 GU604 root[327096]: LID closed
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6816] device (wlan0): supplicant interface state: completed -> disconnected
Nov 19 19:04:53 GU604 NetworkManager[1534]: <info>  [1732064693.6820] device (wlan0): state change: disconnected -> unmanaged (reason 'unma>
Nov 19 19:04:53 GU604 geoclue[4062]: WiFi scan failed
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Nov 19 19:04:53 GU604 systemd[1]: Reached target Sleep.
Nov 19 19:04:53 GU604 systemd[1]: Starting NVIDIA system suspend actions...
Nov 19 19:04:53 GU604 suspend[327097]: nvidia-suspend.service
Nov 19 19:04:53 GU604 logger[327097]: <13>Nov 19 19:04:53 suspend: nvidia-suspend.service
Nov 19 19:04:53 GU604 wpa_supplicant[1692]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 19 19:04:54 GU604 wpa_supplicant[1692]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 19 19:04:54 GU604 wpa_supplicant[1692]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Nov 19 19:04:54 GU604 kernel: rfkill: input handler enabled
Nov 19 19:04:57 GU604 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Nov 19 19:04:57 GU604 systemd[1]: Finished NVIDIA system suspend actions.
Nov 19 19:04:57 GU604 systemd[1]: nvidia-suspend.service: Consumed 2.060s CPU time, 16.9M memory peak.
Nov 19 19:04:57 GU604 systemd[1]: Starting System Suspend...
Nov 19 19:04:57 GU604 systemd-sleep[327126]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Nov 19 19:04:57 GU604 systemd-sleep[327126]: This is not recommended, and might result in unexpected behavior, particularly
Nov 19 19:04:57 GU604 systemd-sleep[327126]: in suspend-then-hibernate operations or setups with encrypted home directories.
Nov 19 19:04:57 GU604 systemd-sleep[327126]: Performing sleep operation 'suspend'...
Nov 19 19:04:57 GU604 kernel: PM: suspend entry (deep)

Last edited by stuckinvim (2024-11-20 11:31:32)

pixeled

Member

Registered: 2024-11-25

Posts: 5

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

Hello,

I registered just to let you know that I am suffering from the exact same issue, also on a Asus Zephyrus M16 (GU604VZ).

Which linux version are you running? I'm asking because I'm under the impression that I had this problem earlier, then it was gone with version 6.11.9, and now its back again with version 6.12.1. I haven't done a rollback to test this though. If I do, I'll come back here to share the results.

edit: It seems that other Asus Zephyrus laptops, such as the G14, (can) also suffer from this issue as discussed here: https://bbs.archlinux.org/viewtopic.php?id=288099. In that case it seemed to be a BIOS issue. I'll see if I can update my BIOS as well and report back.

Last edited by pixeled (2024-11-25 07:27:30)

stuckinvim

Member

Registered: 2024-08-22

Posts: 9

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

I just upgraded to 6.12.1 today, but the issue has been persistent since 6.11.6. I've seen the issues with BIOS on the Zephyrus motherboards on numerous forums (most seem to point to S0 sleep). I'm running v313 of the GU604VI UEFI firmware right now, but the issue is persistent with that as well. I'll do some more digging on this issue and post updates when I can.

pixeled

Member

Registered: 2024-11-25

Posts: 5

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

Okay, good to know, thanks!

I've checked my UEFI and it seems I was also running firmware version 313 already (which seems to be the latest). While in the UEFI I noticed Asus ErP functionality was disabled, so I enabled it, since it also seems to be related to power management as well.

Also just downgraded to 6.11.9 to see if it makes a difference.

Will report back again with some results

pixeled

Member

Registered: 2024-11-25

Posts: 5

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

Small update. Yesterday morning I've changed the following things:

- Enable 'ASUS ErP' setting/feature in the UEFI
- Explicitly added `modprobe.blacklist=nouveau` to my kernel boot parameters (was already in `/etc/modprobe.d/nvidia.conf`, added as a boot parameter to enforce it earlier)
- Downgraded my kernel to version 6.11.9

Since these changes it seems like the laptop is able to go in and out of suspend successfully.

I'll keep monitoring this more closely the next few days and further try to determine which of the three described changes may have lead to this positive behavior.

Last edited by pixeled (2024-11-26 10:46:03)

stuckinvim

Member

Registered: 2024-08-22

Posts: 9

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

Just now seeing this since the past week had me extremely busy. Turns out I already had ErP enabled and the nouveau module blacklisted both in the GRUB command line and in /etc/modprobe.d/50-nvidia.conf. Downgraded to 6.11.9 yesterday, but it doesn't seem to change anything. Some poking around on other forums has led me to some answers that point to configuration issues in /etc/systemd/sleep.conf and /etc/systemd/sleep.conf.d/*.conf, and other answers pointing to potential driver issues on 40 series cards. A little scared to test either though since my laptop is kind of a necessity for university classes, and it's a pain to continuously have to open it up to disconnect the battery to reset the EC just so I can boot...

pixeled

Member

Registered: 2024-11-25

Posts: 5

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

Hey, just a small update again.

Today I upgraded the kernel from 6.11.9 to 6.12.3 (since 6.12.1 also resulted in suspension issues and 6.12.2 seems to have been skipped by Arch?) to see if things have improved. After rebooting I immediately ran into the issue again where the laptop is unable to wake from suspend. After downgrading to 6.11.9 and rebooting, I'm successfully able to go into, and come back from, suspend once more. For me this supports my theory that kernels newer than 6.11.9 seem to have a regression related to system suspend/wake.

Some extra details about my system:
- Out of all nvidia drivers variants for Arch, I've installed the `nvidia-open-dkms` one, currently running version 565.77-1.
- I'm *not* early-loading the nvidia-* modules (i.e. they're not explicitly added to the MODULES in `/etc/mkinitcpio.conf`)
- Aside from the earlier mentioned `modprobe.blacklist=nouveau` kernel boot parameter, I've *not* set any other (nvidia related) kernel parameters (such as `modeset` or `fbdev`)
- I'm running KDE + Wayland (+ SDDM). This is the reason for not having added the above kernel parameters - as I understand, the latest nvidia drivers + Wayland handle this themselves.
- My `/etc/systemd/sleep.conf` seems to be completely default, with all options commented out. I have no `/etc/systemd/sleep.conf.d/` directory
- I've setup the system according to the tips on the Arch Wiki here and here
  - Related to the above, enabling the `nvidia-resume.service` and `nvidia-suspend.service` systemd-services seem to be particularly important - looking at their logs, they are actively doing stuff during suspension and waking up

Hope the above will point you towards a solution for your suspension problems. In the meanwhile I'll keep testing new 6.12.* kernel versions as they come out.

Last edited by pixeled (2024-12-10 08:36:06)

pixeled

Member

Registered: 2024-11-25

Posts: 5

Re: Asus ROG Zephyrus M16 Not Waking From Deep Sleep

In this post/message I will post my luck with the different kernel versions and whether or not the GU604VZ is able to suspend and wake up properly:

- 6.11.9: yes
- 6.12.1: no
- 6.12.3: no (tested 9 december)
- 6.12.4: no (tested 12 december)