Getting Hibernate To Work On A New CentOS 7.2.1115 Install
Hi, I am a new CentOS user (quite familiar with Fedora 1-23+) and I decided to try a new install of CentOS on a ASUS R503U.
However, I can not get hibernate to work. I try:
systemctl hibenaate and I get:
Failed to execute operation: sleep verb not supported Btw, the problem does not go away with super-user.
I was wondering how to get around this issue. I would like the abililty to hibernate and come back in the last state. Thanks!
5 thoughts on - Getting Hibernate To Work On A New CentOS 7.2.1115 Install
This error message is generated when the sleep operation is not possible. Do you have sufficient SWAP configured on your system?
From: Ned Slider
To: CentOS@CentOS.org Sent: Sunday, June 12, 2016 11:46 AM
Subject: Re: [CentOS] Getting hibernate to work on a new CentOS 7.2.1115 install
This error message is generated when the sleep operation is not possible. Do you have sufficient SWAP configured on your system?
___________________
Thanks! The machine in question has 2 GiB of memory. I asked for an automatic partitioning of the disk during installation and the installer chose 3.some GiB. I usually use twice the RAM but I let it go this time since it was what was recommended by the automatic anaconda.
What swap should I go for there?
Thanks again!
cat /sys/power/state cat /sys/power/disk
The first should include ‘disk’ and the second should say enabled or some such. Note that hibernation is probably not supported by the CentOS kernel if this is on a UEFI computer with Secure Boot enabled
(it’s not supported by Fedora kernels) as it’s a possible vector to defeat the point of Secure Boot.
systemd does check to see if there’s enough unused swap to fit Active(anon) mem into for hibernation, and if not then hibernation won’t be possible.
And yet another thing is that it’s possible the initramfs isn’t using resume= which is currently a problem on Fedora. So you might need to add this to the grub.cfg on the kernel command line, something like resume=/dev/VG/swap or wherever it is. If it’s a /dev/sdXY, i.e. on a regular partition, then use UUID.
Hi, Thank you for this.
I get:
freeze mem
[disabled]
some such. So, clearly this is not set correctly. How do I make these changes, if I am allowed to?
(it’s not supported by Fedora kernels) as it’s a possible vector to defeat the point of Secure Boot.
I do have SecureBoot disabled (the computer would not boot after installation otherwise) and that is when I found the hidden “flag” to disable SecureBoot. resume= which is currently a problem on Fedora. So you might need to add this to the grub.cfg on the kernel command line, something like resume=/dev/VG/swap or wherever it is. If it’s a /dev/sdXY, i.e. on a regular partition, then use UUID. I know how to get it working on Fedora (modify /etc/default/grub and grub-instlall) or so I believe. Should I have to do the same thing on CentOS?
Thanks again!
–
Hi,
I wanted to see if anyone had any suggestions on what I could do to get hibernate working. Just as a reminder, I get:
freeze mem
[disabled]
some such. So, clearly this is not set correctly. How do I make these changes, if I am allowed to?
(it’s not supported by Fedora kernels) as it’s a possible vector to defeat the point of Secure Boot.
I do have SecureBoot disabled (the computer would not boot after installation otherwise) and that is when I found the hidden “flag” to disable SecureBoot. resume= which is currently a problem on Fedora. So you might need to add this to the grub.cfg on the kernel command line, something like resume=/dev/VG/swap or wherever it is. If it’s a /dev/sdXY, i.e. on a regular partition, then use UUID. I know how to get it working on Fedora (modify /etc/default/grub and grub-instlall) or so I believe. Should I have to do the same thing on CentOS?
Thanks again!
–