Monitor not turning on after hibernating

Lamboorg · 2025-11-18 05:21:07

When getting my screen locked and eventually getting into hibernation for some reason my monitor does not turn back on, and if it was to turn on it would simply freeze.
I'm using nvidia and installed the correct/latest drivers and enabled hibernation.

I'm using SDDM display manager.

Does someone know the solution to this problem I'm facing?

seth · 2025-11-18 09:01:37

No, but we'll need some details on the situation.
Notably whether "hibernation" actually refers to S4 or maybe S3 or s2idle.
When it "simply freezes", can you still reboot w/ the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (nb. you'll have to first enable it *before* the freeze) + RESUB?
Then please post your complete system journal for the previous boot (w/ the failing wakeup)

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Lamboorg · 2025-11-19 11:39:05

Hi seth,

Thanks for the clarification. I've gathered the details you requested:

I let the pc hibernate and here is a full log with that event happening: https://0x0.st/Kfdw.txt

The output for cat /sys/power/mem_sleep is s2idle [deep]

Let me know if you need any further logs or information!

Thanks for helping

seth · 2025-11-19 15:16:43

Nov 19 19:59:53 archlinux systemctl[17248]: Call to Hibernate failed: Not enough suitable swap space for hibernation available on compatible block devices and file systems
Nov 19 20:00:05 archlinux systemctl[17449]: Call to Hibernate failed: Not enough suitable swap space for hibernation available on compatible block devices and file systems

Nov 19 20:09:05 archlinux kernel: ACPI: PM: Preparing to enter system sleep state S3

There's an enormous amount of noise that seems to come from the rtl8192ee device but the system wakes up and then continues until you

Nov 19 20:16:37 archlinux systemd-logind[630]: Power key pressed short.
Nov 19 20:16:37 archlinux systemd-logind[630]: Powering off...
Nov 19 20:16:37 archlinux systemd-logind[630]: System is powering down.

What brings us to
* nvidia
* hyprland
* hyridle

Can you suspend and wake the system from the multi-user.target (2nd link below)
If yes, can you from not-hyprland (be it weston or, ideally, and uncomposited X11 session, "startx")
Can you ssh into the system and restart the graphical target (there's confusingly sddm AND uwsm???)

In doubt "module_blacklist=ucsi_ccg,nvidia_uvm", https://wiki.archlinux.org/title/Kernel_parameters (the USB controller on the nvidia GPU and uvm is mostly relevant for CUDA)

Lamboorg · 2025-11-19 16:43:52

I tried suspending the system in TTY and Weston which also worked perfectly fine with Hyprland. The problem is when I tried to just leave my PC as is, and wait for automatic suspension.

Like always it suspended after a few minutes. But this time when turning it on I gave it fully 3-4 minutes. In the first 2 minutes the monitor as always wasn't turning on but then the login screen suddenly popped up.

It kind of worked except for the fact that I had this as well before. This time it actually did not freeze when I got to log back in for some reason, but the previous times i tried to login, it did freeze. So my best guess is that when it suspends the system for a prolonged time it starts to freeze (I don't know if that makes sense but at least the previous times I let my PC sit for much longer).

About the rtl8192ee, that should be my WiFi adapter that I never use since I prefer cable all the way. The noise happened also on other distros that I used before making my decision to step up my learning journey with Arch.

Hibernating manually does not work because:

 systemctl hibernate                                                                                                                                         
Call to Hibernate failed: Not enough suitable swap space for hibernation available on compatible block devices and file systems

I was told by a guy on my journey that swap space are most important when you don't have a lot of RAM. In this installation I did want to have swap space so I configured it anyways. I also have 32GB of RAM tho. Is it the swap space causing issues? I'm using zram to simplify everything. Think it's more efficient.

If all that makes no sense, I guess the only valid problem is SDDM or NVIDIA (even tho I configured it and ran:

sudo systemctl enable nvidia-suspend.service
sudo systemctl enable nvidia-hibernate.service
sudo systemctl enable nvidia-resume.service

)

seth · 2025-11-19 20:26:04

I was told by a guy on my journey that swap space are most important when you don't have a lot of RAM.

https://chrisdown.name/2018/01/02/in-de … -swap.html

However if you don't run OOM you don't need swap - except for actual hibernation (S4) but even a dynamically created swapfile can do in that case.

If all that makes no sense, I guess the only valid problem is SDDM or NVIDIA (even tho I configured it and ran:

Try https://wiki.archlinux.org/title/SDDM#Wayland - https://bbs.archlinux.org/viewtopic.php … 7#p2273377
What's up about

seth wrote:

there's confusingly sddm AND uwsm?

why are you somehow using both?

Though b/c

also worked perfectly fine with Hyprland. The problem is when I tried to just leave my PC as is, and wait for automatic suspension

I guess hypridle also locks the screen or at least first triggers some kind of DPMS?
Can you disable that and only make it automatically?

Lamboorg · 2025-11-20 06:35:30

seth wrote:

there's confusingly sddm AND uwsm?
why are you somehow using both?

when I installed Hyrpland, two sessions were installed, "Hyprland (uwsm-managed)" and just "Hyprland". I didn't see that "Hyprland (uwsm-managed)" was selected as default until you mentioning that I was using SDDM + uwsm.

Thanks for the info about swap space!

Today again I left my PC for 5 minutes to let it suspend "automatically" and the issue was not there. With issue I mean it did not freeze. Upon waking up the system for some reason SDDM does not load my wallpaper but at least the freeze problem did not occur. I assume that when having multiple windows open or services running it freezes, but for now, for some reason the issue freezing issue is not here anymore (could also be because I switched my default session to the standard "Hypland" session which gives me less issues).

Since: https://wiki.archlinux.org/title/SDDM#Wayland

SDDM considers its Wayland support experimental.

I guess that having some sort of issues with wallpaper on the locked screen could be normal.

I think the best option at this point would be to just leave it as it is (since the freezing issue stopped for some reason) and/or comment out the part where it locks my user after being idle.

Thanks for all the links, were really useful to get a better understanding with what I'm doing

Also I got to see how I'm going to fix the issue with my wireless card.

seth · 2025-11-20 08:32:50

Also I got to see how I'm going to fix the issue with my wireless card.

Do you have an UEFI option to disable it?

Ftr:

and the issue was not there

Is this now w/ or w/o setting SDDM to the wayland backend?

Lamboorg · 2025-11-20 19:24:26

seth wrote:

Is this now w/ or w/o setting SDDM to the wayland backend?

It was without. I was gonna set it but since the issue kind of resolved now I preferred to leave it at that and see how it goes.

Most probably it was SDDM + uwsm having conflicts.

I'm gonna observe this behaviour and see if it should happen again throughout the next day.

About the wireless card, instead of disabling it through my boot manager I tried installing the newest firmware with pacman. Haven't seen any noise since the last time I checked journalctl. I will check on that as well in throughout the next day.

Lamboorg · 2025-11-26 11:58:24

I'm reporting back after observing my system for a few days.

The monitor "No signal"/freezing issue despite the system turning on did happen about once. I'm not really sure what the problem is since I was not able to find any information in my journal logs.

About the Wireless Card giving a lot of noise in my logs has been fixed by installing/updating the appropriate firmware I was not aware of.

For now I assume that the issue is being caused by an app or program that I'm using and when the system goes to sleep it's interfering with stuff so I'll keep an eye out for the apps running.

Thank you seth for helping me, I think by pointing out that I was using SDDM and uwsm at the same time I was able to get most problems out of the way by changing to the standard hyprland session and the wake-up process is working way better than before.

seth · 2025-11-26 12:37:28

The monitor "No signal"/freezing issue despite the system turning on did happen about once. I'm not really sure what the problem is since I was not able to find any information in my journal logs.

If the system doesn't resume you won't get any logs about it not resuming - the best you can hope fore are problem indicators *before* the suspend.

Arch Linux

#1 2025-11-18 05:21:07

Monitor not turning on after hibernating

#2 2025-11-18 09:01:37

Re: Monitor not turning on after hibernating

#3 2025-11-19 11:39:05

Re: Monitor not turning on after hibernating

#4 2025-11-19 15:16:43

Re: Monitor not turning on after hibernating

#5 2025-11-19 16:43:52

Re: Monitor not turning on after hibernating

#6 2025-11-19 20:26:04

Re: Monitor not turning on after hibernating

#7 2025-11-20 06:35:30

Re: Monitor not turning on after hibernating

#8 2025-11-20 08:32:50

Re: Monitor not turning on after hibernating

#9 2025-11-20 19:24:26

Re: Monitor not turning on after hibernating

#10 2025-11-26 11:58:24

Re: Monitor not turning on after hibernating

#11 2025-11-26 12:37:28

Re: Monitor not turning on after hibernating

Board footer