You are not logged in.
Pages: 1
Hi,
When I suspend, either manually or through timeout, I get a black screen with a cursor and the computer does not sleep. This is the same with a fresh install, however sleeping functions normally on windows.
Any ideas?
Cheers guys
Edit:
Hardware
i5-11400 - B560m
980ti
gnome - 41.1
X11
Last edited by Cactus_Chaos (2022-01-16 07:05:26)
Offline
https://bbs.archlinux.org/viewtopic.php?id=57855
What hardware, what's in the logs?
Offline
Online
https://bbs.archlinux.org/viewtopic.php?id=57855
What hardware, what's in the logs?
Added the hardware, any idea what logs would be most helpful?
Offline
Yes, the system journal for the boot where you tried and failed to suspend the system - "sudo journalctl -b" if it's the current one.
Online
When sleeping I can't exit the screen, hence forced to just power of my pc. See logs below after suspend executed ![]()
Dec 08 17:35:01 Desktop rtkit-daemon[3261]: Supervising 4 threads of 1 processes of 1 users.
Dec 08 17:35:01 Desktop rtkit-daemon[3261]: Successfully made thread 3889 of process 3219 owned by '120' RT at priority 5.
Dec 08 17:35:01 Desktop rtkit-daemon[3261]: Supervising 5 threads of 1 processes of 1 users.
Dec 08 17:35:01 Desktop systemd[595]: Started Sound Service.
Dec 08 17:35:01 Desktop gnome-shell[1276]: Registering session with GDM
Dec 08 17:35:05 Desktop NetworkManager[460]: <info> [1638948905.1718] manager: sleep: sleep requested (sleeping: no enabled: yes)
Dec 08 17:35:05 Desktop NetworkManager[460]: <info> [1638948905.1719] manager: NetworkManager state is now ASLEEP
Dec 08 17:35:05 Desktop gnome-shell[1276]: Screen lock is locked down, not locking
Dec 08 17:35:05 Desktop systemd[1]: Reached target Sleep.
Dec 08 17:35:05 Desktop systemd[1]: Starting System Suspend...
Dec 08 17:35:05 Desktop systemd-sleep[5042]: Entering sleep state 'suspend'...
Dec 08 17:35:05 Desktop kernel: PM: suspend entry (deep)Offline
"sudo journalctl -b", but because of the new revelation about the post-sleep condition, that's probably not getting us anywhere.
See the link I psoted in #3 and since you mentioned it: also the 3rd link below (mandatory, check the windows settings, don't assume)
Online
I have disable fast-boot and hibernate on all windows OS (Sleep works fine on windows). Still no cigar, had a look at the third link but not quite sure how to best use.
Offline
Did you reboot both OS (windows twice because of voodoo) after disabling windows fast-start?
"had a look at the third link" you mean the link in https://01.org/blogs/rzhang/2015/best-p … ate-issues ?
Read it and start working through the "Debugging" section.
Online
Sorry for the late reply.
Reinstalled Arch on the SSD without windows (Only new arch instance is in Grub).
Just using terminal, now when the command:
systemctl hybrid-sleepIs ran, the system sleeps, and relaunches on mouse movement. However the screen is frozen (No cursor movement) and does not respond to mouse movement.
Although Alt f1/f2 switches between a black screen with still cursor.
Starting to sound like something funky about the motherboard:
B550m Aurus Pro
Offline
Can you suspend and resume from the mutli-user.target (no gnome, see 2nd link below)
Online
Tried suspending with mult-user.target (Note didn't install gnome on this clean install), same thing. Keyboard and mouse turn off then on, same black screen or back to the terminal with ctl-alt-f1 but frozen.
Thanks
Offline
How do you have a mouse on the multi-user.target?
The point of the test is to avoid a display server.
Online
As in the leds on them haha ![]()
Offline
So the usb powers up again.
Next test: try to boot w/ "nomodeset", https://wiki.archlinux.org/title/Kernel_parameters and try from there to see whether the problem is the drm.
Do you btw. have the opportunity to ssh into the malfunctioning system?
Online
Issue has gone away with latest update!
Offline
For future reference. I had the same problem; whenever suspend was triggered (either manually, through timeout, or lid close) computer would initiate the suspend sequence and then get stuck on a blank screen with a cursor, and would not respond to any input other than a forced reboot through SysRq. My setup:
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
NVIDIA GeForce RTX 2070
Gnome 41.3
Xorg 21.1.3-1
nvidia 495.46-9
Kernel v5.16.1-arch1-1My journalctl -b-1 after a reboot looked exactly like OP's. I then tried setting nomodeset=0 in my kernel boot line; this worked but prevented the NVIDIA card from detecting the built-in laptop display (I could only use an external display connected to a mini-DP port). nvidia-drm.modeset=0 did not have any effect whatsoever.
In the end, what worked for me was disabling the systemd units for advanced NVIDIA power-management (i.e. reverting to the kernel-driver callback-based power management, https://forums.developer.nvidia.com/t/f … 470/187150):
$ sudo systemctl disable nvidia-{resume,hibernate,suspend}.service
$ sudo systemctl stop nvidia-{resume,hibernate,suspend}.service # for good measure, although they should be stoppedOffline
"… disable --now …"
So writing to the NVreg_TemporaryFilePath blocked the S3? Where did you direct that?
Online
Pages: 1