So here is my trouble - i put my laptop with Linux Mint 17 to hibernation and after i decided to resume session i see only a black screen so i am now to start in recovery mode. I don't need to restore that session - i just want to get my Linux back to work. What is the way to edit GRUB loading script to just start new session? Now it looks like this I also moved a RESUME file from /etc/initramfs-tools/conf.d/ - still no luck - got black screen. Any ideas?

I have writethrough bcache working on Debian Sid with an underlying LUKS + LVM. My swap partition (already present) is lying unused as an LVM volume. I know that I am supposed to stop bcache before hibernation (suspend to disk), and resume bcache after resume (cannot be active during either). How exactly do I ensure that? Are there are any pre- and post- scripts for this? If so, how should stop and restart bcache. All that echo n > /sys ... business can go remarkably awry if one does not know what one is doing. Getting hibernation working is the last pending thing after the install.

I have a problem with hibernating my computer. Everything was working before an update. The update installed Plasma 6.3.5. Hibernating from the start menu doesn't work either. After the update, the following command reports an error under normal user:

$ loginctl hibernate
Error registering authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0)

However, under root, the

$ loginctl hibernate

works as expected. A normal user is a member of these groups:

$ id
uid=1000(ibarina) gid=1000(ibarina) groups=1000(ibarina),6(disk),7(lp),10(wheel),18(audio),27(video),85(usb),100(users),106(lpadmin),250(portage),272(plugdev),377(pcap)

Moreover,

grep loginctl /var/log/everything/current

gives

Jul 17 17:22:49 [loginctl] Failed to hibernate system via elogind: Interactive authentication required.

Installed versions: sys-auth/polkit-126-r1 sys-auth/elogind-255.5-r2

On my Ubuntu 20.04 (problem persists since 16.04) Sony VAIO laptop if I close the lid, wait till the yellow led to blink and then turn the laptop on again, awakes everything but keyboard, which turns on it's backlight after first keypress but doesn't react to anything, so does the touchpad. So I get almost fully working system, but completely unusuable. My problem is that I don't even know where to search for problem origin. I don't know how the laptop power and keyboard management works in Ubuntu, not on systemd or SysV level, nor on kernel level. So, no logs for you, my friends, until you ask for any. =) How can I solve this very annoying issue please?

I am trying to add hibernation to ubuntu 18 on laptop. There are 3 disks, ssd m2, ssd and sd-card. Previously there were windows 10 on ssd m2 and ubuntu on ssd; now I have only one ubuntu on ssd m2. So I created 10gb swap file : fjod@fjod-HP-Laptop-15-db1xxx:~$ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 9,8G 0B -2 fjod@fjod-HP-Laptop-15-db1xxx:~$ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 15 фев 6 16:36 18f88db1-b367-45b1-9444-0f2ca150583b -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 фев 6 16:36 513E-F188 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 10 фев 6 16:36 a1c2f79e-34ac-410e-b110-ba52f526face -> ../../sda1 fjod@fjod-HP-Laptop-15-db1xxx:~$ cat /proc/swaps Filename Type Size Used Priority /swapfile file 10239996 0 -2 fjod@fjod-HP-Laptop-15-db1xxx:~$ grep swap /etc/fstab /swapfile none swap sw 0 0 /swapfile none swap sw 0 0 fjod@fjod-HP-Laptop-15-db1xxx:~$ cd / && ls -l swapfile -rw------- 1 root root 10485760000 фев 6 16:33 swapfile fjod@fjod-HP-Laptop-15-db1xxx:/$ cat /etc/fstab | grep -i swap /swapfile none swap sw 0 0 /swapfile none swap sw 0 0 Now I need to add it's UUID to make hibernation work, so: fjod@fjod-HP-Laptop-15-db1xxx:/$ sudo blkid /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/loop2: TYPE="squashfs" /dev/loop3: TYPE="squashfs" /dev/loop4: TYPE="squashfs" /dev/loop5: TYPE="squashfs" /dev/loop6: TYPE="squashfs" /dev/loop7: TYPE="squashfs" /dev/nvme0n1: PTUUID="e5f2647b-98c1-45cd-93c1-4bdeb2bd11d1" PTTYPE="gpt" /dev/nvme0n1p1: UUID="513E-F188" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="20210fff-3590-4c0f-826c-e64cb03894a8" /dev/nvme0n1p2: UUID="18f88db1-b367-45b1-9444-0f2ca150583b" TYPE="ext4" PARTUUID="ce5ffbc2-5f80-4d12-9167-34d2b9676755" /dev/sda1: UUID="a1c2f79e-34ac-410e-b110-ba52f526face" TYPE="ext4" PARTLABEL="kingston" PARTUUID="6e777b1f-a124-4821-8bae-c1b956e7e3fe" /dev/loop8: TYPE="squashfs" /dev/loop9: TYPE="squashfs" /dev/loop10: TYPE="squashfs" /dev/loop11: TYPE="squashfs" /dev/loop12: TYPE="squashfs" /dev/loop13: TYPE="squashfs" /dev/loop14: TYPE="squashfs" /dev/loop15: TYPE="squashfs" /dev/loop16: TYPE="squashfs" /dev/loop17: TYPE="squashfs" /dev/loop18: TYPE="squashfs" /dev/loop19: TYPE="squashfs" /dev/loop20: TYPE="squashfs" /dev/loop21: TYPE="squashfs" /dev/loop22: TYPE="squashfs" /dev/sdb1: TYPE="exfat" fjod@fjod-HP-Laptop-15-db1xxx:/$ grep swap /etc/fstab /swapfile none swap sw 0 0 /swapfile none swap sw 0 0 But I don't see it's UUID anywhere. What should I do? Looks like I have swapfile somewhere on disk, but how to point hibernation to it? ------------edit1------------------- using this tutorial fjod@fjod-HP-Laptop-15-db1xxx:~$ mount | grep " / " /dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro) fjod@fjod-HP-Laptop-15-db1xxx:~$ sudo blkid -g [sudo] password for fjod: fjod@fjod-HP-Laptop-15-db1xxx:~$ sudo blkid -g fjod@fjod-HP-Laptop-15-db1xxx:~$ sudo blkid /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/loop2: TYPE="squashfs" /dev/loop3: TYPE="squashfs" /dev/loop4: TYPE="squashfs" /dev/loop5: TYPE="squashfs" /dev/loop6: TYPE="squashfs" /dev/loop7: TYPE="squashfs" /dev/nvme0n1: PTUUID="e5f2647b-98c1-45cd-93c1-4bdeb2bd11d1" PTTYPE="gpt" /dev/nvme0n1p1: UUID="513E-F188" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="20210fff-3590-4c0f-826c-e64cb03894a8" /dev/nvme0n1p2: UUID="18f88db1-b367-45b1-9444-0f2ca150583b" TYPE="ext4" PARTUUID="ce5ffbc2-5f80-4d12-9167-34d2b9676755" /dev/sda1: UUID="a1c2f79e-34ac-410e-b110-ba52f526face" TYPE="ext4" PARTLABEL="kingston" PARTUUID="6e777b1f-a124-4821-8bae-c1b956e7e3fe" so the id = 18f88db1-b367-45b1-9444-0f2ca150583b offset: od@fjod-HP-Laptop-15-db1xxx:~$ sudo filefrag -v /swapfile Filesystem type is: ef53 File size of /swapfile is 10485760000 (2560000 blocks of 4096 bytes) ext: logical_offset: physical_offset: length: expected: flags: 0: 0.. 8191: 50290688.. 50298879: 8192: 1: 8192.. 10239: 50302976.. 50305023: 2048: 50298880: 2: 10240.. 14335: 50307072.. 50311167: 4096: 50305024: 3: 14336.. 38911: 50472960.. 50497535: 24576: 50311168: 4: 38912.. 45055: 50505728.. 50511871: 6144: 50497536: in the end : fjod@fjod-HP-Laptop-15-db1xxx:~$ cat /etc/initramfs-tools/conf.d/resume resume=UUID=18f88db1-b367-45b1-9444-0f2ca150583b resume_offset=50290688 /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=18f88db1-b367-45b1-9444-0f2ca150583b resume_offset=50290688" I try to hibernate, but computer fails to boot at all. ------------edit2-------------- I found another great tutorial here , now it hibernates fine, but after hibernation power is still on and I have to shutdown laptop using power button. After turning it on, I see my programs launched. -------------edit3----------------------- Resume from hibernate works 50/50 and is painfully slow. In the end, I wont use it (sigh).

I am running Centos 7 and all I want to do is make my computer go to sleep immediately. There is a setting I have set to make my computer go to sleep but only after a certain amount of inactivity but when I leave work, I want to be able to make it go to sleep immediately right after instead of turning my computer off. I looked and found this link https://www.cyberciti.biz/faq/linux-command-to-suspend-hibernate-laptop-netbook-pc/ and I tried both commands sudo systemctl suspend and sudo systemctl hibernate and get the message A dependency job for suspend.target failed. See 'journalctl -xe' for details. I just want to be able to make my computer go to sleep so that I can pick up from where I left off the day before instead of turning off my computer everytime I leave from work.

I have installed Debian 8 with sysvinit and Xfce on a ThinkPad X220. The video card is Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)/Integrated Graphics Chipset: Intel(R) HD Graphics 3000. Kernel versions available to me are 4.7 from backports and 3.16 (heavily patched by Canonical kernel team) from stable. When I hibernate using pure kernel (echo disk > /sys/power/state done by pm-hibernate run by xfce4-pm-helper) and XScreenSaver turns the screen off, on resume the screen is still turned off (not just the backlight: I checked with a flashlight), and nothing seems to turn it on again (I tried Ctrl+Alt+F* suggested at ThinkWiki and Alt+SysRq+V), but the remaining system seems to be working (at least, when I do an Alt+SysRq+E,I,S,U,B, I can find messages from a successful resume and syslogd being terminated by signal 15 in /var/log/syslog). I'm able to connect via ssh, but both chvt 1; chvt 7 and various combinations of export DISPLAY=:0; xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto do nothing. I disabled LVDS1 and tried to reenable it, I got: xrandr: Configure crtc 0 failed and the following lines in dmesg: [ 390.432051] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff9ae6caa2f000 when fb was deleted [ 390.432066] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb Some people suggested ddccontrol, but it doesn't detect DDC on my system. Is screen is on while hibernating, it stays working after resume. If I install uswsusp , hibernate works (as a bonus, I get some form of compression and ability to cancel hibernating at the last second), but only most of the time. The usual resume procedure looks like this: 1. resume: Loading image data pages (in default video mode) 1. Video mode is switched to native resolution, screen is filled with noise (full screen when EFI-booting, a small horizontal stripe on the top when BIOS-booting) 1. Loud click from speakers, screen momentarily turns black with s2disk: returned to userspace, then I get my XScreenSaver lock dialog. Sooner or later, right after the Loading data pages screen turns black and the laptop resets (I see the BIOS boot logo). I installed grub-efi on a thumbdrive (to avoid repartitioning) for the sake of efi-backed pstore. For a week, I hibernated and resumed the laptop once or twice per day without problems and almost beleived that EFI has solved the problem, but then the failure occured again, and no logs were found in /sys/fs/pstore (pstore: Registered efi as persistent store backend is visible in dmesg). I think that when resuming successfully for the last time before the next one failed the screen was not fully filled with noise and a black stripe was wisible on the bottom before I got returned to userspace and X screen back. As far as I know, suspend to RAM works flawlessly both with echo mem > /sys/power/state and s2ram. I do that more frequently than hibernating (several times per day) and so far, no glitches have occured. For now, I set up XScreenSaver to never turn the screen off, thus preventing the most common cause of the failure (XScreenSaver locking and turning screen off before hibernation), but I'm still able to encounter the glitch by closing the lid fast enough after choosing "hibernate". **UPD**: I've been using pure kernel hibernate for some time now, and I've just encountered the same reset after loading saved image which has been happening to me when using uswsusp. Apparently I've never used it on this X220 for long enough for it to happen before. So, as it turns out, I have no reliable ways to hibernate: both echo disk > /sys/power/state and s2disk fail after 5-7 hibernations, but pure kernel doesn't restore video card state properly, too. What else can I try to make some form of hibernate working?

I managed to resize my LVM partitions, set up my swapfile, and disable secure boot, so now I can hibernate with sudo systemctl hibernate. However, I want to be able to hibernate from my power menu (wlogout) without needing to use sudo. The systemctl commands suspend, reboot, and poweroff all work without needing sudo. Why does hibernate require sudo, and is there a way to drop it, so I don't need to interact via the command line for this one power option? Using: - Ubuntu 24.04 LTS - Sway WM (not GNOME)

I have a acer aspire 5750G laptop. I am running ubuntu 11.04. The uname -a reads the following: > Linux admin-Aspire-5750G 2.6.38-13-generic-pae #56-Ubuntu SMP Tue Feb 14 14:32:30 UTC 2012 i686 i686 i386 GNU/Linux Whenever the wakes up from suspend or hibernate, it shows a blank screen. Same thing happens when the lid is closed and opened later. What should I do to fix this? **Edit#1:** I have the pm-utils installed. I could suspend using pm-suspend. When I press any key to wake up, the machine wakes up but hangs. It does not respond to any keyboard or mouse keys after wake up. What could be wrong here?

I want to hibernate on low battery:

SUBSYSTEM=="power_supply", \
    ATTR{status}=="Discharging", \
    ATTR{capacity}=="[0-5]", \
    RUN+="/usr/bin/systemctl hibernate", \

This works well if the system is awake. If suspended however, it doesn't hibernate until I wake it, then instead of allowing me to unlock it immediately hibernates. How can I make this event either work while suspended, or trigger a wakeup (and then hibernate) itself, without me opening the lid? --- I have tried adding:

ATTR{power/wakeup}="enabled"

without success. Indeed there is no wakeup currently in /sys/class/power_supply/BAT1/power/ - actually though /sys/class/power_supply/BAT1/device/power/wakeup exists and is already enabled. I gather I can't make the udev rule run while suspended, I need to trigger it to wake on low battery separately (then the udev rule can run and hibernate). This seems already implemented in [drivers/acpi/battery.c](https://github.com/torvalds/linux/blob/22da5264abf497a10a4ed629f07f4ba28a7ed5eb/drivers/acpi/battery.c#L994-L1001) :

/*
	 * Wakeup the system if battery is critical low
	 * or lower than the alarm level
	 */
	if ((battery->state & ACPI_BATTERY_STATE_CRITICAL) ||
	    (test_bit(ACPI_BATTERY_ALARM_PRESENT, &battery->flags) &&
	     (battery->capacity_now alarm)))
		acpi_pm_wakeup_event(&battery->device->dev);

But that has not worked for me, I don't know if 'critical low' is another textual capacity level, I've only seen as low as 'Low', but it was at the time lower than the /sys/class/power_supply/BAT1/alarm. --- NB: I am aware of hybrid-sleep, but that is not what I want, firstly since I would like to conserve _some_ battery; but also so that I can use suspend-then-hibernate such that it hibernates on either low battery _or_ time delay.

I have been struggling for over a month with a new Lenovo Thinkpad P16 Gen2 laptop running Ubuntu 22.04 LTS, that **would not successfully suspend**. Maybe 90% of the time it worked okay, the other 10% reboot was necessary. This was unacceptable to me. Eventually, I decided it would be worthwhile to hibernate the machine instead of suspending it. I had to disable Secure Boot to do so. As this is a home computer I thought the risk was small. *I have started four or five posts here looking for a solution with nothing found. Sorry if the admins of this page have a problem with this, but each post interrogated a different aspect of the problem.* However, the sudo systemctl hibernate command did not work. The computer would save its state and immediately wake up. Not what I wanted. It was suggested that I disable wakeup on the devices listed as enabled in the output of acpitool -w |grep enabled. But one of these devices would not disable wakeup with the acpitool -W command. So still no acceptable hibernation. Then, by chance, I looked at the man page of acpitool where I came upon > **-S, --suspend to disk** ? > Put the machine into sleep state S4, if possible. Requires write access to /proc/acpi/sleep (kernel 2.4.x) or /sys/power/state (kernel > 2.6.x) **This proved to be a solution to my problem.** Unlike sudo systemctl hibernate, sudo acpitool -S achieves hibernation and successfully returns from it when the power is turned on. The only problem here is I'm not sure how to enable it in the Ubuntu Gnome GUI. But I can't find anything about this on the internet other than the man page. I still have these questions: **I am not sure what the difference between the two commands is internally and would like to know.** **I'd also like to know if there are any bad side effects I might encounter in using this command.** **UPDATE:** In response to the request of @waltinator I have the following data: 1. journal after sudo acpitool -S: $ sudo journalctl --since="-5 minutes" | pastebinit https://paste.ubuntu.com/p/CJq9YFKmbB/ 2. journal after sudo systemctl hibernate: $ sudo journalctl --since="-5 minutes" | pastebinit https://paste.ubuntu.com/p/432vmz2xqJ/ 3. here is a pastebin from a week ago when I still was trying to use suspend: $ journalctl --boot=-1 | tail -n 2000 | pastebinit https://paste.ubuntu.com/p/QdDYcKGNGw/ **UPDATE 2:** Having now looked at the first and second pastebins, I can see that acpitool takes a much simpler and more direct (close to the metal) approach than does systemctl hibernate. It gets right down to business and by Line 21 is attempting to put the system into sleep state S4, which succeeds. systemctl hibernate on the other hand, does a lot of messing about with the network interface, eventually deciding to wake back up at line 101. I am not sure why it would do this since the point of hibernate is described as turning the machine off once the state is saved. It seems to me that systemctl is sharing code between suspend and hibernate. I am not sure what the intention of the developers was but this seems like a bug to me. The use case of a single user wanting to just save state and then turn the machine off is not properly supported.

I am running Ubuntu 22.04 LTS on my Lenovo Thinkpad P16 gen2 machine. I want to enable hibernation because the resume process is too unreliable on this machine which also has an nVidia RTX 3500 ada gpu. Maybe, if I am lucky, suspend successfully awakens 90% of the time. Since the machine is nvram-based I figure wakeup would not take overly long, and anyway, I am willing to pay the price of reliability over speed here. I created a swap partition and told swapon to use this partition. I disabled Secure Boot. Can anyone describe what this PXSX process is and why it's wakeup capablities cannot be turned off? Then following the steps listed in this tutorial , I was finally able to allow the command sudo systemctl hibernate to proceed. **It succeeded in shutting the computer down, only to have it reawaken immediately thereafter.** Researching this, I find the seemingly authoritative and excellent documentation System Sleep States . In it, I learn that the file controlling the hibernate process is /sys/power/disk. It is described as follows: > This file controls the operating mode of hibernation > (Suspend-to-Disk). Specifically, it tells the kernel what to do after > creating a hibernation image. > > Reading from it returns a list of supported options ... > > The currently selected option is shown in square brackets, which means > that the operation represented by it will be carried out after > creating and saving the image when hibernation is triggered by writing > disk to /sys/power/state. On my system, this is what I have: /sys/power$ cat disk [platform] shutdown reboot suspend test_resume I would like to change that to platform [shutdown] reboot suspend test_resume at least as an experiment. But the system won't let me edit that file, even as root. I don't understand this. $ ls -al /sys/power total 0 drwxr-xr-x 3 root root 0 Mar 7 11:45 . dr-xr-xr-x 13 root root 0 Mar 7 11:45 .. -rw-r--r-- 1 root root 4096 Mar 7 13:32 disk ... The file 'disk' is writable, the /sys/power directory is writable, although its parent (/sys) isn't. So, in sum, two mysteries: **1. Why is the system restarting immediately after shutting down?** **2. What is preventing me from editing this file (either through sudo or upon logging in as root)?** **UPDATE:** Following the suggestions of @telcoM below, I set out to disable the wakeup capabilities of those processes acpitool listed as being wakeup-capable. These were those processes: $ acpitool -w | grep enabled 3. PEG1 S4 *enabled pci:0000:00:01.0 7. XHCI S3 *enabled pci:0000:00:14.0 19. RP05 S4 *enabled pci:0000:00:1c.4 27. RP09 S4 *enabled pci:0000:00:1d.0 28. PXSX S4 *enabled pci:0000:20:00.0 35. RP13 S4 *enabled pci:0000:00:1d.4 67. AWAC S4 *enabled platform:ACPI000E:00 68. SLPB S3 *enabled platform:PNP0C0E:00 69. LID S4 *enabled platform:PNP0C0D:00 My plan was initially to disable all but #69, the laptop lid process. It failed. I could disable all but #28, the PXSX process, would not be disable. I went so far as to disable #69, the lid, which was not my original plan. No set of processes I could disable produced a system where sudo systemctl hibernate produced a shut down system that would stay shut down. In all cases it shut down and popped back up a few seconds later. So still looking for a way to make this beast hibernate. Can anyone explain what this PXSX process is and why it might be resisting all attempts to make it unwilling to have its wakeup capability shut off.

How likely is it that disabling Secure Boot on a home computer running Linux would suffer from the advertised threat of > unauthorized code—such as bootkits and rootkits—from being executed > during the boot process? How would such animals get onto a home computer of which I am the only user? It seems unlikely to me that that would be a problem in my instance. **But maybe I am missing something?** I am interested in doing this because I would like to enable hibernation on this computer, which, because it has an nVidia GPU, cannot be reliably suspended. The computer has a swap partition and nvram rather than a hard disk, and I think the delays would be tolerable and less annoying than the frequent need to reboot.

I am using MX Linux, without systemd. Sometimes after a while, and every time after sleep or hibernation, domain name resolution stops working, that is ping 8.8.8.8 works, but ping google.com does not. I have to reboot **twice** before it can work again, relogin does not help. I also know it is (probably) not hardware related, because I had the same issue on a new notebook and a fresh MX Linux install. I know this is not a support forum, so my question is: what could cause MX Linux to lose the ability to resolve domain names after sleep?

I'am trying to make my laptop to hibernate , but it can't , showing me an error (call to hibernate failed : not enough swap space for hibernate ) so my old swap partition was 1giga so i extended it to 17giga (because i have a 16 giga memory) and I should add a new swap file with this size so I add it using this command sudo swapoff -a sudo nano /etc/fstab sudo swapon /swapfile sudo nano /etc/fstab sudo blkid /swapfile but it didn't work and i search if still the old partition and i found it so what is the solution ??

I run Debian with KDE Plasma on Xorg. I have tried all the main ways on the internet to properly wake the computer after it going to sleep. But whatever I do, it doesn't work. * I have gone to the Power Management too, but I didn't find anything that I could change there. * This problem is there even if the laptop lid is closed or not. If the laptop lid is closed, and I open it, it gets frozen (like a very dim screen with a mouse pointer is there, so dim as if it was about to turn on the monitor but froze). And if the laptop lid is not closed and the computer goes to sleep, any key I press doesn't work. * I have backlit keyboard on my laptop... The light comes up but nothing on the screen. Even the mouse (trackpad) won't work. * I have to manually every time press the power button and shut off the laptop and start it again. I am kind of new to linux, so if any information is required from my side and it is a command, I would appreciate the command given as well. Or if it isn't a command, I would like to have the steps of getting that information

I am encountering strange behavior on my laptop since two weeks or so. When disconnected from the charging cable the machine will not wake up after closing and reopening the lid (most of the time). If that happens, not even pressing and holding the power button does anything until the power cable is plugged back in. It will also spontaneously shut down (the battery still shows plenty of charge) and cannot be powered back up until plugged in, exactly as stated above. Lastly when plugged in the battery will not be charged but rather be "stuck" at its reported charge level. Note that this issue is relatively recent. A couple of weeks ago all functions worked as to be expected. Here's my system information:

System:
  Host: archyoga Kernel: 6.12.8-arch1-1 arch: x86_64 bits: 64
  Desktop: Hyprland v: 0.46.2 Distro: Arch Linux
Machine:
  Type: Convertible System: LENOVO product: 20QGS6GG00 v: ThinkPad X1 Yoga 4th
    serial: 
  Mobo: LENOVO model: 20QGS6GG00 v: SDK0J40697 WIN
    serial:  UEFI: LENOVO v: N2HET77W (1.60 )
    date: 02/06/2024

Edit: I managed to take a couple of photos with error codes that occur, when the system shuts down: Edit: Here is the output of the upower command:

upower -i $(upower --enumerate | grep battery)
  native-path:          BAT0
  vendor:               SMP
  model:                5B10W13931
  serial:               4214
  power supply:         yes
  updated:              Mon 13 Jan 2025 01:12:49 AM CET (16 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               pending-charge
    warning-level:       none
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    charge-cycles:       154
    percentage:          91%
    capacity:            100%
    technology:          lithium-polymer
    charge-start-threshold:        75%
    charge-end-threshold:          80%
    charge-threshold-supported:    yes
    icon-name:          'battery-full-charging-symbolic'

My Linux laptop (openSUSE Tumbleweed) should hibernate but won't and I do not understand why. I have had similar systems (Arch Linux) hibernate under the same circumstances (LVM on LUKS). Here is my config: - EFI-GRUB boot - LVM on LUKS; LVM has root, home and swap partitions - Swap enabled and mounted by UUID in /etc/fstab, swapon -s shows it being active. It is 32GB in size with 16GB RAM installed. - GRUB has resume statements in the default config and /boot/grub2/grub.cfg (see below). Here are a few commands to check hibernation capabilities of kernel and system: # zgrep HIBERN /proc/config.gz CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_HIBERNATE_CALLBACKS=y CONFIG_HIBERNATION=y CONFIG_HIBERNATION_SNAPSHOT_DEV=y CONFIG_HIBERNATION_COMP_LZO=y # CONFIG_HIBERNATION_COMP_LZ4 is not set CONFIG_HIBERNATION_DEF_COMP="lzo" So the kernel *is* configured to support hibernation. This boot (by GRUB) has: # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.11.6-2-default root=/dev/mapper/cryptolvm-opensuse splash=silent resume=/dev/mapper/cryptolvm-swap mem_sleep_default=deep security=selinux selinux=1 enforcing=1 mitigations=auto I tried varying resume= using UUID=.... with the swap's UUID with no effect. # cat /sys/power/state freeze mem Here disk is missing but I do not know why. Of course this will not work now: # systemctl hibernate Call to Hibernate failed: Sleep verb 'hibernate' is not configured or configuration is not supported by kernel Exit 1 Does the kernel depend on the BIOS to enable hibernation? (Not to my knowledge.) In this case, can I check something there?

When I attempt to hibernate, my laptop hangs. It shows the screen wallpaper, then a black screen (as if it's going to hibernate), then the screen wallpaper again. Then it seems to freeze; I cannot get any more response out of it at that point. What am I missing? Thanks. I am running Fedora 40 Linux with kernel 6.11.10-200.fc40.x86_64. Here is what I attempted so far: - Created a swapfile larger than zram0 swap + 64 Gig system ram.

btrfs filesystem mkswapfile --size 80G /swapfile

- Edited /etc/fstab and put in: /swapfile none swap sw 0 0 - Rebooted, run:

swapon -s
    Filename                                Type            Size            Used            Priority
    /swapfile                               file            83886076        0               -2
    /dev/zram0                              partition       8388604         0               100

- See the luks UUID, and the btrfs filesystem UUID:

blkid | grep luks
    /dev/mapper/luks-319127be-114d-4dd2-884b-0a04642c538a: LABEL="fedora" UUID="7a4b5350-4d8a-44ee-83b7-f612701eca51" UUID_SUB="f98c2850-16e0-4144-a4df-da5f1302e0a9" BLOCK_SIZE="4096" TYPE="btrfs"

- See the btrfs offset:

btrfs inspect-internal map-swapfile -r /swapfile
    134685952

- vim /etc/default/grub and modified GRUB_CMDLINE_LINUX (shown here line wrapped):

GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-319127be-114d-4dd2-884b-0a04642c538a rhgb quiet
    mem_sleep_default=deep resume=UUID=7a4b5350-4d8a-44ee-83b7-f612701eca51 
    resume_offset=134685952"

- Edit resume.conf: vim /etc/dracut.conf.d/resume.conf - Insert the following. Note the spaces in the first two entries:

add_device+=" /dev/mapper/luks-319127be-114d-4dd2-884b-0a04642c538a "
    add_dracutmodules+=" resume "
    resume="UUID=7a4b5350-4d8a-44ee-83b7-f612701eca51"
    resume_offset="134685952"

- Remake grub config. Remake initramfs image:

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
    dracut -f

- vim /etc/systemd/sleep.conf and put in it:

[Sleep]
       AllowHibernation=yes
       HibernateMode=platform shutdown
       HibernateState=disk

- Now run: systemctl daemon-reload - Reboot - On command line: systemctl hibernate - Machine freezes. Edit: Note that I've disabled Secure Boot, and I've disabled selinux. It looks like it takes 30 or so seconds to shut down. The system does not hibernate, it goes to power off now. After this poweroff, when I power the machine back on my existing desktop is gone so it's not recovering from hibernate.

I have a problem with hibernating my computer. Everything was working before an update. The update installed Plasma 6 and =x11-drivers/nvidia-drivers-550.127.05-r1. The kernel has not been updated. After the update, the following command does nothing: $ loginctl hibernate When I trace it using ltrace, I get the following output: $ ltrace loginctl hibernate setlocale(LC_ALL, "") = "C" elogind_set_program_name(0x7fffb8445a2d, 0x7f266b11bde0, 1, 0) = 0x7f266b135e08 log_setup(0x7fffb8445a2d, 0x7f266b11bde0, 1, 0) = 0 rlimit_nofile_bump(0x80000, 0x7fffb84452c0, 11, 0x7f266b0a9874) = 0 sigbus_install(0, 7, 0, 0x8000000000000000) = 0 getopt_long(2, 0x7fffb8445538, "hp:P:als:H:M:n:o:ci", 0x55aa2480b200, nil) = -1 bus_connect_transport(0, 0, 0, 0x7fffb84453e0) = 0 sd_bus_set_allow_interactive_authorization(0x55aa2482a2a0, 1, 128, 0x7f266b0a928b) = 0 dispatch_verb(2, 0x7fffb8445538, 0x55aa2480b560, 0x55aa2482a2a0 strcmp("halt", "hibernate") = -8 strcmp("poweroff", "hibernate") = 8 strcmp("reboot", "hibernate") = 10 strcmp("kexec", "hibernate") = 3 strcmp("suspend", "hibernate") = 11 strcmp("hibernate", "hibernate") = 0 geteuid() = 1000 on_tty(0x55aa248068c5, 0x7fffb8445a36, 0x55aa2482a2a0, 0x7f266b07986b) = 1 sd_bus_call_method(0x55aa2482a2a0, 0x55aa24806046, 0x55aa2480602e, 0x55aa24807968) = 0xffffff92 polkit_agent_open_if_enabled(0, 1, 0x55aa24808270, 785) = 0 log_get_max_level(5, 0, 0, 0x7f266b096094) = 6 sd_bus_call_method(0x55aa2482a2a0, 0x55aa24806046, 0x55aa2480602e, 0x55aa24807968) = 0xffffff92 log_get_max_level(0x55aa2482a010, 0x55aa2482cd40, 0, 785) = 6 memset(0x7fffb8444f90, '\0', 1024) = 0x7fffb8444f90 _bus_error_message(0x7fffb8444f70, 0xffffff92, 0x7fffb8444f90, 0x7fffb8444f90) = 0x7f266b13520d log_internal(3, 0xffffff92, 0x55aa24807b89, 366) = 0xffffff92 sd_bus_error_free(0x7fffb8444f70, 0x7fffb84443c0, 0, 0x7fffb8444f68) = 0 ) = 0xffffff92 polkit_agent_close(0x7fffb8444f70, 0x7fffb84443c0, 0, 0x7fffb8444f68 --- SIGCHLD (Child exited) --- ) = 0 strv_free(0, 0xfd6b, 0, 0x7f266b091343) = 0 sd_bus_flush_close_unref(0x55aa2482a2a0, 0xfd6b, 0, 0x7f266b091343) = 0 sd_notifyf(0, 0x55aa24806720, 110, 0x7f266b172b20) = 0 polkit_agent_close(0x55aa2482a010, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 pager_close(0, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 mac_selinux_finish(0, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 +++ exited (status 1) +++ Any idea where the problem might be? Everything was working before that update. Hibernating from the start menu doesn't work either. Syslog prints this: # grep loginctl /var/log/everything/current Nov 17 09:47:44 [loginctl] Failed to hibernate system via elogind: Connection timed out What currently goes wrong? The computer does not hibernate. **EDIT**: The command echo disk > /sys/power/state also does not hibernate, although cat /sys/power/state prints freeze mem disk.