You are not logged in.
As said in the title, when I suspend the laptop, and open it back, it freezes, I can't use my mouse, I can't move to TTY, I can't do a thing, and my caps lock key led starts flickering, the only thing I can do is force shutdown the laptop, saying that here is some information about my laptop:
Host: HP ZBook Fury 17.3 inch G8 Mobile Workstation PC (SBKPFV3)
Kernel: Linux 6.12.66-1-lts
WM: KWin (Wayland)
CPU: 11th Gen Intel(R) Core(TM) i7-11850H (8) @ 4.80 GHz
GPU 1: NVIDIA RTX A5000 Mobile
GPU 2: Intel UHD Graphics @ 1.45 GHz [Integrated]
Memory: 3.87 GiB / 62.47 GiB (6%)
Swap: Disabled
I started experiencing that when i switched my graphics from discrete to hybrid ( to save battery ), not that i use nvidia open modules so here are the results of
pacman -Q | grep "nvidia"lib32-nvidia-utils 590.48.01-1
libva-nvidia-driver 0.0.14-1
linux-firmware-nvidia 20260110-1
nvidia-open-dkms 590.48.01-2
nvidia-prime 1.0-5
nvidia-settings 590.48.01-1
nvidia-utils 590.48.01-2I am highly suspecting the GPU is the cause, I tried to ask ai about it since its my first time using hybrid graphics in arch but didn't reach a thing, another problem that i guess its related to the GPU is that when booting to the system and after the boot, sddm doesn't work, well, it works sometimes and some others it doesn't work, but when i do
sudo systemctl restart sddm it works fine
I am open to share some logs if that will help.
Last edited by RayenHadd (2026-01-28 14:38:54)
Offline
Read https://bbs.archlinux.org/viewtopic.php?id=311852 and see whether you can produce a journal when rebooting w/ sysrq+REISUB
booting to the system and after the boot, sddm doesn't work, well, it works sometimes and some others it doesn't work, but when i do
sudo systemctl restart sddm
it works fine
Online
Read https://bbs.archlinux.org/viewtopic.php?id=311852 and see whether you can produce a journal when rebooting w/ Sysrq+REISUB
Thanks for the suggestions, I have enabled the Sysrq + REISUB binding, and it worked with me, And firstly I logged a journal of the sddm problem, I wanted a clean journal, to see what happens, so I did:
sudo journalctl -b > journal.txtthat I will share, then I suspended the system, three times, one before enabling the REISUB bindings and this is what I have noticed:
The system doesn't freeze instantly, it waits for a second or half and freezes
second attempt was after enabling the REISUB bindings and this is what I noticed:
The system goes on sleep mode successfully
Unexpectedly the system wakes up normally from the sleep mode
As you can see it seems like everything is working normally so for the third time I did click the sleep button on my KDE menu and I noticed that:
The system show text (I guess its log)
I cannot move to TTY and do anything
More text shows up after I do the REISUB bindings
the text looks like a log, I took a picture of it, the logs are in this format:
[147.72…. (dots replaces a lot of numbers)] CPU or (GPU I don't know the picture is not clear, but It's not only [C/G]PU there is a lot of other things): ...........
This is an example how a line looks if somebody can identify it,
there is in the logs a lot of intel and Nvidia stuff, I tried to see those logs by doing
sudo journalctl -k -b -1Here is the detailed logs (I see a lot of Nvidia errors): https://paste.c-net.org/HistoryRigged
Here are the logs of the first login (sddm related): https://paste.c-net.org/BubblesBasket
Here are the logs of error after suspend done with simple
sudo journalctl -b -1https://paste.c-net.org/WinslowGlands
Hope these logs helps, thanks.
Offline
Jan 27 13:37:23 artbook kernel: PM: suspend exit
Jan 27 13:37:23 artbook kernel: NVRM: kgspHealthCheck_TU102: ****************************** GSP-CrashCat Report *******************************
Jan 27 13:37:23 artbook kernel: NVRM: kgspPrintGspBinBuildId_IMPL: GSP bin buildId: cf812cb3f2f1e8c8209dc2e446fdf536ba9ec88f
Jan 27 13:37:23 artbook kernel: NVRM: GPU at PCI:0000:01:00: GPU-d6d45493-ad27-63b7-7786-8e7c414c8bce
Jan 27 13:37:23 artbook kernel: NVRM: Xid (PCI:0000:01:00): 120, GSP task panic: unknown error (0) @ pc:0x19da988, aux:0x0, partition:2#0, task:3Hybrid graphics, nvidia Ampere.
Try https://aur.archlinux.org/packages?O=0&K=580xx and disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware
Might relate to https://wiki.archlinux.org/title/PRIME# … Management - try to add "nvidia.NVreg_DynamicPowerManagement=0x03" to the https://wiki.archlinux.org/title/Kernel_parameters
Online
Hybrid graphics, nvidia Ampere.
Try https://aur.archlinux.org/packages?O=0&K=580xx and disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware
Might relate to https://wiki.archlinux.org/title/PRIME# … Management - try to add "nvidia.NVreg_DynamicPowerManagement=0x03" to the https://wiki.archlinux.org/title/Kernel_parameters
Thanks for the downgrading tip, I downgraded and the suspend functionality works very well, but still the sddm problem is not solved, I have tested with and without these kernel parameters
nvidia.NVreg_DynamicPowerManagement=0x03, nvidia.NVreg_EnableGpuFirmware=0but still sometimes sddm shows and works and most of the time it doesn't and i need to manually do
sudo systemctl restart sddmin a TTY environment, other than that i will follow more in the https://forums.developer.nvidia.com/c/g … /linux/148 to see when to upgrade from version 580, if you have any idea on how to solve the sddm problem, i will be happy to apply it to my system so sddm works the way it should, thanks for your help.
Offline
The simple approach is to slightly delay the SDDM start (this has shown up a lot recently, across the DMs and GPUs, most likely systemd at work)
Online
The simple approach is to slightly delay the SDDM start (this has shown up a lot recently, across the DMs and GPUs, most likely systemd at work)
Thank you very much, you really helped me, by delaying sddm by 2 seconds, it works normally now, for anyone who's reading in this thread, I delayed sddm launch by, executing the following
# This command creates a directory if it doesn't exist
sudo mkdir -p /etc/systemd/system/sddm.service.d
# Edits and creates a file
sudo nvim /etc/systemd/system/sddm.service.d/delay.confand when you open the editor add the following:
[Service]
ExecStartPre=/bin/sleep 2And it will work with you.
Note that I did that because
sudo systemctl edit sddm.service didn't work for me.
Thanks for the help.
Offline
"Didn't work" how?
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online
"Didn't work" how?
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Thanks, I did,
for the systemctl command and why it didn't work, I don't know exactly, that's what I did:
sudo systemctl edit sddm
Found modifications outside of the staging area, which would be discarded.
/etc/systemd/system/sddm.service.d/override.conf: after editing, new contents are empty, not writing file.So I created delay.conf to solve the problem, I don't know if KDE plasma did something here "/etc/systemd/system/sddm.service.d/override.conf",
Thanks for the help.
Offline