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

seth · 2026-02-19 10:08:05

Test nouveau first.

You'll have to add this key to your known gpg keys, https://aur.archlinux.org/cgit/aur.git/ … -kdump#n13 or skip checking, https://wiki.archlinux.org/title/Makepk … e_checking

gpg --search 2DDF72E5A5A55BA89DAA42E1C23D91F3A125FEA8

To stress that, "rebooting" the crash kernel is not like a regular reboot where you'd restart the system, the BIOS posts etcetc, you're booting another kernel while the system keeps running.
You do have the nvidia kernel module installed for the kernel version (I guess you're changing from the main to the LTS one?) you're using as crash kernel?
(This is btw. not necessary - you can use the same kernel binary for both functions, it's a bit like running "exec bash" from a bash prompt)

silverfos_ · 2026-02-21 05:43:49

Running Nouveau as I speak. Sleep issue still there. No changes in that. No brightness control either but that's not the issue here, so it can wait. Either go back to proprietary or find other ways. Anyways,

kexec e

Still gives a black screen. It's possible it isn't a GPU issue too.

"rebooting" the crash kernel is not like a regular reboot where you'd restart the system, the BIOS posts etcetc, you're booting another kernel while the system keeps running.

I didn't know it just changed kernel while running. If kernel is crashed, how will it boot into same kernel again? Considering I'm using same binary (linux lts) for both crash and regular operations...
Also do inform if you need journal for nouveau REISUB too

Last edited by silverfos_ (2026-02-21 05:50:34)

seth · 2026-02-21 08:51:36

If kernel is crashed, how will it boot into same kernel again?

Same way you'd start eg. your browser again after the browser crashes.

Still gives a black screen.

w/ kdump setup??

Does this also happen when only booting the mulit-user.target?
Do you have the suspend issues when booting the multi-user.target along the "nomodeset" kernel parameter?
(2nd link below)

silverfos_ · 2026-02-21 13:36:10

With my own kdump setup, at least screen used to go dark. With simple-kdump it just freezes on last screen when testing. Imma try without gui and get back in a while.

Does this also happen when only booting the mulit-user.target?

Also, if multi-user.target is same as graphical.target, then yes? Well, when links are made it says multi-user.target.wants so yes if going by that logic.
Anyways, assuming nomodeset is without gpu, imma try and get back

So I tried setting default as multi-user since I wasn't sure if it's same or not. And it opened without a graphical interface. To conclude, no it doesn't wake up after suspend WITHOUT nomodeset.
Imma update in a min about with it.
And.... Nope. No wake even with nomodeset
Also can I switch back, away from nouveau? It's bad, I can't lie. 2 tabs and the display looks like a picture taken from a fast moving vehicle.

Last edited by silverfos_ (2026-02-22 07:55:51)

seth · 2026-02-22 08:46:27

No wake even with nomodeset

It's rather unlikely to be the GPU then.

Also can I switch back, away from nouveau?

Yes of course, you don't have to use it beyond immediate tests anyway.

So the kernel resumes (sysrq+b reboots), there's no output regardless of drm or userspace, there's no journal preserved from sysrq+S,U, but apparently it's not the nvme (provided resuming didn't work from a live distro boot)
Had you tried the arch install iso or grml or tinycore linux or so?
r/n I can only imagine some bug in systemd/udev

silverfos_ · 2026-02-26 15:38:28

So I tried same steps in a different USB, cause why not. Opened iso, mounted @root to /mnt and boot efi partition to /mnt/boot.
Did

systemctl suspend

which of course, did not wakeup. Only difference is that, normal suspend the display backlight turns on. This time it didn't.

Last edited by silverfos_ (2026-02-26 15:39:39)

seth · 2026-02-26 21:26:48

normal suspend the display backlight turns on. This time it didn't

sysrq+b would still work, though?

mounted @root to /mnt and boot efi partition to /mnt/boot

what if you don't but instead outright blacklist nvme?

silverfos_ · 2026-02-27 13:49:10

sysrq+b would still work, though?

Yes it did work.

what if you don't but instead outright blacklist nvme?

Wouldn't that just not take the installed Arch in that case? If I did this from iso, I can't mount the root present in nvme since it's blacklisted, can i?

Last edited by silverfos_ (2026-02-27 13:50:03)

seth · 2026-02-27 15:08:48

If I did this from iso, I can't mount the root present in nvme since it's blacklisted, can i?

Yesno you can't - that's the plan. Shy of "try to replace the nvme w/ some ssd".

silverfos_ · 2026-02-28 14:22:37

So... I should mount root, blacklist nvme from the iso and then suspend. Gotcha. Imma try and be back in a min

Alright. Done. Same result. Black screen, no wakeup.
I ran

modprobe -r nvme
modprobe -r nvme_keyring
modprobe -r nvme_auth

Only noticable difference was that it took a few more seconds to suspend and wakeup. Yes, I waited for it to wake up. No signs of it after 5 mins. So not the nvme i suppose. Firmware or something else. Since not GPU either.

Last edited by silverfos_ (2026-02-28 14:42:20)

seth · 2026-02-28 14:43:56

So... I should mount root, blacklist nvme from the iso and then suspend.

No, you'd boot the iso w/ nvme blacklisted (and by inference not able to mount any partition on the nvme at all)

silverfos_ · 2026-02-28 17:49:18

Well, dunno about inferences but I blacklisted the nvme as soon as I booted up the iso. After testing with mount once more, of course

seth · 2026-02-28 19:43:28

Well, dunno about inferences but I blacklisted the nvme as soon as I booted up the iso

You're supposed to boot the system w/ "module_blacklist=nvme" added the the kernel parameters, if you at this point still can mount anything on the nvme, the parameter wasn't applied.

The next/last step would be

seth wrote:

Shy of "try to replace the nvme w/ some ssd".

Or boot a live system w/ the nvme removed from the system.
The system wakes up, the kernel responds, you can issue sysrq+REISUB and at least the B works but the journal doesn't get synced and systemd cannot stumble because SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0 so everything points to a problem w/ the nvme

silverfos_ · 2026-03-01 15:26:17

You're supposed to boot the system w/ "module_blacklist=nvme" added the the kernel parameters, if you at this point still can mount anything on the nvme, the parameter wasn't applied.

Boot into normal arch with that parameter? Sure I can try that.

Or boot a live system w/ the nvme removed from the system.

That, I can't do. I've never gone under the hood of a laptop, nor do I have the necessary tools for it

Yea did the blacklist and... As expected it didn't load the partition and went into emergency shell... I dunno what else I expected
.
.
.
Was i supposed to do this on the iso?
.
Welp, did it anyways. Module blacklisted message when loading iso. And couldn't mount so... Yea. And dunno about REIS but B worked. Oh and, obvious, but no wakeup after sleep

Last edited by silverfos_ (2026-03-01 15:45:56)

seth · 2026-03-01 16:03:48

Was i supposed to do this on the iso?

Yes.

silverfos_ · 2026-03-02 03:51:38

silverfos_ wrote:

Welp, did it anyways. Module blacklisted message when loading iso. And couldn't mount so... Yea. And dunno about REIS but B worked. Oh and, obvious, but no wakeup after sleep

Well, I did.

silverfos_ · 2026-03-10 14:27:25

So... i guess nothing can be done since it is an SSD issue? Am i supposed to inform this issue somewhere with the ssd model mentioned?

seth · 2026-03-10 16:27:19

We do not know what the issue is since we completely lack any data - despite the kernel actually resuming (what's frustrating)
If the system shows the *same* (not! similar) behavior despite the nvme not being accessed and nvme actually being blacklisted it's rather not the nvme.

https://bbs.archlinux.org/viewtopic.php … 6#p2284726
Pair the multi-user.taget w/ "nomodeset initcall_blacklist=simpledrm_platform_driver_init", https://wiki.archlinux.org/title/Kernel_parameters
You might have to also https://wiki.archlinux.org/title/GRUB/T … ramebuffer

silverfos_ · 2026-03-11 14:04:12

Well, i am using systemd boot so grub framebuffer settings not needed i suppose. I shall place the kernel parameters while being in multi-user.target i assume. I'll do so and return journal in a sec.
No wake. Completely black screen.
Journal: https://paste.c-net.org/ChoiceStanford

So I've been looking through the arch wiki for past 3 hours or so. And only now am i discovering a page dedicated to my model:
https://wiki.archlinux.org/title/Lenovo … uspend_bug
And maybe, just maybe, this could be the issue. They said any modern firmware version should fix this but It doesn't seem to help in this case, since mine's the latest available version throughout.
I've been reading into the steps they did in Forum post and I was wondering, should I try the bios reset too? I tried enabling S0xi but issue still persists.

Last edited by silverfos_ (2026-03-11 16:11:04)

A. Rose · 2026-03-11 18:58:42

Hello!

I'm having the same issue with a GTX1650 on the 800xx dkms kernel with linux 6.19.6 and linux-lts 6.18.3; the same issue also occurs when exiting Niri, launching Hyprland, and suspending / closing the lid at any time. I am however able to exit from any X based wm with no issue, so I know for a fact it is an issue with the display briefly powering off (SDDM closes on X ⇒ display goes dark ⇒ Wayland starts and it comes back) wherein the display isn't handled for a short period of time (SDDM closes on X ⇒ display goes dark).

I've followed all the directions in the thread so far, as well as any related documentation I can find.

Unfortunately, I am not able to exit once my screen goes dark with REISUB, as hardware inputs stop being handled (Caps lock doesn't toggle, etc.)

When testing on a rolled back system version with timeshift, everything works as expected, so I know it's not a hardware issue, my system is also not dual booted, so I know at least on my end that isn't a factor.

I've attached some information here, though for the time being it doesn't have anything you don't already have, so I'll continue watching this thread for now.

https://0x0.st/s/nMfOknMe4bB0-fwVv4xIvA/P2y5.txt

UPDATE: I did another test with a second system SSHing in and found that the display can power off without any issues, it's specifically turning the display back on when the lid opens which causes the system to hang. The display comes on fine when booting and loading into SDDM, so it must be an issue outside of that.

Last edited by A. Rose (2026-03-11 19:10:09)

seth · 2026-03-11 21:42:15

framebuffer settings not needed i suppose

"not possible" - unfortunately

The wiki wrote:

If dual booting, Windows updates may trigger the BIOS to enter a confused state.

https://bbs.archlinux.org/viewtopic.php … 4#p2285434

A.Rose wrote:

I am not able to exit once my screen goes dark with REISUB, as hardware inputs stop being handled (Caps lock doesn't toggle, etc.)

THis would constitute a completely different problem, systems failing to wake at all happens more frequently, but for the OP the kernel resumes and handles keyboard input, we just can't get any log data about what actually is failing then.

GTX1650 on the 800xx dkms kernel with linux 6.19.6 and linux-lts 6.18.3 … testing on a rolled back system version with timeshift, everything works as expected

In your case it seems to be around 6.19 + nvidia 580xx

I am not able to exit once my screen goes dark with REISUB, as hardware inputs stop being handled (Caps lock doesn't toggle, etc.)

The capslock led isn't a strong indicator whether the sysrq will still work, https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - nb. that you've to explicitly enable that first.

I've attached some information here

Ideally post the full system journal for the boot, but also please open a new threads since your problem differs in many aspects from the situation at hand.

silverfos_ · 2026-03-12 13:21:16

The wiki wrote:

If dual booting, Windows updates may trigger the BIOS to enter a confused state.
https://bbs.archlinux.org/viewtopic.php … 4#p2285434

No updates in windows since then. As i have mentioned, since this is ltsc it seldom gets any updates so fast boot is still off.

silverfos_ · 2026-03-16 13:35:10

Just to add something, I don't know if it is related or not. When you reach the login screen of Arch after boot, none of the buttons for shutdown or restart or sleep work. Is that also die to the s2idle situation?

seth · 2026-03-16 14:26:22

When you reach the login screen of Arch after boot, none of the buttons for shutdown or restart or sleep work.

Do the later/ever and is this the case w/ any DM (also which one are you currently using?)

silverfos_ · 2026-03-17 16:45:56

seth wrote:

Do the later/ever and is this the case w/ any DM (also which one are you currently using?)

Currently Using SDDM. haven't tried wit others. What did you mean by Later/ever?

Arch Linux

#51 2026-02-19 10:08:05

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

#52 2026-02-21 05:43:49

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

#53 2026-02-21 08:51:36

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

#54 2026-02-21 13:36:10

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

#55 2026-02-22 08:46:27

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

#56 2026-02-26 15:38:28

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

#57 2026-02-26 21:26:48

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

#58 2026-02-27 13:49:10

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

#59 2026-02-27 15:08:48

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

#60 2026-02-28 14:22:37

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

#61 2026-02-28 14:43:56

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

#62 2026-02-28 17:49:18

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

#63 2026-02-28 19:43:28

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

#64 2026-03-01 15:26:17

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

#65 2026-03-01 16:03:48

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

#66 2026-03-02 03:51:38

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

#67 2026-03-10 14:27:25

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

#68 2026-03-10 16:27:19

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

#69 2026-03-11 14:04:12

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

#70 2026-03-11 18:58:42

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

#71 2026-03-11 21:42:15

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

#72 2026-03-12 13:21:16

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

#73 2026-03-16 13:35:10

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

#74 2026-03-16 14:26:22

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

#75 2026-03-17 16:45:56

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

Board footer