I do not have an nVidia GPU, so I cannot confirm this. I have a discrete GPU though.
Weird thing of EOS is that I could find no place where to file bugs and discuss with developers.
Try official Telegram group https://t.me/Endeavouros
With olders kernel (worked hibernate) - driver for discrete GPU loaded and running?
Bugs with the installation can be reported here:
In case of specific code related issue/bug you can also report on GitHub directly (But forum is the first place in most cases):
And you can find me on telegram all the time as i got message on my phone in case, tag me there will help too:
I can answer most questions or forward.
With olders kernel (worked hibernate) - driver for discrete GPU loaded and running?
Yes, my current configuration is to only use the dGPU.
Tried to discuss the issue in telegram, but nothing new came up. The problem remains.
When I’ll find the time, I’ll try to install arch on a USB pen drive to see what happens with mkinitcpio and dracut.
I bet it is somehow kernel related, not dracut, as i have 3 devices with no issue hibernating. 2 AMD CPU and one intel.
And LTS-Kernel is 6.12, and is also still working for you?
We do have a patched dracut version on EndeavourOS now too.
Check if you have it:
sudo pacman -Qs dracut
Yes, the LTS kernel 6.12 works and was even updated today. There is no Dracut update yet.
Why could it be Dracut? We found out in our experiments in Telegram that hibernation works in LTS and Zen kernels until i install the NVIDIA driver (package). After installing NVIDIA, hibernation stops working.
Although, there are probably different situations.
yes totally unclear.. let me check if i can hibernate running Nvidia ..
journalctl -b -0 | grep resume
Sep 10 10:18:08 joe-b550gamingxv2 kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=XXX rw rootflags=subvol=@ nowatchdog nvme_load=YES resume=UUID=XXX nvidia_drm.modeset=1 loglevel=3
Sep 10 10:18:08 joe-b550gamingxv2 kernel: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=XXX rw rootflags=subvol=@ nowatchdog nvme_load=YES resume=UUID=XXX nvidia_drm.modeset=1 loglevel=3
Sep 10 10:18:08 joe-b550gamingxv2 systemd-hibernate-resume-generator[270]: Reported hibernation image: ID=endeavouros kernel=6.16.5-arch1-1 UUID=XXX offset=0
Sep 10 10:18:08 joe-b550gamingxv2 dracut-cmdline[336]: Using kernel command line parameters: rd.driver.pre=btrfs BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=XXX rw rootflags=subvol=@ nowatchdog nvme_load=YES resume=UUID=XXX nvidia_drm.modeset=1 loglevel=3
Sep 10 10:18:08 joe-b550gamingxv2 systemd-hibernate-resume[589]: Reported hibernation image: ID=endeavouros kernel=6.16.5-arch1-1 UUID=XXX offset=0
Sep 10 10:18:08 joe-b550gamingxv2 kernel: PM: hibernation: resume from hibernation
Sep 10 10:18:37 joe-b550gamingxv2 kernel: PM: hibernation: resume failed (-5)
Sep 10 10:18:37 joe-b550gamingxv2 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
Sep 10 10:18:37 joe-b550gamingxv2 systemd[1]: systemd-hibernate-resume.service: Consumed 3.674s CPU time, 2M memory peak.
kernel: PM: hibernation: resume failed (-5)
is all it shows .. so same here using Nvidia no issue hibernating without Nvidia on the same machine (disable the device vifo)
Kernel 6.16.5-arch1-1, Intel graphics, no NVIDIA — all good:
$ journalctl -b -u systemd-hibernate
Sep 10 10:29:19 t14-mch systemd[1]: Starting System Hibernate...
Sep 10 10:29:19 t14-mch systemd-sleep[263905]: Successfully froze unit 'user.slice'.
Sep 10 10:29:19 t14-mch systemd-sleep[263905]: Performing sleep operation 'hibernate'...
Sep 10 10:30:12 t14-mch systemd-sleep[263905]: System returned from sleep operation 'hibernate'.
Sep 10 10:30:12 t14-mch systemd-sleep[263905]: Successfully thawed unit 'user.slice'.
Sep 10 10:30:12 t14-mch systemd[1]: systemd-hibernate.service: Deactivated successfully.
Sep 10 10:30:12 t14-mch systemd[1]: Finished System Hibernate.
Sep 10 10:30:12 t14-mch systemd[1]: systemd-hibernate.service: Consumed 3.217s CPU time, 1.7M memory peak, 512K memory swap peak.
Kernel 6.16.5-zen1-1-zen with Nvidia - hibernate failed
[user@viktorpc ~]$ journalctl -b -u systemd-hibernate
-- No entries --
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$ journalctl -b -0 | grep resume
sep 10 13:35:01 viktorpc kernel: Command line: initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:01 viktorpc kernel: Kernel command line: initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:01 viktorpc systemd-hibernate-resume-generator[195]: Reported hibernation image: ID=endeavouros kernel=6.16.5-zen1-1-zen UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b offset=0
sep 10 13:35:01 viktorpc dracut-cmdline[257]: Using kernel command line parameters: rd.driver.pre=btrfs initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:02 viktorpc systemd-hibernate-resume[522]: Reported hibernation image: ID=endeavouros kernel=6.16.5-zen1-1-zen UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b offset=0
sep 10 13:35:02 viktorpc kernel: PM: hibernation: resume from hibernation
sep 10 13:35:08 viktorpc kernel: PM: hibernation: resume failed (-5)
sep 10 13:35:08 viktorpc systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
sep 10 13:35:08 viktorpc systemd[1]: systemd-hibernate-resume.service: Consumed 1.556s CPU time, 1.5M memory peak.
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$ journalctl -b | grep -iE 'error|warn|critical'
sep 10 13:35:01 viktorpc kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
sep 10 13:35:01 viktorpc kernel: ACPI BIOS Error (bug): Failure creating named object [\_TZ.ETMD], AE_ALREADY_EXISTS (20250404/dswload2-326)
sep 10 13:35:01 viktorpc kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
sep 10 13:35:01 viktorpc kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PC00.LPCB.H_EC.SEN2 (20250404/dspkginit-438)
sep 10 13:35:01 viktorpc kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PC00.LPCB.H_EC.CHRG (20250404/dspkginit-438)
sep 10 13:35:01 viktorpc kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PC00.LPCB.H_EC.SEN4 (20250404/dspkginit-438)
sep 10 13:35:01 viktorpc kernel: RAS: Correctable Errors collector initialized.
sep 10 13:35:08 viktorpc kernel: nvidia 0000:01:00.0: PM: failed to quiesce async: error -5
sep 10 13:35:08 viktorpc kernel: ACPI Warning: \_SB.IETM._TRT: Found unexpected NULL package element (20250404/nsrepair-187)
sep 10 13:35:08 viktorpc kernel: ACPI Warning: \_SB.IETM._TRT: Missing expected return value (20250404/nsrepair-203)
sep 10 13:35:08 viktorpc kernel: ACPI Warning: \_SB.IETM._TRT: Expected return object of type Reference (20250404/nspredef-249)
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! DC power limits table is not supported
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! Failed to get SysPwrLimitGetInfo!!
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! Client (presumably SBIOS) has requested to disable Dynamic Boost DC controller
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$
[user@viktorpc ~]$ journalctl -b -0 | grep -iE nvidia
sep 10 13:35:01 viktorpc kernel: Command line: initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:01 viktorpc kernel: Kernel command line: initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:01 viktorpc dracut-cmdline[257]: Using kernel command line parameters: rd.driver.pre=btrfs initrd=\6362dae4ea3d40c2969c2f9219b2bac2\6.16.5-zen1-1-zen\initrd nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1 systemd.machine_id=6362dae4ea3d40c2969c2f9219b2bac2
sep 10 13:35:01 viktorpc kernel: nvidia: loading out-of-tree module taints kernel.
sep 10 13:35:01 viktorpc kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
sep 10 13:35:01 viktorpc kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
sep 10 13:35:01 viktorpc kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
sep 10 13:35:01 viktorpc kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
sep 10 13:35:01 viktorpc kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 580.82.07 Release Build (root@viktorpc)
sep 10 13:35:02 viktorpc systemd-modules-load[230]: Inserted module 'nvidia_uvm'
sep 10 13:35:02 viktorpc kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64 580.82.07 Release Build (root@viktorpc)
sep 10 13:35:02 viktorpc kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
sep 10 13:35:08 viktorpc kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
sep 10 13:35:08 viktorpc kernel: nvidia 0000:01:00.0: [drm] fb1: nvidia-drmdrmfb frame buffer device
sep 10 13:35:08 viktorpc kernel: nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] returns -5
sep 10 13:35:08 viktorpc kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5
sep 10 13:35:08 viktorpc kernel: nvidia 0000:01:00.0: PM: failed to quiesce async: error -5
sep 10 13:35:09 viktorpc kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input20
sep 10 13:35:09 viktorpc kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input21
sep 10 13:35:09 viktorpc kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input22
sep 10 13:35:09 viktorpc kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input23
sep 10 13:35:10 viktorpc systemd[1]: Started nvidia-powerd service.
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: nvidia-powerd version:2.0 (build 1)
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: DBus Connection is established
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! DC power limits table is not supported
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! Failed to get SysPwrLimitGetInfo!!
sep 10 13:35:10 viktorpc nvidia-powerd[1014]: ERROR! Client (presumably SBIOS) has requested to disable Dynamic Boost DC controller
[user@viktorpc ~]$
Same with default/lts kernels and Nvidia
I have no idea (not even an NVIDIA card), but to me it looks like NVIDIA’s Dynamic Power Management doesn’t play well with the rest.
You could possibly try to change the NVreg_DynamicPowerManagement option in /etc/modprobe.d/nvidia.conf or the like, see for example
Don’t forget to to rebuild your initrd, for example using
sudo reinstall-kernels
No guarantees (quoted GitHub is 6 years old), but I think the parameter still exists.
current nvidia packaging is enabling the nvidia systemd services automatically, so it should all be set properly. But may something is change with kernel that is not implemented in nvidia properly.
Same machine with the Nvidia disabled is properly hibernating here.
As a side note: You did notice you have many duplicate entries in your kernel command line?!
Interesting. Similar problem here. I’ll have to try both options.
I’m afraid to break the boot, so I want to ask: is it necessary to edit /etc/kernel/cmdline like this (delete duplicates) and run the sudo reinstall-kernels?
nvme_load=YES nowatchdog rw root=UUID=08db16c9-7946-43e9-b507-7d577377adb0 resume=UUID=ed3b9417-349b-4bbe-bcda-f3f789b17a1b nvidia_drm.modeset=1
The problem @ViktorT repoted here Laptop resuming from hibernation but does not restore the previous session seems to be significantly different from the one I described.
In my case the system crashes during the resume 100% of the times. It crashes and caps lock starts blinking.
So there may be two different problems here.
Interesting fact however: disabling my dGPU from the machine firmware seems to fix the problem. So this is somehow related to the dGPU it seems.
I did some other tests, with no interesting result though.
I replaced dracut with mkinitcpio in my fresh installation on USB of EOS: the crash disappeared and I can freely hibernate and resume from hibernation with the latest kernel. For confirmation I then re-installed dracut and… I still could not reproduce the crash anymore. Therefore this test says nothing interesting.
I did the same in my regular installation: installing mkinitcpio did not fix the crash.
Unclear results, but I can probably state that dracut does not seem to be involved.
For what reason resume was fixed in my USB installation but not in my regular installation is currently unknown.
I do not have other ideas other than switching to another distro and see what happens or file a report against the kernel.