[gentoo-user] hibernation

[gentoo-user] hibernation

[Michael Vetter]

Hello there,

I use i3 as my window manager and use xfce4-power-manager for saving
battery and stuff on my laptop. Today I tried "hibernation" for the
first time and realized: it does not work.

All I did so far was installing fce4-power-manager selecting some
sections in kernel config that seemed necessary and installed polkit.

However when I close my notebook's lid (I configured xfce4-power-manager
to switch into hibernation in this case) it shuts down, but when i press
the start button, it just does a normal restart.
What am I missing?

Michael

Re: [gentoo-user] hibernation

[Randolph Maaßen]

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Dec 3, 2014 11:33 AM, "Michael Vetter" <michael.vetter@uni-konstanz.de>
wrote:
>
> Hello there,
>
> I use i3 as my window manager and use xfce4-power-manager for saving
> battery and stuff on my laptop. Today I tried "hibernation" for the
> first time and realized: it does not work.
>
> All I did so far was installing fce4-power-manager selecting some
> sections in kernel config that seemed necessary and installed polkit.
>
> However when I close my notebook's lid (I configured xfce4-power-manager
> to switch into hibernation in this case) it shuts down, but when i press
> the start button, it just does a normal restart.
> What am I missing?
>
> Michael
>

Maybe you need to pass the resume-partition parameter to the kernel in the
bootloader. Point it to your swap device.

You can boot normal with this parameter set and not hibernated

[-- Attachment #2: Type: text/html, Size: 1109 bytes --]

Re: [gentoo-user] hibernation

[J. Roeleveld]

On Wednesday, December 03, 2014 11:32:10 AM Michael Vetter wrote:
> Hello there,
> 
> I use i3 as my window manager and use xfce4-power-manager for saving
> battery and stuff on my laptop. Today I tried "hibernation" for the
> first time and realized: it does not work.
> 
> All I did so far was installing fce4-power-manager selecting some
> sections in kernel config that seemed necessary and installed polkit.
> 
> However when I close my notebook's lid (I configured xfce4-power-manager
> to switch into hibernation in this case) it shuts down, but when i press
> the start button, it just does a normal restart.
> What am I missing?
> 
> Michael

To test hibernate try the following:

1) Stop all important stuff
2) run the following as root:
#  echo disk > /sys/power/state

If this works, then you can try to configure a power management tool. 
Please also ensure you only have 1 power management tool configured.

--
Joost

Re: [gentoo-user] hibernation

[Marc Stürmer]

Am 03.12.2014 um 11:32 schrieb Michael Vetter:

> However when I close my notebook's lid (I configured xfce4-power-manager
> to switch into hibernation in this case) it shuts down, but when i press
> the start button, it just does a normal restart.

Do you want to configure

a) simply hibernation, which means that the RAM is still powered by your 
battery and just the rest of the computer is being switched off (CPU, 
HDDs and so on)

or

b) suspend to disk, which means that the whole content of the RAM is 
being written on your HDD and after that your computer is being shut 
down entirely?

Re: [gentoo-user] hibernation

[Michael Vetter]

> Maybe you need to pass the resume-partition parameter to the kernel in
the bootloader. Point it to your swap device.

Maybe I should add: I have EFI notebook, and my kernel is copied to
/boot/EFI/Boot/bootx64.efi. So I boot over that EFI thing because it
seemed the easiest thing to set up..

> b) suspend to disk, which means that the whole content of the RAM is
> being written on your HDD and after that your computer is being shut
> down entirely?

Yes, thats what I want to achive.

Re: [gentoo-user] hibernation

[J. Roeleveld]

On 4 December 2014 17:30:28 CET, Michael Vetter <michael.vetter@uni-konstanz.de> wrote:
>> Maybe you need to pass the resume-partition parameter to the kernel
>in
>the bootloader. Point it to your swap device.
>
>Maybe I should add: I have EFI notebook, and my kernel is copied to
>/boot/EFI/Boot/bootx64.efi. So I boot over that EFI thing because it
>seemed the easiest thing to set up..

You can set the resume partition in the kernel. Might be an option.

>> b) suspend to disk, which means that the whole content of the RAM is
>> being written on your HDD and after that your computer is being shut
>> down entirely?
>
>Yes, thats what I want to achive.

Did you try suspending using the echo command I mentioned earlier?

--
Joost


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] hibernation

[Michael Vetter]

> Did you try suspending using the echo command I mentioned earlier?
Yes, it seemed to work (just starting up again didn't).

> You can set the resume partition in the kernel. Might be an option.
Okay, so I changed my kernel command string from "root=/dev/sdb2" to
"root=/dev/sdb2,resume=/dev/mapper/g-SWAP".

Then typed your suspension command again, now the system isn't booting
up anymore: kernel prints trace.

-- 
Michael

Re: [gentoo-user] hibernation

[Randolph Maaßen]

2014-12-04 17:58 GMT+01:00 Michael Vetter <michael.vetter@uni-konstanz.de>:
>> Did you try suspending using the echo command I mentioned earlier?
> Yes, it seemed to work (just starting up again didn't).
>
>> You can set the resume partition in the kernel. Might be an option.
> Okay, so I changed my kernel command string from "root=/dev/sdb2" to
> "root=/dev/sdb2,resume=/dev/mapper/g-SWAP".

In my menuconfig I have a space separated list, not comma separated.
So I guess the boot failure is, that the kernel can't find the root
partition /dev/sdb2,resume...

>
> Then typed your suspension command again, now the system isn't booting
> up anymore: kernel prints trace.
>
> --
> Michael
>



-- 
Mit freundlichen Grüßen / Best regards

Randolph Maaßen

Re: [gentoo-user] hibernation

[Michael Vetter]

Am 04/12/14 18:10, schrieb Randolph Maaßen:
> 2014-12-04 17:58 GMT+01:00 Michael Vetter <michael.vetter@uni-konstanz.de>:
>>> Did you try suspending using the echo command I mentioned earlier?
>> Yes, it seemed to work (just starting up again didn't).
>>
>>> You can set the resume partition in the kernel. Might be an option.
>> Okay, so I changed my kernel command string from "root=/dev/sdb2" to
>> "root=/dev/sdb2,resume=/dev/mapper/g-SWAP".
> 
> In my menuconfig I have a space separated list, not comma separated.
> So I guess the boot failure is, that the kernel can't find the root
> partition /dev/sdb2,resume...

Okay, sorry thought this is equivalent to [1].
Anyways, I changed it to space and my system boots now.
So I tried the suspend command again, but when rebooting its like a
fresh reboot.

Any ideas?

[1] http://man7.org/linux/man-pages/man7/bootparam.7.html

-- 
Michael

Re: [gentoo-user] hibernation

[J. Roeleveld]

On 4 December 2014 18:32:16 CET, Michael Vetter <michael.vetter@uni-konstanz.de> wrote:
>Am 04/12/14 18:10, schrieb Randolph Maaßen:
>> 2014-12-04 17:58 GMT+01:00 Michael Vetter
><michael.vetter@uni-konstanz.de>:
>>>> Did you try suspending using the echo command I mentioned earlier?
>>> Yes, it seemed to work (just starting up again didn't).
>>>
>>>> You can set the resume partition in the kernel. Might be an option.
>>> Okay, so I changed my kernel command string from "root=/dev/sdb2" to
>>> "root=/dev/sdb2,resume=/dev/mapper/g-SWAP".
>> 
>> In my menuconfig I have a space separated list, not comma separated.
>> So I guess the boot failure is, that the kernel can't find the root
>> partition /dev/sdb2,resume...
>
>Okay, sorry thought this is equivalent to [1].
>Anyways, I changed it to space and my system boots now.
>So I tried the suspend command again, but when rebooting its like a
>fresh reboot.
>
>Any ideas?
>
>[1] http://man7.org/linux/man-pages/man7/bootparam.7.html

Yes.
If using LVM for the swap partition (and subsequently the resume) you need to use an initramfs.

I will dig out the script I use on my laptop and post it tomorrow. (It boots faster with a custom script compared to the genkernel or dracut ones)

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] hibernation

[J. Roeleveld]

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

On Thursday, December 04, 2014 07:52:44 PM J.  Roeleveld wrote:
> On 4 December 2014 18:32:16 CET, Michael Vetter <michael.vetter@uni-
konstanz.de> wrote:
> >Am 04/12/14 18:10, schrieb Randolph Maaßen:
> >> 2014-12-04 17:58 GMT+01:00 Michael Vetter
> >
> ><michael.vetter@uni-konstanz.de>:
> >>>> Did you try suspending using the echo command I mentioned earlier?
> >>> 
> >>> Yes, it seemed to work (just starting up again didn't).
> >>> 
> >>>> You can set the resume partition in the kernel. Might be an option.
> >>> 
> >>> Okay, so I changed my kernel command string from "root=/dev/sdb2" to
> >>> "root=/dev/sdb2,resume=/dev/mapper/g-SWAP".
> >> 
> >> In my menuconfig I have a space separated list, not comma separated.
> >> So I guess the boot failure is, that the kernel can't find the root
> >> partition /dev/sdb2,resume...
> >
> >Okay, sorry thought this is equivalent to [1].
> >Anyways, I changed it to space and my system boots now.
> >So I tried the suspend command again, but when rebooting its like a
> >fresh reboot.
> >
> >Any ideas?
> >
> >[1] http://man7.org/linux/man-pages/man7/bootparam.7.html
> 
> Yes.
> If using LVM for the swap partition (and subsequently the resume) you need
> to use an initramfs.
> 
> I will dig out the script I use on my laptop and post it tomorrow. (It boots
> faster with a custom script compared to the genkernel or dracut ones)

Bit later then planned.

The "init" file is the initramfs init-file.
The "config" is what I configure in the kernel:

$ zcat /proc/config.gz | grep initramfs
CONFIG_INITRAMFS_SOURCE="/usr/src/initramfs/config"

There are a few changes you'll need to do:
1) In the "init" file, change the name of the swap-partition you use
2) In the "config" file, change the following paths:
  - init-file
3) In the "config" file, run the command mentioned at the end of the file and
    add the result of the command to the end of the " config " file.

I have been using this config succesfully for over a year on my laptop.

--
Joost

[-- Attachment #2: config --]
[-- Type: text/plain, Size: 5094 bytes --]

# vim: set ft=initramfs :

# init script
file /init /usr/src/initramfs/init 0755 0 0

# basic device nodes
dir /dev 0755 0 0
nod /dev/console 0600 0 0 c 5 1

# mount point for our real root
dir /root 0700 0 0

dir /lib 0755 0 0

dir /etc 755 0 0

# utilities needed to do anything useful
dir /bin 0755 0 0
dir /sbin 0755 0 0
dir /usr 755 0 0
dir /usr/lib 755 0 0
dir /usr/sbin 755 0 0
dir /usr/bin 755 0 0
dir /lib64 755 0 0
dir /usr/lib64 755 0 0
file /bin/busybox /bin/busybox 0755 0 0

# some busybox symlinks
slink /bin/dd busybox 777 0 0
slink /bin/cp busybox 777 0 0
slink /bin/df busybox 777 0 0
slink /bin/ln busybox 777 0 0
slink /bin/ls busybox 777 0 0
slink /bin/mv busybox 777 0 0
slink /bin/ps busybox 777 0 0
slink /bin/rm busybox 777 0 0
slink /bin/sh busybox 777 0 0
slink /bin/vi busybox 777 0 0
slink /bin/ash busybox 777 0 0
slink /bin/cat busybox 777 0 0
slink /bin/pwd busybox 777 0 0
slink /bin/sed busybox 777 0 0
slink /bin/tar busybox 777 0 0
slink /bin/date busybox 777 0 0
slink /bin/echo busybox 777 0 0
slink /bin/grep busybox 777 0 0
slink /bin/gzip busybox 777 0 0
slink /bin/kill busybox 777 0 0
slink /bin/more busybox 777 0 0
slink /bin/ping busybox 777 0 0
slink /bin/sync busybox 777 0 0
slink /bin/true busybox 777 0 0
slink /bin/zcat busybox 777 0 0
slink /bin/chgrp busybox 777 0 0
slink /bin/chmod busybox 777 0 0
slink /bin/chown busybox 777 0 0
slink /bin/dmesg busybox 777 0 0
slink /bin/egrep busybox 777 0 0
slink /bin/false busybox 777 0 0
slink /bin/fgrep busybox 777 0 0
slink /bin/mkdir busybox 777 0 0
slink /bin/mknod busybox 777 0 0
slink /bin/mount busybox 777 0 0
slink /bin/pidof busybox 777 0 0
slink /bin/rmdir busybox 777 0 0
slink /bin/sleep busybox 777 0 0
slink /bin/touch busybox 777 0 0
slink /bin/uname busybox 777 0 0
slink /bin/gunzip busybox 777 0 0
slink /bin/hostname busybox 777 0 0
slink /bin/mktemp busybox 777 0 0
slink /bin/umount busybox 777 0 0
slink /bin/usleep busybox 777 0 0
slink /usr/bin/[ ../../bin/busybox 777 0 0
slink /usr/bin/du ../../bin/busybox 777 0 0
slink /usr/bin/id ../../bin/busybox 777 0 0
slink /usr/bin/tr ../../bin/busybox 777 0 0
slink /usr/bin/wc ../../bin/busybox 777 0 0
slink /usr/bin/cmp ../../bin/busybox 777 0 0
slink /usr/bin/cut ../../bin/busybox 777 0 0
slink /usr/bin/env ../../bin/busybox 777 0 0
slink /usr/bin/tee ../../bin/busybox 777 0 0
slink /usr/bin/tty ../../bin/busybox 777 0 0
slink /usr/bin/yes ../../bin/busybox 777 0 0
slink /usr/bin/chvt ../../bin/busybox 777 0 0
slink /usr/bin/find ../../bin/busybox 777 0 0
slink /usr/bin/expr ../../bin/busybox 777 0 0
slink /usr/bin/free ../../bin/busybox 777 0 0
slink /usr/bin/head ../../bin/busybox 777 0 0
slink /usr/bin/deallocvt ../../bin/busybox 777 0 0
slink /usr/bin/tail ../../bin/busybox 777 0 0
slink /usr/bin/sort ../../bin/busybox 777 0 0
slink /usr/bin/test ../../bin/busybox 777 0 0
slink /usr/bin/time ../../bin/busybox 777 0 0
slink /usr/bin/uniq ../../bin/busybox 777 0 0
slink /usr/bin/wget ../../bin/busybox 777 0 0
slink /usr/bin/dirname ../../bin/busybox 777 0 0
slink /usr/bin/killall ../../bin/busybox 777 0 0
slink /usr/bin/clear ../../bin/busybox 777 0 0
slink /usr/bin/bzcat ../../bin/busybox 777 0 0
slink /usr/bin/reset ../../bin/busybox 777 0 0
slink /usr/bin/unzip ../../bin/busybox 777 0 0
slink /usr/bin/which ../../bin/busybox 777 0 0
slink /usr/bin/xargs ../../bin/busybox 777 0 0
slink /usr/bin/strings ../../bin/busybox 777 0 0
slink /usr/bin/logger ../../bin/busybox 777 0 0
slink /usr/bin/openvt ../../bin/busybox 777 0 0
slink /usr/bin/hexdump ../../bin/busybox 777 0 0
slink /usr/bin/uptime ../../bin/busybox 777 0 0
slink /usr/bin/whoami ../../bin/busybox 777 0 0
slink /usr/bin/readlink ../../bin/busybox 777 0 0
slink /usr/bin/install ../../bin/busybox 777 0 0
slink /usr/bin/basename ../../bin/busybox 777 0 0
slink /usr/bin/bunzip2 ../../bin/busybox 777 0 0
slink /sbin/halt ../bin/busybox 777 0 0
slink /sbin/init ../bin/busybox 777 0 0
slink /sbin/klogd ../bin/busybox 777 0 0
slink /sbin/route ../bin/busybox 777 0 0
slink /sbin/poweroff ../bin/busybox 777 0 0
slink /sbin/swapoff ../bin/busybox 777 0 0
slink /sbin/switch_root ../bin/busybox 777 0 0
slink /sbin/syslogd ../bin/busybox 777 0 0
slink /sbin/ifconfig ../bin/busybox 777 0 0
slink /sbin/reboot ../bin/busybox 777 0 0
slink /sbin/pivot_root ../bin/busybox 777 0 0
slink /sbin/swapon ../bin/busybox 777 0 0
slink /sbin/mdev ../bin/busybox 777 0 0
slink /usr/sbin/chroot ../../bin/busybox 777 0 0
# end of busybox symlinks

# lvm configuration
dir /etc/lvm 755 0 0
file /etc/lvm/lvm.conf /etc/lvm/lvm.conf 644 0 0
file /sbin/lvm /sbin/lvm 555 0 0
slink /sbin/vgchange lvm 777 0 0
slink /sbin/vgscan lvm 777 0 0

dir /var 755 0 0
dir /var/log 755 0 0
dir /var/lock 755 0 0

# proc and sysfs mountpoints
dir /proc 755 0 0
dir /sys 755 0 0

dir /newroot 755 0 0

# Auto-add dependencies - Run following command as root and paste the output below
# for i in lvm busybox  ; do ldd `which ${i}` | cut -d'>' -f2 | awk '{print $1}' ; done | sort -u | grep -v linux-vdso.so.1 | grep -v not | sed 's/\(.*\)/file \1 \1 0755 0 0/'


[-- Attachment #3: init --]
[-- Type: application/x-shellscript, Size: 941 bytes --]

Re: [gentoo-user] hibernation

[Marc Stürmer]

Am 04.12.2014 um 17:30 schrieb Michael Vetter:

> Yes, thats what I want to achive.

The sad thing about hibernation is, that it has always kinda been some 
kind of lackluster in the kernel and quite disappointing. It is a kind 
of area which does not get much love in the kernel for at least over one 
decade.

he number of computers it does not work is bigger than the number of 
computers it does work on correctly.

At least last time I tried it it was quite like that. Hibernation is 
disabled by default on Ubuntu 14.04, because it is so unreliable and 
broken.

In fact, there are three different kind of implementations around namely:

a) the thing in the main line kernel, which seems to work quite subpar, 
which is being used by the utility swsusp,
b) something in the user space being called uswsusp,
c) and an alternative implementation for the kernel being named "Tux on 
Ice."

Many do consider Tux on Ice the most reliable way to get hibernation up 
and running on Linux, unfortunately development seems to be stalled 
since always about one year and it is not part of the main line kernel.

So if you want to get this working reliable, good luck. You'll need it.

[gentoo-user] Re: hibernation

[James]

Marc Stürmer <mail <at> marc-stuermer.de> writes:


> The sad thing about hibernation is, that it has always kinda been some 
> kind of lackluster in the kernel and quite disappointing. It is a kind 
> of area which does not get much love in the kernel for at least over one 
> decade.

> So if you want to get this working reliable, good luck. You'll need it.

Hibernation depends on a myriad of CPU variants, setting and the matching
memory issues. (U)efi is a good place to start your long, arduous journey
of research [1] ; see S4.


I would research the problem and fix it with winblows as the operating
system, if possible; then hope that those setting are not changed
by booting linux. Often you can copy the bios setting from the laptop
and find tools to at least view the contents legibly. It does depend
on the bios. Maybe you need a vendor supplied bios update/downgrade.

Maybe Coreboot, has some old work laying around that is relevant to
your needs [2]. It is mostly a research journey, that may lead
to success or failure. Hard to say, as sometimes the same make and 
model of a laptop, has diffent internal components (like firmware, bios
and chips)...


Good hunting!
James



[1] http://technet.microsoft.com/en-us/library/dn387089.aspx

[2] http://www.coreboot.org/Laptop

Re: [gentoo-user] Re: hibernation

[J. Roeleveld]

On Friday, December 05, 2014 03:08:25 PM James wrote:
> Marc Stürmer <mail <at> marc-stuermer.de> writes:
> > The sad thing about hibernation is, that it has always kinda been some
> > kind of lackluster in the kernel and quite disappointing. It is a kind
> > of area which does not get much love in the kernel for at least over one
> > decade.
> > 
> > So if you want to get this working reliable, good luck. You'll need it.
> 
> Hibernation depends on a myriad of CPU variants, setting and the matching
> memory issues. (U)efi is a good place to start your long, arduous journey
> of research [1] ; see S4.

Not my experience, suspend-to-disk works quite well. The biggest issue was 
with certain drivers not being able to re-initialize certain hardware. (Yes, I 
am talking about the likes of Nvidia)
With current kernels, it does work though.

> I would research the problem and fix it with winblows as the operating
> system, if possible; then hope that those setting are not changed
> by booting linux. Often you can copy the bios setting from the laptop
> and find tools to at least view the contents legibly. It does depend
> on the bios. Maybe you need a vendor supplied bios update/downgrade.
> 
> Maybe Coreboot, has some old work laying around that is relevant to
> your needs [2]. It is mostly a research journey, that may lead
> to success or failure. Hard to say, as sometimes the same make and
> model of a laptop, has diffent internal components (like firmware, bios
> and chips)...

For suspend-to-ram, I agree.
Suspend-to-disk can be handled by the OS.

--
Joost

Re: [gentoo-user] Re: hibernation

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1020 bytes --]

On Saturday 06 Dec 2014 07:41:18 J. Roeleveld wrote:
> > Hibernation depends on a myriad of CPU variants, setting and the matching
> > memory issues. (U)efi is a good place to start your long, arduous journey
> > of research [1] ; see S4.
> 
> Not my experience, suspend-to-disk works quite well. The biggest issue was 
> with certain drivers not being able to re-initialize certain hardware.
> (Yes, I  am talking about the likes of Nvidia)
> With current kernels, it does work though.

It is not just Nvidia.  Suspend to disk (hybernation) worked fine on my laptop 
for years.  Then something changed in the kernel and now although it will 
hybernate, waking up causes all sort of failures and crashes.  It is a kernel 
bug, I found out that someone reported it last year, but it has not been fixed 
yet it seems.

On another PC both hybernation and sleep have gone through a cyclical pattern 
of working or not working over the years.  Thankfully now they are working!  
:-)

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Re: hibernation

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Sat, 6 Dec 2014 11:15:07 +0000, Mick wrote:

> It is not just Nvidia.  Suspend to disk (hybernation) worked fine on my
> laptop for years.  Then something changed in the kernel and now
> although it will hybernate, waking up causes all sort of failures and
> crashes.  It is a kernel bug, I found out that someone reported it last
> year, but it has not been fixed yet it seems.

I had a similar experience and found it as caused by the ethernet driver.
I added a line to my hibernate script to unload the module before
hibernating and the problem went away.


-- 
Neil Bothwick

The Japanese call us lazy, but at least we cook our fish!

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]