/[gentoo]/xml/htdocs/doc/en/power-management-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/power-management-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.15 Revision 1.42
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.15 2005/10/28 14:48:06 so Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.42 2010/01/22 15:48:00 nightmorph Exp $ -->
4<guide link="/doc/en/power-management-guide.xml"> 4
5<guide>
5<title>Power Management Guide</title> 6<title>Power Management Guide</title>
6 7
7<author title="Author"> 8<author title="Author">
8 <mail link="fragfred@gmx.de">Dennis Nienhüser</mail> 9 <mail link="earthwings@gentoo.org">Dennis Nienhüser</mail>
10</author>
11<author title="Editor">
12 <mail link="chriswhite@gentoo.org">Chris White</mail>
13</author>
14<author title="Editor">
15 <mail link="nightmorph"/>
9</author> 16</author>
10 17
11<abstract> 18<abstract>
12Power Management is the key to extend battery run time on mobile systems like 19Power Management is the key to extend battery run time on mobile systems like
13laptops. This guide assists you setting it up on your laptop. 20laptops. This guide assists you setting it up on your laptop.
15 22
16<!-- The content of this document is licensed under the CC-BY-SA license --> 23<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 25<license/>
19 26
20<version>1.25</version> 27<version>1.45</version>
21<date>2005-10-02</date> 28<date>2010-01-22</date>
22 29
23<chapter> 30<chapter>
24<title>Introduction</title> 31<title>Introduction</title>
25<section> 32<section>
26<title>Why Power Management?</title>
27<body> 33<body>
28 34
29<p> 35<p>
30Capacity and lifetime of laptop batteries have improved much in the last years. 36Capacity and lifetime of laptop batteries have improved much in the last years.
31Nevertheless modern processors consume much more energy than older ones and 37Nevertheless modern processors consume much more energy than older ones and
35intelligent Power Management policies. 41intelligent Power Management policies.
36</p> 42</p>
37 43
38</body> 44</body>
39</section> 45</section>
40
41<section> 46<section>
42<title>A quick overview</title> 47<title>A Quick Overview</title>
43<body> 48<body>
44 49
45<p> 50<p>
46Please notice that this guide describes Power Management for <e>laptops</e>. 51Please notice that this guide describes Power Management for <e>laptops</e>.
47While some sections might also suite for <e>servers</e>, others do not and may 52While some sections might also suite for <e>servers</e>, others do not and may
53As this guide has become rather long, here's a short overview helping you to 58As this guide has become rather long, here's a short overview helping you to
54find your way through it. 59find your way through it.
55</p> 60</p>
56 61
57<p> 62<p>
58The <e>Prerequisites</e> chapter talks about some requirements that should be 63The <uri link="#doc_chap2">Prerequisites</uri> chapter talks about some
59met before any of the following device individual sections will work. This 64requirements that should be met before any of the following device individual
60includes BIOS settings, kernel configuration and some simplifications in user 65sections will work. This includes BIOS settings, kernel configuration and some
61land. The following three chapters focus on devices that typically consume 66simplifications in user land. The following three chapters focus on devices
62most energy - processor, display and hard drive. Each can be configured 67that typically consume most energy - processor, display and hard drive. Each
63seperately. <e>CPU Power Management</e> shows how to adjust the processor's 68can be configured seperately. <uri link="#doc_chap3">CPU Power Management</uri>
64frequency to save a maximum of energy whithout losing too much performance. A 69shows how to adjust the processor's frequency to save a maximum of energy
65few different tricks prevent your hard drive from working unnecessarily often 70without losing too much performance. A few different tricks prevent your hard
66in <e>Disk Power Management</e> (decreasing noise level as a nice side 71drive from working unnecessarily often in <uri link="#doc_chap5">Disk Power
67effect). Some notes on graphics cards, Wireless LAN and USB finish the device 72Management</uri> (decreasing noise level as a nice side effect). Some notes on
68section in <e>Power Management for other devices</e> while another chapter is 73graphics cards, Wireless LAN and USB finish the device section in <uri
69dedicated to the (rather experimental) <e>sleep states</e>. Last not least 74link="#doc_chap6">Power Management For Other Devices</uri> while another
70<e>Troubleshooting</e> lists common pitfalls. 75chapter is dedicated to the (rather experimental) <uri link="#doc_chap7">sleep
76states</uri>. Last not least <uri link="#doc_chap8">Troubleshooting</uri> lists
77common pitfalls.
71</p> 78</p>
72 79
73</body> 80</body>
74</section>
75
76<section> 81</section>
82<section>
77<title>Power Budget for each component</title> 83<title>Power Budget For Each Component</title>
78<body> 84<body>
79 85
80<figure link="/images/energy-budget.png" short="Which component consumes how 86<figure link="/images/energy-budget.png" short="Which component consumes how
81much energy?" caption="Power budget for each component"/> 87much energy?" caption="Power budget for each component"/>
82 88
93</chapter> 99</chapter>
94 100
95<chapter> 101<chapter>
96<title>Prerequisites</title> 102<title>Prerequisites</title>
97<section> 103<section>
98<title>What has to be done first</title>
99<body>
100
101<p>
102Before going into the details on making individual devices Power Management
103aware, make sure certain requirements are met. After controlling the BIOS
104settings, some kernel options want to be enabled - these are in short ACPI,
105sleep states and CPU frequency scaling. As power saving most of the time comes
106along with performance loss or increased latency, it should only be enabled
107when running on batteries. That's where a new runlevel <e>battery</e> comes in
108handy.
109</p>
110
111</body> 104<body>
112</section> 105
106<p>
107Before discussing the details of making individual devices Power Management
108aware, make sure certain requirements are met. After controlling BIOS settings,
109some kernel options want to be enabled - these are in short ACPI, sleep states
110and CPU frequency scaling. As power saving most of the time comes along with
111performance loss or increased latency, it should only be enabled when running
112on batteries. That's where a new runlevel <e>battery</e> comes in handy.
113</p>
114
115</body>
113<section> 116</section>
117<section>
114<title>The BIOS part</title> 118<title>The BIOS Part</title>
115<body> 119<body>
116 120
117<p> 121<p>
118First have a look into your BIOS Power Management settings. The best way is to 122First have a look into your BIOS Power Management settings. The best way is to
119combine BIOS and operating system policies, but for the moment it's better to 123combine BIOS and operating system policies, but for the moment it's better to
123</p> 127</p>
124 128
125</body> 129</body>
126</section> 130</section>
127<section> 131<section>
132<title>Setting USE Flags</title>
133<body>
134
135<p>
136Please check that the <c>acpi</c> USE flag is set in
137<path>/etc/make.conf</path>. Other USE flags that might be interesting for your
138system are <c>apm</c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>,
139<c>pmu</c>. See <path>/usr/portage/profiles/use*.desc</path> for details. If
140you forgot to set one of these flags, you can recompile affected packages using
141the <c>--newuse</c> flag in <c>emerge</c>, see <c>man emerge</c>.
142</p>
143
144</body>
145</section>
146<section>
128<title>Configuring the kernel</title> 147<title>Configuring The Kernel</title>
129<body> 148<body>
130 149
131<p> 150<p>
132ACPI (Advanced Configuration and Power Interface) support in the kernel is 151ACPI (Advanced Configuration and Power Interface) support in the kernel is
133still work in progress. Using a recent kernel will make sure you'll get the 152still work in progress. Using a recent kernel will make sure you'll get the
134most out of it. 153most out of it.
135</p> 154</p>
136 155
137<p> 156<p>
138There are different kernel sources in Portage. I'd recommend using 157There are different kernel sources in Portage. I'd recommend using
139<c>gentoo-sources</c> or <c>suspend2-sources</c>. The latter contains patches 158<c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches
140for Software Suspend 2, see the chapter about sleep states for details. When 159for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep states</uri>
141configuring the kernel, activate at least these options: 160for more details. When configuring the kernel, activate at least these options:
142</p> 161</p>
143 162
144<pre caption="Minimum kernel setup for Power Management (Kernel 2.6)"> 163<pre caption="Minimum kernel setup for Power Management (Kernel 2.6)">
145Power Management Options ---&gt; 164Power management and ACPI options ---&gt;
146 [*] Power Management Support 165[*] Power Management support
147 [ ] Software Suspend 166 [ ] Software Suspend
148 167
149 ACPI( Advanced Configuration and Power Interface ) Support ---&gt; 168 ACPI( Advanced Configuration and Power Interface ) Support ---&gt;
150 [*] ACPI Support 169 [ ] Deprecated /proc/acpi/ files
151 [ ] Sleep States
152 [ ] /proc/acpi/sleep (deprecated)
153 [*] AC Adapter 170 [*] AC Adapter
154 [*] Battery 171 [*] Battery
155 &lt;M&gt; Button 172 &lt;M&gt; Button
156 &lt;M&gt; Video 173 &lt;M&gt; Video
157 [ ] Generic Hotkey 174 [ ] Generic Hotkey
163 &lt; &gt; Toshiba Laptop Extras 180 &lt; &gt; Toshiba Laptop Extras
164 (0) Disable ACPI for systems before Jan 1st this year 181 (0) Disable ACPI for systems before Jan 1st this year
165 [ ] Debug Statements 182 [ ] Debug Statements
166 [*] Power Management Timer Support 183 [*] Power Management Timer Support
167 &lt; &gt; ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL) 184 &lt; &gt; ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)
168 185
169 CPU Frequency Scaling ---&gt; 186 CPU Frequency Scaling ---&gt;
170 [*] CPU Frequency scaling 187 [*] CPU Frequency scaling
171 [ ] Enable CPUfreq debugging 188 [ ] Enable CPUfreq debugging
172 &lt; &gt; CPU frequency translation statistics 189 &lt; &gt; CPU frequency translation statistics
173 [ ] CPU frequency translation statistics details 190 [ ] CPU frequency translation statistics details
186(see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba laptop, enable 203(see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba laptop, enable
187the appropriate section. 204the appropriate section.
188</p> 205</p>
189 206
190<p> 207<p>
191The kernel has to know how to enable CPU frequency scaling on your processor. As 208The kernel has to know how to enable CPU frequency scaling on your processor.
192each type of CPU has a different interface, you've got to choose the right 209As each type of CPU has a different interface, you've got to choose the right
193driver for your processor. Be careful here - enabling <e>Intel Pentium 4 clock 210driver for your processor. Be careful here - enabling <c>Intel Pentium 4 clock
194modulation</e> on a Pentium M system will lead to strange results for example. 211modulation</c> on a Pentium M system will lead to strange results for example.
195Consult the kernel documentation if you're unsure which one to take. 212Consult the kernel documentation if you're unsure which one to take.
196</p> 213</p>
197 214
198<p> 215<p>
199Compile your kernel, make sure the right modules get loaded at startup and boot 216Compile your kernel, make sure the right modules get loaded at startup and boot
200into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to get 217into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to
201the acpi daemon. This one informs you about events like switching from AC to 218get the acpi daemon. This one informs you about events like switching from AC
202battery or closing the lid. Make sure the modules are loaded if you didn't 219to battery or closing the lid. Make sure the modules are loaded if you didn't
203compile them into the kernel and start acpid by executing 220compile them into the kernel and start acpid by executing <c>/etc/init.d/acpid
204<c>/etc/init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load 221start</c>. Run <c>rc-update add acpid default</c> to load it on startup. You'll
205it on startup. You'll soon see how to use it. 222soon see how to use it.
206</p> 223</p>
207 224
208<pre caption="Installing acpid"> 225<pre caption="Installing acpid">
209# <i>emerge sys-power/acpid</i> 226# <i>emerge sys-power/acpid</i>
210# <i>/etc/init.d/acpid start</i> 227# <i>/etc/init.d/acpid start</i>
212</pre> 229</pre>
213 230
214</body> 231</body>
215</section> 232</section>
216<section> 233<section>
217<title>Creating a "battery" runlevel</title> 234<title>Creating A "battery" Runlevel</title>
218<body> 235<body>
219 236
220<p> 237<p>
221The default policy will be to enable Power Management only when needed - 238The default policy will be to enable Power Management only when needed -
222running on batteries. To make the switch between AC and battery convenient, 239running on batteries. To make the switch between AC and battery convenient,
223create a runlevel <e>battery</e> that holds all the scripts starting and 240create a runlevel <c>battery</c> that holds all the scripts starting and
224stopping Power Management. 241stopping Power Management.
225</p> 242</p>
226 243
227<note> 244<note>
228You can safely skip this section if you don't like the idea of having another 245You can safely skip this section if you don't like the idea of having another
229runlevel. However, skipping this step will make the rest a bit trickier to set 246runlevel. However, skipping this step will make the rest a bit trickier to set
230up. The next sections assume a runlevel <e>battery</e> exists. 247up. The next sections assume a runlevel <c>battery</c> exists.
231</note> 248</note>
232 249
233<pre caption="Creating a battery runlevel"> 250<pre caption="Creating a battery runlevel">
234# <i>cd /etc/runlevels</i> 251# <i>cd /etc/runlevels</i>
235# <i>cp -a default battery</i> 252# <i>cp -a default battery</i>
236</pre> 253</pre>
237 254
238<p> 255<p>
239Finished. Your new runlevel <e>battery</e> contains everything like 256Finished. Your new runlevel <c>battery</c> contains everything like
240<e>default</e>, but there is no automatic switch between both yet. Time to 257<c>default</c>, but there is no automatic switch between both yet. Time to
241change it. 258change it.
242</p> 259</p>
243 260
244</body> 261</body>
245</section> 262</section>
246<section> 263<section>
247<title>Reacting on ACPI events</title> 264<title>Reacting On ACPI Events</title>
248<body> 265<body>
249 266
250<p> 267<p>
251Typical ACPI events are closing the lid, changing the power source or pressing 268Typical ACPI events are closing the lid, changing the power source or pressing
252the sleep button. An important event is changing the power source, which should 269the sleep button. An important event is changing the power source, which should
259<c>on_ac_power</c> command from <c>sys-power/powermgmt-base</c> - make sure the 276<c>on_ac_power</c> command from <c>sys-power/powermgmt-base</c> - make sure the
260package is installed on your system. 277package is installed on your system.
261</p> 278</p>
262 279
263<pre caption="Installing powermgt-base"> 280<pre caption="Installing powermgt-base">
264<i># emerge powermgmt-base</i> 281# <i>emerge powermgmt-base</i>
265</pre> 282</pre>
266 283
267<p> 284<p>
268You are now able to determine the power source by executing 285You are now able to determine the power source by executing <c>on_ac_power
269<c>on_ac_power &amp;&amp; echo AC available || echo Running on batteries</c> in 286&amp;&amp; echo AC available || echo Running on batteries</c> in a shell. The
270a shell. The script below is responsible for changing runlevels. Save it as 287script below is responsible for changing runlevels. Save it as
271<path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>. 288<path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>.
272</p> 289</p>
273 290
274<pre caption="/etc/acpi/actions/pmg_switch_runlevel.sh"> 291<pre caption="/etc/acpi/actions/pmg_switch_runlevel.sh">
275#!/bin/bash 292#!/bin/bash
280<comment># END configuration</comment> 297<comment># END configuration</comment>
281 298
282 299
283if [ ! -d "/etc/runlevels/${RUNLEVEL_AC}" ] 300if [ ! -d "/etc/runlevels/${RUNLEVEL_AC}" ]
284then 301then
285 logger "${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting." 302 logger "${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting."
286 exit 1 303 exit 1
287fi 304fi
288 305
289if [ ! -d "/etc/runlevels/${RUNLEVEL_BATTERY}" ] 306if [ ! -d "/etc/runlevels/${RUNLEVEL_BATTERY}" ]
290then 307then
291 logger "${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting." 308 logger "${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting."
292 exit 1 309 exit 1
293fi 310fi
294 311
295if on_ac_power 312if on_ac_power
296then 313then
297 if [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_AC}" ]] 314 if [[ "$(&lt;/var/lib/init.d/softlevel)" != "${RUNLEVEL_AC}" ]]
298 then 315 then
299 logger "Switching to ${RUNLEVEL_AC} runlevel" 316 logger "Switching to ${RUNLEVEL_AC} runlevel"
300 /sbin/rc ${RUNLEVEL_AC} 317 /sbin/rc ${RUNLEVEL_AC}
301 fi 318 fi
302elif [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_BATTERY}" ]] 319elif [[ "$(&lt;/var/lib/init.d/softlevel)" != "${RUNLEVEL_BATTERY}" ]]
303then 320then
304 logger "Switching to ${RUNLEVEL_BATTERY} runlevel" 321 logger "Switching to ${RUNLEVEL_BATTERY} runlevel"
305 /sbin/rc ${RUNLEVEL_BATTERY} 322 /sbin/rc ${RUNLEVEL_BATTERY}
306fi 323fi
307</pre> 324</pre>
308 325
309<p> 326<p>
310Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> to 327Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> to
311make the script executable. The last thing that needs to be done is calling the 328make the script executable. The last thing that needs to be done is calling the
312script whenever the power source changes. That's done by catching ACPI events 329script whenever the power source changes. That's done by catching ACPI events
313with the help of <c>acpid</c>. First you need to know which events are 330with the help of <c>acpid</c>. First you need to know which events are
314generated when the power source changes. The events are called 331generated when the power source changes. The events are called
315<e>ac_adapter</e> and <e>battery</e> on most laptops, but it might be different 332<c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be different
316on yours. 333on yours.
317</p> 334</p>
318 335
319<pre caption="Determining ACPI events for changing the power source"> 336<pre caption="Determining ACPI events for changing the power source">
320<i># tail -f /var/log/acpid | grep "received event"</i> 337# <i>tail -f /var/log/messages | grep "ACPI event"</i>
321</pre> 338</pre>
322 339
323<p> 340<p>
324Run the command above and pull the power cable. You should see something 341Run the command above and pull the power cable. You should see something like
325like this: 342this:
326</p> 343</p>
327 344
328<pre caption="Sample output for power source changes"> 345<pre caption="Sample output for power source changes">
329[Tue Sep 20 17:39:06 2005] received event "ac_adapter AC 00000080 00000000" 346[Tue Sep 20 17:39:06 2005] ACPI event "ac_adapter AC 00000080 00000000"
330[Tue Sep 20 17:39:06 2005] received event "battery BAT0 00000080 00000001" 347[Tue Sep 20 17:39:06 2005] ACPI event "battery BAT0 00000080 00000001"
331</pre> 348</pre>
332 349
333<p> 350<p>
334The interesting part is the quoted string after <e>received event</e>. It will 351The interesting part is the quoted string after <c>received event</c>. It will
335be matched by the event line in the files you are going to create below. Don't 352be matched by the event line in the files you are going to create below. Don't
336worry if your system generates multiple events or always the same. As long as 353worry if your system generates multiple events or always the same. As long as
337any event is generated, runlevel changing will work. 354any event is generated, runlevel changing will work.
338</p> 355</p>
339 356
354<p> 371<p>
355Finally acpid has to be restarted to recognize the changes. 372Finally acpid has to be restarted to recognize the changes.
356</p> 373</p>
357 374
358<pre caption="Finishing runlevel switching with acpid"> 375<pre caption="Finishing runlevel switching with acpid">
359<i># /etc/init.d/acpid restart</i> 376# <i>/etc/init.d/acpid restart</i>
360</pre> 377</pre>
361 378
362<p> 379<p>
363Give it a try: Plug AC in and out and watch syslog for the "Switching to AC 380Give it a try: Plug AC in and out and watch syslog for the "Switching to AC
364mode" or "Switching to battery mode" messages. See the Troubleshooting 381mode" or "Switching to battery mode" messages. See the <uri
365section if the script is not able to detect the power source correctly. 382link="#doc_chap8">Troubleshooting section</uri> if the script is not able to
383detect the power source correctly.
366</p> 384</p>
367 385
368<p> 386<p>
369Due to the nature of the event mechanism, your laptop will boot into runlevel 387Due to the nature of the event mechanism, your laptop will boot into runlevel
370<e>default</e> regardless of the AC/battery state. This is fine when running 388<c>default</c> regardless of the AC/battery state. This is fine when running
371from AC, but we'd like to boot into the battery runlevel otherwise. One 389from AC, but we'd like to boot into the battery runlevel otherwise. One
372solution would be to add another entry to the boot loader with the parameter 390solution would be to add another entry to the boot loader with the parameter
373<c>softlevel=battery</c>, but it's likely to forget choosing it. A better way 391<c>softlevel=battery</c>, but it's likely to forget choosing it. A better way
374is faking an ACPI event in the end of the boot process and letting 392is faking an ACPI event in the end of the boot process and letting
375<path>pmg_switch_runlevel.sh</path> script decide whether a 393<path>pmg_switch_runlevel.sh</path> script decide whether a runlevel change is
376runlevel change is necessary. Open <path>/etc/conf.d/local.start</path> in your 394necessary. Open <path>/etc/conf.d/local.start</path> in your favourite editor
377favourite editor and add these lines: 395and add these lines:
378</p> 396</p>
379 397
380<pre caption="Runlevel adjustment at boot time by editing local.start"> 398<pre caption="Runlevel adjustment at boot time by editing local.start">
381<comment># Fake acpi event to switch runlevel if running on batteries</comment> 399<comment># Fake acpi event to switch runlevel if running on batteries</comment>
382/etc/acpi/actions/pmg_switch_runlevel.sh "battery/battery" 400/etc/acpi/actions/pmg_switch_runlevel.sh "battery/battery"
383</pre> 401</pre>
384 402
385<p> 403<p>
386Prepared like this you can activate Power Management policies for individual 404Prepared like this you can activate Power Management policies for individual
387devices. 405devices.
388</p> 406</p>
389 407
390</body> 408</body>
391</section> 409</section>
392</chapter> 410</chapter>
393 411
394<chapter> 412<chapter>
395<title>CPU Power Management</title> 413<title>CPU Power Management</title>
396<section> 414<section>
415<body>
416
417<p>
418Mobile processors can operate at different frequencies. Some allow changing
419voltage as well. Most of the time your CPU doesn't need to run at full speed
420and scaling it down will save much energy - often without any performance
421decrease.
422</p>
423
424</body>
425</section>
426<section>
397<title>Some technical terms</title> 427<title>Some Technical Terms</title>
398<body> 428<body>
399 429
400<p> 430<p>
401CPU frequency scaling brings up some technical terms that might be unknown to 431CPU frequency scaling brings up some technical terms that might be unknown to
402you. Here's a quick introduction. 432you. Here's a quick introduction.
403</p> 433</p>
404 434
405<p> 435<p>
406First of all, the kernel has to be able to change the processor's frequency. 436First of all, the kernel has to be able to change the processor's frequency.
407The <e>CPUfreq processor driver</e> knows the commands to do it on your CPU. 437The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU.
408Thus it's important to choose the right one in your kernel. You should 438Thus it's important to choose the right one in your kernel. You should already
409already have done it above. Once the kernel knows how to change frequencies, 439have done it above. Once the kernel knows how to change frequencies, it has to
410it has to know which frequency it should set. This is done according to the 440know which frequency it should set. This is done according to the <b>policy</b>
411<e>policy</e> which consists of a <e>CPUfreq policy</e> and a 441which consists of a <b>CPUfreq policy</b> and a <b>governor</b>. A CPUfreq
412<e>governor</e>. A CPUfreq policy are just two numbers which define a range 442policy are just two numbers which define a range the frequency has to stay
413the frequency has to stay between - minimal and maximal frequency. The 443between - minimal and maximal frequency. The governor now decides which of the
414governor now decides which of the available frequencies in between minimal 444available frequencies in between minimal and maximal frequency to choose. For
415and maximal frequency to choose. For example, the <e>powersave governor</e> 445example, the <b>powersave governor</b> always chooses the lowest frequency
416always chooses the lowest frequency available, the <e>performance 446available, the <b>performance governor</b> the highest one. The <b>userspace
417governor</e> the highest one. The <e>userspace governor</e> makes no decision 447governor</b> makes no decision but chooses whatever the user (or a program in
418but chooses whatever the user (or a program in userspace) wants - which means 448userspace) wants - which means it reads the frequency from
419it reads the frequency from
420<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>. 449<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>.
421</p> 450</p>
422 451
423<p> 452<p>
424This doesn't sound like dynamic frequency changes yet and in fact it isn't. 453This doesn't sound like dynamic frequency changes yet and in fact it isn't.
425Dynamics however can be accomplished with various approaches. For example, 454Dynamics however can be accomplished with various approaches. For example, the
426the <e>ondemand governor</e> makes its decisions depending on the current CPU 455<b>ondemand governor</b> makes its decisions depending on the current CPU load.
427load. The same is done by various userland tools like <c>cpudyn</c>, 456The same is done by various userland tools like <c>cpudyn</c>, <c>cpufreqd</c>,
428<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to 457<c>powernowd</c> and many more. ACPI events can be used to enable or disable
429enable or disable dynamic frequency changes depending on power source. 458dynamic frequency changes depending on power source.
430</p> 459</p>
431 460
432</body> 461</body>
433</section>
434<section> 462</section>
463<section>
435<title>Setting the frequency manually</title> 464<title>Setting The Frequency</title>
436<body> 465<body>
437 466
438<p> 467<p>
439Decreasing CPU speed and voltage has two advantages: On the one hand less 468Decreasing CPU speed and voltage has two advantages: On the one hand less
440energy is consumed, on the other hand there is thermal improvement as your 469energy is consumed, on the other hand there is thermal improvement as your
443between performance loss and energy saving. 472between performance loss and energy saving.
444</p> 473</p>
445 474
446<note> 475<note>
447Not every laptop supports frequency scaling. If unsure, have a look at the list 476Not every laptop supports frequency scaling. If unsure, have a look at the list
448of supported processors in the <e>Troubleshooting</e> section to verify your's 477of supported processors in the <uri link="#doc_chap8">Troubleshooting</uri>
449is supported. 478section to verify yours is supported.
450</note> 479</note>
451 480
452<p> 481<p>
453It's time to test whether CPU frequency changing works. Let's install another 482It's time to test whether CPU frequency changing works. Let's install another
454tool which is very handy for debugging purposes: <c>sys-power/cpufrequtils</c> 483tool: <c>sys-power/cpufrequtils</c>.
455</p> 484</p>
456 485
457<pre caption="Checking CPU frequency"> 486<pre caption="Checking CPU frequency">
458# <i>emerge cpufrequtils</i> 487# <i>emerge cpufrequtils</i>
459# <i>cpufreq-info</i> 488# <i>cpufreq-info</i>
480 509
481<p> 510<p>
482Now play around with <c>cpufreq-set</c> to make sure frequency switching works. 511Now play around with <c>cpufreq-set</c> to make sure frequency switching works.
483Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand 512Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand
484governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as 513governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as
485expected, you might find help in the Troubleshooting section in the end of this 514expected, you might find help in the <uri link="#doc_chap8">Troubleshooting
486guide. 515section</uri> in the end of this guide.
516</p>
517
487</p> 518<p>
519<c>cpufrequtils</c> can operate in an automatic mode (when you use the
520<b>ondemand</b> governor), you can also switch to the <b>userspace</b> governor
521if you want to manually set a specific speed. You can also statically set your
522CPU to its highest or lowest frequency by using the <b>performance</b>
523and <b>powersave</b> governors, respectively.
524</p>
488 525
526<pre caption="Changing CPU speeds">
527<comment>(Set the highest available frequency)</comment>
528# <i>cpufreq-set -g performance</i>
529<comment>(Set the lowest available frequency)</comment>
530# <i>cpufreq-set -g powersave</i>
531<comment>(Set a specific frequency)</comment>
532# <i>cpufreq-set -g userspace</i>
533# <i>cpufreq-set -f 2.00ghz</i>
534</pre>
535
489</body> 536</body>
490</section>
491<section> 537</section>
492<title>Automated frequency adaption</title> 538<section>
539<title>Other CPU Speed Utilities</title>
493<body> 540<body>
494 541
495<p> 542<p>
496The above is quite nice, but not doable in daily life. Better let your system 543While <c>cpufrequtils</c> may be the best all-around program, there are some
497set the appropriate frequency automatically. There are many different 544other choices available in Portage. The following table gives a quick overview
498approaches to do this. The following table gives a quick overview to help you 545of available CPU speed utilities. It's roughly separated in three categories
499decide on one of them. It's roughly seperated in three categories
500<e>kernel</e> for approaches that only need kernel support, <e>daemon</e> for 546<b>kernel</b> for approaches that only need kernel support, <b>daemon</b> for
501programs that run in the background and <e>graphical</e> for programs that 547programs that run in the background and <b>graphical</b> for programs that
502provide a GUI for easy configuration and changes. 548provide a GUI for easy configuration and changes.
503</p> 549</p>
504 550
505<table> 551<table>
506<tr> 552<tr>
530 <ti>Kernel</ti> 576 <ti>Kernel</ti>
531 <ti>CPU load</ti> 577 <ti>CPU load</ti>
532 <ti>N.A.</ti> 578 <ti>N.A.</ti>
533 <ti>N.A.</ti> 579 <ti>N.A.</ti>
534 <ti> 580 <ti>
535 Unlike the ondemand governor, conversative doesn't jump to maximum 581 Unlike the ondemand governor, conversative doesn't jump to maximum
536 frequency when CPU load is high, but increases the frequency step by 582 frequency when CPU load is high, but increases the frequency step by step.
537 step. Further tuning through files in 583 Further tuning through files in
538 <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still 584 <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires
539 requires userland tools (programs, scripts) if governor switching or 585 userland tools (programs, scripts) if governor switching or similar is
540 similar is desired. 586 desired.
541 </ti> 587 </ti>
542</tr> 588</tr>
543<tr> 589<tr>
544 <ti><uri link="http://mnm.uib.es/~gallir/cpudyn/">cpudyn</uri></ti> 590 <ti><uri link="http://mnm.uib.es/~gallir/cpudyn/">cpudyn</uri></ti>
545 <ti>Daemon</ti> 591 <ti>Daemon</ti>
552 </ti> 598 </ti>
553</tr> 599</tr>
554<tr> 600<tr>
555 <ti><uri link="http://sourceforge.net/projects/cpufreqd/">cpufreqd</uri></ti> 601 <ti><uri link="http://sourceforge.net/projects/cpufreqd/">cpufreqd</uri></ti>
556 <ti>Daemon</ti> 602 <ti>Daemon</ti>
557 <ti>Battery state, CPU load, temperature, running programs</ti> 603 <ti>Battery state, CPU load, temperature, running programs and more</ti>
558 <ti>All available</ti> 604 <ti>All available</ti>
559 <ti>None</ti> 605 <ti>None</ti>
560 <ti> 606 <ti>
561 Sophisticated (but also complicated) setup. 607 Sophisticated (but somewhat complicated) setup. Extendible through plugins
608 like sensor monitoring (lm_sensors) or coordinating some NVidia based
609 graphics card memory and core. Cpufreqd is SMP aware and can optionally be
610 controlled manually at runtime.
562 </ti> 611 </ti>
563</tr> 612</tr>
564<tr> 613<tr>
565 <ti> 614 <ti>
566 <uri link="http://www.deater.net/john/powernowd.html">powernowd</uri> 615 <uri link="http://www.deater.net/john/powernowd.html">powernowd</uri>
573 Supports SMP. 622 Supports SMP.
574 </ti> 623 </ti>
575</tr> 624</tr>
576<tr> 625<tr>
577 <ti> 626 <ti>
578 <uri link="http://fatcat.ftj.agh.edu.pl/~nelchael/index.php?cat=projs&amp;subcat=ncpufreqd&amp;language=en">ncpufreqd</uri> 627 <uri
628 link="http://projects.simpledesigns.com.pl/project/ncpufreqd/">ncpufreqd</uri>
579 </ti> 629 </ti>
580 <ti>Daemon</ti> 630 <ti>Daemon</ti>
581 <ti>Temperature</ti> 631 <ti>Temperature</ti>
582 <ti>None</ti> 632 <ti>None</ti>
583 <ti>Powersave, performance</ti> 633 <ti>Powersave, performance</ti>
623 673
624<p> 674<p>
625While adjusting the frequency to the current load looks simple at a first 675While adjusting the frequency to the current load looks simple at a first
626glance, it's not such a trivial task. A bad algorithm can cause switching 676glance, it's not such a trivial task. A bad algorithm can cause switching
627between two frequencies all the time or wasting energy when setting frequency 677between two frequencies all the time or wasting energy when setting frequency
628to an unnecessary high level. 678to an unnecessary high level.
629</p> 679</p>
630 680
631<p> 681<p>
632Which one to choose? If you have no idea about it, try <c>cpufreqd</c>: 682Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:
633</p> 683</p>
637</pre> 687</pre>
638 688
639<p> 689<p>
640<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>. 690<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>.
641The default one that ships with cpufreqd may look a bit confusing. I recommend 691The default one that ships with cpufreqd may look a bit confusing. I recommend
642replacing it with the one from Gentoo developer Henrik Brix Andersen (see 692replacing it with the one from former Gentoo developer Henrik Brix Andersen
643below). 693(see below). Please notice that you need cpufreqd-2.0.0 or later. Earlier
694versions have a different syntax for the config file.
644</p> 695</p>
645 696
646<pre caption="/etc/cpufreqd.conf"> 697<pre caption="/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)">
647[General] 698[General]
648pidfile=/var/run/cpufreqd.pid 699pidfile=/var/run/cpufreqd.pid
649poll_interval=2 700poll_interval=3
650pm_type=acpi 701enable_plugins=acpi_ac, acpi_battery
702enable_remote=1
703remote_group=wheel
651verbosity=5 704verbosity=5
705[/General]
652 706
653[Profile] 707[Profile]
654name=ondemand 708name=ondemand
655minfreq=0% 709minfreq=0%
656maxfreq=100% 710maxfreq=100%
657policy=ondemand 711policy=ondemand
712[/Profile]
658 713
659[Profile] 714[Profile]
660name=conservative 715name=conservative
661minfreq=0% 716minfreq=0%
662maxfreq=100% 717maxfreq=100%
663policy=conservative 718policy=conservative
719[/Profile]
664 720
665[Profile] 721[Profile]
666name=powersave 722name=powersave
667minfreq=0% 723minfreq=0%
668maxfreq=100% 724maxfreq=100%
669policy=powersave 725policy=powersave
726[/Profile]
670 727
671[Profile] 728[Profile]
672name=performance 729name=performance
673minfreq=0% 730minfreq=0%
674maxfreq=100% 731maxfreq=100%
675policy=performance 732policy=performance
733[/Profile]
676 734
677[Rule] 735[Rule]
678name=battery 736name=battery
679ac=off 737ac=off
680profile=conservative 738profile=conservative
739[/Rule]
681 740
682[Rule] 741[Rule]
683name=battery_low 742name=battery_low
684ac=off 743ac=off
685battery_interval=0-10 744battery_interval=0-10
686profile=powersave 745profile=powersave
746[/Rule]
687 747
688[Rule] 748[Rule]
689name=ac 749name=ac
690ac=on 750ac=on
691profile=ondemand 751profile=ondemand
752[/Rule]
692</pre> 753</pre>
693 754
694<p> 755<p>
695Now you can start the cpufreqd daemon. Add it to the <e>default</e> and 756Now you can start the cpufreqd daemon. Add it to the <c>default</c> and
696<e>battery</e> runlevel as well. 757<c>battery</c> runlevel as well.
697</p> 758</p>
698 759
699<pre caption="Starting cpufreqd"> 760<pre caption="Starting cpufreqd">
700# <i>rc-update add cpufreqd default battery</i> 761# <i>rc-update add cpufreqd default battery</i>
701# <i>rc</i> 762# <i>/etc/init.d/cpufreqd start</i>
763</pre>
764
765<p>
766Sometimes it can be desirable to select another policy than the daemon chooses,
767for example when battery power is low, but you know that AC will be available
768soon. In that case you can turn on cpufreqd's manual mode with <c>cpufreqd-set
769manual</c> and select one of your configured policies (as listed by
770<c>cpufreqd-get</c>). You can leave manual mode by executing <c>cpufreqd-set
771dynamic</c>.
702</pre> 772</p>
703 773
704<warn> 774<warn>
705Do not run more than one of the above programs at the same time. It may cause 775Do not run more than one of the above programs at the same time. It may cause
706confusion like switching between two frequencies all the time. 776confusion like switching between two frequencies all the time.
707</warn> 777</warn>
708 778
709</body> 779</body>
710</section> 780</section>
711
712<section> 781<section>
713<title>Verifying the result</title> 782<title>Verifying the result</title>
714
715<body> 783<body>
716 784
717<p> 785<p>
718The last thing to check is that your new policies do a good job. An easy way to 786The last thing to check is that your new policies do a good job. An easy way to
719do so is monitoring CPU speed while working with your laptop: 787do so is monitoring CPU speed while working with your laptop:
722<pre caption="Monitoring CPU speed"> 790<pre caption="Monitoring CPU speed">
723# <i>watch grep \"cpu MHz\" /proc/cpuinfo</i> 791# <i>watch grep \"cpu MHz\" /proc/cpuinfo</i>
724</pre> 792</pre>
725 793
726<p> 794<p>
727If <path>/proc/cpuinfo</path> doesn't get updated (see Troubleshooting), 795If <path>/proc/cpuinfo</path> doesn't get updated (see <uri
728monitor the CPU frequency with: 796link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with
797<c>sys-apps/x86info</c>:
729</p> 798</p>
730 799
731<pre caption="Alternative CPU speed monitoring"> 800<pre caption="Alternative CPU speed monitoring">
732# <i>watch x86info -mhz</i> 801# <i>watch x86info -mhz</i>
733</pre> 802</pre>
734 803
735<p> 804<p>
736Depending on your setup, CPU speed should increase on heavy load, decrease on 805Depending on your setup, CPU speed should increase on heavy load, decrease on
737no activity or just stay at the same level. When using cpufreqd and verbosity 806no activity or just stay at the same level. When using <c>cpufreqd</c> and
738set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional 807verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get
739information about what's happening reported to syslog. 808additional information about what's happening reported to <c>syslog</c>.
740</p> 809</p>
741 810
742</body> 811</body>
743</section> 812</section>
744</chapter> 813</chapter>
745 814
746<chapter> 815<chapter>
747<title>LCD Power Management</title> 816<title>LCD Power Management</title>
748<section> 817<section>
749<title>Energy consumer no. 1</title>
750<body> 818<body>
751 819
752<p> 820<p>
753As you can see in <uri link="#doc_chap1_fig1">figure 1.1</uri>, the LCD display 821As you can see in <uri link="#doc_chap1_fig1">figure 1.1</uri>, the LCD
754consumes the biggest part of energy (might not be the case for non-mobile 822display consumes the biggest part of energy (might not be the case for
755CPU's). Thus it's quite important not only to shut the display off when not 823non-mobile CPU's). Thus it's quite important not only to shut the display off
756needed, but also to reduce it's backlight if possible. Most laptops offer the 824when not needed, but also to reduce it's backlight if possible. Most laptops
757possibility to control the backlight dimming. 825offer the possibility to control the backlight dimming.
758</p>
759
760<p> 826</p>
827
828</body>
829</section>
830<section>
831<title>Standby settings</title>
832<body>
833
834<p>
761First thing to check is the standby/suspend/off timings of the display. As this 835The first thing to check is the standby/suspend/off timings of the display. As
762depends heavily on your windowmanager, I'll let you figure it out yourself. 836this depends heavily on your windowmanager, I'll let you figure it out
763Just two common places: Blanking the terminal can be done with <c>setterm 837yourself. Just two common places: Blanking the terminal can be done with
764-blank &lt;number-of-minutesM&gt;</c>, <c>setterm -powersave on</c> and 838<c>setterm -blank &lt;number-of-minutesM&gt;</c>, <c>setterm -powersave on</c>
765<c>setterm -powerdown &lt;number-of-minutesM&gt;</c>. 839and <c>setterm -powerdown &lt;number-of-minutesM&gt;</c>. For X.org, modify
766For X.org, modify <path>/etc/X11/xorg.conf</path> similar to this: 840<path>/etc/X11/xorg.conf</path> similar to this:
767</p> 841</p>
768 842
769<pre caption="LCD suspend settings in X.org and XFree86"> 843<pre caption="LCD suspend settings in X.org">
770Section "ServerLayout" 844Section "ServerFlags"
771 Identifier [...]
772 [...]
773 Option "BlankTime" "5" <comment># Blank the screen after 5 minutes (Fake)</comment> 845 Option "blank time" "5" <comment># Blank the screen after 5 minutes (Fake)</comment>
774 Option "StandbyTime" "10" <comment># Turn off screen after 10 minutes (DPMS)</comment> 846 Option "standby time" "10" <comment># Turn off screen after 10 minutes (DPMS)</comment>
775 Option "SuspendTime" "20" <comment># Full suspend after 20 minutes</comment> 847 Option "suspend time" "20" <comment># Full suspend after 20 minutes</comment>
776 Option "OffTime" "30" <comment># Turn off after half an hour</comment> 848 Option "off time" "30" <comment># Turn off after half an hour</comment>
777 [...] 849 [...]
778EndSection 850EndSection
779 851
780[...] 852[...]
781 853
782Section "Monitor" 854Section "Monitor"
783 Identifier [...] 855 Identifier [...]
784 Option "DPMS" "true" 856 Option "DPMS"
785 [...] 857 [...]
786EndSection 858EndSection
787</pre> 859</pre>
788 860
789<p> 861</body>
790This is the same for XFree86 and <path>/etc/X11/XF86Config</path>. 862</section>
791</p> 863<section>
864<title>Backlight dimming</title>
865<body>
792 866
793<p> 867<p>
794Probably more important is the backlight dimming. If you have access to the 868Probably more important is the backlight dimming. If you have access to the
795dimming settings via a tool, write a small script that dims the backlight in 869dimming settings via a tool, write a small script that dims the backlight in
796battery mode and place it in your <e>battery</e> runlevel. The following script 870battery mode and place it in your <c>battery</c> runlevel. The following script
797should work on most IBM Thinkpads. It needs the <c>app-laptop/ibm-acpi</c> 871should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
798package or the appropriate option in your kernel has to be enabled. 872appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops,
873install <c>sys-power/acpitool</c> and skip configuration of <c>thinkpad_acpi</c>
874(formerly called <c>ibm_acpi</c>) as described below.
799</p> 875</p>
800 876
801<warn> 877<warn>
802Support for setting brightness is marked experimental in ibm-acpi. It accesses 878Support for setting brightness is marked experimental in thinkpad_acpi. It
803hardware directly and may cause severe harm to your system. Please read the 879accesses hardware directly and may cause severe harm to your system. Please
804<uri link="http://ibm-acpi.sourceforge.net/">ibm-acpi website</uri> 880read the <uri link="http://ibm-acpi.sourceforge.net/">thinkpad_acpi
881website</uri>
805</warn> 882</warn>
806 883
807<p> 884<p>
808To be able to set the brightness level, the ibm_acpi module has to be loaded 885To be able to set the brightness level, the thinkpad_acpi module has to be
809with the experimental parameter. 886loaded with the experimental parameter.
810</p> 887</p>
811 888
812<pre caption="automatically loading the ibm_acpi module"> 889<pre caption="automatically loading the thinkpad_acpi module">
813<comment>(Please read the warnings above before doing this!)</comment> 890<comment>(Please read the warnings above before doing this!)</comment>
814<i># emerge ibm-acpi</i>
815<i># echo "options ibm_acpi experimental=1" >> /etc/modules.d/ibm_acpi</i> 891# <i>echo "options thinkpad_acpi experimental=1" >> /etc/modprobe.d/thinkpad_acpi</i>
816<i># /sbin/modules-update</i> 892# <i>update-modules</i>
817<i># echo ibm_acpi >> /etc/modules.autoload.d/kernel-2.6</i> 893# <i>echo thinkpad_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
818<i># modprobe ibm_acpi</i> 894# <i>modprobe thinkpad_acpi</i>
819</pre> 895</pre>
820 896
821<p> 897<p>
822This should work without error messages and a file 898This should work without error messages and a file
823<path>/proc/acpi/ibm/brightness</path> should be created after loading the 899<path>/proc/acpi/ibm/brightness</path> should be created after loading the
824module. An init script will take care of choosing the brightness according 900module. An init script will take care of choosing the brightness according to
825to the power source. 901the power source.
826</p> 902</p>
827 903
828<pre caption="/etc/conf.d/lcd-brightness"> 904<pre caption="/etc/conf.d/lcd-brightness">
829<comment># See /proc/acpi/ibm/brightness for available values</comment> 905<comment># See /proc/acpi/ibm/brightness for available values</comment>
830<comment># Please read /usr/share/doc/ibm-acpi-*/README.gz</comment> 906<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>
831 907
832<comment># brigthness level in ac mode. Default is 7.</comment> 908<comment># brightness level in ac mode. Default is 7.</comment>
833BRIGHTNESS_AC=7 909BRIGHTNESS_AC=7
834 910
835<comment># brightness level in battery mode. Default is 4.</comment> 911<comment># brightness level in battery mode. Default is 4.</comment>
836BRIGHTNESS_BATTERY=4 912BRIGHTNESS_BATTERY=4
837</pre> 913</pre>
850 if [ -f /proc/acpi/ibm/brightness ] 926 if [ -f /proc/acpi/ibm/brightness ]
851 then 927 then
852 ebegin "Setting LCD brightness" 928 ebegin "Setting LCD brightness"
853 echo "level ${LEVEL}" > /proc/acpi/ibm/brightness 929 echo "level ${LEVEL}" > /proc/acpi/ibm/brightness
854 eend $? 930 eend $?
931 elif [[ -e /usr/bin/acpitool &amp;&amp; -n $(acpitool -T | grep "LCD brightness") ]]
932 then
933 ebegin "Setting LCD brightness"
934 acpitool -l $LEVEL >/dev/null || ewarn "Unable to set lcd brightness"
935 eend $?
855 else 936 else
856 ewarn "Setting LCD brightness is not supported." 937 ewarn "Setting LCD brightness is not supported."
857 ewarn "Check that ibm_acpi is loaded into the kernel" 938 ewarn "For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel"
939 ewarn "For Toshiba laptops, you've got to install sys-power/acpitool"
858 fi 940 fi
859} 941}
860 942
861start() { 943start() {
862 set_brightness 944 set_brightness
871When done, make sure brightness is adjusted automatically by adding it to the 953When done, make sure brightness is adjusted automatically by adding it to the
872battery runlevel. 954battery runlevel.
873</p> 955</p>
874 956
875<pre caption="Enabling automatic brightness adjustment"> 957<pre caption="Enabling automatic brightness adjustment">
876<i># chmod +x /etc/init.d/lcd-brightness</i> 958# <i>chmod +x /etc/init.d/lcd-brightness</i>
877<i># rc-update add lcd-brightness battery</i> 959# <i>rc-update add lcd-brightness battery</i>
878<i># rc</i> 960# <i>rc</i>
879</pre> 961</pre>
880 962
881</body> 963</body>
882</section> 964</section>
883</chapter> 965</chapter>
884 966
885<chapter> 967<chapter>
886<title>Disk Power Management</title> 968<title>Disk Power Management</title>
887<section> 969<section>
888<title>Sleep when idle</title> 970<body>
971
972<p>
973Hard disks consume less energy in sleep mode. Therefore it makes sense to
974activate power saving features whenever the hard disk is not used for a certain
975amount of time. I'll show you two alternative possibilities to do it. First,
976laptop-mode will save most energy due to several measures which prevent or at
977least delay write accesses. The drawback is that due to the delayed write
978accesses a power outage or kernel crash will be more dangerous for data loss.
979If you don't like this, you have to make sure that there are no processes which
980write to your hard disk frequently. Afterwards you can enable power saving
981features of your hard disk with <c>hdparm</c> as the second alternative.
982</p>
983
889<body> 984</body>
985</section>
986<section>
987<title>Increasing idle time - laptop-mode</title>
988<body>
890 989
891<p>
892Let's bring the hard disk to sleep as early as possible whenever it is not
893needed. I'll show you two possibilities to do it. First <c>cpudyn</c> supports
894Disk Power Management. Uncomment the lines in the "Disk Options" section in
895<path>/etc/conf.d/cpudyn</path>. To put your first disk to sleep after 60
896seconds of no activity, you would modify it like this:
897</p> 990<p>
898 991Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated,
899<pre caption="Using cpudyn for disk standby"> 992dirty buffers are written to disk on read calls or after 10 minutes (instead of
900<comment>################################################ 99330 seconds). This minimizes the time the hard disk needs to be spun up.
901# DISK OPTIONS
902# (disabled by default)
903################################################
904
905#
906# Timeout to put the disk in standby mode if there was no
907# io during that period (in seconds)
908#
909</comment>
910TIMEOUT=60
911<comment>
912#
913# Specified disks to spindown (comma separated devices)
914#
915</comment>
916DISKS=/dev/hda
917</pre>
918
919<p> 994</p>
920The second possibility is using a small script and hdparm. Create 995
921<path>/etc/init.d/pm.hda</path> like this: 996<pre caption="Automated start of laptop-mode">
997# <i>emerge laptop-mode-tools</i>
998</pre>
999
922</p> 1000<p>
1001<c>laptop-mode-tools</c> has its configuration file in
1002<path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it,
1003it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it
1004automatically.
1005</p>
923 1006
1007<p>
1008Recent versions (1.11 and later) of laptop-mode-tools include a new tool
1009<c>lm-profiler</c>. It will monitor your system's disk usage and running
1010network services and suggests to disable unneeded ones. You can either disable
1011them through laptop-mode-tools builtin runlevel support (which will be reverted
1012by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/<c>battery</c>
1013runlevels (recommended).
1014</p>
1015
1016<pre caption="Sample output from running lm-profiler">
1017# <i>lm-profiler</i>
1018Profiling session started.
1019Time remaining: 600 seconds
1020[4296896.602000] amarokapp
1021Time remaining: 599 seconds
1022[4296897.714000] sort
1023[4296897.970000] mv
1024Time remaining: 598 seconds
1025Time remaining: 597 seconds
1026[4296900.482000] reiserfs/0
1027</pre>
1028
1029<p>
1030After profiling your system for ten minutes, lm-profiler will present a list of
1031services which might have caused disk accesses during that time.
1032</p>
1033
1034<pre caption="lm-profiler suggests to disable some services">
1035Program: "atd"
1036Reason: standard recommendation (program may not be running)
1037Init script: /etc/init.d/atd (GUESSED)
1038
1039Do you want to disable this service in battery mode? [y/N]: <i>n</i>
1040</pre>
1041
1042<p>
1043To disable atd as suggested in the example above, you would run <c>rc-update
1044del atd battery</c>. Be careful not to disable services that are needed for
1045your system to run properly - <c>lm-profiler</c> is likely to generate some
1046false positives. Do not disable a service if you are unsure whether it's
1047needed.
1048</p>
1049
1050</body>
1051</section>
1052<section>
1053<title>Limiting Write Accesses</title>
1054<body>
1055
1056<p>
1057If you don't want to use laptop-mode, you must take special care to disable
1058services that write to your disk frequently - <c>syslogd</c> is a good
1059candidate, for example. You probably don't want to shut it down completely, but
1060it's possible to modify the config file so that "unnecessary" things don't get
1061logged and thus don't create disk traffic. <c>Cups</c> writes to disk
1062periodically, so consider shutting it down and only enable it manually when
1063needed.
1064</p>
1065
1066<pre caption="Disabling cups in battery mode">
1067# <i>rc-update del cupsd battery</i>
1068</pre>
1069
1070<p>
1071You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to find
1072services to disable. Once you eliminated all of them, go on with configuring
1073hdparm.
1074</p>
1075
1076</body>
1077</section>
1078<section>
1079<title>hdparm</title>
1080<body>
1081
1082<p>
1083The second possibility is using <c>hdparm</c>. Skip this if
1084you are using laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and
1085add the following values to your drive entries. This example assumes your hard
1086drive is called <b>hda</b>:
1087</p>
1088
924<pre caption="Using hdparm for disk standby"> 1089<pre caption="Using /etc/conf.d/hdparm for disk standby">
925#!/sbin/runscript 1090hda_args="-q -S12"
926
927depend() {
928 after hdparm
929}
930
931start() {
932 ebegin "Activating Power Management for Hard Drives"
933 hdparm -q -S12 /dev/hda
934 eend $?
935}
936
937stop () {
938 ebegin "Deactivating Power Management for Hard Drives"
939 hdparm -q -S253 /dev/hda
940 eend $?
941}
942</pre> 1091</pre>
943 1092
1093<p>
1094This will activate power management for your hard drive. If you ever want to
1095deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> and
1096change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/hda</c>.
944<p> 1097</p>
945See <c>man hdparm</c> for the options. If your script is ready, add it to the 1098
946battery runlevel. 1099<p>
1100See <c>man hdparm</c> for the options. Though you can always start <c>hdparm</c>
1101manually when you are on battery power by running <c>/etc/init.d/hdparm
1102start</c>, it's much easier to automate its startup and shutdown. To do so, add
1103<c>hdparm</c> to the battery runlevel so that it will automatically enable power
1104management.
947</p> 1105</p>
948 1106
949<pre caption="Automate disk standby settings"> 1107<pre caption="Automate disk standby settings">
950# <i>chmod +x /etc/init.d/pm.hda</i>
951# <i>/sbin/depscan.sh</i>
952# <i>rc-update add pm.hda battery</i> 1108# <i>rc-update add hdparm battery</i>
953</pre> 1109</pre>
954 1110
955<impo> 1111<impo>
956Be careful with sleep/spin down settings of your hard drive. Setting it to 1112Be careful with sleep/spin down settings of your hard drive. Setting it to
957small values might wear out your drive and lose warranty. 1113small values might wear out your drive and lose warranty.
958</impo> 1114</impo>
959 1115
960</body> 1116</body>
961</section> 1117</section>
962<section> 1118<section>
963<title>Increasing idle time - laptop-mode</title>
964<body>
965
966<p>
967Recent kernels (2.6.6 and greater, recent 2.4 ones and others with patches)
968include the so-called <e>laptop-mode</e>. When activated, dirty buffers are
969written to disk on read calls or after 10 minutes (instead of 30 seconds). This
970minimizes the time the hard disk needs to be spun up.
971</p>
972
973<pre caption="Automated start of laptop-mode">
974# <i>emerge laptop-mode-tools</i>
975</pre>
976
977<p>
978<c>laptop-mode-tools</c> has it's configuration file in
979<path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it,
980it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it
981automatically.
982</p>
983
984</body>
985</section>
986<section>
987<title>Other tricks</title> 1119<title>Other tricks</title>
988<body> 1120<body>
989
990<p>
991Besides putting your disk to sleep state as early as possible, it is a good
992idea to minimize disk accesses. Have a look at processes that write to your
993disk frequently - the syslogd is a good candidate. You probably don't want to
994shut it down completely, but it's possible to modify the config file so that
995"unnecessary" things don't get logged and thus don't create disk traffic. Cups
996writes to disk periodically, so consider shutting it down and only enable it
997manually when needed.
998</p>
999
1000<pre caption="Disabling cups in battery mode">
1001# <i>rc-update del cupsd battery</i>
1002</pre>
1003 1121
1004<p> 1122<p>
1005Another possibility is to deactivate swap in battery mode. Before writing a 1123Another possibility is to deactivate swap in battery mode. Before writing a
1006swapon/swapoff switcher, make sure there is enough RAM and swap isn't used 1124swapon/swapoff switcher, make sure there is enough RAM and swap isn't used
1007heavily, otherwise you'll be in big problems. 1125heavily, otherwise you'll be in big problems.
1008</p> 1126</p>
1009 1127
1010<p> 1128<p>
1011If you don't want to use laptop-mode, it's still possible to minimize disk 1129If you don't want to use laptop-mode, it's still possible to minimize disk
1012access by mounting certain directories as <e>tmpfs</e> - write accesses are not 1130access by mounting certain directories as <c>tmpfs</c> - write accesses are not
1013stored on a disk, but in main memory and get lost with unmounting. Often it's 1131stored on a disk, but in main memory and get lost with unmounting. Often it's
1014useful to mount <path>/tmp</path> like this - you don't have to pay special 1132useful to mount <path>/tmp</path> like this - you don't have to pay special
1015attention as it gets cleared on every reboot regardless whether it was mounted 1133attention as it gets cleared on every reboot regardless whether it was mounted
1016on disk or in RAM. Just make sure you have enough RAM and no program (like a 1134on disk or in RAM. Just make sure you have enough RAM and no program (like a
1017download client or compress utility) needs extraordinary much space in 1135download client or compress utility) needs extraordinary much space in
1023none /tmp tmpfs size=32m 0 0 1141none /tmp tmpfs size=32m 0 0
1024</pre> 1142</pre>
1025 1143
1026<warn> 1144<warn>
1027Pay attention to the size parameter and modify it for your system. If you're 1145Pay attention to the size parameter and modify it for your system. If you're
1028unsure, don't try this at all, it can become a perfomance bottleneck easily. In 1146unsure, don't try this at all, it can become a performance bottleneck easily. In
1029case you want to mount <path>/var/log</path> like this, make sure to merge the 1147case you want to mount <path>/var/log</path> like this, make sure to merge the
1030log files to disk before unmounting. They are essential. Don't attempt to mount 1148log files to disk before unmounting. They are essential. Don't attempt to mount
1031/var/tmp like this. Portage uses it for compiling... 1149<path>/var/tmp</path> like this. Portage uses it for compiling...
1032</warn> 1150</warn>
1033 1151
1034</body> 1152</body>
1035</section> 1153</section>
1036</chapter> 1154</chapter>
1037 1155
1038<chapter> 1156<chapter>
1039<title>Power Management for other devices</title> 1157<title>Power Management For Other Devices</title>
1040<section> 1158<section>
1041<title>Graphics cards</title> 1159<title>Graphics Cards</title>
1042<body> 1160<body>
1043 1161
1044<p> 1162<p>
1045In case you own an ATI graphics card supporting PowerPlay (dynamic clock 1163In case you own an ATI graphics card supporting PowerPlay (dynamic clock
1046scaling for the the graphics processing unit GPU), you can activate this 1164scaling for the graphics processing unit GPU), you can activate this
1047feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) 1165feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the
1048the <c>DynamicClocks</c> option in the Device section. Please notice that 1166<c>DynamicClocks</c> option in the Device section. Please notice that this
1049this feature will lead to crashes on some systems. 1167feature will lead to crashes on some systems.
1050</p> 1168</p>
1051 1169
1052<pre caption="Enabling ATI PowerPlay support in X.org"> 1170<pre caption="Enabling ATI PowerPlay support in X.org">
1053Section "Device" 1171Section "Device"
1054[...] 1172[...]
1061<section> 1179<section>
1062<title>Wireless Power Management</title> 1180<title>Wireless Power Management</title>
1063<body> 1181<body>
1064 1182
1065<p> 1183<p>
1066Wireless LAN cards consume quite a few energy. Put them in Power Management 1184Wireless LAN cards consume quite a bit of energy. Put them in Power Management
1067mode in analogy to the pm.hda script. 1185mode just like your hard drives.
1068</p>
1069
1070<pre caption="WLAN Power Management automated">
1071#!/sbin/runscript
1072start() {
1073 ebegin "Activating Power Management for Wireless LAN"
1074 iwconfig wlan0 power on power max period 3
1075 eend $?
1076}
1077
1078stop () {
1079 ebegin "Deactivating Power Management for Wireless LAN"
1080 iwconfig wlan0 power off
1081 eend $?
1082}
1083</pre>
1084
1085<p> 1186</p>
1086Starting this script will put wlan0 in Power Management mode, going to sleep at 1187
1087the latest three seconds after no traffic. 1188<note>
1088Save it as <path>/etc/init.d/pm.wlan0</path> and add it to the battery runlevel 1189This script assumes your wireless interface is called <c>wlan0</c>; replace
1089like the disk script above. See <c>man iwconfig</c> for details and more 1190this with the actual name of your interface.
1090options. If your driver and access point support changing the beacon time, this 1191</note>
1091is a good starting point to save even more energy. 1192
1092</p> 1193<p>
1093 1194Add the following option to <path>/etc/conf.d/net</path> to automatically enable
1094<pre caption="Power Management for WLAN"> 1195power management for your wireless card:
1095# <i>chmod +x /etc/init.d/pm.wlan0</i>
1096# <i>/sbin/depscan.sh</i>
1097# <i>rc-update add pm.wlan0 battery</i>
1098</pre> 1196</p>
1197
1198<pre caption="Automated WLAN Power Management">
1199iwconfig_wlan0="power on"
1200</pre>
1201
1202<p>
1203See <c>man iwconfig</c> for details and more options like the period between
1204wakeups or timeout settings. If your driver and access point support changing
1205the beacon time, this is a good starting point to save even more energy.
1206</p>
1099 1207
1100</body> 1208</body>
1101</section> 1209</section>
1102<section> 1210<section>
1103<title>USB Power Management</title> 1211<title>USB Power Management</title>
1107There are two problems with USB devices regarding energy consumption: First, 1215There are two problems with USB devices regarding energy consumption: First,
1108devices like USB mice, digital cameras or USB sticks consume energy while 1216devices like USB mice, digital cameras or USB sticks consume energy while
1109plugged in. You cannot avoid this (nevertheless remove them in case they're not 1217plugged in. You cannot avoid this (nevertheless remove them in case they're not
1110needed). Second, when there are USB devices plugged in, the USB host controller 1218needed). Second, when there are USB devices plugged in, the USB host controller
1111periodically accesses the bus which in turn prevents the CPU from going into 1219periodically accesses the bus which in turn prevents the CPU from going into
1112sleep mode. The kernel offers an experimental option to enable suspension of 1220sleep mode. The kernel offers an experimental option to enable suspension of
1113USB devices through driver calls or one of the <path>power/state</path> files 1221USB devices through driver calls or one of the <path>power/state</path> files
1114in <path>/sys</path>. 1222in <path>/sys</path>.
1115</p> 1223</p>
1116 1224
1117<pre caption="Enabling USB suspend support in the kernel"> 1225<pre caption="Enabling USB suspend support in the kernel">
1124</body> 1232</body>
1125</section> 1233</section>
1126</chapter> 1234</chapter>
1127 1235
1128<chapter> 1236<chapter>
1129<title>Sleep states: sleep, standby, suspend to disk</title> 1237<title>Sleep States: sleep, standby, and suspend to disk</title>
1130<section> 1238<section>
1131<title>Overview</title>
1132<body> 1239<body>
1133 1240
1134<p> 1241<p>
1135ACPI defines different sleep states. The more important ones are 1242ACPI defines different sleep states. The more important ones are
1136</p> 1243</p>
1137 1244
1138<ul> 1245<ul>
1139 <li>S1 aka Standby</li> 1246 <li>S1 aka Standby</li>
1140 <li>S3 aka Suspend to RAM aka Sleep</li> 1247 <li>S3 aka Suspend to RAM aka Sleep</li>
1141 <li>S4 aka Suspend to Disk aka Hibernate</li> 1248 <li>S4 aka Suspend to Disk aka Hibernate</li>
1142</ul> 1249</ul>
1143 1250
1159</p> 1266</p>
1160 1267
1161<pre caption="Kernel configuration for the various suspend types"> 1268<pre caption="Kernel configuration for the various suspend types">
1162 Power Management Options ---&gt; 1269 Power Management Options ---&gt;
1163 [*] Power Management support 1270 [*] Power Management support
1164 ACPI (Advanced Configuration and Power Interface) Support ---&gt; 1271 [*] Suspend to RAM and standby
1165 [*] ACPI Support
1166 [*] Sleep States
1167</pre> 1272</pre>
1168 1273
1169<p> 1274<p>
1170Once your kernel is prepared like above, you can use the 1275Once your kernel is properly configured, you can use the
1171<c>hibernate-script</c> to activate suspend or sleep mode. Let's install that 1276<c>hibernate-script</c> to activate suspend or sleep mode. Let's install that
1172first. 1277first.
1173</p> 1278</p>
1174 1279
1175<pre caption="Installing the hibernate-script"> 1280<pre caption="Installing the hibernate-script">
1176<i># emerge hibernate-script</i> 1281# <i>emerge hibernate-script</i>
1177</pre> 1282</pre>
1178 1283
1179<p> 1284<p>
1180Some configuration has to be done in <path>/etc/hibernate</path> The default 1285Some configuration has to be done in <path>/etc/hibernate</path>. The default
1181package introduces two configuration files <path>hibernate.conf</path> and 1286package introduces a few configuration files for each sleep state. Options that
1182<path>ram.conf</path>. 1287are common to all suspend methods are placed in <path>common.conf</path>; make
1183</p> 1288sure this file is properly set up for your system.
1184
1185<p> 1289</p>
1186To configure sleep, edit <path>ram.conf</path> in <path>/etc/hibernate</path>. 1290
1187<c>UseSysfsPowerState mem</c> is already setup correctly, but you have to go
1188through the rest of the configuration file and set it up for your system. The
1189comments and option names will guide you. If you use nfs or samba shares over
1190the network, make sure to shutdown the appropriate init scripts to avoid
1191timeouts.
1192</p> 1291<p>
1292To configure sleep, edit <path>sysfs-ram.conf</path> in
1293<path>/etc/hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup
1294correctly, but if you need to make further changes to this particular sleep
1295state (or any other sleep state) you should add them to
1296<path>/etc/hibernate/hibernate.conf</path>. The comments and option names will
1297guide you. If you use nfs or samba shares over the network, make sure to
1298shutdown the appropriate init scripts to avoid timeouts.
1299</p>
1300
1301<note>
1302For more information on setting up sleep states, read <c>man
1303hibernate.conf</c>.
1304</note>
1193 1305
1194<p> 1306<p>
1195Ready? Now is the last chance to backup any data you want to keep after 1307Ready? Now is the last chance to backup any data you want to keep after
1196executing the next command. Notice that you probably have to hit a special key 1308executing the next command. Notice that you probably have to hit a special key
1197like <e>Fn</e> to resume from sleep. 1309like <c>Fn</c> to resume from sleep.
1198</p> 1310</p>
1199 1311
1200<pre caption="Calling sleep"> 1312<pre caption="Calling sleep">
1201<i># hibernate-ram</i> 1313# <i>hibernate-ram</i>
1202</pre> 1314</pre>
1203 1315
1204<p> 1316<p>
1205If you're still reading, it seems to work. You can also setup standby (S1) in 1317If you're still reading, it seems to work. You can also setup standby (S1) in a
1206a similar way by copying <path>ram.conf</path> to <path>standby.conf</path> 1318similar way by editing <path>sysfs-ram.conf</path> and changing
1207and creating a symlink <path>/usr/sbin/hibernate-standby</path> pointing to 1319"UseSysfsPowerState mem" to "UseSysfsPowerState standby". S3 and S4 are the more
1208<path>/usr/sbin/hibernate</path>. S3 and S4 are the more interesting sleep
1209states due to greater energy savings however. 1320interesting sleep states due to greater energy savings however.
1210</p> 1321</p>
1211 1322
1212</body> 1323</body>
1213</section> 1324</section>
1214<section> 1325<section>
1227Shutdown any NFS or samba server/client before hibernating. 1338Shutdown any NFS or samba server/client before hibernating.
1228</warn> 1339</warn>
1229 1340
1230<p> 1341<p>
1231There are two different implementations for S4. The original one is swsusp, 1342There are two different implementations for S4. The original one is swsusp,
1232then there is the newer suspend2 with a nicer interface (including 1343then there is the newer tuxonice (formerly suspend2) with a nicer interface
1233fbsplash support). A <uri link="http://suspend2.net/features.html#compare"> 1344(including fbsplash support). A <uri
1234feature comparison</uri> is available at the <uri link="http://suspend2.net"> 1345link="http://tuxonice.net/features.html#compare">feature comparison</uri> is
1235suspend2 Homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of 1346available at the <uri link="http://www.tuxonice.net">tuxonice homepage</uri>.
1236swsusp, but it has been merged back. 1347There used to be Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been
1237</p> 1348merged back.
1238
1239<p> 1349</p>
1350
1351<p>
1240Suspend2 is not included in the mainline kernel yet, therefore you either have 1352TuxOnIce is not included in the mainline kernel yet, therefore you either have
1241to patch your kernel sources with the patches provided by 1353to patch your kernel sources with the patches provided by <uri
1242<uri link="http://suspend2.net">suspend2.net</uri> or use 1354link="http://www.tuxonice.net">tuxonice.net</uri> or use
1243<c>sys-kernel/suspend2-sources</c>. 1355<c>sys-kernel/tuxonice-sources</c>.
1244</p>
1245
1246<p> 1356</p>
1357
1358<p>
1247The kernel part for both swusp and suspend2 is as follows: 1359The kernel part for both swusp and TuxOnIce is as follows:
1248</p> 1360</p>
1249 1361
1250<pre caption="Kernel configuration for the various suspend types"> 1362<pre caption="Kernel configuration for the various suspend types">
1251Power Management Options ---&gt; 1363Power Management support ---&gt;
1252 <comment>(hibernate with swsusp)</comment> 1364 <comment>(hibernate with swsusp)</comment>
1253 [*] Software Suspend 1365 [*] Hibernation (aka 'suspend to disk')
1254 <comment>(replace /dev/SWAP with your swap partition)</comment> 1366 <comment>(replace /dev/SWAP with your swap partition)</comment>
1255 (/dev/SWAP) Default resume partition 1367 (/dev/SWAP) Default resume partition
1256 1368
1257 <comment>(hibernate with suspend2)</comment> 1369 <comment>(hibernate with TuxOnIce)</comment>
1258 Software Suspend 2 1370 Enhanced Hibernation (TuxOnIce)
1259 --- Image Storage (you need at least one writer) 1371 --- Image Storage (you need at least one allocator)
1260 [*] File Writer 1372 [*] File Allocator
1261 [*] Swap Writer 1373 [*] Swap Allocator
1262 --- General Options 1374 --- General Options
1263 [*] LZF image compression 1375 [*] Compression support
1264 <comment>(replace /dev/SWAP with your swap partition)</comment>
1265 (swap:/dev/SWAP) Default resume device name
1266 [ ] Allow Keep Image Mode 1376 [ ] Allow Keep Image Mode
1377 [*] Replace swsusp by default
1267</pre> 1378</pre>
1268 1379
1269<p> 1380<p>
1270The configuration for swsusp is rather easy. If you didn't store the location 1381The configuration for swsusp is rather easy. If you didn't store the location
1271of your swap partition in the kernel config, you can also pass it as a 1382of your swap partition in the kernel config, you can also pass it as a
1272parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not 1383parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not
1273possible due to a broken image, use the <c>noresume</c> kernel parameter. The 1384possible due to a broken image, use the <c>noresume</c> kernel parameter. The
1274<c>hibernate-cleanup</c> init script invalidates swsusp images during the 1385<c>hibernate-cleanup</c> init script invalidates swsusp images during the boot
1275boot process. 1386process.
1276</p> 1387</p>
1277 1388
1278<pre caption="Invalidating swsusp images during the boot process"> 1389<pre caption="Invalidating swsusp images during the boot process">
1279<i># rc-update add hibernate-cleanup boot</i> 1390# <i>rc-update add hibernate-cleanup boot</i>
1280</pre> 1391</pre>
1281 1392
1282<p> 1393<p>
1283To activate hibernate with swsusp, use the hibernate script and set 1394To activate hibernate with swsusp, use the hibernate script and set
1284<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/hibernate.conf</path>. 1395<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>.
1285</p> 1396</p>
1286 1397
1287<warn> 1398<warn>
1288Backup your data before doing this. Run <c>sync</c> before executing one of the 1399Backup your data before doing this. Run <c>sync</c> before executing one of the
1289commands to have cached data written to disk. First try it outside of X, then 1400commands to have cached data written to disk. First try it outside of X, then
1290with X running, but not logged in. 1401with X running, but not logged in.
1291</warn> 1402</warn>
1292 1403
1293<p> 1404<p>
1294If you experience kernel panics due to uhci or similar, try to compile USB 1405If you experience kernel panics due to uhci or similar, try to compile USB
1295support as module and unload the modules before sending your laptop to sleep 1406support as module and unload the modules before sending your laptop to sleep
1296mode. There are configuration options for this in <path>hibernate.conf</path> 1407mode. There are configuration options for this in <path>common.conf</path>
1297</p> 1408</p>
1298 1409
1299<pre caption="Hibernating with swsusp"> 1410<pre caption="Hibernating with swsusp">
1300<i># nano -w /etc/hibernate.conf</i> 1411# <i>nano -w /etc/hibernate/common.conf</i>
1301<comment>(Make sure you have a backup of your data)</comment> 1412<comment>(Make sure you have a backup of your data)</comment>
1302<i># hibernate</i> 1413# <i>hibernate</i>
1303</pre> 1414</pre>
1304 1415
1305<p> 1416<p>
1306The following section discusses the setup of suspend2 including fbsplash 1417The following section discusses the setup of TuxOnIce including fbsplash support
1307support for a nice graphical progress bar during suspend and resume. 1418for a nice graphical progress bar during suspend and resume.
1308</p>
1309
1310<p> 1419</p>
1420
1421<p>
1311The first part of the configuration is similar to the configuration of 1422The first part of the configuration is similar to the configuration of swsusp.
1312swsusp. In case you didn't store the location of your swap partition in the 1423In case you didn't store the location of your swap partition in the kernel
1313kernel config, you have to pass it as a kernel parameter with the 1424config, you have to pass it as a kernel parameter with the
1314<c>resume2=swap:/dev/SWAP</c> directive. If booting is not possible due to a 1425<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a
1315broken image, append the <c>noresume2</c> parameter. Additionally, the 1426broken image, append the <c>noresume</c> parameter. Additionally, the
1316<c>hibernate-cleanup</c> init script invalidates suspend2 images during the 1427<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the boot
1317boot process. 1428process.
1318</p> 1429</p>
1319 1430
1320<pre caption="Invalidating suspend2 images during the boot process"> 1431<pre caption="Invalidating TuxOnIce images during the boot process">
1321<i># rc-update add hibernate-cleanup boot</i> 1432# <i>rc-update add hibernate-cleanup boot</i>
1322</pre> 1433</pre>
1323 1434
1324<p>Now edit <path>/etc/hibernate/hibernate.conf</path>, enable the
1325<e>suspend2</e> section and comment everything in the <e>sysfs_power_state</e>
1326and <e>acpi_sleep</e> sections. Do not enable the fbsplash part in global
1327options yet.
1328</p> 1435<p>
1436Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</c>
1437options you need. Do not enable the <c>fbsplash</c> options in
1438<c>common.conf</c> just yet.
1439</p>
1329 1440
1330<pre caption="Hibernating with suspend2"> 1441<pre caption="Hibernating with TuxOnIce">
1331<i># nano -w /etc/hibernate.conf</i> 1442# <i>nano -w /etc/hibernate/tuxonice.conf</i>
1332<comment>(Make sure you have a backup of your data)</comment> 1443<comment>(Make sure you have a backup of your data)</comment>
1333<i># hibernate</i> 1444# <i>hibernate</i>
1334</pre> 1445</pre>
1335 1446
1336<p> 1447<p>
1337Please configure fbsplash now if you didn't do already. To enable fbsplash 1448Please configure <c>fbsplash</c> now if you didn't do already. To enable
1338support during hibernation, the <c>sys-apps/suspend2-userui</c> package is 1449fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> package
1339needed. Additionally, you've got to enable the <e>fbsplash</e> USE flag. 1450is needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag.
1340</p> 1451</p>
1341 1452
1342<pre caption="Installing suspend2-userui"> 1453<pre caption="Installing tuxonice-userui">
1343<i># mkdir -p /etc/portage</i>
1344<i># echo sys-apps/suspend2-userui fbsplash >> /etc/portage/package.use</i> 1454# <i>echo "sys-apps/tuxonice-userui fbsplash" >> /etc/portage/package.use</i>
1345<i># emerge suspend2-userui</i> 1455<comment>(It may be marked ~arch, so first it must be keyworded)</comment>
1456# <i>echo "sys-apps/tuxonice-userui" >> /etc/portage/package.keywords</i>
1457# <i>emerge tuxonice-userui</i>
1346</pre> 1458</pre>
1347 1459
1348<p> 1460<p>
1349The ebuild tells you to make a symlink to the theme you want to use. For 1461The ebuild tells you to make a symlink to the theme you want to use. For
1350example, to use the <c>livecd-2005.1</c> theme, run the following command: 1462example, to use the <c>livecd-2005.1</c> theme, run the following command:
1351</p> 1463</p>
1352 1464
1353<pre caption="Using the livecd-2005.1 theme during hibernation"> 1465<pre caption="Using the livecd-2005.1 theme during hibernation">
1354<i># ln -sfn /etc/splash/livecd-2005.1 /etc/splash/suspend2</i> 1466# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>
1355</pre> 1467</pre>
1356 1468
1357<p> 1469<p>
1358If you don't want a black screen in the first part of the resume process, you 1470If you don't want a black screen in the first part of the resume process, you
1359have to add the <c>suspend2ui_fbsplash</c> tool to your initrd image. Assuming 1471have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. Assuming
1360you created the initrd image with <c>splash_geninitramfs</c> and saved it as 1472you created the initrd image with <c>splash_geninitramfs</c> and saved it as
1361<path>/boot/fbsplash-emergence-1024x768</path>, here's how to do 1473<path>/boot/fbsplash-emergence-1024x768</path>, here's how to do that.
1362that.
1363</p> 1474</p>
1364 1475
1365<pre caption="Adding suspend2ui_fbsplash to an initrd image"> 1476<pre caption="Adding tuxoniceui_fbsplash to an initrd image">
1366<i># mount /boot</i> 1477# <i>mount /boot</i>
1367<i># mkdir ~/initrd.d</i> 1478# <i>mkdir ~/initrd.d</i>
1368<i># cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i> 1479# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>
1369<i># cd ~/initrd.d</i> 1480# <i>cd ~/initrd.d</i>
1370<i># gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i> 1481# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>
1371<i># rm fbsplash-emergence-1024x768</i> 1482# <i>rm fbsplash-emergence-1024x768</i>
1372<i># cp /usr/sbin/suspend2ui_fbsplash sbin/</i> 1483# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>
1373<i># find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-suspend2-emergence-1024x768</i> 1484# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-tuxonice-emergence-1024x768</i>
1374</pre> 1485</pre>
1375 1486
1376<p> 1487<p>
1377Afterwards adjust <path>grub.conf</path> respectively <path>lilo.conf</path> 1488Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that
1378so that your suspend2 kernel uses 1489your TuxOnIce kernel uses
1379<path>/boot/fbsplash-suspend2-emergence-1024x768</path> as initrd image. You 1490<path>/boot/fbsplash-tuxonice-emergence-1024x768</path> as initrd image. You can
1380can now test a dry run to see if everything is setup correctly. 1491now test a dry run to see if everything is setup correctly.
1381</p> 1492</p>
1382 1493
1383<pre caption="Test run for fbsplash hibernation"> 1494<pre caption="Test run for fbsplash hibernation">
1384<i># suspend2ui_fbsplash -t</i> 1495# <i>tuxoniceui_fbsplash -t</i>
1385</pre> 1496</pre>
1386 1497
1387<p> 1498<p>
1388Afterwards open <path>/etc/hibernate/hibernate.conf</path> again and activate 1499Afterwards open <path>/etc/hibernate/common.conf</path> and activate the
1389the fbsplash options. Execute <c>hibernate</c> and enjoy. 1500fbsplash options. Execute <c>hibernate</c> and enjoy.
1390</p> 1501</p>
1391 1502
1392</body> 1503</body>
1393</section> 1504</section>
1394</chapter> 1505</chapter>
1395 1506
1396<chapter> 1507<chapter>
1397<title>Troubleshooting</title> 1508<title>Troubleshooting</title>
1398<section> 1509<section>
1399<title>If things go wrong...</title>
1400<body> 1510<body>
1401 1511
1402<p> 1512<p>
1403<e>Q:</e> I'm trying to change the CPU frequency, but 1513<e>Q:</e> I'm trying to change the CPU frequency, but
1404<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor</path> does not 1514<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor</path> does not
1406</p> 1516</p>
1407 1517
1408<p> 1518<p>
1409<e>A:</e> Make sure your processor supports CPU frequency scaling and you chose 1519<e>A:</e> Make sure your processor supports CPU frequency scaling and you chose
1410the right CPUFreq driver for your processor. Here is a list of processors that 1520the right CPUFreq driver for your processor. Here is a list of processors that
1411are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, 1521are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, ARM-SA1110,
1412ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD 1522AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD mobile Duron,
1413mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, 1523AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, Intel mobile
1414Intel mobile PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, 1524PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, Intel Xeon,
1415Intel Xeon, Intel Pentium M (Centrino), National Semiconductors Geode GX, 1525Intel Pentium M (Centrino), National Semiconductors Geode GX, Transmeta Crusoe,
1416Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several 1526VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several "PowerBook" and
1417"PowerBook" and "iBook2" and various processors on some ACPI 2.0-compatible 1527"iBook2" and various processors on some ACPI 2.0-compatible systems (only if
1418systems (only if "ACPI Processor Performance States" are available to the 1528"ACPI Processor Performance States" are available to the ACPI/BIOS interface).
1419ACPI/BIOS interface).
1420</p> 1529</p>
1421 1530
1422<p> 1531<p>
1423<e>Q:</e> My laptop supports frequency scaling, but 1532<e>Q:</e> My laptop supports frequency scaling, but
1424<path>/sys/devices/system/cpu/cpu0/cpufreq/</path> is empty. 1533<path>/sys/devices/system/cpu/cpu0/cpufreq/</path> is empty.
1429Try to update the BIOS, especially if a broken DSDT is reported. You can also 1538Try to update the BIOS, especially if a broken DSDT is reported. You can also
1430try to fix it yourself (which is beyond the scope of this guide). 1539try to fix it yourself (which is beyond the scope of this guide).
1431</p> 1540</p>
1432 1541
1433<p> 1542<p>
1434<e>Q:</e> My laptop supports frequency scaling, but according to /proc/cpuinfo 1543<e>Q:</e> My laptop supports frequency scaling, but according to
1435the speed never changes. 1544<path>/proc/cpuinfo</path> the speed never changes.
1436</p> 1545</p>
1437 1546
1438<p> 1547<p>
1439<e>A:</e> Probably you have activated symmetric multiprocessing support 1548<e>A:</e> Probably you have activated symmetric multiprocessing support
1440(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older 1549(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older
1441kernels had a bug causing this. In that case, run <c>emerge x86info</c>, 1550kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update
1442update your kernel as asked and check the current frequency with 1551your kernel as asked and check the current frequency with <c>x86info -mhz</c>.
1443<c>x86info -mhz</c>.
1444</p> 1552</p>
1445 1553
1446<p> 1554<p>
1447<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in 1555<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in
1448another OS. 1556another OS.
1449</p> 1557</p>
1450 1558
1451<p> 1559<p>
1452<e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower 1560<e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower
1453minimum frequency. Notice that throttling doesn't save much energy and is 1561minimum frequency. Notice that throttling doesn't save much energy and is mainly
1454mainly used for thermal management (keeping your laptop cool and quiet). You 1562used for thermal management (keeping your laptop cool and quiet). You can read
1455can read the current throttling state with <c>cat 1563the current throttling state with <c>cat /proc/acpi/processor/CPU/throttling</c>
1456/proc/acpi/processor/CPU/throttling</c> and change it with <c>echo -n "0:x" > 1564and change it with <c>echo -n "0:x" > /proc/acpi/processor/CPU/limit</c>, where
1457/proc/acpi/processor/CPU/limit</c>, where x is one of the Tx states listed in 1565x is one of the Tx states listed in
1458<path>/proc/acpi/processor/CPU/throttling</path>. 1566<path>/proc/acpi/processor/CPU/throttling</path>.
1459</p> 1567</p>
1460 1568
1461<p> 1569<p>
1462<e>Q:</e> When configuring the kernel, powersave, performance and userspace 1570<e>Q:</e> When configuring the kernel, powersave, performance and userspace
1486<e>A:</e> Check that battery support is compiled into your kernel. If you use 1594<e>A:</e> Check that battery support is compiled into your kernel. If you use
1487it as a module, make sure the module is loaded. 1595it as a module, make sure the module is loaded.
1488</p> 1596</p>
1489 1597
1490<p> 1598<p>
1599<e>Q:</e> My system logger reports things like "logger: ACPI group battery /
1600action battery is not defined".
1601</p>
1602
1603<p>
1604<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path>
1605script that is shipped with acpid. You can safely ignore it. If you like to get
1606rid of it, you can comment the appropriate line in
1607<path>/etc/acpi/default.sh</path> as shown below:
1608</p>
1609
1610<pre caption="Disabling warnings about unknown acpi events">
1611 *) # logger "ACPI action $action is not defined"
1612</pre>
1613
1614<p>
1491<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events. 1615<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events.
1492</p> 1616</p>
1493 1617
1494<p> 1618<p>
1495<e>A:</e> This seems to be a kernel bug. Read on <uri 1619<e>A:</e> This seems to be a kernel bug. Read on <uri
1496link="http://bugme.osdl.org/show_bug.cgi?id=1752">here</uri>. 1620link="http://bugme.osdl.org/show_bug.cgi?id=1752">here</uri>.
1497</p> 1621</p>
1498 1622
1499<p> 1623<p>
1500<e>Q:</e> I activated the DynamicClocks option in <path>xorg.conf</path> and 1624<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path>
1501now X.org crashes / the screen stays black / my laptop doesn't shutdown 1625and now X.org crashes / the screen stays black / my laptop doesn't shutdown
1502properly. 1626properly.
1503</p> 1627</p>
1504 1628
1505<p> 1629<p>
1506<e>A:</e> This happens on some systems. You have to disable DynamicClocks. 1630<e>A:</e> This happens on some systems. You have to disable
1507</p> 1631<c>DynamicClocks</c>.
1508
1509<p> 1632</p>
1633
1634<p>
1510<e>Q:</e> I want to use suspend2, but it tells me my swap partition is too 1635<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too
1511small. Resizing is not an option. 1636small. Resizing is not an option.
1512</p> 1637</p>
1513 1638
1514<p> 1639<p>
1515<e>A:</e> If there is enough free space on your system, you can use the 1640<e>A:</e> If there is enough free space on your system, you can use the
1516filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it 1641filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it as
1517as well. More information can be found in 1642well. More information can be found in
1518<path>/usr/src/linux/Documentation/power/suspend2.txt</path>. 1643<path>/usr/src/linux/Documentation/power/tuxonice.txt</path>.
1519</p> 1644</p>
1520 1645
1521<p> 1646<p>
1522<e>Q:</e> I just bought a brand new battery, but it only lasts for some 1647<e>Q:</e> I just bought a brand new battery, but it only lasts for some
1523minutes! What am I doing wrong? 1648minutes! What am I doing wrong?
1524</p> 1649</p>
1525 1650
1526<p> 1651<p>
1527<e>A:</e> First follow your manufacturer's advice on how to charge the battery 1652<e>A:</e> First follow your manufacturer's advice on how to charge the battery
1528correctly. 1653correctly.
1529</p> 1654</p>
1530 1655
1531<p> 1656<p>
1532<e>Q:</e> The above didn't help. What should I do then? 1657<e>Q:</e> The above didn't help. What should I do then?
1533</p> 1658</p>
1550<p> 1675<p>
1551<e>Q:</e> My problem is not listed above. Where should I go next? 1676<e>Q:</e> My problem is not listed above. Where should I go next?
1552</p> 1677</p>
1553 1678
1554<p> 1679<p>
1555<e>A:</e> Don't fear to contact me, <mail link="fragfred@gmx.de">Dennis 1680<e>A:</e> Don't fear to contact me, <mail link="earthwings@gentoo.org">Dennis
1556Nienhüser</mail>, directly. 1681Nienhüser</mail>, directly. The <uri link="http://forums.gentoo.org">Gentoo
1682Forums</uri> are a good place to get help as well. If you prefer IRC, try the
1683<c>#gentoo-laptop</c> <uri link="irc://irc.gentoo.org">channel</uri>.
1557</p> 1684</p>
1558 1685
1559</body> 1686</body>
1560</section> 1687</section>
1561</chapter> 1688</chapter>

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.42

  ViewVC Help
Powered by ViewVC 1.1.20