1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
=== pm-utils ===
What is pm-utils?
* Pm-utils provides simple shell command line tools to suspend and
hibernate computer that can be used to run vendor, distribution, or
user supplied scripts on suspend and resume.
Why do we need it?
* All the main distributions are re-implementing the same
functionality to support common power management
operations. pm-utils provides a standardized distribution agnostic
layout and interface for common power management tasks, which frees
software and hardware vendors from having to maintain
distribution-specific suspend/resume functionality.
* Suspend/resume functionality can be easily modified by installing
files into the /etc/pm/sleep.d directory. These files, known as
"hooks" can perform specific tasks on suspend/resume, such as:
- enabling and disabling standby LED's on laptop hardware
- enabling suspend GUI's like suspend2
- re-enabling video
- starting and stopping services that can't cope with suspending
- re-syncing the time with ntp
- removing and modprobing modules when needed
- setting grub to be the default target for a hibernate-resume
- other wacky things that need doing on specific systems
How do "hooks" work?
* You put an executable file in /etc/pm/sleep.d. When suspend or
hibernate is called, several things happen:
1) The files in /etc/pm/config.d/* are evaluated in C sort order.
These files can be provided by individual packages outside of
pm-utils, and contain globally available configuration settings
for pm-utils and the hooks.
2) Each of the hooks in /etc/pm/sleep.d/* are executed in C sort
order, with a command line argument of either "suspend" or "hibernate".
3) The system suspends or hibernates.
4) Some event happens to wake the machine up
5) Each of /etc/pm/sleep.d/* are executed in reverse C sort order,
with a command line argument of "resume" or "thaw".
End-user customization and debugging:
* If a particular hook is causing problems on your system, you can disable it
using the HOOK_BLACKLIST environment variable by creating a file in
/etc/pm/config.d and adding the line:
HOOK_BLACKLIST="hookname 99another-hook"
* If a parameter (or lack thereof) passed to pm-suspend and friends is causing
problems, or you need to debug the suspend/resume process to work out what
quirks are causing problems, you can use the ADD_PARAMETERS and
DROP_PARAMETERS environment variables. To do this, create a file in
/etc/pm/config.d, and add the following lines to it:
ADD_PARAMETERS="--parameter-to-add --another-parameter"
DROP_PARAMETERS="--parameter-to-drop --another-parameter-to-drop"
If you want to drop all parameters (for testing purposes, or to work around
bugs in HAL), you can use DROP_PARAMETERS="all"
* If you suspect that a kernel module is preventing you from being
able to suspend and resume, you can use the SUSPEND_MODULES
environment variable to have that module removed when the system
suspends and reloaded when the system wakes up.
* To find out what parameters can be passed to pm-suspend and friends, run them
with '--help' as the first parameter as root. This will print out the
options that it supports and which hooks or modules handle those options.
That's it!
|
