Display doesn't power on after sleep/suspend (lid close or menu)

silverfos_ · 2026-01-30 16:27:58

seth wrote:

Did the ACPI errors only appear after switching to the 580xx drivers (and are you currently still using those)?

no, it's always been there ever since I first installed. Just that since you mentions ACPI i payed attention to it.

Also, you're stubbornly ignoring the comments about
seth wrote:
don't ignore the windows fast start condition (this isn't optional)

Oh my bad i forgot to specify. It's been off since the first day I got this pc. I haven't turned it on since.
Here's the cat:
https://paste.c-net.org/IglooHodges

Last edited by silverfos_ (2026-01-30 16:30:08)

seth · 2026-01-30 20:01:02

It's been off since the first day I got this pc. I haven't turned it on since.

But maybe Microsoft did (this frequently happens w/ updates) - please have a look and ensure that fast-start is still disabled.

silverfos_ · Yesterday 03:30:32

Ran the powercfg command again for safe measure. It is disabled (I haven't updated since the first use day, since I switched to win10 ltsc immediately). No change in suspend

seth · Yesterday 14:45:32

So the kernel resumes, but you're losing the nvme and it's not (likely) APST.
Ahead of the nvme is an mt7921e - can you disable the wifi chip in the UEFI?
Does the system resume from suspend when using nouveau instead of nvidia?

silverfos_ · Today 13:20:22

seth wrote:

So the kernel resumes, but you're losing the nvme and it's not (likely) APST.
Ahead of the nvme is an mt7921e - can you disable the wifi chip in the UEFI?

disabled. here's the journalctl:
https://paste.c-net.org/SilentFrankie
as for nouveau, i will update in the future.
Additionally, is there any specific reason why the "root directory is getting lost"? It doesn't happen on the windows so it shouldn't be cause of the specific SSD, should it?

Last edited by silverfos_ (Today 14:12:38)

seth · Today 15:11:35

This is conjecture, based off the fact that despite rebooting w/ sysrq+REISUB the wakeup isn't logged.
Why that is, if that is, is what we're trying to figure - but the HW most likely will no longer respond.
The usual suspects would be aspm, apst and of course a hibernating windows - but apparently that's not the cause.

You could try to lie to the BIOS,

acpi_osi=! acpi_osi="Windows 2015"

https://learn.microsoft.com/en-us/windo … inacpi-osi

Can you btw. reboot by frenetically pressing ctrl+alt+del?

Arch Linux

#26 2026-01-30 16:27:58

Re: Display doesn't power on after sleep/suspend (lid close or menu)

#27 2026-01-30 20:01:02

Re: Display doesn't power on after sleep/suspend (lid close or menu)

#28 Yesterday 03:30:32

Re: Display doesn't power on after sleep/suspend (lid close or menu)

#29 Yesterday 14:45:32

Re: Display doesn't power on after sleep/suspend (lid close or menu)

#30 Today 13:20:22

Re: Display doesn't power on after sleep/suspend (lid close or menu)

#31 Today 15:11:35

Re: Display doesn't power on after sleep/suspend (lid close or menu)

Board footer