From ArchWiki
Revision as of 22:04, 30 July 2012 by Magus (talk | contribs) (Adding section on editing the GRUB2 defaults.)
Jump to navigation Jump to search

zh-CN:Pm-utils Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary end pm-utils is the new suspend and powerstate setting framework. It is designed to replace such scripts as those provided by the powersave package.

pm-utils can be thought of as a collection of shell scripts that wrap the kernel mode suspend/resume with the various hacks. These hacks are needed to work around bugs in drivers and subsystems that are not yet aware of suspend. It is easily extensible by putting custom hooks into a directory, which can either be done by the system administrator or those hooks can be part of a package, especially if this package needs special attention during a system suspend or power state transition.

A lesser known feature is one that mimics toggling done by Laptop Mode Tools, although the responsible scripts have been deleted from the Arch Linux package.

Used in conjunction with the cpufrequtils package, notebook (and desktop) owners are provided with a complete power management suite.


Install the pm-utils package which is available in the official repositories.

Note: If you run into issues when resuming video, it might be necessary to also install vbetool from the official repositories.
Note: If you are starting from a clean install, make sure that you have acpi installed.

Run pm-suspend or pm-hibernate as root to trigger suspend manually. The suspend scripts write log to /var/log/pm-suspend.log.

suspend backend

The Arch Linux package ships with support for the following backends: kernel, tuxonice and uswsusp which can be seen from command:

pacman -Ql pm-utils | grep module.d

Suspend backend is specified by the SLEEP_MODULE configuration variable in /etc/pm/config.d and defaults to the kernel backend. To use the alternative suspend backends the respective packages need to be installed. Both of these are available in the Arch User Repository:

Furthermore, pm-utils ships with its own video quirks database in /usr/lib/pm-utils/video-quirks/.

Basic Configuration

Standby / Suspend to RAM

In the ideal case, running pm-suspend as root should initiate suspend to memory, meaning that all running state will be preserved in RAM and all components other than RAM will be shut down to conserve power. Pressing the power button should initiate a resume from this state.

In some cases, it is possible that running pm-suspend causes hangs or other issues. This may be due to specific "misbehaving" modules. If you know which modules could cause such issues, adding a SUSPEND_MODULES config to /etc/pm/config.d/modules of the form:

SUSPEND_MODULES="uhci_hd button ehci_hd"

should cause these modules to be specifically unloaded before suspend and reloaded after resume.

To configure invoking pm-suspend automatically on power events like laptop lid close, please refer to Acpid.

Hibernation (suspend2disk)

In order for suspend2disk (hibernate) to work, the parameter resume=SWAP_PARTITION has to be passed to the Kernel parameters (where SWAP_PARTITION is either your swap device, i.e. /dev/sdaX, or your swap UUID) .Consult Kernel parameters for more info.

Editing GRUB2's defaults

The easiest way to modify the kernel parameters is to edit the default for GRUB2 held in /etc/defaults/grub. If /dev/sda5 is your swap partition then change GRUB_CMDLINE_LINUX to:


Don't forget to run grub-mkconfig afterwards.

Including GRUB2's os-prober lines

According to the debian wiki, here is a handy solution for GRUB2 that will insert the resume line with the swap device the system is using when running the script. Replace (line 141):

linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}


linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args} resume=`swapon -s | grep '/dev/sd.[0-9]' -o`

When the machine is placed into hibernation, it will now move all data from RAM to the swap partition.

For discussion regarding permanence, please refer to this thread.

Even if your swap partition is smaller than RAM, you still have a big chance in hibernating successfully. According to kernel documentation: "/sys/power/image_size controls the size of the image created by the suspend-to-disk mechanism [...] which is set to 2/5 of available RAM by default. [...] The suspend-to-disk mechanism will do its best to ensure the image size will not exceed that number." You may either decrease it due to a small swap partition or increase it in purpose of possible hibernation speed up.

Warning: You may have to add the resume hook to /etc/mkinitcpio.conf, see below!

Suspend to Swap-File

If you want to suspend-to-disk without having a Swap partition see

Mkinitcpio Resume Hook

If your system still doesn't resume from hibernation, even after you've added the proper lines to your grub config files, your system may require the resume hook be added to the initrd image (even if you use LVM), otherwise the kernel will not resume. You can see if this is happening if the hibernation works fine, no error messages appear in /var/log/pm-suspend.log and the kernel logs the following message: "PM: Hibernation image not present or could not be loaded." To add the resume hook, edit /etc/mkinitcpio.conf as root and add resume to the HOOKS array:

HOOKS="base udev autodetect ide scsi sata lvm2 resume filesystems"

Note that this is an example, and your HOOKS array may look different.

resume must be placed after ide, scsi, sata and/or lvm2, but before filesystems. Of course, there has to be an appropriate resume file in /usr/lib/initcpio/hooks (formerly /lib/initcpio/hooks), but it should already be there, as it is part of the mkinitcpio package.

Finally, you must rebuild the initrd image for these changes to take effect:

# mkinitcpio -p linux
Note: If you use a custom kernel, then you might have to change the value of the -p option.

Suspend/Hibernate as regular user

Three methods are available to suspend without the need for a root password: using Udev, using UPower, and giving the user the appropriate permissions with visudo.

UPower method

Install upower. To suspend to RAM:

$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \
/org/freedesktop/UPower org.freedesktop.UPower.Suspend

To suspend to disk (hibernate):

$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \
/org/freedesktop/UPower org.freedesktop.UPower.Hibernate

User Permission Method

Because the pm-utils scripts must be run as root, you may want to make the scripts accessible to normal users by running sudo without the root password. To do so, edit the /etc/sudoers file with visudo as root. For more information, see sudo.

Add the following lines, replacing username with your own user name, then save and exit visudo:

username  ALL = NOPASSWD: /usr/sbin/pm-hibernate
username  ALL = NOPASSWD: /usr/sbin/pm-suspend

Or you can enable it for a group, using the following lines, replacing group:

%group   ALL = NOPASSWD: /usr/sbin/pm-hibernate
%group   ALL = NOPASSWD: /usr/sbin/pm-suspend
Note: These must come after any user privilege specifications, e.g., username ALL=(ALL) ALL, or they will not work.

You can now run the scripts without a password by simply running:

$ sudo pm-hibernate


$ sudo pm-suspend

Also, add yourself to the power group so that way using things like applets to do suspend will work. If you do not do this, when you try to use suspend though things like GNOME's shutdown applet, your computer will just play a very annoying loud triple beep and lock the screen.

# gpasswd -a username power

You should now be able to use your Desktop Environment's power management tools to automatically suspend or hibernate when doing things like closing the laptop lid, running low on battery power, etc.

Power saving

pm-utils supports running commands depending on whether the system is connected to the AC adapter or not; therefore, a script has to be created inside the folder /etc/pm/power.d/. An example of such a script can be found in the crunchbang forum. Be aware that upower must be running in order to detect changing AC states (see more information).

Suspend on idle/inactivity

One method relies on xautolock program. Add following: xautolock -time 30 -locker "sudo pm-suspend" & to ~/.xinitrc. This implies that pm-suspend is called after 30 minutes of inactivity.

Using Swap file instead of regular swap partition

If you want use swap file instead of regular swap patition read this.

Advanced Configuration

The main configuration file is /usr/lib/pm-utils/defaults. You should not edit this file, since after a package update it might be overwritten with the default settings. Put your config file into /etc/pm/config.d/ instead. You can just put a simple text file with

SUSPEND_MODULES="button uhci_hcd"

named modules or config into /etc/pm/config.d and it will override the settings in the system-wide configuration file.

Available variables for use in config files

the list of modules to be unloaded before suspend
SLEEP_MODULE="tuxonice uswsusp kernel"
the default sleep/wake systems to try
forces the system to shut down rather than reboot

Disabling a hook

If a hook is run which you do not like or which you think is not useful or even harmful, we would appreciate a bug report for that. You can however easily disable hooks by just creating an empty file corresponding to the hook in /etc/pm/sleep.d/. Say you want to disable the hook /usr/lib/pm-utils/sleep.d/45pcmcia, you can do this easily by calling

# touch /etc/pm/sleep.d/45pcmcia

Do not set the executable bit on that dummy-hook.

Alternative method

Create a file in /etc/pm/config.d with the modules you want to blacklist in the HOOK_BLACKLIST variable. For example, to manage power saving yourself, use:

HOOK_BLACKLIST="hal-cd-polling intel-audio-powersave journal-commit laptop-mode pcie_aspm readahead sata_alpm sched-powersave xfs_buffer wireless"

Creating your own hooks

If you want to do something specific to your setup during suspend or hibernate, then you can easily put your own hook into /etc/pm/sleep.d. The hooks in this directory will be called in alphabetic order during suspend (that is the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume. The general convention to be followed on number ordering is:.

00 - 49
User and most package supplied hooks. If a hook assumes that all of the usual services and userspace infrastructure is still running, it should be here.
50 - 74
Service handling hooks. Hooks that start or stop a service belong in this range. At or before 50, hooks can assume that all services are still enabled.
75 - 89
Module and non-core hardware handling. If a hook needs to load/unload a module, or if it needs to place non-video hardware that would otherwise break suspend or hibernate into a safe state, it belongs in this range. At or before 75, hooks can assume all modules are still loaded.
90 - 99
Reserved for critical suspend hooks.

I am showing a pretty useless demonstration hook here, that will just put some informative lines into your log file:

case $1 in
        echo "Hey guy, we are going to suspend to disk!"
        echo "Oh, this time we are doing a suspend to RAM. Cool!"
        echo "Oh, suspend to disk is over, we are resuming..."
        echo "Hey, the suspend to RAM seems to be over..."
    *)  echo "Somebody is calling me totally wrong."

Put this into /etc/pm/sleep.d/66dummy, do a chmod +x /etc/pm/sleep.d/66dummy and it will spew some useless lines during suspend and resume.

Warning: All the hooks run as root. This means that you need to be careful when creating temporary files, check that the PATH environment variable is set correctly, etc. to avoid security problems.

How it works

The concept is quite easy: the main script (pm-action, called via symlinks as either pm-suspend, pm-hibernate or pm-suspend-hybrid) executes so-called "hooks", executable scripts, in the alphabetical sorted order with the parameter suspend (suspend to RAM) or hibernate (suspend to disk). Once all hooks are done, it puts the machine to sleep. After the machine has woken up again, all those hooks are executed in reverse order with the parameter resume (resume from RAM) or thaw (resume from disk). The hooks perform various tasks, such as preparing the bootloader, stopping the Bluetooth subsystem, or unloading of critical modules.

Both pm-suspend and pm-hibernate are usually called from Udev, initiated by desktop applets like gnome-power-manager or kpowersave.

Note: suspend-hybrid is a placeholder right now -- it is not completely implemented.

There is also the possibility to set the machine into high-power and low-power mode, the command pm-powersave is used with an additional parameter of true or false. It works basically the same as the suspend framework.

The hooks for suspend are placed in

distribution / package provided hooks
hooks added by the system administrator

The hooks for the power state are placed in

distribution / package provided hooks
hooks added by the system administrator

Hooks in /etc/pm/ take precedence over those in /usr/lib/pm-utils/, so the system administrator can override the defaults provided by the distribution.

Pm-suspend internals

This outlines the internal actions when pm-suspend is run, describing how pm-utils gracefully falls back onto the kernel method if the requirements of other methods are not met.

$ pm-suspend

The first step is set-up preliminary variables and source parent scripts:

export STASHNAME=pm-suspend
export METHOD="$(echo ${0##*pm-} |tr - _)"
. "/usr/lib/pm-utils/pm-functions"

The variable METHOD is extracted from the executable name, suspend from pm-suspend and hibernate from pm-hibernate.

The location of runtime configuration parameters is defined in /usr/lib/pm-utils/pm-functions as PM_UTILS_RUNDIR="/var/run/pm-utils" and STORAGEDIR="${PM_UTILS_RUNDIR}/${STASHNAME}/storage". Therefore STORAGEDIR="/var/run/pm-utils/pm-suspend/storage"; this is where pm-suspend will cache its configuration. Disabled hooks are stored as plain text files with the hook name prefixed by "disable_hook:". Configuration parameters are appended to the parameters file:

$  ls -lah /var/run/pm-utils/pm-suspend/storage/
-rw-r--r-- 1 root root  20 May 19 09:57 disable_hook:99video
-rw-r--r-- 1 root root   0 May 19 02:59 parameters
-rw-r--r-- 1 root root 247 May 19 02:59 parameters.rm
-rw-r--r-- 1 root root   9 May 19 02:59 state:cpu0_governor
-rw-r--r-- 1 root root   9 May 19 02:59 state:cpu1_governor

Then pm-functions will source the files located in /etc/pm/config.d/ in addition to /usr/lib/pm-utils/defaults. Upon returning, pm-functions will proceed to source the files specified by $SLEEP_METHOD as /usr/lib/pm-utils/module.d/$SLEEP_METHOD[...] if they exist:

for mod in $SLEEP_MODULE; do
    [ -f "$mod" ] || continue
    . "$mod"

Otherwise, if $SLEEP_MODULE is empty, do_suspend() will be set to the kernel backend as described above:

if [ -z "$SUSPEND_MODULE" ]; then
    if grep -q mem /sys/power/state; then
       do_suspend() { echo -n "mem" >/sys/power/state; }
    elif [ -c /dev/pmu ] && pm-pmu --check; then
       do_suspend() { pm-pmu --suspend; }
    elif grep -q standby /sys/power/state; then
       do_suspend() { echo -n "standby" >/sys/power/state; }

Assuming $SLEEP_MODULE is not empty and uswsusp is specified, /usr/lib/pm-utils/module.d/uswsusp is executed. This script checks several requirements (these are the requirements for being able to use uswsusp):

  • [ -z $SUSPEND_MODULE ]
  • command_exists s2ram
  • grep -q mem /sys/power/state || ( [ -c /dev/pmu ] && pm-pmu --check; );

If these requirements are met, do_suspend() is defined as:

   s2ram --force $OPTS

Most importantly, the uswsusp module runs:

add_before_hooks uswsusp_hooks
add_module_help uswsusp_help

The first function, add_before_hook disables the pm-utils hooks 99video since this functionality is subsumed by s2ram. The second function, add_module_help, adds uswsusp-module-specific help, which in essence replaces the help function provided by 99video.

Back to pm-suspend:

command_exists "check_$METHOD" && command_exists "do_$METHOD"

This verifies that the check_suspend and do_suspend methods have been defined. The check_suspend method simply verifies that $SUSPEND_MODULE is not empty:

check_suspend() { [ -n "$SUSPEND_MODULE" ]; }

Lastly, pm-suspend must run all hooks that have not been disabled, sync file-system buffers, and run do_suspend:

if run_hooks sleep "$ACTION $METHOD"; then
    # Sleep only if we know how and if a hook did not inhibit us.
    log "$(date): performing $METHOD"
    "do_$METHOD" || r=128
    log "$(date): Awake."

The method run_hooks is a wrapper for _run_hooks, which the case of pm-suspend is called as run_hooks sleep "suspend suspend". Given that:


The method _run_hooks, will for each hook in "${PM_UTILS_LIBDIR}/$1.d" and "${PM_UTILS_ETCDIR}/$1.d", check that sleep has not been inhibited and update the runtime parameters stored in $PARAMETERS before running each hook via run_hook $hook $2. In the case of Suspend-to-RAM, all the hooks in {/usr/lib/pm-utils/sleep.d/,/etc/pm/sleep.d/} will be enumerated, and run_hook will be passed the parameters $hook and "suspend suspend". The method run_hook uses the hook_ok function to verify that the hook has not been disabled before executing the hook with the "suspend suspend" parameters.


If suspend or hibernate did not work correctly, you will probably find some information in the log file /var/log/pm-suspend.log. For example, which hooks were run and what the output of them was should be in that log file.

Also, check the output of the pm-is-supported command. This command (with the --hibernate or --suspend flag) will do some sanity checking and report any errors it finds in your configuration. It will not detect all possible errors, but may still be useful.

Segmentation faults

If you experience segmentation faults that might result in an unresponsive system and missing keys then try to set the UUID in the resume-path in /boot/grub/menu.lst as explained above.

Reboot instead of resume from suspend

This problem started when saving NVS area during suspend was introduced (in 2.6.35-rc4) (mailing list post). However, it is known that this mechanism does not work on all machines, so the kernel developers allow the user to disable it with the help of the acpi_sleep=nonvs kernel command line option. This option could be pass to the kernel through GRUB options by editing the file /boot/grub/menu.lst (GRUB 0.97) on the kernel line.

Resume from suspend shuts down instead of wake up

On an Acer Aspire AS3810TG, resuming from suspend shuts down the computer instead of waking it up. If you experience a similar issue, try passing the parameter i8042.reset=1 to your kernel. In GRUB2, the line in /boot/grub/grub.cfg should be something like this:

linux /vmlinuz-linux root=/dev/vg00/root resume=/dev/vg00/swap i8042.reset=1 ro

Although I have not tested this, you could also set this parameter live without having to restart by doing:

# sysctl -e -w i8042.reset=1

Blank screen when waking from suspend

Some laptops (e.g. Dell Inspiron Mini 1018) will just show a black screen with no backlight after resuming from suspend. If this happens to you, try going into the BIOS of the laptop and disabling Intel SpeedStep if it is present.

You could also try, without disabling SpeedStep, creating a quirk in /etc/pm/sleep.d/ with this content (requires vbetool):

case "$1" in
sleep 5
vbetool dpms off
vbetool dpms on
*) exit $NA

save it as you want but with a 00 in front of the name so this is called last when resuming; remember to chmod +x the script. Try adjusting the sleep time if the other commands are called too soon, or if it works well, you can also try removing that line.

Some other laptops (e.g. Toshiba Portégé R830) will just show a black screen with no backlight after resuming from suspend, with fans blowing at top speed. If this is what you're seeing, try going into the BIOS and disable the VT-d virtualization setting by switching to "VT-x only".

VirtualBox problems

The VirtualBox kernel modules cause pm-suspend and pm-hibernate to fail on some laptops. (See this discussion). Instead of suspending or hibernating, the system freezes and indicator LEDs blink (the suspend indicator in the case of ThinkPads and the Caps Lock and Scroll Lock indicators in the case of the MSI Wind U100). The pm-suspend and pm-hibernate logs appear normal.

The problem can be fixed by removing the modules before suspension or hibernation and reloading them afterwards. That can be accomplished through a script:

 rmmod vboxdrv
 modprobe vboxdrv
Note: Some users reported that it is sufficient to rebuild the kernel module by running vboxbuild as root.

Hibernate with missing swap partition

If you try to hibernate without an active swap partition, your system will look like it is going into hibernate, and then immediately resume again. There are no error messages warning you that there is no swap partition, even when verbose logging is activated, so this problem can be very hard to debug. On my system, the swap partition was somehow corrupted and deactivated, so this may happen even if you set up a swap partition during install. If hibernate displays this behaviour, make sure that you actually have a swap partition that is being used as such. The output of the blkid command should look e.g. like

# blkid
/dev/sda1: UUID="00000-000-000-0000000" TYPE="ext2" 
/dev/sda2: UUID="00000-000-000-0000000" TYPE="ext4"
/dev/sda3: UUID="00000-000-000-0000000" TYPE="ext4"
/dev/sda4: UUID="00000-000-000-0000000" TYPE="swap"

with one of the lines having "swap" as the type. If this is not the case, consult Swap#Swap partition for instructions on re-creating/activating the swap partition.

Black screen with unblinking cursor when trying to suspend

If you get a black screen with unblinking cursor when trying to do

$ sudo pm-suspend

have a look at /var/log/pm-suspend.log and search for "ehci" or "xhci". Some of the names you could find may be "ehci_hd", "xhci_hd" or "ehci_hcd".

Then as root create the file /etc/pm/config.d/modules and include this code with the exact name of the ehci or xhci module you found. For example:


Suspend should now be working.

Blank screen issue

Some users have reported having issues with their laptops not resuming after a suspend or hibernate. This is due to the autodetect hook in "HOOKS" array of the /etc/mkinitcpio.conf file. This can be disabled using the same method for adding the resume hook. Just remove autodetect from the list and follow the steps to build the new image. See Resume Hook for more details on building the new image.

Note: If you are using plymouth it may be an other reason to this issue. Adding resume before plymouth in "HOOKS" array of the /etc/mkinitcpio.conf file should fix this.

Unable to Resume with 64 bit OS

Certain motherboards/BIOS combinations (specifically known are some Zotac ITX boards, perhaps others) will not resume properly from suspend if any 64 bit operating system is installed. The solution is the enter your BIOS setup and Disable the "Memory Remapping Hole" in your DRAM configuration page. This will probably fix the suspend to RAM problem but will probably result in your OS not detecting all of your RAM.

Tips and Tricks

Having the HD power management level automatically set again on resume

Do it like this:

 if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then
 	hdparm -B 254 /dev/sda > /dev/null

Then run:

$ sudo chmod +x /etc/pm/sleep.d/50-hdparm_pm

If the above Bash script fails the work, the following may work instead:

 case "$1" in
                sleep 6
                hdparm -B 254 /dev/sda
 exit $NA

Lower -B switch values may be effective. See hdparm.

Restarting the mouse

On some laptops the mouse will hang after an otherwise successful suspend. One way to remedy this is to force a re-initialization of the PS/2 driver (here i8042) through a hook in /etc/pm/hooks (see hooks)

echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind

Add sleep modes to Openbox menu

Openbox users can add the new scripts as additional shutdown options within the Openbox menu by adding the items to a new or existing sub-menu in ~/.config/openbox/menu.xml, for example:

<menu id="64" label="Shutdown">
	<item label="Lock"> <action name="Execute"> <execute>xscreensaver-command -lock</execute> </action> </item>
	<item label="Logout"> <action name="Exit"/> </item>
	<item label="Reboot"> <action name="Execute"> <execute>sudo shutdown -r now</execute> </action> </item>
	<item label="Poweroff"> <action name="Execute"> <execute>sudo shutdown -h now </execute> </action> </item>
	<item label="Hibernate"> <action name="Execute"> <execute>sudo pm-hibernate</execute> </action> </item>
	<item label="Suspend"> <action name="Execute"> <execute>sudo pm-suspend</execute> </action> </item>

Handling "sleep" and "power" buttons

"Sleep" and "power" buttons are handled by acpid in /etc/acpi/ (see "button/power" and "power/sleep" entries). You may want to substitute the default actions with calls to pm-suspend and pm-hibernate.

Locking the screen saver on hibernate or suspend

It is a good idea to have the system require a password after waking up. One way to do this is to make a script /etc/pm/sleep.d/00screensaver-lock (making sure it is chmodded to 755 and owned by root:root, like other similar scripts in this area). Replace username with your username and add your desired screen locker in between the "" after su $USER -c.

 # 00screensaver-lock: lock workstation on hibernate or suspend

 DBUS=$(ps aux | grep 'dbus-launch' | grep -v root)
 if [[ ! -z $DBUS ]];then
  USER=$(echo $DBUS | awk '{print $1}')
  USERHOME=$(getent passwd $USER | cut -d: -f6)
  export XAUTHORITY="$USERHOME/.Xauthority"
  for x in /tmp/.X11-unix/*; do
    DISPLAYNUM=$(echo $x | sed s#/tmp/.X11-unix/X##)
    if [[ -f "$XAUTHORITY" ]]; then
            export DISPLAY=":$DISPLAYNUM"
  export XAUTHORITY="$USERHOME/.Xauthority"
  export DISPLAY=":0"

 case "$1" in
       su $USER -c "/usr/bin/slimlock" & # or any other such as /usr/bin/xscreensaver-command -lock
    *) exit $NA

Note: for the previous script to work TTY lock must be disabled in slimlock. Be sure to set tty_lock 0 in /etc/slimlock.conf [1].

For some the above script might not work, use this one instead:

 # 00screensaver-lock: lock workstation on hibernate or suspend

 username= # add your username here, i.e.: username=foobar

 export XAUTHORITY="$USERHOME/.Xauthority"
 export DISPLAY=":0"

  case "$1" in
       su $username -c "/usr/bin/slimlock" & # or any other such as /usr/bin/xscreensaver-command -lock
    *) exit $NA

Other Resources


This wiki entry was originally sourced from the OpenSUSE Wiki (Licensed under GPL). A big thank you goes to the pm-utils developers and documenters for their time.