hibernate with keystroke?

[Ranjan Maitra]

Hi,

I have been trying to get to hibernate using a single keystroke. So,
here is what i tried:

put pm-hibernate in my sudo. Checked this by using:

sudo pm-hibernate

This works without a hitch.

Then I keyed in ctrl-f12 to be equivalent to sudo pm-hibernate. 
(also tried sudo /usr/sbin/pm-hibernate).

Tried this, but this does not work. Pretty much nothing happens.

I am quite confident that there is nothing wrong with the syntax because
I replaced it with (say) slock and it locks the screen just fine.

What should I be doing here?

Alternatively, what is the command that is executed when I go through
gnome-logout and then press hibernate? I would just like to mimic that,
I guess.

Many thanks for any help/suggestions!

Best wishes,
Ranjan

[poma]

On 21.03.2013 03:22, Ranjan Maitra wrote:
> Hi,
>
> I have been trying to get to hibernate using a single keystroke. So,
> here is what i tried:
>
> put pm-hibernate in my sudo. Checked this by using:
>
> sudo pm-hibernate
>
> This works without a hitch.
>
> Then I keyed in ctrl-f12 to be equivalent to sudo pm-hibernate. 
> (also tried sudo /usr/sbin/pm-hibernate).
>
> Tried this, but this does not work. Pretty much nothing happens.
>
> I am quite confident that there is nothing wrong with the syntax because
> I replaced it with (say) slock and it locks the screen just fine.
>
> What should I be doing here?
>
> Alternatively, what is the command that is executed when I go through
> gnome-logout and then press hibernate? I would just like to mimic that,
> I guess.

Fedora 18 == systemd ;)
systemctl suspend/hibernate/hybrid-sleep are display manager independent.
man systemctl
btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.
Yours working?

Suspend example:

dconf dump /org/gnome/settings-daemon/plugins/media-keys/
[/]
custom-keybindings=['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/']
logout=''
screensaver='<Primary><Alt>l'

[custom-keybindings/custom0]
binding='<Primary><Alt>Delete'
command='gnome-session-quit --logout'
name='Logout'
..

dconf write
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/name
"'Suspend'"
dconf write
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/command
"'systemctl suspend'"
dconf write
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/binding
"'<Shift>F11'"
dconf write
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings
"['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/',
'/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/']"
..

dconf dump /org/gnome/settings-daemon/plugins/media-keys/
[/]
custom-keybindings=['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/',
'/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/']
logout=''
screensaver='<Primary><Alt>l'

[custom-keybindings/custom11]
binding='<Shift>F11'
command='systemctl suspend'
name='Suspend'

[custom-keybindings/custom0]
binding='<Primary><Alt>Delete'
command='gnome-session-quit --logout'
name='Logout'

[poma]

On 22.03.2013 01:32, poma wrote:
...
> btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.

Actually, dracut --hostonly generated initramfs broke the hibernate.
dracut 1 - 0 systemd :)
Hi Ho Silver!

poma

[Harald Hoyer]

Am 22.03.2013 02:23, schrieb poma:
> On 22.03.2013 01:32, poma wrote:
> ...
> > btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.
>
> Actually, dracut --hostonly generated initramfs broke the hibernate.
> dracut 1 - 0 systemd :)
> Hi Ho Silver!
>
> poma

Does it work, if you specify "resume=<swap_device>" on the kernel command line?

[poma]

On 22.03.2013 07:18, Harald Hoyer wrote:
> Am 22.03.2013 02:23, schrieb poma:
> > On 22.03.2013 01:32, poma wrote:
> > ...
> > > btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.
> >
> > Actually, dracut --hostonly generated initramfs broke the hibernate.
> > dracut 1 - 0 systemd :)
> > Hi Ho Silver!
> >
> > poma
>
> Does it work, if you specify "resume=<swap_device>" on the kernel command line?

resume=/dev/md1
Nope.
Version: 024-29.git20130227.fc18

md/raid1:md1: not clean -- starting background reconstruction
md/raid1:md1: active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 8585871360
md: resync of RAID array md1
 md1: unknown partition table
Adding 8384636k swap on /dev/md1.  Priority:-1 extents:1 across:8384636k
md: md1: resync done.

poma

[Harald Hoyer]

Am 22.03.2013 12:45, schrieb poma:
> On 22.03.2013 07:18, Harald Hoyer wrote:
> > Am 22.03.2013 02:23, schrieb poma:
> > > On 22.03.2013 01:32, poma wrote:
> > > ...
> > > > btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.
> > >
> > > Actually, dracut --hostonly generated initramfs broke the hibernate.
> > > dracut 1 - 0 systemd :)
> > > Hi Ho Silver!
> > >
> > > poma
> >
> > Does it work, if you specify "resume=<swap_device>" on the kernel command line?
>
> resume=/dev/md1
> Nope.
> Version: 024-29.git20130227.fc18
>
> md/raid1:md1: not clean -- starting background reconstruction
> md/raid1:md1: active with 2 out of 2 mirrors
> md1: detected capacity change from 0 to 8585871360
> md: resync of RAID array md1
>  md1: unknown partition table
> Adding 8384636k swap on /dev/md1.  Priority:-1 extents:1 across:8384636k
> md: md1: resync done.
>
> poma

you must not resume from a raid array

[poma]

On 22.03.2013 13:00, Harald Hoyer wrote:
...
> you must not resume from a raid array

Dracut's Host-Only mode is more restrictive than what is superficially
evident. Bummer!
Thanks for pointing that out.

poma

[Kevin Cummings]

On 03/22/2013 11:23 AM, poma wrote:
> On 22.03.2013 13:00, Harald Hoyer wrote:
> ...
> > you must not resume from a raid array
>
> Dracut's Host-Only mode is more restrictive than what is superficially
> evident. Bummer!

That's most likely because at boot time the software raid arrays haven't
been determined yet (/dev/mdX)....

[poma]

On 22.03.2013 22:44, Kevin J. Cummings wrote:
> On 03/22/2013 11:23 AM, poma wrote:
> > On 22.03.2013 13:00, Harald Hoyer wrote:
> > ...
> > > you must not resume from a raid array
> >
> > Dracut's Host-Only mode is more restrictive than what is superficially
> > evident. Bummer!
>
> That's most likely because at boot time the software raid arrays haven't
> been determined yet (/dev/mdX)....

Excellent point!
Are your swap raidised? :)

poma

[Kevin Cummings]

On Mar 22, 2013, at 18:08, poma  wrote:
> On 22.03.2013 22:44, Kevin J. Cummings wrote:
> > On 03/22/2013 11:23 AM, poma wrote:
> > > On 22.03.2013 13:00, Harald Hoyer wrote:
> > > ...
> > > > you must not resume from a raid array
> > >
> > > Dracut's Host-Only mode is more restrictive than what is superficially
> > > evident. Bummer!
> >
> > That's most likely because at boot time the software raid arrays haven't
> > been determined yet (/dev/mdX)....
>
> Excellent point!
> Are your swap raidised? :)

No.

--
Kevin J. Cummings
[e-mail]
[e-mail]
[e-mail]
Registered Linux User #1232
(http://www.linuxcounter.net/)

[poma]

On 22.03.2013 13:00, Harald Hoyer wrote:
...
> you must not resume from a raid array

Let me show you how country feels :)

Version: 025-35.git20130211.fc18 [1]

/etc/dracut.conf.d/dracut-custom.conf:
# Custom dracut config file

# /etc/dracut.conf.d/*.conf will override the settings in /etc/dracut.conf

# build initrd only to boot current hardware
hostonly="yes"

# Bring up <device> in initramfs, <device> should be the device name.
# Beside device name, it would be nice if one can use fstab alike UUID.
# This can be useful in hostonly mode for resume support when
# your swap is on LVM an encrypted partition or on a MD RAID partition.
add_device+=" /dev/md1 "
..

The corresponding command:
dracut --hostonly --device /dev/md1 [-f] [-v]
..

PM: Hibernation image not present or could not be loaded.
PM: Hibernation mode set to 'platform'
PM: Marking nosave pages: [mem 0x0009e000-0x000fffff]
PM: Marking nosave pages: [mem 0xcfef0000-0xffffffff]
PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
PM: Basic memory bitmaps created
PM: Syncing filesystems ... done.
PM: Preallocating image memory... done (allocated 279164 pages)
PM: Allocated 1116656 kbytes in 0.30 seconds (3722.18 MB/s)
PM: freeze of devices complete after 1463.281 msecs
PM: late freeze of devices complete after 0.472 msecs
PM: noirq freeze of devices complete after 0.354 msecs
PM: Saving platform NVS memory
PM: Creating hibernation image:
PM: Need to copy 292982 pages
PM: Normal pages needed: 292982 + 1024, available pages: 738735
PM: Restoring platform NVS memory
PM: noirq restore of devices complete after 21.957 msecs
PM: early restore of devices complete after 0.352 msecs
PM: restore of devices complete after 1290.944 msecs
PM: Image restored successfully.
PM: Basic memory bitmaps freed
..

Swap redundancy is good, right? ;)

poma

[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=383753
 -  Rebuilt for Fedora 18

[Harald Hoyer]

Am 22.03.2013 21:32, schrieb poma:
> On 22.03.2013 13:00, Harald Hoyer wrote:
> ...
> > you must not resume from a raid array
>
> Let me show you how country feels :)
>
> Version: 025-35.git20130211.fc18 [1]
>
> /etc/dracut.conf.d/dracut-custom.conf:
> # Custom dracut config file
>
> # /etc/dracut.conf.d/*.conf will override the settings in /etc/dracut.conf
>
> # build initrd only to boot current hardware
> hostonly="yes"
>
> # Bring up <device> in initramfs, <device> should be the device name.
> # Beside device name, it would be nice if one can use fstab alike UUID.
> # This can be useful in hostonly mode for resume support when
> # your swap is on LVM an encrypted partition or on a MD RAID partition.
> add_device+=" /dev/md1 "
> ..
>
> The corresponding command:
> dracut --hostonly --device /dev/md1 [-f] [-v]
> ..
>
> PM: Hibernation image not present or could not be loaded.
> PM: Hibernation mode set to 'platform'
> PM: Marking nosave pages: [mem 0x0009e000-0x000fffff]
> PM: Marking nosave pages: [mem 0xcfef0000-0xffffffff]
> PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
> PM: Basic memory bitmaps created
> PM: Syncing filesystems ... done.
> PM: Preallocating image memory... done (allocated 279164 pages)
> PM: Allocated 1116656 kbytes in 0.30 seconds (3722.18 MB/s)
> PM: freeze of devices complete after 1463.281 msecs
> PM: late freeze of devices complete after 0.472 msecs
> PM: noirq freeze of devices complete after 0.354 msecs
> PM: Saving platform NVS memory
> PM: Creating hibernation image:
> PM: Need to copy 292982 pages
> PM: Normal pages needed: 292982 + 1024, available pages: 738735
> PM: Restoring platform NVS memory
> PM: noirq restore of devices complete after 21.957 msecs
> PM: early restore of devices complete after 0.352 msecs
> PM: restore of devices complete after 1290.944 msecs
> PM: Image restored successfully.
> PM: Basic memory bitmaps freed
> ..
>
> Swap redundancy is good, right? ;)
>
> poma

Sure, if it works for you :)

One recommendation: please use UUID= instead of relying on the kernel numbering
scheme for devices, if you want to avoid problems.

[poma]

On 23.03.2013 06:05, Harald Hoyer wrote:
> Am 22.03.2013 21:32, schrieb poma:
> > On 22.03.2013 13:00, Harald Hoyer wrote:
> > ...
> > > you must not resume from a raid array
> >
> > Let me show you how country feels :)
> >
> > Version: 025-35.git20130211.fc18 [1]
> >
> > /etc/dracut.conf.d/dracut-custom.conf:
> > # Custom dracut config file
> >
> > # /etc/dracut.conf.d/*.conf will override the settings in /etc/dracut.conf
> >
> > # build initrd only to boot current hardware
> > hostonly="yes"
> >
> > # Bring up <device> in initramfs, <device> should be the device name.
> > # Beside device name, it would be nice if one can use fstab alike UUID.
> > # This can be useful in hostonly mode for resume support when
> > # your swap is on LVM an encrypted partition or on a MD RAID partition.
> > add_device+=" /dev/md1 "
> > ..
> >
> > The corresponding command:
> > dracut --hostonly --device /dev/md1 [-f] [-v]
> > ..
> >
> > PM: Hibernation image not present or could not be loaded.
> > PM: Hibernation mode set to 'platform'
> > PM: Marking nosave pages: [mem 0x0009e000-0x000fffff]
> > PM: Marking nosave pages: [mem 0xcfef0000-0xffffffff]
> > PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
> > PM: Basic memory bitmaps created
> > PM: Syncing filesystems ... done.
> > PM: Preallocating image memory... done (allocated 279164 pages)
> > PM: Allocated 1116656 kbytes in 0.30 seconds (3722.18 MB/s)
> > PM: freeze of devices complete after 1463.281 msecs
> > PM: late freeze of devices complete after 0.472 msecs
> > PM: noirq freeze of devices complete after 0.354 msecs
> > PM: Saving platform NVS memory
> > PM: Creating hibernation image:
> > PM: Need to copy 292982 pages
> > PM: Normal pages needed: 292982 + 1024, available pages: 738735
> > PM: Restoring platform NVS memory
> > PM: noirq restore of devices complete after 21.957 msecs
> > PM: early restore of devices complete after 0.352 msecs
> > PM: restore of devices complete after 1290.944 msecs
> > PM: Image restored successfully.
> > PM: Basic memory bitmaps freed
> > ..
> >
> > Swap redundancy is good, right? ;)
> >
> > poma
>
> Sure, if it works for you :)
>
> One recommendation: please use UUID= instead of relying on the kernel numbering
> scheme for devices, if you want to avoid problems.

Yeah, UUIDs are being used from the day one.
But what I meant is:
add_device+=" <PARTUUID> " directive in addition to the " <device> " as
device name such as in the current 'dracut.conf' schema.
Although, this is resolved by an explicit specification of a swap UUID,
i.e. rd.md.uuid=<MD array UUID> to the boot loader, so that directive is
not required in this case.

poma

[Harald Hoyer]

Am 23.03.13 18:17, schrieb poma:
> On 23.03.2013 06:05, Harald Hoyer wrote:
> > Am 22.03.2013 21:32, schrieb poma:
> > > On 22.03.2013 13:00, Harald Hoyer wrote:
> > > ...
> > > > you must not resume from a raid array
> > >
> > > Let me show you how country feels :)
> > >
> > > Version: 025-35.git20130211.fc18 [1]
> > >
> > > /etc/dracut.conf.d/dracut-custom.conf:
> > > # Custom dracut config file
> > >
> > > # /etc/dracut.conf.d/*.conf will override the settings in /etc/dracut.conf
> > >
> > > # build initrd only to boot current hardware
> > > hostonly="yes"
> > >
> > > # Bring up <device> in initramfs, <device> should be the device name.
> > > # Beside device name, it would be nice if one can use fstab alike UUID.
> > > # This can be useful in hostonly mode for resume support when
> > > # your swap is on LVM an encrypted partition or on a MD RAID partition.
> > > add_device+=" /dev/md1 "
> > > ..
> > >
> > > The corresponding command:
> > > dracut --hostonly --device /dev/md1 [-f] [-v]
> > > ..
> > >
> > > PM: Hibernation image not present or could not be loaded.
> > > PM: Hibernation mode set to 'platform'
> > > PM: Marking nosave pages: [mem 0x0009e000-0x000fffff]
> > > PM: Marking nosave pages: [mem 0xcfef0000-0xffffffff]
> > > PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
> > > PM: Basic memory bitmaps created
> > > PM: Syncing filesystems ... done.
> > > PM: Preallocating image memory... done (allocated 279164 pages)
> > > PM: Allocated 1116656 kbytes in 0.30 seconds (3722.18 MB/s)
> > > PM: freeze of devices complete after 1463.281 msecs
> > > PM: late freeze of devices complete after 0.472 msecs
> > > PM: noirq freeze of devices complete after 0.354 msecs
> > > PM: Saving platform NVS memory
> > > PM: Creating hibernation image:
> > > PM: Need to copy 292982 pages
> > > PM: Normal pages needed: 292982 + 1024, available pages: 738735
> > > PM: Restoring platform NVS memory
> > > PM: noirq restore of devices complete after 21.957 msecs
> > > PM: early restore of devices complete after 0.352 msecs
> > > PM: restore of devices complete after 1290.944 msecs
> > > PM: Image restored successfully.
> > > PM: Basic memory bitmaps freed
> > > ..
> > >
> > > Swap redundancy is good, right? ;)
> > >
> > > poma
> >
> > Sure, if it works for you :)
> >
> > One recommendation: please use UUID= instead of relying on the kernel numbering
> > scheme for devices, if you want to avoid problems.
>
> Yeah, UUIDs are being used from the day one.
> But what I meant is:
> add_device+=" <PARTUUID> " directive in addition to the " <device> " as
> device name such as in the current 'dracut.conf' schema.
> Although, this is resolved by an explicit specification of a swap UUID,
> i.e. rd.md.uuid=<MD array UUID> to the boot loader, so that directive is
> not required in this case.
>
> poma

/dev/disk/by-uuid/.... can be used instead of UUID=

[poma]

On 24.03.2013 11:14, Harald Hoyer wrote:
...
> /dev/disk/by-uuid/.... can be used instead of UUID=

True.
Thanks.

poma

[poma]

On 22.03.2013 02:23, poma wrote:
...
> Actually, dracut --hostonly generated initramfs broke the hibernate.
> dracut 1 - 0 systemd :)

Actually, it's a feature.
Sorry.
dracut 1 - 1 systemd.

poma

[Ranjan Maitra]

Thanks very much! You really made my day -- I have been trying all
sorts of things to do this over the past two years or so....

hibernate does not work for me -- does not really wake up to anything
meaningfull on a Dell Latitude E540 (? ) for any of the 3.8 kernels:
does work for me all right on my trusty Thinkpad T61.

Thanks again for the help re: hibernate.
Ranjan

On Fri, 22 Mar 2013 01:32:24 +0100 poma 
wrote:
> On 21.03.2013 03:22, Ranjan Maitra wrote:
> > Hi,
> >
> > I have been trying to get to hibernate using a single keystroke. So,
> > here is what i tried:
> >
> > put pm-hibernate in my sudo. Checked this by using:
> >
> > sudo pm-hibernate
> >
> > This works without a hitch.
> >
> > Then I keyed in ctrl-f12 to be equivalent to sudo pm-hibernate. 
> > (also tried sudo /usr/sbin/pm-hibernate).
> >
> > Tried this, but this does not work. Pretty much nothing happens.
> >
> > I am quite confident that there is nothing wrong with the syntax because
> > I replaced it with (say) slock and it locks the screen just fine.
> >
> > What should I be doing here?
> >
> > Alternatively, what is the command that is executed when I go through
> > gnome-logout and then press hibernate? I would just like to mimic that,
> > I guess.
>
> Fedora 18 == systemd ;)
> systemctl suspend/hibernate/hybrid-sleep are display manager independent.
> man systemctl
> btw on 3.8.3-203.fc18.x86_64 the hibernate is broken on some mobos.
> Yours working?
>
> Suspend example:
>
> dconf dump /org/gnome/settings-daemon/plugins/media-keys/
> [/]
> custom-keybindings=['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/']
> logout=''
> screensaver='<Primary><Alt>l'
>
> [custom-keybindings/custom0]
> binding='<Primary><Alt>Delete'
> command='gnome-session-quit --logout'
> name='Logout'
> ..
>
> dconf write
> /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/name
> "'Suspend'"
> dconf write
> /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/command
> "'systemctl suspend'"
> dconf write
> /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/binding
> "'<Shift>F11'"
> dconf write
> /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings
> "['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/',
> '/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/']"
> ..
>
> dconf dump /org/gnome/settings-daemon/plugins/media-keys/
> [/]
> custom-keybindings=['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/',
> '/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom11/']
> logout=''
> screensaver='<Primary><Alt>l'
>
> [custom-keybindings/custom11]
> binding='<Shift>F11'
> command='systemctl suspend'
> name='Suspend'
>
> [custom-keybindings/custom0]
> binding='<Primary><Alt>Delete'
> command='gnome-session-quit --logout'
> name='Logout'
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[poma]

On 22.03.2013 02:35, Ranjan Maitra wrote:
...
> hibernate does not work for me -- does not really wake up to anything
> meaningfull on a Dell Latitude E540 (? ) for any of the 3.8 kernels:

Elaborate it on the https://bugzilla.redhat.com/ ;)

poma