You are not logged in.

#1 2022-07-17 00:23:26

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 18,648

[SOLVED] VivoBook 17 K712EA Won't resume after suspend

Still tuning my new laptop.  The last major issue remaining is that the device will suspend, but when it wakes up the back light comes on, and the previous display remains on the screen, but nothing else happens.  No more journal entries, no response to keyboard or mouse, clock does not update, cannot ping the box from the net..  It is an Intel system with Intel Iris Xe graphics.

I have updated the uEFI firmaware.
I get the same results with sddm/plasma, gdm/Gnome, and booting to Multiuser.target and using only the console.

The tail of the journal after attempting from just the console looks as such:

ewaller@odin/home/ewaller % journalctl -b -11 | tail
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5040] dhcp4 (wlan0): state changed no lease
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5043] dhcp6 (wlan0): canceled DHCP transaction
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5043] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5043] dhcp6 (wlan0): state changed no lease
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5069] device (wlan0): set-hw-addr: set MAC address to 86:40:2F:AF:16:60 (scanning)
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5118] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jul 16 12:16:23 odin NetworkManager[362]: <info>  [1657998983.5141] device (wlan0): set-hw-addr: reset MAC address to F4:26:79:3F:CD:16 (unmanage)
Jul 16 12:16:23 odin systemd[1]: Reached target Sleep.
Jul 16 12:16:23 odin systemd[1]: Starting System Suspend...
Jul 16 12:16:23 odin systemd-sleep[701]: Entering sleep state 'suspend'...
ewaller@odin/home/ewaller % 

From Plasma/sddm

ewaller@odin/home/ewaller % journalctl -b -2 | tail
Jul 16 15:49:10 odin wpa_supplicant[474]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Jul 16 15:49:10 odin wpa_supplicant[474]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jul 16 15:49:10 odin kscreenlocker_greet[1033]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Jul 16 15:49:10 odin wpa_supplicant[474]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jul 16 15:49:10 odin wpa_supplicant[474]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Jul 16 15:49:10 odin kscreenlocker_greet[1033]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Jul 16 15:49:10 odin systemd[1]: Reached target Sleep.
Jul 16 15:49:10 odin systemd[1]: Starting System Suspend...
Jul 16 15:49:10 odin systemd-sleep[1079]: Entering sleep state 'suspend'...
Jul 16 15:49:10 odin kernel: PM: suspend entry (s2idle)
ewaller@odin/home/ewaller % 

I've tried command line switches :
init_on_alloc=0 and intel_iommu=off

Nothing in the uEFI setup menu is particularly interesting.  I can enable hyperthreading and VM support.  I can influence USB configuration and a few other things.  Boot order, Secure boot, and firmware passwords.    Nothing about sleep modes, PCI-e configurations.  Nothing about Fast Boot or Intel Rapid Start Technology.  No fast boot partition on the system when new.

Did I miss anything, or do I need to wait for the kernel to transmogrify?   It is not a big deal, this system spends 99% of its life on shore power, has reasonable battery life (without standby), and boots from a cold start to sddm in under 4 seconds.

Last edited by ewaller (2022-07-31 17:28:49)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#2 2022-07-31 17:28:27

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 18,648

Re: [SOLVED] VivoBook 17 K712EA Won't resume after suspend

Solved

Turn off VMD in the uEFI setup menu. (sometimes mistakenly called the BIOS menu)

https://www.asus.com/no/support/FAQ/1044458/

Has to do with IRST (Intel rapid start technology).   Notes below are primarily for If I come back to try to enable IRST in the future.

The system has a partition that was present in the system as delivered that is the size of my RAM:

/dev/nvme0n1p2     534528     567295      32768    16M Microsoft reserved

But the partition type is not what I wold expect according to the WiKi.
The Wiki says the partition type should be Intel Fast Flash, but it seems to be Microsoft Reserved
https://wiki.archlinux.org/title/Power_ … ogy_(IRST)
From the l subcommand of fdisk

...
Intel Fast Flash               D3BFE2DE-3DAF-11DF-BA40-E3A556D89593
...
Microsoft reserved             E3C9E316-0B5C-4DB8-817D-F92DF00215AE

Is it possible that this system is using E3C9E316-0B5C-4DB8-817D-F92DF00215AE for IRST?  That is the only thing that makes sense.

Regardless, the original issue of not waking from sleep is resolved.

Last edited by ewaller (2022-07-31 17:31:58)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

Board footer

Powered by FluxBB