Arch Linux

CabalCrow

Member

Registered: 2024-05-14

Posts: 22

Asus laptop can't wakeup or turn off after closing the lid.

After closing the lid and then opening it back up the laptop has gone asleep and is completely unresponsive. Nothing can wake it up or turn it off. I need to wait for it to run out of power to turn it off.

The kernel version is 6.6.59-1-lts. The content of /sys/power/mem_sleep is [s2idle].

Any idea what could be the issue, and if there is a way to fix this or at least disable the sleep when closing the lid?

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,738

Website

Re: Asus laptop can't wakeup or turn off after closing the lid.

Is this a new laptop? Try the linux package instead, perhaps the hardware is too new for the LTS kernel.

Holding the power button down for 4 seconds hard resets most laptops (at the risk of data corruption), if that helps at all.

What is your graphics hardware & driver?

lspci -knn -d ::03xx

---

Para todos todo, para nosotros nada

CabalCrow

Member

Registered: 2024-05-14

Posts: 22

Re: Asus laptop can't wakeup or turn off after closing the lid.

I thought the power button didn't work, but I was just not holding it long enough - you need to hold it for full 20 seconds on my laptop to actually force a power off.

I will try the new kernel, the laptop is somewhat new I just realised I forgot to mention the model: asus vivobook M1605X.

Here the lspci output:

03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:1a13]
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

pixeled

Member

Registered: 2024-11-25

Posts: 7

Re: Asus laptop can't wakeup or turn off after closing the lid.

Hello CabalCrow,

Just writing to inform you (and other readers) that this sounds very similar to an issue I'm facing with my Asus Zephyrus M16, currently being discussed here. There's also a recent report of someone where the laptop freezes on wakeup here, but I'm not sure if its related. Your issue sounds very similar to mine (and another user) however, it has the exact same symptoms. There does not seem to be a solution yet, but I the more the merrier I suppose?