* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2005-10-28 14:48 Stefano Rossi
0 siblings, 0 replies; 20+ messages in thread
From: Stefano Rossi @ 2005-10-28 14:48 UTC (permalink / raw
To: gentoo-doc-cvs
so 05/10/28 14:48:06
Modified: xml/htdocs/doc/en power-management-guide.xml
Log:
#106878 update for this guide
Revision Changes Path
1.15 +409 -157 xml/htdocs/doc/en/power-management-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.15&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.15&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml.diff?r1=1.14&r2=1.15&cvsroot=gentoo
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- power-management-guide.xml 10 Jun 2005 18:45:21 -0000 1.14
+++ power-management-guide.xml 28 Oct 2005 14:48:06 -0000 1.15
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.14 2005/06/10 18:45:21 swift Exp $ -->
-<guide link="power-management-guide.xml">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.15 2005/10/28 14:48:06 so Exp $ -->
+<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
<author title="Author">
@@ -14,11 +14,11 @@
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.24</version>
-<date>2005-06-10</date>
+<version>1.25</version>
+<date>2005-10-02</date>
<chapter>
<title>Introduction</title>
@@ -27,7 +27,7 @@
<body>
<p>
-Capacity and lifetime of laptop batteries has improved much in the last years.
+Capacity and lifetime of laptop batteries have improved much in the last years.
Nevertheless modern processors consume much more energy than older ones and
each laptop generation introduces more devices hungry for energy. That's why
Power Management is more important than ever. Increasing battery run time
@@ -58,16 +58,16 @@
The <e>Prerequisites</e> chapter talks about some requirements that should be
met before any of the following device individual sections will work. This
includes BIOS settings, kernel configuration and some simplifications in user
-land. The following three chapters focus on devices that typically consume most
-energy - processor, display and hard drive. Each can be configured seperately.
-<e>CPU Power Management</e> shows how to adjust the processor's frequency to
-save a maximum of energy whithout losing too much performance. A few different
-tricks prevent your hard drive from working unnecessarily often in <e>Disk Power
-Management</e> (decreasing noise level as a nice side effect). Some notes on
-Wireless LAN and USB finish the device section in <e>Power Management for other
-devices</e> while another chapter is dedicated to the (rather experimental)
-<e>sleep states</e>. Last not least <e>Troubleshooting</e> lists common
-pitfalls.
+land. The following three chapters focus on devices that typically consume
+most energy - processor, display and hard drive. Each can be configured
+seperately. <e>CPU Power Management</e> shows how to adjust the processor's
+frequency to save a maximum of energy whithout losing too much performance. A
+few different tricks prevent your hard drive from working unnecessarily often
+in <e>Disk Power Management</e> (decreasing noise level as a nice side
+effect). Some notes on graphics cards, Wireless LAN and USB finish the device
+section in <e>Power Management for other devices</e> while another chapter is
+dedicated to the (rather experimental) <e>sleep states</e>. Last not least
+<e>Troubleshooting</e> lists common pitfalls.
</p>
</body>
@@ -135,42 +135,55 @@
</p>
<p>
-In kernel config, activate at least these options:
+There are different kernel sources in Portage. I'd recommend using
+<c>gentoo-sources</c> or <c>suspend2-sources</c>. The latter contains patches
+for Software Suspend 2, see the chapter about sleep states for details. When
+configuring the kernel, activate at least these options:
</p>
<pre caption="Minimum kernel setup for Power Management (Kernel 2.6)">
Power Management Options --->
[*] Power Management Support
[ ] Software Suspend
- [ ] Suspend-to-Disk Support
ACPI( Advanced Configuration and Power Interface ) Support --->
[*] ACPI Support
[ ] Sleep States
+ [ ] /proc/acpi/sleep (deprecated)
[*] AC Adapter
[*] Battery
<M> Button
+ <M> Video
+ [ ] Generic Hotkey
<M> Fan
<M> Processor
<M> Thermal Zone
< > ASUS/Medion Laptop Extras
+ < > IBM ThinkPad Laptop Extras
< > Toshiba Laptop Extras
+ (0) Disable ACPI for systems before Jan 1st this year
[ ] Debug Statements
+ [*] Power Management Timer Support
+ < > ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)
CPU Frequency Scaling --->
[*] CPU Frequency scaling
+ [ ] Enable CPUfreq debugging
+ < > CPU frequency translation statistics
+ [ ] CPU frequency translation statistics details
Default CPUFreq governor (userspace)
<*> 'performance' governor
<*> 'powersave' governor
<*> 'ondemand' cpufreq policy governor
+ <*> 'conservative' cpufreq governor
<*> CPU frequency table helpers
<M> ACPI Processor P-States driver
<*> <i>CPUFreq driver for your processor</i>
</pre>
<p>
-Decide yourself whether you want to enable Software Suspend, Suspend-to-Disk and
-Sleep States (see below). If you own an ASUS, Medion or Toshiba laptop, enable
+Decide yourself whether you want to enable Software Suspend, and Sleep States
+(see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba laptop, enable
the appropriate section.
</p>
@@ -237,8 +250,25 @@
<p>
Typical ACPI events are closing the lid, changing the power source or pressing
the sleep button. An important event is changing the power source, which should
-cause a runlevel switch. Create the following files to switch between
-<e>default</e> and <e>battery</e> runlevel depending on the power source:
+cause a runlevel switch. A small script will take care of it.
+</p>
+
+<p>
+First you need a script which changes the runlevel to <c>default</c>
+respectively <c>battery</c> depending on the power source. The script uses the
+<c>on_ac_power</c> command from <c>sys-power/powermgmt-base</c> - make sure the
+package is installed on your system.
+</p>
+
+<pre caption="Installing powermgt-base">
+<i># emerge powermgmt-base</i>
+</pre>
+
+<p>
+You are now able to determine the power source by executing
+<c>on_ac_power && echo AC available || echo Running on batteries</c> in
+a shell. The script below is responsible for changing runlevels. Save it as
+<path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>.
</p>
<pre caption="/etc/acpi/actions/pmg_switch_runlevel.sh">
@@ -276,29 +306,56 @@
fi
</pre>
+<p>
+Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> to
+make the script executable. The last thing that needs to be done is calling the
+script whenever the power source changes. That's done by catching ACPI events
+with the help of <c>acpid</c>. First you need to know which events are
+generated when the power source changes. The events are called
+<e>ac_adapter</e> and <e>battery</e> on most laptops, but it might be different
+on yours.
+</p>
+
+<pre caption="Determining ACPI events for changing the power source">
+<i># tail -f /var/log/acpid | grep "received event"</i>
+</pre>
+
+<p>
+Run the command above and pull the power cable. You should see something
+like this:
+</p>
+
+<pre caption="Sample output for power source changes">
+[Tue Sep 20 17:39:06 2005] received event "ac_adapter AC 00000080 00000000"
+[Tue Sep 20 17:39:06 2005] received event "battery BAT0 00000080 00000001"
+</pre>
+
+<p>
+The interesting part is the quoted string after <e>received event</e>. It will
+be matched by the event line in the files you are going to create below. Don't
+worry if your system generates multiple events or always the same. As long as
+any event is generated, runlevel changing will work.
+</p>
+
<pre caption="/etc/acpi/events/pmg_ac_adapter">
<comment># replace "ac_adapter" below with the event generated on your laptop</comment>
-<comment># See /var/log/acpid</comment>
+<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>
event=ac_adapter.*
action=/etc/acpi/actions/pmg_switch_runlevel.sh %e
</pre>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-02-12 11:53 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2006-02-12 11:53 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 21576 bytes --]
nightmorph 06/02/12 11:53:08
Modified: xml/htdocs/doc/en power-management-guide.xml
Log:
Power management guide updated for bug 122017
Revision Changes Path
1.17 +253 -123 xml/htdocs/doc/en/power-management-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.17&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.17&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml.diff?r1=1.16&r2=1.17&cvsroot=gentoo
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- power-management-guide.xml 1 Jan 2006 11:51:43 -0000 1.16
+++ power-management-guide.xml 12 Feb 2006 11:53:08 -0000 1.17
@@ -1,11 +1,11 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.16 2006/01/01 11:51:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.17 2006/02/12 11:53:08 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
<author title="Author">
- <mail link="fragfred@gmx.de">Dennis Nienhüser</mail>
+ <mail link="earthwings@gentoo.org">Dennis Nienhüser</mail>
</author>
<abstract>
@@ -17,13 +17,12 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.25</version>
-<date>2005-10-02</date>
+<version>1.26</version>
+<date>2006-02-12</date>
<chapter>
<title>Introduction</title>
<section>
-<title>Why Power Management?</title>
<body>
<p>
@@ -95,12 +94,11 @@
<chapter>
<title>Prerequisites</title>
<section>
-<title>What has to be done first</title>
<body>
<p>
-Before going into the details on making individual devices Power Management
-aware, make sure certain requirements are met. After controlling the BIOS
+Before discussing the details of making individual devices Power Management
+aware, make sure certain requirements are met. After controlling BIOS
settings, some kernel options want to be enabled - these are in short ACPI,
sleep states and CPU frequency scaling. As power saving most of the time comes
along with performance loss or increased latency, it should only be enabled
@@ -125,6 +123,21 @@
</body>
</section>
<section>
+<title>Setting USE flags</title>
+<body>
+
+<p>
+Please check that the <c>acpi</c> USE flag is set in
+<path>/etc/make.conf</path>. Other USE flags that might be interesting for your
+system are <c>apm</c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>,
+<c>pmu</c>. See <path>/usr/portage/profiles/use*.desc</path> for details. If
+you forgot to set one of these flags, you can recompile affected packages using
+the <c>--newuse</c> flag in <c>emerge</c>, see <c>man 1 emerge</c>.
+</p>
+
+</body>
+</section>
+<section>
<title>Configuring the kernel</title>
<body>
@@ -282,27 +295,27 @@
if [ ! -d "/etc/runlevels/${RUNLEVEL_AC}" ]
then
- logger "${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting."
- exit 1
+ logger "${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting."
+ exit 1
fi
if [ ! -d "/etc/runlevels/${RUNLEVEL_BATTERY}" ]
then
- logger "${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting."
- exit 1
+ logger "${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting."
+ exit 1
fi
if on_ac_power
then
if [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_AC}" ]]
- then
- logger "Switching to ${RUNLEVEL_AC} runlevel"
- /sbin/rc ${RUNLEVEL_AC}
- fi
+ then
+ logger "Switching to ${RUNLEVEL_AC} runlevel"
+ /sbin/rc ${RUNLEVEL_AC}
+ fi
elif [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_BATTERY}" ]]
then
- logger "Switching to ${RUNLEVEL_BATTERY} runlevel"
- /sbin/rc ${RUNLEVEL_BATTERY}
+ logger "Switching to ${RUNLEVEL_BATTERY} runlevel"
+ /sbin/rc ${RUNLEVEL_BATTERY}
fi
</pre>
@@ -394,6 +407,19 @@
<chapter>
<title>CPU Power Management</title>
<section>
+<body>
+
+<p>
+Mobile processors can operate at different frequencies. Some allow changing
+voltage as well. Most of the time your CPU doesn't need to run at full speed
+and scaling it down will save much energy - often without any performance
+decrease.
+</p>
+
+</body>
+</section>
+
+<section>
<title>Some technical terms</title>
<body>
@@ -554,11 +580,14 @@
<tr>
<ti><uri link="http://sourceforge.net/projects/cpufreqd/">cpufreqd</uri></ti>
<ti>Daemon</ti>
- <ti>Battery state, CPU load, temperature, running programs</ti>
+ <ti>Battery state, CPU load, temperature, running programs and more</ti>
<ti>All available</ti>
<ti>None</ti>
<ti>
- Sophisticated (but also complicated) setup.
+ Sophisticated (but somewhat complicated) setup. Extendible through plugins
+ like sensor monitoring (lm_sensors) or coordinating some NVidia based
+ graphics card memory and core. Cpufreqd is SMP aware and can optionally be
+ controlled manually at runtime.
</ti>
</tr>
<tr>
@@ -640,55 +669,64 @@
<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>.
The default one that ships with cpufreqd may look a bit confusing. I recommend
replacing it with the one from Gentoo developer Henrik Brix Andersen (see
-below).
+below). Please notice that you need cpufreqd-2.0.0 or later. Earlier versions
+have a different syntax for the config file.
</p>
-<pre caption="/etc/cpufreqd.conf">
+<pre caption="/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)">
[General]
pidfile=/var/run/cpufreqd.pid
-poll_interval=2
-pm_type=acpi
+poll_interval=3
+enable_plugins=acpi_ac, acpi_battery
verbosity=5
+[/General]
[Profile]
name=ondemand
minfreq=0%
maxfreq=100%
policy=ondemand
+[/Profile]
[Profile]
name=conservative
minfreq=0%
maxfreq=100%
policy=conservative
+[/Profile]
[Profile]
name=powersave
minfreq=0%
maxfreq=100%
policy=powersave
+[/Profile]
[Profile]
name=performance
minfreq=0%
maxfreq=100%
policy=performance
+[/Profile]
[Rule]
name=battery
ac=off
profile=conservative
+[/Rule]
[Rule]
name=battery_low
ac=off
battery_interval=0-10
profile=powersave
+[/Rule]
[Rule]
name=ac
ac=on
profile=ondemand
+[/Rule]
</pre>
<p>
@@ -701,6 +739,15 @@
# <i>rc</i>
</pre>
+<p>
+Sometimes it can be desirable to select another policy than the daemon chooses,
+for example when battery power is low, but you know that AC will be available
+soon. In that case you can turn on cpufreqd's manual mode with
+<c>cpufreqd-set manual</c> and select one of your configured policies (as
+listed by <c>cpufreqd-get</c>). You can leave manual mode by executing
+<c>cpufreqd-set dynamic</c>.
+</p>
+
<warn>
Do not run more than one of the above programs at the same time. It may cause
confusion like switching between two frequencies all the time.
@@ -746,7 +793,6 @@
<chapter>
<title>LCD Power Management</title>
<section>
-<title>Energy consumer no. 1</title>
<body>
<p>
@@ -757,13 +803,19 @@
possibility to control the backlight dimming.
</p>
+</body>
+</section>
+<section>
+<title>Standby settings</title>
+<body>
+
<p>
-First thing to check is the standby/suspend/off timings of the display. As this
-depends heavily on your windowmanager, I'll let you figure it out yourself.
-Just two common places: Blanking the terminal can be done with <c>setterm
--blank <number-of-minutesM></c>, <c>setterm -powersave on</c> and
-<c>setterm -powerdown <number-of-minutesM></c>.
-For X.org, modify <path>/etc/X11/xorg.conf</path> similar to this:
+The first thing to check is the standby/suspend/off timings of the display. As
+this depends heavily on your windowmanager, I'll let you figure it out
+yourself. Just two common places: Blanking the terminal can be done with
+<c>setterm -blank <number-of-minutesM></c>, <c>setterm -powersave on</c>
+and <c>setterm -powerdown <number-of-minutesM></c>. For X.org, modify
+<path>/etc/X11/xorg.conf</path> similar to this:
</p>
<pre caption="LCD suspend settings in X.org and XFree86">
@@ -790,12 +842,19 @@
This is the same for XFree86 and <path>/etc/X11/XF86Config</path>.
</p>
+</body>
+</section>
+<section>
+<title>Backlight dimming</title>
+<body>
+
<p>
Probably more important is the backlight dimming. If you have access to the
dimming settings via a tool, write a small script that dims the backlight in
battery mode and place it in your <e>battery</e> runlevel. The following script
-should work on most IBM Thinkpads. It needs the <c>app-laptop/ibm-acpi</c>
-package or the appropriate option in your kernel has to be enabled.
+should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
+appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops, install
+<c>app-laptop/acpitool</c> and skip configuration of ibm_acpi as described below.
</p>
<warn>
@@ -811,7 +870,6 @@
<pre caption="automatically loading the ibm_acpi module">
<comment>(Please read the warnings above before doing this!)</comment>
-<i># emerge ibm-acpi</i>
<i># echo "options ibm_acpi experimental=1" >> /etc/modules.d/ibm_acpi</i>
<i># /sbin/modules-update</i>
<i># echo ibm_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
@@ -827,7 +885,7 @@
<pre caption="/etc/conf.d/lcd-brightness">
<comment># See /proc/acpi/ibm/brightness for available values</comment>
-<comment># Please read /usr/share/doc/ibm-acpi-*/README.gz</comment>
+<comment># Please read /usr/src/linux/Documentation/ibm-acpi.txt</comment>
<comment># brigthness level in ac mode. Default is 7.</comment>
BRIGHTNESS_AC=7
@@ -852,9 +910,15 @@
ebegin "Setting LCD brightness"
echo "level ${LEVEL}" > /proc/acpi/ibm/brightness
eend $?
+ elif [[ -e /usr/bin/acpitool && -n $(acpitool -T | grep "LCD brightness") ]]
+ then
+ ebegin "Setting LCD brightness"
+ acpitool -l $LEVEL >/dev/null || ewarn "Unable to set lcd brightness"
+ eend $?
else
ewarn "Setting LCD brightness is not supported."
- ewarn "Check that ibm_acpi is loaded into the kernel"
+ ewarn "For IBM Thinkpads, check that ibm_acpi is loaded into the kernel"
+ ewarn "For Toshiba laptops, you've got to install app-laptop/acpitool"
fi
}
@@ -885,59 +949,141 @@
<chapter>
<title>Disk Power Management</title>
<section>
-<title>Sleep when idle</title>
+<body>
+<p>
+Hard disks consume less energy in sleep mode. Therefore it makes sense to
+activate power saving features whenever the hard disk is not used for a certain
+amount of time. I'll show you two alternative possibilities to do it. First,
+laptop-mode will save most energy due to several measures which prevent or at
+least delay write accesses. The drawback is that due to the delayed write
+accesses a power outage or kernel crash will be more dangerous for data loss.
+If you don't like this, you have to make sure that there are no processes which
+write to your hard disk frequently. Afterwards you can enable power saving
+features of your hard disk with hdparm as the second alternative.
+</p>
+
+</body>
+</section>
+
+<section>
+<title>Increasing idle time - laptop-mode</title>
<body>
<p>
-Let's bring the hard disk to sleep as early as possible whenever it is not
-needed. I'll show you two possibilities to do it. First <c>cpudyn</c> supports
-Disk Power Management. Uncomment the lines in the "Disk Options" section in
-<path>/etc/conf.d/cpudyn</path>. To put your first disk to sleep after 60
-seconds of no activity, you would modify it like this:
+Recent kernels (2.6.6 and greater, recent 2.4 ones and others with patches)
+include the so-called <e>laptop-mode</e>. When activated, dirty buffers are
+written to disk on read calls or after 10 minutes (instead of 30 seconds). This
+minimizes the time the hard disk needs to be spun up.
</p>
-<pre caption="Using cpudyn for disk standby">
-<comment>################################################
-# DISK OPTIONS
-# (disabled by default)
-################################################
+<pre caption="Automated start of laptop-mode">
+# <i>emerge laptop-mode-tools</i>
+</pre>
-#
-# Timeout to put the disk in standby mode if there was no
-# io during that period (in seconds)
-#
-</comment>
-TIMEOUT=60
-<comment>
-#
-# Specified disks to spindown (comma separated devices)
-#
-</comment>
-DISKS=/dev/hda
+<p>
+<c>laptop-mode-tools</c> has its configuration file in
+<path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it,
+it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it
+automatically.
+</p>
+
+<p>
+Recent versions (1.11 and later) of laptop-mode-tools include a new tool
+<c>lm-profiler</c>. It will monitor your system's disk usage and running
+network services and suggests to disable unneeded ones. You can either disable
+them through laptop-mode-tools builtin runlevel support (which will be reverted
+by Gentoo's <c>/sbin/rc</c>) or use your <e>default</e>/<e>battery</e>
+runlevels (recommended).
+</p>
+
+<pre caption="Sample output from running lm-profiler">
+# lm-profiler
+Profiling session started.
+Time remaining: 600 seconds
+[4296896.602000] amarokapp
+Time remaining: 599 seconds
+[4296897.714000] sort
+[4296897.970000] mv
+Time remaining: 598 seconds
+Time remaining: 597 seconds
+[4296900.482000] reiserfs/0
+</pre>
+
+<p>
+After profiling your system for ten minutes, lm-profiler will present a list of
+services which might have caused disk accesses during that time.
+</p>
+
+<pre caption="lm-profiler suggests to disable some services">
+Program: "atd"
+Reason: standard recommendation (program may not be running)
+Init script: /etc/init.d/atd (GUESSED)
+
+Do you want to disable this service in battery mode? [y/N]: n
</pre>
<p>
-The second possibility is using a small script and hdparm. Create
-<path>/etc/init.d/pm.hda</path> like this:
+To disable atd as suggested in the example above, you would run <c>rc-update
+del atd battery</c>. Be careful not to disable services that are needed for
+your system to run properly - lm-profiler is likely to generate some false
+positives. Do not disable a service if you are unsure whether it's needed.
+</p>
+
+</body>
+</section>
+
+<section>
+<title>Limiting write accesses</title>
+<body>
+
+<p>
+If you don't want to use laptop-mode, you must take special care to disable
+services that write to your disk frequently - <c>syslogd</c> is a good
+candidate, for example. You probably don't want to shut it down completely, but
+it's possible to modify the config file so that "unnecessary" things don't get
+logged and thus don't create disk traffic. Cups writes to disk periodically, so
+consider shutting it down and only enable it manually when needed.
+</p>
+
+<pre caption="Disabling cups in battery mode">
+# <i>rc-update del cupsd battery</i>
+</pre>
+
+<p>
+You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to find
+services to disable. Once you eliminated all of them, go on with configuring
+hdparm.
+</p>
+
+</body>
+</section>
+
+<section>
+<title>hdparm</title>
+<body>
+
+<p>
+The second possibility is using a small script and hdparm. Skip this if you
+are using laptop-mode. Otherwise, create <path>/etc/init.d/pmg_hda</path>:
</p>
<pre caption="Using hdparm for disk standby">
#!/sbin/runscript
depend() {
- after hdparm
+after hdparm
}
start() {
- ebegin "Activating Power Management for Hard Drives"
- hdparm -q -S12 /dev/hda
- eend $?
+ebegin "Activating Power Management for Hard Drives"
+hdparm -q -S12 /dev/hda
+eend $?
}
stop () {
- ebegin "Deactivating Power Management for Hard Drives"
- hdparm -q -S253 /dev/hda
- eend $?
+ebegin "Deactivating Power Management for Hard Drives"
+hdparm -q -S253 /dev/hda
+eend $?
}
</pre>
@@ -947,9 +1093,9 @@
</p>
<pre caption="Automate disk standby settings">
-# <i>chmod +x /etc/init.d/pm.hda</i>
+# <i>chmod +x /etc/init.d/pmg_hda</i>
# <i>/sbin/depscan.sh</i>
-# <i>rc-update add pm.hda battery</i>
+# <i>rc-update add pmg_hda battery</i>
</pre>
<impo>
@@ -959,49 +1105,12 @@
</body>
</section>
-<section>
-<title>Increasing idle time - laptop-mode</title>
-<body>
-
-<p>
-Recent kernels (2.6.6 and greater, recent 2.4 ones and others with patches)
-include the so-called <e>laptop-mode</e>. When activated, dirty buffers are
-written to disk on read calls or after 10 minutes (instead of 30 seconds). This
-minimizes the time the hard disk needs to be spun up.
-</p>
-<pre caption="Automated start of laptop-mode">
-# <i>emerge laptop-mode-tools</i>
-</pre>
-
-<p>
-<c>laptop-mode-tools</c> has it's configuration file in
-<path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it,
-it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it
-automatically.
-</p>
-
-</body>
-</section>
<section>
<title>Other tricks</title>
<body>
<p>
-Besides putting your disk to sleep state as early as possible, it is a good
-idea to minimize disk accesses. Have a look at processes that write to your
-disk frequently - the syslogd is a good candidate. You probably don't want to
-shut it down completely, but it's possible to modify the config file so that
-"unnecessary" things don't get logged and thus don't create disk traffic. Cups
-writes to disk periodically, so consider shutting it down and only enable it
-manually when needed.
-</p>
-
-<pre caption="Disabling cups in battery mode">
-# <i>rc-update del cupsd battery</i>
-</pre>
-
-<p>
Another possibility is to deactivate swap in battery mode. Before writing a
swapon/swapoff switcher, make sure there is enough RAM and swap isn't used
heavily, otherwise you'll be in big problems.
@@ -1063,15 +1172,20 @@
<body>
<p>
-Wireless LAN cards consume quite a few energy. Put them in Power Management
-mode in analogy to the pm.hda script.
+Wireless LAN cards consume quite a bit of energy. Put them in Power Management
+mode in analogy to the pmg_hda script.
</p>
+<note>
+This script assumes your wireless interface is called <c>wlan0</c>; replace
+this with the actual name of your interface.
+</note>
+
<pre caption="WLAN Power Management automated">
#!/sbin/runscript
start() {
ebegin "Activating Power Management for Wireless LAN"
- iwconfig wlan0 power on power max period 3
+ iwconfig wlan0 power on
eend $?
}
@@ -1083,18 +1197,18 @@
</pre>
<p>
-Starting this script will put wlan0 in Power Management mode, going to sleep at
-the latest three seconds after no traffic.
-Save it as <path>/etc/init.d/pm.wlan0</path> and add it to the battery runlevel
-like the disk script above. See <c>man iwconfig</c> for details and more
-options. If your driver and access point support changing the beacon time, this
-is a good starting point to save even more energy.
+Starting this script will activate power saving features for wlan0. Save it as
+<path>/etc/init.d/pmg_wlan0</path> and add it to the battery runlevel like the
+disk script above. See <c>man iwconfig</c> for details and more options like
+the period between wakeups or timeout settings. If your driver and access point
+support changing the beacon time, this is a good starting point to save even
+more energy.
</p>
<pre caption="Power Management for WLAN">
-# <i>chmod +x /etc/init.d/pm.wlan0</i>
+# <i>chmod +x /etc/init.d/pmg_wlan0</i>
# <i>/sbin/depscan.sh</i>
-# <i>rc-update add pm.wlan0 battery</i>
+# <i>rc-update add pmg_wlan0 battery</i>
</pre>
</body>
@@ -1128,7 +1242,6 @@
<chapter>
<title>Sleep states: sleep, standby, suspend to disk</title>
<section>
-<title>Overview</title>
<body>
<p>
@@ -1167,7 +1280,7 @@
</pre>
<p>
-Once your kernel is prepared like above, you can use the
+Once your kernel is properly configured, you can use the
<c>hibernate-script</c> to activate suspend or sleep mode. Let's install that
first.
</p>
@@ -1396,7 +1509,6 @@
<chapter>
<title>Troubleshooting</title>
<section>
-<title>If things go wrong...</title>
<body>
<p>
@@ -1488,6 +1600,21 @@
</p>
<p>
+<e>Q:</e> My system logger reports things like "logger: ACPI group battery / action
+battery is not defined".
+</p>
+
+<p>
+<e>A:</e> This message is generated by the /etc/acpi/default.sh script that is
+shipped with acpid. You can safely ignore it. If you like to get rid of it, you
+can comment the appropriate line in /etc/acpi/default.sh as shown below:
+</p>
+
+<pre caption="Disabling warnings about unknown acpi events">
+ *) # logger "ACPI action $action is not defined"
+</pre>
+
+<p>
<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events.
</p>
@@ -1552,8 +1679,11 @@
</p>
<p>
-<e>A:</e> Don't fear to contact me, <mail link="fragfred@gmx.de">Dennis
-Nienhüser</mail>, directly.
+<e>A:</e> Don't fear to contact me, <mail link="earthwings@gentoo.org">Dennis
+Nienhüser</mail>, directly. The
+<uri link="http://forums.gentoo.org">Gentoo Forums</uri> are a good place to
+get help as well. If you prefer IRC, try the <e>#gentoo-laptop</e> channel at
+<e>irc.freenode.net</e>.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-02-16 18:45 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2006-02-16 18:45 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/02/16 18:45:10
Modified: xml/htdocs/doc/en power-management-guide.xml
Log:
Fixed <no cpufreqd found> error for bug 123062
Revision Changes Path
1.18 +4 -2 xml/htdocs/doc/en/power-management-guide.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.18&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml?rev=1.18&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/power-management-guide.xml.diff?r1=1.17&r2=1.18&cvsroot=gentoo
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- power-management-guide.xml 12 Feb 2006 11:53:08 -0000 1.17
+++ power-management-guide.xml 16 Feb 2006 18:45:09 -0000 1.18
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.17 2006/02/12 11:53:08 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.18 2006/02/16 18:45:09 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -17,8 +17,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.26</version>
-<date>2006-02-12</date>
+<version>1.27</version>
+<date>2006-02-16</date>
<chapter>
<title>Introduction</title>
@@ -678,6 +678,8 @@
pidfile=/var/run/cpufreqd.pid
poll_interval=3
enable_plugins=acpi_ac, acpi_battery
+enable_remote=1
+remote_group=wheel
verbosity=5
[/General]
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-07-27 8:13 Lukasz Damentko
0 siblings, 0 replies; 20+ messages in thread
From: Lukasz Damentko @ 2006-07-27 8:13 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 28011 bytes --]
rane 06/07/27 08:13:32
Modified: power-management-guide.xml
Log:
#123776, fixed the coding style a lot
Revision Changes Path
1.19 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.18&r2=1.19
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- power-management-guide.xml 16 Feb 2006 18:45:09 -0000 1.18
+++ power-management-guide.xml 27 Jul 2006 08:13:32 -0000 1.19
@@ -1,12 +1,15 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.18 2006/02/16 18:45:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.19 2006/07/27 08:13:32 rane Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
<author title="Author">
<mail link="earthwings@gentoo.org">Dennis Nienhüser</mail>
</author>
+<author title="Editor">
+ <mail link="chriswhite@gentoo.org">Chris White</mail>
+</author>
<abstract>
Power Management is the key to extend battery run time on mobile systems like
@@ -17,8 +20,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.27</version>
-<date>2006-02-16</date>
+<version>1.28</version>
+<date>2006-07-26</date>
<chapter>
<title>Introduction</title>
@@ -36,9 +39,8 @@
</body>
</section>
-
<section>
-<title>A quick overview</title>
+<title>A Quick Overview</title>
<body>
<p>
@@ -54,26 +56,27 @@
</p>
<p>
-The <e>Prerequisites</e> chapter talks about some requirements that should be
-met before any of the following device individual sections will work. This
-includes BIOS settings, kernel configuration and some simplifications in user
-land. The following three chapters focus on devices that typically consume
-most energy - processor, display and hard drive. Each can be configured
-seperately. <e>CPU Power Management</e> shows how to adjust the processor's
-frequency to save a maximum of energy whithout losing too much performance. A
-few different tricks prevent your hard drive from working unnecessarily often
-in <e>Disk Power Management</e> (decreasing noise level as a nice side
-effect). Some notes on graphics cards, Wireless LAN and USB finish the device
-section in <e>Power Management for other devices</e> while another chapter is
-dedicated to the (rather experimental) <e>sleep states</e>. Last not least
-<e>Troubleshooting</e> lists common pitfalls.
+The <uri link="#doc_chap2">Prerequisites</uri> chapter talks about some
+requirements that should be met before any of the following device individual
+sections will work. This includes BIOS settings, kernel configuration and some
+simplifications in user land. The following three chapters focus on devices
+that typically consume most energy - processor, display and hard drive. Each
+can be configured seperately. <uri link="#doc_chap3">CPU Power Management</uri>
+shows how to adjust the processor's frequency to save a maximum of energy
+whithout losing too much performance. A few different tricks prevent your hard
+drive from working unnecessarily often in <uri link="#doc_chap5">Disk Power
+Management</uri> (decreasing noise level as a nice side effect). Some notes on
+graphics cards, Wireless LAN and USB finish the device section in
+<uri link="#doc_chap6">Power Management For Other Devices</uri> while another
+chapter is dedicated to the (rather experimental) <uri link="#doc_chap7">sleep
+states</uri>. Last not least <uri link="#doc_chap8">Troubleshooting</uri>
+lists common pitfalls.
</p>
</body>
</section>
-
<section>
-<title>Power Budget for each component</title>
+<title>Power Budget For Each Component</title>
<body>
<figure link="/images/energy-budget.png" short="Which component consumes how
@@ -109,7 +112,7 @@
</body>
</section>
<section>
-<title>The BIOS part</title>
+<title>The BIOS Part</title>
<body>
<p>
@@ -123,7 +126,7 @@
</body>
</section>
<section>
-<title>Setting USE flags</title>
+<title>Setting USE Flags</title>
<body>
<p>
@@ -132,13 +135,13 @@
system are <c>apm</c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>,
<c>pmu</c>. See <path>/usr/portage/profiles/use*.desc</path> for details. If
you forgot to set one of these flags, you can recompile affected packages using
-the <c>--newuse</c> flag in <c>emerge</c>, see <c>man 1 emerge</c>.
+the <c>--newuse</c> flag in <c>emerge</c>, see <c>man emerge</c>.
</p>
</body>
</section>
<section>
-<title>Configuring the kernel</title>
+<title>Configuring The Kernel</title>
<body>
<p>
@@ -150,8 +153,9 @@
<p>
There are different kernel sources in Portage. I'd recommend using
<c>gentoo-sources</c> or <c>suspend2-sources</c>. The latter contains patches
-for Software Suspend 2, see the chapter about sleep states for details. When
-configuring the kernel, activate at least these options:
+for Software Suspend 2, see the chapter about <uri link="#doc_chap7">sleep
+states</uri> for more details. When configuring the kernel, activate at least
+these options:
</p>
<pre caption="Minimum kernel setup for Power Management (Kernel 2.6)">
@@ -203,8 +207,8 @@
<p>
The kernel has to know how to enable CPU frequency scaling on your processor. As
each type of CPU has a different interface, you've got to choose the right
-driver for your processor. Be careful here - enabling <e>Intel Pentium 4 clock
-modulation</e> on a Pentium M system will lead to strange results for example.
+driver for your processor. Be careful here - enabling <c>Intel Pentium 4 clock
+modulation</c> on a Pentium M system will lead to strange results for example.
Consult the kernel documentation if you're unsure which one to take.
</p>
@@ -227,20 +231,20 @@
</body>
</section>
<section>
-<title>Creating a "battery" runlevel</title>
+<title>Creating A "battery" Runlevel</title>
<body>
<p>
The default policy will be to enable Power Management only when needed -
running on batteries. To make the switch between AC and battery convenient,
-create a runlevel <e>battery</e> that holds all the scripts starting and
+create a runlevel <c>battery</c> that holds all the scripts starting and
stopping Power Management.
</p>
<note>
You can safely skip this section if you don't like the idea of having another
runlevel. However, skipping this step will make the rest a bit trickier to set
-up. The next sections assume a runlevel <e>battery</e> exists.
+up. The next sections assume a runlevel <c>battery</c> exists.
</note>
<pre caption="Creating a battery runlevel">
@@ -249,15 +253,15 @@
</pre>
<p>
-Finished. Your new runlevel <e>battery</e> contains everything like
-<e>default</e>, but there is no automatic switch between both yet. Time to
+Finished. Your new runlevel <c>battery</c> contains everything like
+<c>default</c>, but there is no automatic switch between both yet. Time to
change it.
</p>
</body>
</section>
<section>
-<title>Reacting on ACPI events</title>
+<title>Reacting On ACPI Events</title>
<body>
<p>
@@ -274,7 +278,7 @@
</p>
<pre caption="Installing powermgt-base">
-<i># emerge powermgmt-base</i>
+# <i>emerge powermgmt-base</i>
</pre>
<p>
@@ -307,12 +311,12 @@
if on_ac_power
then
- if [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_AC}" ]]
+ if [[ "$(</var/lib/init.d/softlevel)" != "${RUNLEVEL_AC}" ]]
then
logger "Switching to ${RUNLEVEL_AC} runlevel"
/sbin/rc ${RUNLEVEL_AC}
fi
-elif [[ "$(cat /var/lib/init.d/softlevel)" != "${RUNLEVEL_BATTERY}" ]]
+elif [[ "$(</var/lib/init.d/softlevel)" != "${RUNLEVEL_BATTERY}" ]]
then
logger "Switching to ${RUNLEVEL_BATTERY} runlevel"
/sbin/rc ${RUNLEVEL_BATTERY}
@@ -325,12 +329,12 @@
script whenever the power source changes. That's done by catching ACPI events
with the help of <c>acpid</c>. First you need to know which events are
generated when the power source changes. The events are called
-<e>ac_adapter</e> and <e>battery</e> on most laptops, but it might be different
+<c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be different
on yours.
</p>
<pre caption="Determining ACPI events for changing the power source">
-<i># tail -f /var/log/acpid | grep "received event"</i>
+# <i>tail -f /var/log/acpid | grep "received event"</i>
</pre>
<p>
@@ -344,7 +348,7 @@
</pre>
<p>
-The interesting part is the quoted string after <e>received event</e>. It will
+The interesting part is the quoted string after <c>received event</c>. It will
be matched by the event line in the files you are going to create below. Don't
worry if your system generates multiple events or always the same. As long as
any event is generated, runlevel changing will work.
@@ -369,18 +373,19 @@
</p>
<pre caption="Finishing runlevel switching with acpid">
-<i># /etc/init.d/acpid restart</i>
+# <i>/etc/init.d/acpid restart</i>
</pre>
<p>
Give it a try: Plug AC in and out and watch syslog for the "Switching to AC
-mode" or "Switching to battery mode" messages. See the Troubleshooting
-section if the script is not able to detect the power source correctly.
+mode" or "Switching to battery mode" messages. See the
+<uri link="#doc_chap8">Troubleshooting section</uri> if the script is not
+able to detect the power source correctly.
</p>
<p>
Due to the nature of the event mechanism, your laptop will boot into runlevel
-<e>default</e> regardless of the AC/battery state. This is fine when running
+<c>default</c> regardless of the AC/battery state. This is fine when running
from AC, but we'd like to boot into the battery runlevel otherwise. One
solution would be to add another entry to the boot loader with the parameter
<c>softlevel=battery</c>, but it's likely to forget choosing it. A better way
@@ -420,7 +425,7 @@
</section>
<section>
-<title>Some technical terms</title>
+<title>Some Technical Terms</title>
<body>
<p>
@@ -430,17 +435,17 @@
<p>
First of all, the kernel has to be able to change the processor's frequency.
-The <e>CPUfreq processor driver</e> knows the commands to do it on your CPU.
+The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU.
Thus it's important to choose the right one in your kernel. You should
already have done it above. Once the kernel knows how to change frequencies,
it has to know which frequency it should set. This is done according to the
-<e>policy</e> which consists of a <e>CPUfreq policy</e> and a
-<e>governor</e>. A CPUfreq policy are just two numbers which define a range
+<b>policy</b> which consists of a <b>CPUfreq policy</b> and a
+<b>governor</b>. A CPUfreq policy are just two numbers which define a range
the frequency has to stay between - minimal and maximal frequency. The
governor now decides which of the available frequencies in between minimal
-and maximal frequency to choose. For example, the <e>powersave governor</e>
-always chooses the lowest frequency available, the <e>performance
-governor</e> the highest one. The <e>userspace governor</e> makes no decision
+and maximal frequency to choose. For example, the <b>powersave governor</b>
+always chooses the lowest frequency available, the <b>performance
+governor</b> the highest one. The <b>userspace governor</b> makes no decision
but chooses whatever the user (or a program in userspace) wants - which means
it reads the frequency from
<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>.
@@ -449,7 +454,7 @@
<p>
This doesn't sound like dynamic frequency changes yet and in fact it isn't.
Dynamics however can be accomplished with various approaches. For example,
-the <e>ondemand governor</e> makes its decisions depending on the current CPU
+the <b>ondemand governor</b> makes its decisions depending on the current CPU
load. The same is done by various userland tools like <c>cpudyn</c>,
<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to
enable or disable dynamic frequency changes depending on power source.
@@ -458,7 +463,7 @@
</body>
</section>
<section>
-<title>Setting the frequency manually</title>
+<title>Setting The Frequency Manually</title>
<body>
<p>
@@ -471,8 +476,8 @@
<note>
Not every laptop supports frequency scaling. If unsure, have a look at the list
-of supported processors in the <e>Troubleshooting</e> section to verify your's
-is supported.
+of supported processors in the <uri link="#doc_chap8">Troubleshooting</uri>
+section to verify yours is supported.
</note>
<p>
@@ -508,8 +513,8 @@
Now play around with <c>cpufreq-set</c> to make sure frequency switching works.
Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand
governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as
-expected, you might find help in the Troubleshooting section in the end of this
-guide.
+expected, you might find help in the <uri link="#doc_chap8">Troubleshooting section</uri>
+in the end of this guide.
</p>
</body>
@@ -523,8 +528,8 @@
set the appropriate frequency automatically. There are many different
approaches to do this. The following table gives a quick overview to help you
decide on one of them. It's roughly seperated in three categories
-<e>kernel</e> for approaches that only need kernel support, <e>daemon</e> for
-programs that run in the background and <e>graphical</e> for programs that
+<b>kernel</b> for approaches that only need kernel support, <b>daemon</b> for
+programs that run in the background and <b>graphical</b> for programs that
provide a GUI for easy configuration and changes.
</p>
@@ -732,8 +737,8 @@
</pre>
<p>
-Now you can start the cpufreqd daemon. Add it to the <e>default</e> and
-<e>battery</e> runlevel as well.
+Now you can start the cpufreqd daemon. Add it to the <c>default</c> and
+<c>battery</c> runlevel as well.
</p>
<pre caption="Starting cpufreqd">
@@ -757,10 +762,8 @@
</body>
</section>
-
<section>
<title>Verifying the result</title>
-
<body>
<p>
@@ -773,8 +776,8 @@
</pre>
<p>
-If <path>/proc/cpuinfo</path> doesn't get updated (see Troubleshooting),
-monitor the CPU frequency with:
+If <path>/proc/cpuinfo</path> doesn't get updated (see
+<uri link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with:
</p>
<pre caption="Alternative CPU speed monitoring">
@@ -783,9 +786,9 @@
<p>
Depending on your setup, CPU speed should increase on heavy load, decrease on
-no activity or just stay at the same level. When using cpufreqd and verbosity
-set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional
-information about what's happening reported to syslog.
+no activity or just stay at the same level. When using <c>cpufreqd</c> and
+verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional
+information about what's happening reported to <c>syslog</c>.
</p>
</body>
@@ -853,10 +856,10 @@
<p>
Probably more important is the backlight dimming. If you have access to the
dimming settings via a tool, write a small script that dims the backlight in
-battery mode and place it in your <e>battery</e> runlevel. The following script
+battery mode and place it in your <c>battery</c> runlevel. The following script
should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops, install
-<c>app-laptop/acpitool</c> and skip configuration of ibm_acpi as described below.
+<c>app-laptop/acpitool</c> and skip configuration of <c>ibm_acpi</c> as described below.
</p>
<warn>
@@ -872,10 +875,10 @@
<pre caption="automatically loading the ibm_acpi module">
<comment>(Please read the warnings above before doing this!)</comment>
-<i># echo "options ibm_acpi experimental=1" >> /etc/modules.d/ibm_acpi</i>
-<i># /sbin/modules-update</i>
-<i># echo ibm_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
-<i># modprobe ibm_acpi</i>
+# <i>echo "options ibm_acpi experimental=1" >> /etc/modules.d/ibm_acpi</i>
+# <i>/sbin/modules-update</i>
+# <i>echo ibm_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
+# <i>modprobe ibm_acpi</i>
</pre>
<p>
@@ -939,9 +942,9 @@
</p>
<pre caption="Enabling automatic brightness adjustment">
-<i># chmod +x /etc/init.d/lcd-brightness</i>
-<i># rc-update add lcd-brightness battery</i>
-<i># rc</i>
+# <i>chmod +x /etc/init.d/lcd-brightness</i>
+# <i>rc-update add lcd-brightness battery</i>
+# <i>rc</i>
</pre>
</body>
@@ -952,6 +955,7 @@
<title>Disk Power Management</title>
<section>
<body>
+
<p>
Hard disks consume less energy in sleep mode. Therefore it makes sense to
activate power saving features whenever the hard disk is not used for a certain
@@ -961,19 +965,18 @@
accesses a power outage or kernel crash will be more dangerous for data loss.
If you don't like this, you have to make sure that there are no processes which
write to your hard disk frequently. Afterwards you can enable power saving
-features of your hard disk with hdparm as the second alternative.
+features of your hard disk with <c>hdparm</c> as the second alternative.
</p>
</body>
</section>
-
<section>
<title>Increasing idle time - laptop-mode</title>
<body>
<p>
Recent kernels (2.6.6 and greater, recent 2.4 ones and others with patches)
-include the so-called <e>laptop-mode</e>. When activated, dirty buffers are
+include the so-called <c>laptop-mode</c>. When activated, dirty buffers are
written to disk on read calls or after 10 minutes (instead of 30 seconds). This
minimizes the time the hard disk needs to be spun up.
</p>
@@ -994,12 +997,12 @@
<c>lm-profiler</c>. It will monitor your system's disk usage and running
network services and suggests to disable unneeded ones. You can either disable
them through laptop-mode-tools builtin runlevel support (which will be reverted
-by Gentoo's <c>/sbin/rc</c>) or use your <e>default</e>/<e>battery</e>
+by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/<c>battery</c>
runlevels (recommended).
</p>
<pre caption="Sample output from running lm-profiler">
-# lm-profiler
+# <i>lm-profiler</i>
Profiling session started.
Time remaining: 600 seconds
[4296896.602000] amarokapp
@@ -1021,21 +1024,20 @@
Reason: standard recommendation (program may not be running)
Init script: /etc/init.d/atd (GUESSED)
-Do you want to disable this service in battery mode? [y/N]: n
+Do you want to disable this service in battery mode? [y/N]: <i>n</i>
</pre>
<p>
To disable atd as suggested in the example above, you would run <c>rc-update
del atd battery</c>. Be careful not to disable services that are needed for
-your system to run properly - lm-profiler is likely to generate some false
+your system to run properly - <c>lm-profiler</c> is likely to generate some false
positives. Do not disable a service if you are unsure whether it's needed.
</p>
</body>
</section>
-
<section>
-<title>Limiting write accesses</title>
+<title>Limiting Write Accesses</title>
<body>
<p>
@@ -1043,8 +1045,8 @@
services that write to your disk frequently - <c>syslogd</c> is a good
candidate, for example. You probably don't want to shut it down completely, but
it's possible to modify the config file so that "unnecessary" things don't get
-logged and thus don't create disk traffic. Cups writes to disk periodically, so
-consider shutting it down and only enable it manually when needed.
+logged and thus don't create disk traffic. <c>Cups</c> writes to disk periodically,
+so consider shutting it down and only enable it manually when needed.
</p>
<pre caption="Disabling cups in battery mode">
@@ -1059,13 +1061,12 @@
</body>
</section>
-
<section>
<title>hdparm</title>
<body>
<p>
-The second possibility is using a small script and hdparm. Skip this if you
+The second possibility is using a small script and <c>hdparm</c>. Skip this if you
are using laptop-mode. Otherwise, create <path>/etc/init.d/pmg_hda</path>:
</p>
@@ -1107,7 +1108,6 @@
</body>
</section>
-
<section>
<title>Other tricks</title>
<body>
@@ -1120,7 +1120,7 @@
<p>
If you don't want to use laptop-mode, it's still possible to minimize disk
-access by mounting certain directories as <e>tmpfs</e> - write accesses are not
+access by mounting certain directories as <c>tmpfs</c> - write accesses are not
stored on a disk, but in main memory and get lost with unmounting. Often it's
useful to mount <path>/tmp</path> like this - you don't have to pay special
attention as it gets cleared on every reboot regardless whether it was mounted
@@ -1139,7 +1139,7 @@
unsure, don't try this at all, it can become a perfomance bottleneck easily. In
case you want to mount <path>/var/log</path> like this, make sure to merge the
log files to disk before unmounting. They are essential. Don't attempt to mount
-/var/tmp like this. Portage uses it for compiling...
+<path>/var/tmp</path> like this. Portage uses it for compiling...
</warn>
</body>
@@ -1147,9 +1147,9 @@
</chapter>
<chapter>
-<title>Power Management for other devices</title>
+<title>Power Management For Other Devices</title>
<section>
-<title>Graphics cards</title>
+<title>Graphics Cards</title>
<body>
<p>
@@ -1175,7 +1175,7 @@
<p>
Wireless LAN cards consume quite a bit of energy. Put them in Power Management
-mode in analogy to the pmg_hda script.
+mode in analogy to the <c>pmg_hda</c> script.
</p>
<note>
@@ -1242,7 +1242,7 @@
</chapter>
<chapter>
-<title>Sleep states: sleep, standby, suspend to disk</title>
+<title>Sleep States: sleep, standby, and suspend to disk</title>
<section>
<body>
@@ -1288,7 +1288,7 @@
</p>
<pre caption="Installing the hibernate-script">
-<i># emerge hibernate-script</i>
+# <i>emerge hibernate-script</i>
</pre>
<p>
@@ -1309,11 +1309,11 @@
<p>
Ready? Now is the last chance to backup any data you want to keep after
executing the next command. Notice that you probably have to hit a special key
-like <e>Fn</e> to resume from sleep.
+like <c>Fn</c> to resume from sleep.
</p>
<pre caption="Calling sleep">
-<i># hibernate-ram</i>
+# <i>hibernate-ram</i>
</pre>
<p>
@@ -1391,7 +1391,7 @@
</p>
<pre caption="Invalidating swsusp images during the boot process">
-<i># rc-update add hibernate-cleanup boot</i>
+# <i>rc-update add hibernate-cleanup boot</i>
</pre>
<p>
@@ -1412,9 +1412,9 @@
</p>
<pre caption="Hibernating with swsusp">
-<i># nano -w /etc/hibernate.conf</i>
+# <i>nano -w /etc/hibernate.conf</i>
<comment>(Make sure you have a backup of your data)</comment>
-<i># hibernate</i>
+# <i>hibernate</i>
</pre>
<p>
@@ -1433,31 +1433,31 @@
</p>
<pre caption="Invalidating suspend2 images during the boot process">
-<i># rc-update add hibernate-cleanup boot</i>
+# <i>rc-update add hibernate-cleanup boot</i>
</pre>
<p>Now edit <path>/etc/hibernate/hibernate.conf</path>, enable the
-<e>suspend2</e> section and comment everything in the <e>sysfs_power_state</e>
-and <e>acpi_sleep</e> sections. Do not enable the fbsplash part in global
+<c>suspend2</c> section and comment everything in the <c>sysfs_power_state</c>
+and <c>acpi_sleep</c> sections. Do not enable the <c>fbsplash</c> part in global
options yet.
</p>
<pre caption="Hibernating with suspend2">
-<i># nano -w /etc/hibernate.conf</i>
+# <i>nano -w /etc/hibernate.conf</i>
<comment>(Make sure you have a backup of your data)</comment>
-<i># hibernate</i>
+# <i>hibernate</i>
</pre>
<p>
-Please configure fbsplash now if you didn't do already. To enable fbsplash
+Please configure <c>fbsplash</c> now if you didn't do already. To enable fbsplash
support during hibernation, the <c>sys-apps/suspend2-userui</c> package is
-needed. Additionally, you've got to enable the <e>fbsplash</e> USE flag.
+needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag.
</p>
<pre caption="Installing suspend2-userui">
-<i># mkdir -p /etc/portage</i>
-<i># echo sys-apps/suspend2-userui fbsplash >> /etc/portage/package.use</i>
-<i># emerge suspend2-userui</i>
+# <i>mkdir -p /etc/portage</i>
+# <i>echo "sys-apps/suspend2-userui fbsplash" >> /etc/portage/package.use</i>
+# <i>emerge suspend2-userui</i>
</pre>
<p>
@@ -1466,7 +1466,7 @@
</p>
<pre caption="Using the livecd-2005.1 theme during hibernation">
-<i># ln -sfn /etc/splash/livecd-2005.1 /etc/splash/suspend2</i>
+# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/suspend2</i>
</pre>
<p>
@@ -1478,14 +1478,14 @@
</p>
<pre caption="Adding suspend2ui_fbsplash to an initrd image">
-<i># mount /boot</i>
-<i># mkdir ~/initrd.d</i>
-<i># cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>
-<i># cd ~/initrd.d</i>
-<i># gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>
-<i># rm fbsplash-emergence-1024x768</i>
-<i># cp /usr/sbin/suspend2ui_fbsplash sbin/</i>
-<i># find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-suspend2-emergence-1024x768</i>
+# <i>mount /boot</i>
+# <i>mkdir ~/initrd.d</i>
+# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>
+# <i>cd ~/initrd.d</i>
+# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>
+# <i>rm fbsplash-emergence-1024x768</i>
+# <i>cp /usr/sbin/suspend2ui_fbsplash sbin/</i>
+# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-suspend2-emergence-1024x768</i>
</pre>
<p>
@@ -1496,7 +1496,7 @@
</p>
<pre caption="Test run for fbsplash hibernation">
-<i># suspend2ui_fbsplash -t</i>
+# <i>suspend2ui_fbsplash -t</i>
</pre>
<p>
@@ -1545,8 +1545,8 @@
</p>
<p>
-<e>Q:</e> My laptop supports frequency scaling, but according to /proc/cpuinfo
-the speed never changes.
+<e>Q:</e> My laptop supports frequency scaling, but according to
+<path>/proc/cpuinfo</path> the speed never changes.
</p>
<p>
@@ -1607,9 +1607,10 @@
</p>
<p>
-<e>A:</e> This message is generated by the /etc/acpi/default.sh script that is
-shipped with acpid. You can safely ignore it. If you like to get rid of it, you
-can comment the appropriate line in /etc/acpi/default.sh as shown below:
+<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> script
+that is shipped with acpid. You can safely ignore it. If you like to get rid of it,
+you can comment the appropriate line in <path>/etc/acpi/default.sh</path> as shown
+below:
</p>
<pre caption="Disabling warnings about unknown acpi events">
@@ -1626,13 +1627,13 @@
</p>
<p>
-<e>Q:</e> I activated the DynamicClocks option in <path>xorg.conf</path> and
+<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path> and
now X.org crashes / the screen stays black / my laptop doesn't shutdown
properly.
</p>
<p>
-<e>A:</e> This happens on some systems. You have to disable DynamicClocks.
+<e>A:</e> This happens on some systems. You have to disable <c>DynamicClocks</c>.
</p>
<p>
@@ -1684,8 +1685,8 @@
<e>A:</e> Don't fear to contact me, <mail link="earthwings@gentoo.org">Dennis
Nienhüser</mail>, directly. The
<uri link="http://forums.gentoo.org">Gentoo Forums</uri> are a good place to
-get help as well. If you prefer IRC, try the <e>#gentoo-laptop</e> channel at
-<e>irc.freenode.net</e>.
+get help as well. If you prefer IRC, try the <c>#gentoo-laptop</c> channel at
+<uri link="irc://irc.freenode.net">irc.freenode.net</uri>.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-07-27 8:23 Lukasz Damentko
0 siblings, 0 replies; 20+ messages in thread
From: Lukasz Damentko @ 2006-07-27 8:23 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 28453 bytes --]
rane 06/07/27 08:23:01
Modified: power-management-guide.xml
Log:
fixed line wrapping, *no content change*
Revision Changes Path
1.20 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.19&r2=1.20
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- power-management-guide.xml 27 Jul 2006 08:13:32 -0000 1.19
+++ power-management-guide.xml 27 Jul 2006 08:23:01 -0000 1.20
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.19 2006/07/27 08:13:32 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.20 2006/07/27 08:23:01 rane Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -66,11 +66,11 @@
whithout losing too much performance. A few different tricks prevent your hard
drive from working unnecessarily often in <uri link="#doc_chap5">Disk Power
Management</uri> (decreasing noise level as a nice side effect). Some notes on
-graphics cards, Wireless LAN and USB finish the device section in
-<uri link="#doc_chap6">Power Management For Other Devices</uri> while another
+graphics cards, Wireless LAN and USB finish the device section in <uri
+link="#doc_chap6">Power Management For Other Devices</uri> while another
chapter is dedicated to the (rather experimental) <uri link="#doc_chap7">sleep
-states</uri>. Last not least <uri link="#doc_chap8">Troubleshooting</uri>
-lists common pitfalls.
+states</uri>. Last not least <uri link="#doc_chap8">Troubleshooting</uri> lists
+common pitfalls.
</p>
</body>
@@ -101,12 +101,11 @@
<p>
Before discussing the details of making individual devices Power Management
-aware, make sure certain requirements are met. After controlling BIOS
-settings, some kernel options want to be enabled - these are in short ACPI,
-sleep states and CPU frequency scaling. As power saving most of the time comes
-along with performance loss or increased latency, it should only be enabled
-when running on batteries. That's where a new runlevel <e>battery</e> comes in
-handy.
+aware, make sure certain requirements are met. After controlling BIOS settings,
+some kernel options want to be enabled - these are in short ACPI, sleep states
+and CPU frequency scaling. As power saving most of the time comes along with
+performance loss or increased latency, it should only be enabled when running
+on batteries. That's where a new runlevel <e>battery</e> comes in handy.
</p>
</body>
@@ -151,7 +150,7 @@
</p>
<p>
-There are different kernel sources in Portage. I'd recommend using
+There are different kernel sources in Portage. I'd recommend using
<c>gentoo-sources</c> or <c>suspend2-sources</c>. The latter contains patches
for Software Suspend 2, see the chapter about <uri link="#doc_chap7">sleep
states</uri> for more details. When configuring the kernel, activate at least
@@ -182,7 +181,7 @@
[ ] Debug Statements
[*] Power Management Timer Support
< > ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)
-
+
CPU Frequency Scaling --->
[*] CPU Frequency scaling
[ ] Enable CPUfreq debugging
@@ -205,8 +204,8 @@
</p>
<p>
-The kernel has to know how to enable CPU frequency scaling on your processor. As
-each type of CPU has a different interface, you've got to choose the right
+The kernel has to know how to enable CPU frequency scaling on your processor.
+As each type of CPU has a different interface, you've got to choose the right
driver for your processor. Be careful here - enabling <c>Intel Pentium 4 clock
modulation</c> on a Pentium M system will lead to strange results for example.
Consult the kernel documentation if you're unsure which one to take.
@@ -214,12 +213,12 @@
<p>
Compile your kernel, make sure the right modules get loaded at startup and boot
-into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to get
-the acpi daemon. This one informs you about events like switching from AC to
-battery or closing the lid. Make sure the modules are loaded if you didn't
-compile them into the kernel and start acpid by executing
-<c>/etc/init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load
-it on startup. You'll soon see how to use it.
+into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to
+get the acpi daemon. This one informs you about events like switching from AC
+to battery or closing the lid. Make sure the modules are loaded if you didn't
+compile them into the kernel and start acpid by executing <c>/etc/init.d/acpid
+start</c>. Run <c>rc-update add acpid default</c> to load it on startup. You'll
+soon see how to use it.
</p>
<pre caption="Installing acpid">
@@ -282,9 +281,9 @@
</pre>
<p>
-You are now able to determine the power source by executing
-<c>on_ac_power && echo AC available || echo Running on batteries</c> in
-a shell. The script below is responsible for changing runlevels. Save it as
+You are now able to determine the power source by executing <c>on_ac_power
+&& echo AC available || echo Running on batteries</c> in a shell. The
+script below is responsible for changing runlevels. Save it as
<path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>.
</p>
@@ -338,8 +337,8 @@
</pre>
<p>
-Run the command above and pull the power cable. You should see something
-like this:
+Run the command above and pull the power cable. You should see something like
+this:
</p>
<pre caption="Sample output for power source changes">
@@ -378,21 +377,21 @@
<p>
Give it a try: Plug AC in and out and watch syslog for the "Switching to AC
-mode" or "Switching to battery mode" messages. See the
-<uri link="#doc_chap8">Troubleshooting section</uri> if the script is not
-able to detect the power source correctly.
+mode" or "Switching to battery mode" messages. See the <uri
+link="#doc_chap8">Troubleshooting section</uri> if the script is not able to
+detect the power source correctly.
</p>
<p>
Due to the nature of the event mechanism, your laptop will boot into runlevel
<c>default</c> regardless of the AC/battery state. This is fine when running
-from AC, but we'd like to boot into the battery runlevel otherwise. One
-solution would be to add another entry to the boot loader with the parameter
+from AC, but we'd like to boot into the battery runlevel otherwise. One
+solution would be to add another entry to the boot loader with the parameter
<c>softlevel=battery</c>, but it's likely to forget choosing it. A better way
-is faking an ACPI event in the end of the boot process and letting
-<path>pmg_switch_runlevel.sh</path> script decide whether a
-runlevel change is necessary. Open <path>/etc/conf.d/local.start</path> in your
-favourite editor and add these lines:
+is faking an ACPI event in the end of the boot process and letting
+<path>pmg_switch_runlevel.sh</path> script decide whether a runlevel change is
+necessary. Open <path>/etc/conf.d/local.start</path> in your favourite editor
+and add these lines:
</p>
<pre caption="Runlevel adjustment at boot time by editing local.start">
@@ -401,7 +400,7 @@
</pre>
<p>
-Prepared like this you can activate Power Management policies for individual
+Prepared like this you can activate Power Management policies for individual
devices.
</p>
@@ -423,7 +422,6 @@
</body>
</section>
-
<section>
<title>Some Technical Terms</title>
<body>
@@ -436,28 +434,27 @@
<p>
First of all, the kernel has to be able to change the processor's frequency.
The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU.
-Thus it's important to choose the right one in your kernel. You should
-already have done it above. Once the kernel knows how to change frequencies,
-it has to know which frequency it should set. This is done according to the
-<b>policy</b> which consists of a <b>CPUfreq policy</b> and a
-<b>governor</b>. A CPUfreq policy are just two numbers which define a range
-the frequency has to stay between - minimal and maximal frequency. The
-governor now decides which of the available frequencies in between minimal
-and maximal frequency to choose. For example, the <b>powersave governor</b>
-always chooses the lowest frequency available, the <b>performance
-governor</b> the highest one. The <b>userspace governor</b> makes no decision
-but chooses whatever the user (or a program in userspace) wants - which means
-it reads the frequency from
+Thus it's important to choose the right one in your kernel. You should already
+have done it above. Once the kernel knows how to change frequencies, it has to
+know which frequency it should set. This is done according to the <b>policy</b>
+which consists of a <b>CPUfreq policy</b> and a <b>governor</b>. A CPUfreq
+policy are just two numbers which define a range the frequency has to stay
+between - minimal and maximal frequency. The governor now decides which of the
+available frequencies in between minimal and maximal frequency to choose. For
+example, the <b>powersave governor</b> always chooses the lowest frequency
+available, the <b>performance governor</b> the highest one. The <b>userspace
+governor</b> makes no decision but chooses whatever the user (or a program in
+userspace) wants - which means it reads the frequency from
<path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>.
</p>
<p>
This doesn't sound like dynamic frequency changes yet and in fact it isn't.
-Dynamics however can be accomplished with various approaches. For example,
-the <b>ondemand governor</b> makes its decisions depending on the current CPU
-load. The same is done by various userland tools like <c>cpudyn</c>,
-<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to
-enable or disable dynamic frequency changes depending on power source.
+Dynamics however can be accomplished with various approaches. For example, the
+<b>ondemand governor</b> makes its decisions depending on the current CPU load.
+The same is done by various userland tools like <c>cpudyn</c>, <c>cpufreqd</c>,
+<c>powernowd</c> and many more. ACPI events can be used to enable or disable
+dynamic frequency changes depending on power source.
</p>
</body>
@@ -513,8 +510,8 @@
Now play around with <c>cpufreq-set</c> to make sure frequency switching works.
Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand
governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as
-expected, you might find help in the <uri link="#doc_chap8">Troubleshooting section</uri>
-in the end of this guide.
+expected, you might find help in the <uri link="#doc_chap8">Troubleshooting
+section</uri> in the end of this guide.
</p>
</body>
@@ -527,10 +524,10 @@
The above is quite nice, but not doable in daily life. Better let your system
set the appropriate frequency automatically. There are many different
approaches to do this. The following table gives a quick overview to help you
-decide on one of them. It's roughly seperated in three categories
-<b>kernel</b> for approaches that only need kernel support, <b>daemon</b> for
-programs that run in the background and <b>graphical</b> for programs that
-provide a GUI for easy configuration and changes.
+decide on one of them. It's roughly seperated in three categories <b>kernel</b>
+for approaches that only need kernel support, <b>daemon</b> for programs that
+run in the background and <b>graphical</b> for programs that provide a GUI for
+easy configuration and changes.
</p>
<table>
@@ -609,7 +606,8 @@
</tr>
<tr>
<ti>
- <uri link="http://fatcat.ftj.agh.edu.pl/~nelchael/index.php?cat=projs&subcat=ncpufreqd&language=en">ncpufreqd</uri>
+ <uri
+ link="http://fatcat.ftj.agh.edu.pl/~nelchael/index.php?cat=projs&subcat=ncpufreqd&language=en">ncpufreqd</uri>
</ti>
<ti>Daemon</ti>
<ti>Temperature</ti>
@@ -659,7 +657,7 @@
While adjusting the frequency to the current load looks simple at a first
glance, it's not such a trivial task. A bad algorithm can cause switching
between two frequencies all the time or wasting energy when setting frequency
-to an unnecessary high level.
+to an unnecessary high level.
</p>
<p>
@@ -749,10 +747,10 @@
<p>
Sometimes it can be desirable to select another policy than the daemon chooses,
for example when battery power is low, but you know that AC will be available
-soon. In that case you can turn on cpufreqd's manual mode with
-<c>cpufreqd-set manual</c> and select one of your configured policies (as
-listed by <c>cpufreqd-get</c>). You can leave manual mode by executing
-<c>cpufreqd-set dynamic</c>.
+soon. In that case you can turn on cpufreqd's manual mode with <c>cpufreqd-set
+manual</c> and select one of your configured policies (as listed by
+<c>cpufreqd-get</c>). You can leave manual mode by executing <c>cpufreqd-set
+dynamic</c>.
</p>
<warn>
@@ -776,8 +774,8 @@
</pre>
<p>
-If <path>/proc/cpuinfo</path> doesn't get updated (see
-<uri link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with:
+If <path>/proc/cpuinfo</path> doesn't get updated (see <uri
+link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with:
</p>
<pre caption="Alternative CPU speed monitoring">
@@ -787,8 +785,8 @@
<p>
Depending on your setup, CPU speed should increase on heavy load, decrease on
no activity or just stay at the same level. When using <c>cpufreqd</c> and
-verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional
-information about what's happening reported to <c>syslog</c>.
+verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get
+additional information about what's happening reported to <c>syslog</c>.
</p>
</body>
@@ -801,11 +799,11 @@
<body>
<p>
-As you can see in <uri link="#doc_chap1_fig1">figure 1.1</uri>, the LCD display
-consumes the biggest part of energy (might not be the case for non-mobile
-CPU's). Thus it's quite important not only to shut the display off when not
-needed, but also to reduce it's backlight if possible. Most laptops offer the
-possibility to control the backlight dimming.
+As you can see in <uri link="#doc_chap1_fig1">figure 1.1</uri>, the LCD
+display consumes the biggest part of energy (might not be the case for
+non-mobile CPU's). Thus it's quite important not only to shut the display off
+when not needed, but also to reduce it's backlight if possible. Most laptops
+offer the possibility to control the backlight dimming.
</p>
</body>
@@ -817,7 +815,7 @@
<p>
The first thing to check is the standby/suspend/off timings of the display. As
this depends heavily on your windowmanager, I'll let you figure it out
-yourself. Just two common places: Blanking the terminal can be done with
+yourself. Just two common places: Blanking the terminal can be done with
<c>setterm -blank <number-of-minutesM></c>, <c>setterm -powersave on</c>
and <c>setterm -powerdown <number-of-minutesM></c>. For X.org, modify
<path>/etc/X11/xorg.conf</path> similar to this:
@@ -858,8 +856,9 @@
dimming settings via a tool, write a small script that dims the backlight in
battery mode and place it in your <c>battery</c> runlevel. The following script
should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
-appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops, install
-<c>app-laptop/acpitool</c> and skip configuration of <c>ibm_acpi</c> as described below.
+appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops,
+install <c>app-laptop/acpitool</c> and skip configuration of <c>ibm_acpi</c> as
+described below.
</p>
<warn>
@@ -884,8 +883,8 @@
<p>
This should work without error messages and a file
<path>/proc/acpi/ibm/brightness</path> should be created after loading the
-module. An init script will take care of choosing the brightness according
-to the power source.
+module. An init script will take care of choosing the brightness according to
+the power source.
</p>
<pre caption="/etc/conf.d/lcd-brightness">
@@ -1030,8 +1029,9 @@
<p>
To disable atd as suggested in the example above, you would run <c>rc-update
del atd battery</c>. Be careful not to disable services that are needed for
-your system to run properly - <c>lm-profiler</c> is likely to generate some false
-positives. Do not disable a service if you are unsure whether it's needed.
+your system to run properly - <c>lm-profiler</c> is likely to generate some
+false positives. Do not disable a service if you are unsure whether it's
+needed.
</p>
</body>
@@ -1045,8 +1045,9 @@
services that write to your disk frequently - <c>syslogd</c> is a good
candidate, for example. You probably don't want to shut it down completely, but
it's possible to modify the config file so that "unnecessary" things don't get
-logged and thus don't create disk traffic. <c>Cups</c> writes to disk periodically,
-so consider shutting it down and only enable it manually when needed.
+logged and thus don't create disk traffic. <c>Cups</c> writes to disk
+periodically, so consider shutting it down and only enable it manually when
+needed.
</p>
<pre caption="Disabling cups in battery mode">
@@ -1066,8 +1067,8 @@
<body>
<p>
-The second possibility is using a small script and <c>hdparm</c>. Skip this if you
-are using laptop-mode. Otherwise, create <path>/etc/init.d/pmg_hda</path>:
+The second possibility is using a small script and <c>hdparm</c>. Skip this if
+you are using laptop-mode. Otherwise, create <path>/etc/init.d/pmg_hda</path>:
</p>
<pre caption="Using hdparm for disk standby">
@@ -1155,9 +1156,9 @@
<p>
In case you own an ATI graphics card supporting PowerPlay (dynamic clock
scaling for the the graphics processing unit GPU), you can activate this
-feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable)
-the <c>DynamicClocks</c> option in the Device section. Please notice that
-this feature will lead to crashes on some systems.
+feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the
+<c>DynamicClocks</c> option in the Device section. Please notice that this
+feature will lead to crashes on some systems.
</p>
<pre caption="Enabling ATI PowerPlay support in X.org">
@@ -1225,7 +1226,7 @@
plugged in. You cannot avoid this (nevertheless remove them in case they're not
needed). Second, when there are USB devices plugged in, the USB host controller
periodically accesses the bus which in turn prevents the CPU from going into
-sleep mode. The kernel offers an experimental option to enable suspension of
+sleep mode. The kernel offers an experimental option to enable suspension of
USB devices through driver calls or one of the <path>power/state</path> files
in <path>/sys</path>.
</p>
@@ -1250,7 +1251,7 @@
ACPI defines different sleep states. The more important ones are
</p>
-<ul>
+<ul>
<li>S1 aka Standby</li>
<li>S3 aka Suspend to RAM aka Sleep</li>
<li>S4 aka Suspend to Disk aka Hibernate</li>
@@ -1317,9 +1318,9 @@
</pre>
<p>
-If you're still reading, it seems to work. You can also setup standby (S1) in
-a similar way by copying <path>ram.conf</path> to <path>standby.conf</path>
-and creating a symlink <path>/usr/sbin/hibernate-standby</path> pointing to
+If you're still reading, it seems to work. You can also setup standby (S1) in a
+similar way by copying <path>ram.conf</path> to <path>standby.conf</path> and
+creating a symlink <path>/usr/sbin/hibernate-standby</path> pointing to
<path>/usr/sbin/hibernate</path>. S3 and S4 are the more interesting sleep
states due to greater energy savings however.
</p>
@@ -1344,17 +1345,17 @@
<p>
There are two different implementations for S4. The original one is swsusp,
-then there is the newer suspend2 with a nicer interface (including
-fbsplash support). A <uri link="http://suspend2.net/features.html#compare">
-feature comparison</uri> is available at the <uri link="http://suspend2.net">
-suspend2 Homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of
-swsusp, but it has been merged back.
+then there is the newer suspend2 with a nicer interface (including fbsplash
+support). A <uri link="http://suspend2.net/features.html#compare"> feature
+comparison</uri> is available at the <uri link="http://suspend2.net"> suspend2
+Homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of swsusp,
+but it has been merged back.
</p>
<p>
Suspend2 is not included in the mainline kernel yet, therefore you either have
-to patch your kernel sources with the patches provided by
-<uri link="http://suspend2.net">suspend2.net</uri> or use
+to patch your kernel sources with the patches provided by <uri
+link="http://suspend2.net">suspend2.net</uri> or use
<c>sys-kernel/suspend2-sources</c>.
</p>
@@ -1368,7 +1369,7 @@
[*] Software Suspend
<comment>(replace /dev/SWAP with your swap partition)</comment>
(/dev/SWAP) Default resume partition
-
+
<comment>(hibernate with suspend2)</comment>
Software Suspend 2
--- Image Storage (you need at least one writer)
@@ -1386,8 +1387,8 @@
of your swap partition in the kernel config, you can also pass it as a
parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not
possible due to a broken image, use the <c>noresume</c> kernel parameter. The
-<c>hibernate-cleanup</c> init script invalidates swsusp images during the
-boot process.
+<c>hibernate-cleanup</c> init script invalidates swsusp images during the boot
+process.
</p>
<pre caption="Invalidating swsusp images during the boot process">
@@ -1404,7 +1405,7 @@
commands to have cached data written to disk. First try it outside of X, then
with X running, but not logged in.
</warn>
-
+
<p>
If you experience kernel panics due to uhci or similar, try to compile USB
support as module and unload the modules before sending your laptop to sleep
@@ -1423,9 +1424,9 @@
</p>
<p>
-The first part of the configuration is similar to the configuration of
-swsusp. In case you didn't store the location of your swap partition in the
-kernel config, you have to pass it as a kernel parameter with the
+The first part of the configuration is similar to the configuration of swsusp.
+In case you didn't store the location of your swap partition in the kernel
+config, you have to pass it as a kernel parameter with the
<c>resume2=swap:/dev/SWAP</c> directive. If booting is not possible due to a
broken image, append the <c>noresume2</c> parameter. Additionally, the
<c>hibernate-cleanup</c> init script invalidates suspend2 images during the
@@ -1436,9 +1437,10 @@
# <i>rc-update add hibernate-cleanup boot</i>
</pre>
-<p>Now edit <path>/etc/hibernate/hibernate.conf</path>, enable the
-<c>suspend2</c> section and comment everything in the <c>sysfs_power_state</c>
-and <c>acpi_sleep</c> sections. Do not enable the <c>fbsplash</c> part in global
+<p>
+Now edit <path>/etc/hibernate/hibernate.conf</path>, enable the <c>suspend2</c>
+section and comment everything in the <c>sysfs_power_state</c> and
+<c>acpi_sleep</c> sections. Do not enable the <c>fbsplash</c> part in global
options yet.
</p>
@@ -1449,9 +1451,10 @@
</pre>
<p>
-Please configure <c>fbsplash</c> now if you didn't do already. To enable fbsplash
-support during hibernation, the <c>sys-apps/suspend2-userui</c> package is
-needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag.
+Please configure <c>fbsplash</c> now if you didn't do already. To enable
+fbsplash support during hibernation, the <c>sys-apps/suspend2-userui</c>
+package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE
+flag.
</p>
<pre caption="Installing suspend2-userui">
@@ -1473,8 +1476,7 @@
If you don't want a black screen in the first part of the resume process, you
have to add the <c>suspend2ui_fbsplash</c> tool to your initrd image. Assuming
you created the initrd image with <c>splash_geninitramfs</c> and saved it as
-<path>/boot/fbsplash-emergence-1024x768</path>, here's how to do
-that.
+<path>/boot/fbsplash-emergence-1024x768</path>, here's how to do that.
</p>
<pre caption="Adding suspend2ui_fbsplash to an initrd image">
@@ -1489,8 +1491,8 @@
</pre>
<p>
-Afterwards adjust <path>grub.conf</path> respectively <path>lilo.conf</path>
-so that your suspend2 kernel uses
+Afterwards adjust <path>grub.conf</path> respectively <path>lilo.conf</path> so
+that your suspend2 kernel uses
<path>/boot/fbsplash-suspend2-emergence-1024x768</path> as initrd image. You
can now test a dry run to see if everything is setup correctly.
</p>
@@ -1552,8 +1554,8 @@
<p>
<e>A:</e> Probably you have activated symmetric multiprocessing support
(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older
-kernels had a bug causing this. In that case, run <c>emerge x86info</c>,
-update your kernel as asked and check the current frequency with
+kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update
+your kernel as asked and check the current frequency with
<c>x86info -mhz</c>.
</p>
@@ -1602,15 +1604,15 @@
</p>
<p>
-<e>Q:</e> My system logger reports things like "logger: ACPI group battery / action
-battery is not defined".
+<e>Q:</e> My system logger reports things like "logger: ACPI group battery /
+action battery is not defined".
</p>
<p>
-<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> script
-that is shipped with acpid. You can safely ignore it. If you like to get rid of it,
-you can comment the appropriate line in <path>/etc/acpi/default.sh</path> as shown
-below:
+<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path>
+script that is shipped with acpid. You can safely ignore it. If you like to get
+rid of it, you can comment the appropriate line in
+<path>/etc/acpi/default.sh</path> as shown below:
</p>
<pre caption="Disabling warnings about unknown acpi events">
@@ -1627,13 +1629,14 @@
</p>
<p>
-<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path> and
-now X.org crashes / the screen stays black / my laptop doesn't shutdown
+<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path>
+and now X.org crashes / the screen stays black / my laptop doesn't shutdown
properly.
</p>
<p>
-<e>A:</e> This happens on some systems. You have to disable <c>DynamicClocks</c>.
+<e>A:</e> This happens on some systems. You have to disable
+<c>DynamicClocks</c>.
</p>
<p>
@@ -1642,7 +1645,7 @@
</p>
<p>
-<e>A:</e> If there is enough free space on your system, you can use the
+<e>A:</e> If there is enough free space on your system, you can use the
filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it
as well. More information can be found in
<path>/usr/src/linux/Documentation/power/suspend2.txt</path>.
@@ -1655,7 +1658,7 @@
<p>
<e>A:</e> First follow your manufacturer's advice on how to charge the battery
-correctly.
+correctly.
</p>
<p>
@@ -1683,10 +1686,10 @@
<p>
<e>A:</e> Don't fear to contact me, <mail link="earthwings@gentoo.org">Dennis
-Nienhüser</mail>, directly. The
-<uri link="http://forums.gentoo.org">Gentoo Forums</uri> are a good place to
-get help as well. If you prefer IRC, try the <c>#gentoo-laptop</c> channel at
-<uri link="irc://irc.freenode.net">irc.freenode.net</uri>.
+Nienhüser</mail>, directly. The <uri link="http://forums.gentoo.org">Gentoo
+Forums</uri> are a good place to get help as well. If you prefer IRC, try the
+<c>#gentoo-laptop</c> channel at <uri
+link="irc://irc.freenode.net">irc.freenode.net</uri>.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-08-17 0:45 Lukasz Damentko
0 siblings, 0 replies; 20+ messages in thread
From: Lukasz Damentko @ 2006-08-17 0:45 UTC (permalink / raw
To: gentoo-doc-cvs
rane 06/08/17 00:45:29
Modified: power-management-guide.xml
Log:
#144153, typos
Revision Changes Path
1.21 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.20&r2=1.21
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- power-management-guide.xml 27 Jul 2006 08:23:01 -0000 1.20
+++ power-management-guide.xml 17 Aug 2006 00:45:29 -0000 1.21
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.20 2006/07/27 08:23:01 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.21 2006/08/17 00:45:29 rane Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -63,7 +63,7 @@
that typically consume most energy - processor, display and hard drive. Each
can be configured seperately. <uri link="#doc_chap3">CPU Power Management</uri>
shows how to adjust the processor's frequency to save a maximum of energy
-whithout losing too much performance. A few different tricks prevent your hard
+without losing too much performance. A few different tricks prevent your hard
drive from working unnecessarily often in <uri link="#doc_chap5">Disk Power
Management</uri> (decreasing noise level as a nice side effect). Some notes on
graphics cards, Wireless LAN and USB finish the device section in <uri
@@ -524,7 +524,7 @@
The above is quite nice, but not doable in daily life. Better let your system
set the appropriate frequency automatically. There are many different
approaches to do this. The following table gives a quick overview to help you
-decide on one of them. It's roughly seperated in three categories <b>kernel</b>
+decide on one of them. It's roughly separated in three categories <b>kernel</b>
for approaches that only need kernel support, <b>daemon</b> for programs that
run in the background and <b>graphical</b> for programs that provide a GUI for
easy configuration and changes.
@@ -1137,7 +1137,7 @@
<warn>
Pay attention to the size parameter and modify it for your system. If you're
-unsure, don't try this at all, it can become a perfomance bottleneck easily. In
+unsure, don't try this at all, it can become a performance bottleneck easily. In
case you want to mount <path>/var/log</path> like this, make sure to merge the
log files to disk before unmounting. They are essential. Don't attempt to mount
<path>/var/tmp</path> like this. Portage uses it for compiling...
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-10-23 3:40 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2006-10-23 3:40 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/10/23 03:40:54
Modified: power-management-guide.xml
Log:
ex-dev correction
Revision Changes Path
1.22 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.21&r2=1.22
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- power-management-guide.xml 17 Aug 2006 00:45:29 -0000 1.21
+++ power-management-guide.xml 23 Oct 2006 03:40:54 -0000 1.22
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.21 2006/08/17 00:45:29 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.22 2006/10/23 03:40:54 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -20,8 +20,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.28</version>
-<date>2006-07-26</date>
+<version>1.29</version>
+<date>2006-10-22</date>
<chapter>
<title>Introduction</title>
@@ -671,9 +671,9 @@
<p>
<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>.
The default one that ships with cpufreqd may look a bit confusing. I recommend
-replacing it with the one from Gentoo developer Henrik Brix Andersen (see
-below). Please notice that you need cpufreqd-2.0.0 or later. Earlier versions
-have a different syntax for the config file.
+replacing it with the one from former Gentoo developer Henrik Brix Andersen
+(see below). Please notice that you need cpufreqd-2.0.0 or later. Earlier
+versions have a different syntax for the config file.
</p>
<pre caption="/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2006-12-17 3:42 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2006-12-17 3:42 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/12/17 03:42:50
Modified: power-management-guide.xml
Log:
updated power management guide for bug 158290
Revision Changes Path
1.23 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.23&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.22&r2=1.23
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- power-management-guide.xml 23 Oct 2006 03:40:54 -0000 1.22
+++ power-management-guide.xml 17 Dec 2006 03:42:50 -0000 1.23
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.22 2006/10/23 03:40:54 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.23 2006/12/17 03:42:50 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -20,8 +20,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.29</version>
-<date>2006-10-22</date>
+<version>1.30</version>
+<date>2006-12-16</date>
<chapter>
<title>Introduction</title>
@@ -857,7 +857,7 @@
battery mode and place it in your <c>battery</c> runlevel. The following script
should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops,
-install <c>app-laptop/acpitool</c> and skip configuration of <c>ibm_acpi</c> as
+install <c>sys-power/acpitool</c> and skip configuration of <c>ibm_acpi</c> as
described below.
</p>
@@ -891,7 +891,7 @@
<comment># See /proc/acpi/ibm/brightness for available values</comment>
<comment># Please read /usr/src/linux/Documentation/ibm-acpi.txt</comment>
-<comment># brigthness level in ac mode. Default is 7.</comment>
+<comment># brightness level in ac mode. Default is 7.</comment>
BRIGHTNESS_AC=7
<comment># brightness level in battery mode. Default is 4.</comment>
@@ -922,7 +922,7 @@
else
ewarn "Setting LCD brightness is not supported."
ewarn "For IBM Thinkpads, check that ibm_acpi is loaded into the kernel"
- ewarn "For Toshiba laptops, you've got to install app-laptop/acpitool"
+ ewarn "For Toshiba laptops, you've got to install sys-power/acpitool"
fi
}
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-02-20 17:44 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-02-20 17:44 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/02/20 17:44:15
Modified: power-management-guide.xml
Log:
updated power management guide for the new hibernate-script configuration, bug 167098
Revision Changes Path
1.24 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.23&r2=1.24
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- power-management-guide.xml 17 Dec 2006 03:42:50 -0000 1.23
+++ power-management-guide.xml 20 Feb 2007 17:44:15 -0000 1.24
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.23 2006/12/17 03:42:50 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.24 2007/02/20 17:44:15 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -20,8 +20,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.30</version>
-<date>2006-12-16</date>
+<version>1.31</version>
+<date>2007-02-20</date>
<chapter>
<title>Introduction</title>
@@ -1294,19 +1294,26 @@
<p>
Some configuration has to be done in <path>/etc/hibernate</path> The default
-package introduces two configuration files <path>hibernate.conf</path> and
-<path>ram.conf</path>.
+package introduces a few configuration files for each sleep state. Options that
+are common to all suspend methods are placed in <path>common.conf</path>; make
+sure this file is properly set up for your system.
</p>
<p>
-To configure sleep, edit <path>ram.conf</path> in <path>/etc/hibernate</path>.
-<c>UseSysfsPowerState mem</c> is already setup correctly, but you have to go
-through the rest of the configuration file and set it up for your system. The
-comments and option names will guide you. If you use nfs or samba shares over
-the network, make sure to shutdown the appropriate init scripts to avoid
-timeouts.
+To configure sleep, edit <path>sysfs-ram.conf</path> in
+<path>/etc/hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup
+correctly, but you need to make further changes to this particular sleep state
+(or any other sleep state) you should add them to
+<path>/etc/hibernate/hibernate.conf</path>. The comments and option names will
+guide you. If you use nfs or samba shares over the network, make sure to
+shutdown the appropriate init scripts to avoid timeouts.
</p>
+<note>
+For more information on setting up sleep states, read <c>man
+hibernate.conf</c>.
+</note>
+
<p>
Ready? Now is the last chance to backup any data you want to keep after
executing the next command. Notice that you probably have to hit a special key
@@ -1319,10 +1326,9 @@
<p>
If you're still reading, it seems to work. You can also setup standby (S1) in a
-similar way by copying <path>ram.conf</path> to <path>standby.conf</path> and
-creating a symlink <path>/usr/sbin/hibernate-standby</path> pointing to
-<path>/usr/sbin/hibernate</path>. S3 and S4 are the more interesting sleep
-states due to greater energy savings however.
+similar way by editing <path>sysfs-ram.conf</path> and changing
+"UseSysfsPowerState mem" to "UseSysfsPowerState standby". S3 and S4 are the more
+interesting sleep states due to greater energy savings however.
</p>
</body>
@@ -1397,7 +1403,7 @@
<p>
To activate hibernate with swsusp, use the hibernate script and set
-<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/hibernate.conf</path>.
+<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>.
</p>
<warn>
@@ -1409,11 +1415,11 @@
<p>
If you experience kernel panics due to uhci or similar, try to compile USB
support as module and unload the modules before sending your laptop to sleep
-mode. There are configuration options for this in <path>hibernate.conf</path>
+mode. There are configuration options for this in <path>common.conf</path>
</p>
<pre caption="Hibernating with swsusp">
-# <i>nano -w /etc/hibernate.conf</i>
+# <i>nano -w /etc/hibernate/common.conf</i>
<comment>(Make sure you have a backup of your data)</comment>
# <i>hibernate</i>
</pre>
@@ -1438,14 +1444,13 @@
</pre>
<p>
-Now edit <path>/etc/hibernate/hibernate.conf</path>, enable the <c>suspend2</c>
-section and comment everything in the <c>sysfs_power_state</c> and
-<c>acpi_sleep</c> sections. Do not enable the <c>fbsplash</c> part in global
-options yet.
+Now edit <path>/etc/hibernate/suspend2.conf</path>, enable the <c>suspend2</c>
+options you need. Do not enable the <c>fbsplash</c> options in
+<c>common.conf</c> just yet.
</p>
<pre caption="Hibernating with suspend2">
-# <i>nano -w /etc/hibernate.conf</i>
+# <i>nano -w /etc/hibernate/suspend2.conf</i>
<comment>(Make sure you have a backup of your data)</comment>
# <i>hibernate</i>
</pre>
@@ -1458,8 +1463,9 @@
</p>
<pre caption="Installing suspend2-userui">
-# <i>mkdir -p /etc/portage</i>
# <i>echo "sys-apps/suspend2-userui fbsplash" >> /etc/portage/package.use</i>
+<comment>(It may be marked ~arch, so first it must be keyworded)</comment>
+# <i>echo "sys-apps/suspend2-userui" >> /etc/portage/package.keywords</i>
# <i>emerge suspend2-userui</i>
</pre>
@@ -1491,10 +1497,10 @@
</pre>
<p>
-Afterwards adjust <path>grub.conf</path> respectively <path>lilo.conf</path> so
-that your suspend2 kernel uses
-<path>/boot/fbsplash-suspend2-emergence-1024x768</path> as initrd image. You
-can now test a dry run to see if everything is setup correctly.
+Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that
+your suspend2 kernel uses
+<path>/boot/fbsplash-suspend2-emergence-1024x768</path> as initrd image. You can
+now test a dry run to see if everything is setup correctly.
</p>
<pre caption="Test run for fbsplash hibernation">
@@ -1502,8 +1508,8 @@
</pre>
<p>
-Afterwards open <path>/etc/hibernate/hibernate.conf</path> again and activate
-the fbsplash options. Execute <c>hibernate</c> and enjoy.
+Afterwards open <path>/etc/hibernate/common.conf</path> and activate the
+fbsplash options. Execute <c>hibernate</c> and enjoy.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-03-15 19:24 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-03-15 19:24 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/03/15 19:24:34
Modified: power-management-guide.xml
Log:
typo fixes, no content change, bug 171068. thanks to kucrut for reporting and rane for ... rane for... rane for something. he was there at the time. :)
Revision Changes Path
1.25 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.24&r2=1.25
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- power-management-guide.xml 20 Feb 2007 17:44:15 -0000 1.24
+++ power-management-guide.xml 15 Mar 2007 19:24:34 -0000 1.25
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.24 2007/02/20 17:44:15 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.25 2007/03/15 19:24:34 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -1155,7 +1155,7 @@
<p>
In case you own an ATI graphics card supporting PowerPlay (dynamic clock
-scaling for the the graphics processing unit GPU), you can activate this
+scaling for the graphics processing unit GPU), you can activate this
feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the
<c>DynamicClocks</c> option in the Device section. Please notice that this
feature will lead to crashes on some systems.
@@ -1293,7 +1293,7 @@
</pre>
<p>
-Some configuration has to be done in <path>/etc/hibernate</path> The default
+Some configuration has to be done in <path>/etc/hibernate</path>. The default
package introduces a few configuration files for each sleep state. Options that
are common to all suspend methods are placed in <path>common.conf</path>; make
sure this file is properly set up for your system.
@@ -1302,8 +1302,8 @@
<p>
To configure sleep, edit <path>sysfs-ram.conf</path> in
<path>/etc/hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup
-correctly, but you need to make further changes to this particular sleep state
-(or any other sleep state) you should add them to
+correctly, but if you need to make further changes to this particular sleep
+state (or any other sleep state) you should add them to
<path>/etc/hibernate/hibernate.conf</path>. The comments and option names will
guide you. If you use nfs or samba shares over the network, make sure to
shutdown the appropriate init scripts to avoid timeouts.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-05-30 19:09 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-05-30 19:09 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/30 19:09:04
Modified: power-management-guide.xml
Log:
removed stuff about nonexistent 2.4 kernels
Revision Changes Path
1.27 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.26&r2=1.27
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- power-management-guide.xml 16 Apr 2007 05:39:54 -0000 1.26
+++ power-management-guide.xml 30 May 2007 19:09:04 -0000 1.27
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.26 2007/04/16 05:39:54 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.27 2007/05/30 19:09:04 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.32</version>
-<date>2007-04-15</date>
+<version>1.33</version>
+<date>2007-05-30</date>
<chapter>
<title>Introduction</title>
@@ -977,10 +977,9 @@
<body>
<p>
-Recent kernels (2.6.6 and greater, recent 2.4 ones and others with patches)
-include the so-called <c>laptop-mode</c>. When activated, dirty buffers are
-written to disk on read calls or after 10 minutes (instead of 30 seconds). This
-minimizes the time the hard disk needs to be spun up.
+Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated,
+dirty buffers are written to disk on read calls or after 10 minutes (instead of
+30 seconds). This minimizes the time the hard disk needs to be spun up.
</p>
<pre caption="Automated start of laptop-mode">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-07-08 7:48 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-07-08 7:48 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/07/08 07:48:13
Modified: power-management-guide.xml
Log:
updated power management guide for bug 184215
Revision Changes Path
1.28 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.28&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.28&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.27&r2=1.28
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- power-management-guide.xml 30 May 2007 19:09:04 -0000 1.27
+++ power-management-guide.xml 8 Jul 2007 07:48:12 -0000 1.28
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.27 2007/05/30 19:09:04 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.28 2007/07/08 07:48:12 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.33</version>
-<date>2007-05-30</date>
+<version>1.34</version>
+<date>2007-07-08</date>
<chapter>
<title>Introduction</title>
@@ -1069,39 +1069,32 @@
<body>
<p>
-The second possibility is using a small script and <c>hdparm</c>. Skip this if
-you are using laptop-mode. Otherwise, create <path>/etc/init.d/pmg_hda</path>:
+The second possibility is using <c>hdparm</c>. Skip this if
+you are using laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and
+add the following values to your drive entries. This example assumes your hard
+drive is called <b>hda</b>:
</p>
-<pre caption="Using hdparm for disk standby">
-#!/sbin/runscript
-
-depend() {
-after hdparm
-}
-
-start() {
-ebegin "Activating Power Management for Hard Drives"
-hdparm -q -S12 /dev/hda
-eend $?
-}
-
-stop () {
-ebegin "Deactivating Power Management for Hard Drives"
-hdparm -q -S253 /dev/hda
-eend $?
-}
+<pre caption="Using /etc/conf.d/hdparm for disk standby">
+hda_args="-q -S12"
</pre>
<p>
-See <c>man hdparm</c> for the options. If your script is ready, add it to the
-battery runlevel.
+This will activate power management for your hard drive. If you ever want to
+deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> and
+change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/hda</c>.
+</p>
+
+<p>
+See <c>man hdparm</c> for the options. Though you can always start <c>hdparm</c>
+manually when you are on battery power by running <c>/etc/init.d/hdparm
+start</c>, it's much easier to automate its startup and shutdown. To do so, add
+<c>hdparm</c> to the battery runlevel so that it will automatically enable power
+management.
</p>
<pre caption="Automate disk standby settings">
-# <i>chmod +x /etc/init.d/pmg_hda</i>
-# <i>/sbin/depscan.sh</i>
-# <i>rc-update add pmg_hda battery</i>
+# <i>rc-update add hdparm battery</i>
</pre>
<impo>
@@ -1178,7 +1171,7 @@
<p>
Wireless LAN cards consume quite a bit of energy. Put them in Power Management
-mode in analogy to the <c>pmg_hda</c> script.
+mode just like your hard drives.
</p>
<note>
@@ -1186,36 +1179,21 @@
this with the actual name of your interface.
</note>
-<pre caption="WLAN Power Management automated">
-#!/sbin/runscript
-start() {
- ebegin "Activating Power Management for Wireless LAN"
- iwconfig wlan0 power on
- eend $?
-}
+<p>
+Add the following script to <path>/etc/conf.d/net</path> to automatically enable
+power management for your wireless card:
+</p>
-stop () {
- ebegin "Deactivating Power Management for Wireless LAN"
- iwconfig wlan0 power off
- eend $?
-}
+<pre caption="Automated WLAN Power Management">
+iwconfig_wlan0="power on"
</pre>
<p>
-Starting this script will activate power saving features for wlan0. Save it as
-<path>/etc/init.d/pmg_wlan0</path> and add it to the battery runlevel like the
-disk script above. See <c>man iwconfig</c> for details and more options like
-the period between wakeups or timeout settings. If your driver and access point
-support changing the beacon time, this is a good starting point to save even
-more energy.
+See <c>man iwconfig</c> for details and more options like the period between
+wakeups or timeout settings. If your driver and access point support changing
+the beacon time, this is a good starting point to save even more energy.
</p>
-<pre caption="Power Management for WLAN">
-# <i>chmod +x /etc/init.d/pmg_wlan0</i>
-# <i>/sbin/depscan.sh</i>
-# <i>rc-update add pmg_wlan0 battery</i>
-</pre>
-
</body>
</section>
<section>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-07-08 17:51 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-07-08 17:51 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/07/08 17:51:23
Modified: power-management-guide.xml
Log:
typo fix that i forgot to change in the last commit to the file. s/script/option, thanks to cla for noticing on IRC
Revision Changes Path
1.29 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.29&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.29&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.28&r2=1.29
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- power-management-guide.xml 8 Jul 2007 07:48:12 -0000 1.28
+++ power-management-guide.xml 8 Jul 2007 17:51:23 -0000 1.29
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.28 2007/07/08 07:48:12 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.29 2007/07/08 17:51:23 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -1180,7 +1180,7 @@
</note>
<p>
-Add the following script to <path>/etc/conf.d/net</path> to automatically enable
+Add the following option to <path>/etc/conf.d/net</path> to automatically enable
power management for your wireless card:
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-07-24 22:32 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-07-24 22:32 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/07/24 22:32:59
Modified: power-management-guide.xml
Log:
removed outdated hyperlink, bug 186530
Revision Changes Path
1.30 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.29&r2=1.30
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- power-management-guide.xml 8 Jul 2007 17:51:23 -0000 1.29
+++ power-management-guide.xml 24 Jul 2007 22:32:59 -0000 1.30
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.29 2007/07/08 17:51:23 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.30 2007/07/24 22:32:59 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.34</version>
-<date>2007-07-08</date>
+<version>1.35</version>
+<date>2007-07-24</date>
<chapter>
<title>Introduction</title>
@@ -608,10 +608,7 @@
</ti>
</tr>
<tr>
- <ti>
- <uri
- link="http://fatcat.ftj.agh.edu.pl/~nelchael/index.php?cat=projs&subcat=ncpufreqd&language=en">ncpufreqd</uri>
- </ti>
+ <ti>ncpufreqd</ti>
<ti>Daemon</ti>
<ti>Temperature</ti>
<ti>None</ti>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-10-03 17:27 Josh Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Josh Saddler @ 2007-10-03 17:27 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/10/03 17:27:58
Modified: power-management-guide.xml
Log:
added ncpufreqd homepage, bug 186530
Revision Changes Path
1.31 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.31&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.31&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.30&r2=1.31
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- power-management-guide.xml 24 Jul 2007 22:32:59 -0000 1.30
+++ power-management-guide.xml 3 Oct 2007 17:27:58 -0000 1.31
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.30 2007/07/24 22:32:59 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.31 2007/10/03 17:27:58 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.35</version>
-<date>2007-07-24</date>
+<version>1.36</version>
+<date>2007-10-03</date>
<chapter>
<title>Introduction</title>
@@ -608,7 +608,10 @@
</ti>
</tr>
<tr>
- <ti>ncpufreqd</ti>
+ <ti>
+ <uri
+ link="http://projects.simpledesigns.com.pl/project/ncpufreqd/">ncpufreqd</uri>
+ </ti>
<ti>Daemon</ti>
<ti>Temperature</ti>
<ti>None</ti>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2007-12-03 19:31 Sven Vermeulen
0 siblings, 0 replies; 20+ messages in thread
From: Sven Vermeulen @ 2007-12-03 19:31 UTC (permalink / raw
To: gentoo-doc-cvs
swift 07/12/03 19:31:10
Modified: power-management-guide.xml
Log:
#198822 - ACPI events are in messages, also state where x86info is found
Revision Changes Path
1.32 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.32&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.32&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.31&r2=1.32
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- power-management-guide.xml 3 Oct 2007 17:27:58 -0000 1.31
+++ power-management-guide.xml 3 Dec 2007 19:31:10 -0000 1.32
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.31 2007/10/03 17:27:58 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.32 2007/12/03 19:31:10 swift Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.36</version>
-<date>2007-10-03</date>
+<version>1.37</version>
+<date>2007-12-03</date>
<chapter>
<title>Introduction</title>
@@ -336,7 +336,7 @@
</p>
<pre caption="Determining ACPI events for changing the power source">
-# <i>tail -f /var/log/acpid | grep "received event"</i>
+# <i>tail -f /var/log/messages | grep "received event"</i>
</pre>
<p>
@@ -778,7 +778,8 @@
<p>
If <path>/proc/cpuinfo</path> doesn't get updated (see <uri
-link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with:
+link="#doc_chap8">Troubleshooting</uri>), monitor the CPU frequency with
+<c>sys-apps/x86info</c>:
</p>
<pre caption="Alternative CPU speed monitoring">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2008-01-21 12:12 Jan Kundrat
0 siblings, 0 replies; 20+ messages in thread
From: Jan Kundrat @ 2008-01-21 12:12 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 08/01/21 12:12:12
Modified: power-management-guide.xml
Log:
TuxOnIce is new name of former suspend2 (reported by calchan)
Revision Changes Path
1.33 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.33&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.33&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.32&r2=1.33
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- power-management-guide.xml 3 Dec 2007 19:31:10 -0000 1.32
+++ power-management-guide.xml 21 Jan 2008 12:12:12 -0000 1.33
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.32 2007/12/03 19:31:10 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.33 2008/01/21 12:12:12 jkt Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.37</version>
-<date>2007-12-03</date>
+<version>1.38</version>
+<date>2008-01-21</date>
<chapter>
<title>Introduction</title>
@@ -154,8 +154,8 @@
<p>
There are different kernel sources in Portage. I'd recommend using
-<c>gentoo-sources</c> or <c>suspend2-sources</c>. The latter contains patches
-for Software Suspend 2, see the chapter about <uri link="#doc_chap7">sleep
+<c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches
+for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep
states</uri> for more details. When configuring the kernel, activate at least
these options:
</p>
@@ -1332,22 +1332,22 @@
<p>
There are two different implementations for S4. The original one is swsusp,
-then there is the newer suspend2 with a nicer interface (including fbsplash
-support). A <uri link="http://suspend2.net/features.html#compare"> feature
-comparison</uri> is available at the <uri link="http://suspend2.net"> suspend2
+then there is the newer tuxonice (former suspend2) with a nicer interface (including fbsplash
+support). A <uri link="http://tuxonice.net/features.html#compare"> feature
+comparison</uri> is available at the <uri link="http://www.tuxonice.net">tuxonice
Homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of swsusp,
but it has been merged back.
</p>
<p>
-Suspend2 is not included in the mainline kernel yet, therefore you either have
+TuxOnIce is not included in the mainline kernel yet, therefore you either have
to patch your kernel sources with the patches provided by <uri
-link="http://suspend2.net">suspend2.net</uri> or use
-<c>sys-kernel/suspend2-sources</c>.
+link="http://tuxonice.net">tuxonice.net</uri> or use
+<c>sys-kernel/tuxonice-sources</c>.
</p>
<p>
-The kernel part for both swusp and suspend2 is as follows:
+The kernel part for both swusp and TuxOnIce is as follows:
</p>
<pre caption="Kernel configuration for the various suspend types">
@@ -1357,8 +1357,8 @@
<comment>(replace /dev/SWAP with your swap partition)</comment>
(/dev/SWAP) Default resume partition
- <comment>(hibernate with suspend2)</comment>
- Software Suspend 2
+ <comment>(hibernate with TuxOnIce)</comment>
+ Enhanced Hibernation (TuxOnIce)
--- Image Storage (you need at least one writer)
[*] File Writer
[*] Swap Writer
@@ -1406,7 +1406,7 @@
</pre>
<p>
-The following section discusses the setup of suspend2 including fbsplash
+The following section discusses the setup of TuxOnIce including fbsplash
support for a nice graphical progress bar during suspend and resume.
</p>
@@ -1414,23 +1414,23 @@
The first part of the configuration is similar to the configuration of swsusp.
In case you didn't store the location of your swap partition in the kernel
config, you have to pass it as a kernel parameter with the
-<c>resume2=swap:/dev/SWAP</c> directive. If booting is not possible due to a
-broken image, append the <c>noresume2</c> parameter. Additionally, the
-<c>hibernate-cleanup</c> init script invalidates suspend2 images during the
+<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a
+broken image, append the <c>noresume</c> parameter. Additionally, the
+<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the
boot process.
</p>
-<pre caption="Invalidating suspend2 images during the boot process">
+<pre caption="Invalidating TuxOnIce images during the boot process">
# <i>rc-update add hibernate-cleanup boot</i>
</pre>
<p>
-Now edit <path>/etc/hibernate/suspend2.conf</path>, enable the <c>suspend2</c>
+Now edit <path>/etc/hibernate/suspend2.conf</path>, enable the <c>TuxOnIce</c>
options you need. Do not enable the <c>fbsplash</c> options in
<c>common.conf</c> just yet.
</p>
-<pre caption="Hibernating with suspend2">
+<pre caption="Hibernating with TuxOnIce">
# <i>nano -w /etc/hibernate/suspend2.conf</i>
<comment>(Make sure you have a backup of your data)</comment>
# <i>hibernate</i>
@@ -1438,16 +1438,16 @@
<p>
Please configure <c>fbsplash</c> now if you didn't do already. To enable
-fbsplash support during hibernation, the <c>sys-apps/suspend2-userui</c>
+fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c>
package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE
flag.
</p>
-<pre caption="Installing suspend2-userui">
-# <i>echo "sys-apps/suspend2-userui fbsplash" >> /etc/portage/package.use</i>
+<pre caption="Installing tuxonice-userui">
+# <i>echo "sys-apps/tuxonice-userui fbsplash" >> /etc/portage/package.use</i>
<comment>(It may be marked ~arch, so first it must be keyworded)</comment>
-# <i>echo "sys-apps/suspend2-userui" >> /etc/portage/package.keywords</i>
-# <i>emerge suspend2-userui</i>
+# <i>echo "sys-apps/tuxonice-userui" >> /etc/portage/package.keywords</i>
+# <i>emerge tuxonice-userui</i>
</pre>
<p>
@@ -1461,31 +1461,31 @@
<p>
If you don't want a black screen in the first part of the resume process, you
-have to add the <c>suspend2ui_fbsplash</c> tool to your initrd image. Assuming
+have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. Assuming
you created the initrd image with <c>splash_geninitramfs</c> and saved it as
<path>/boot/fbsplash-emergence-1024x768</path>, here's how to do that.
</p>
-<pre caption="Adding suspend2ui_fbsplash to an initrd image">
+<pre caption="Adding tuxoniceui_fbsplash to an initrd image">
# <i>mount /boot</i>
# <i>mkdir ~/initrd.d</i>
# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>
# <i>cd ~/initrd.d</i>
# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>
# <i>rm fbsplash-emergence-1024x768</i>
-# <i>cp /usr/sbin/suspend2ui_fbsplash sbin/</i>
-# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-suspend2-emergence-1024x768</i>
+# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>
+# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-tuxonice-emergence-1024x768</i>
</pre>
<p>
Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that
-your suspend2 kernel uses
-<path>/boot/fbsplash-suspend2-emergence-1024x768</path> as initrd image. You can
+your TuxOnIce kernel uses
+<path>/boot/fbsplash-tuxonice-emergence-1024x768</path> as initrd image. You can
now test a dry run to see if everything is setup correctly.
</p>
<pre caption="Test run for fbsplash hibernation">
-# <i>suspend2ui_fbsplash -t</i>
+# <i>tuxoniceui_fbsplash -t</i>
</pre>
<p>
@@ -1627,7 +1627,7 @@
</p>
<p>
-<e>Q:</e> I want to use suspend2, but it tells me my swap partition is too
+<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too
small. Resizing is not an option.
</p>
@@ -1635,7 +1635,7 @@
<e>A:</e> If there is enough free space on your system, you can use the
filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it
as well. More information can be found in
-<path>/usr/src/linux/Documentation/power/suspend2.txt</path>.
+<path>/usr/src/linux/Documentation/power/tuxonice.txt</path>.
</p>
<p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2008-01-21 12:15 Jan Kundrat
0 siblings, 0 replies; 20+ messages in thread
From: Jan Kundrat @ 2008-01-21 12:15 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 08/01/21 12:15:56
Modified: power-management-guide.xml
Log:
whitespace stuff and line wrapping, *no content change*
Revision Changes Path
1.34 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.34&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.34&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.33&r2=1.34
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- power-management-guide.xml 21 Jan 2008 12:12:12 -0000 1.33
+++ power-management-guide.xml 21 Jan 2008 12:15:56 -0000 1.34
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.33 2008/01/21 12:12:12 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.34 2008/01/21 12:15:56 jkt Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -155,9 +155,8 @@
<p>
There are different kernel sources in Portage. I'd recommend using
<c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches
-for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep
-states</uri> for more details. When configuring the kernel, activate at least
-these options:
+for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep states</uri>
+for more details. When configuring the kernel, activate at least these options:
</p>
<pre caption="Minimum kernel setup for Power Management (Kernel 2.6)">
@@ -1406,8 +1405,8 @@
</pre>
<p>
-The following section discusses the setup of TuxOnIce including fbsplash
-support for a nice graphical progress bar during suspend and resume.
+The following section discusses the setup of TuxOnIce including fbsplash support
+for a nice graphical progress bar during suspend and resume.
</p>
<p>
@@ -1416,8 +1415,8 @@
config, you have to pass it as a kernel parameter with the
<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a
broken image, append the <c>noresume</c> parameter. Additionally, the
-<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the
-boot process.
+<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the boot
+process.
</p>
<pre caption="Invalidating TuxOnIce images during the boot process">
@@ -1438,9 +1437,8 @@
<p>
Please configure <c>fbsplash</c> now if you didn't do already. To enable
-fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c>
-package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE
-flag.
+fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> package
+is needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag.
</p>
<pre caption="Installing tuxonice-userui">
@@ -1511,15 +1509,14 @@
<p>
<e>A:</e> Make sure your processor supports CPU frequency scaling and you chose
the right CPUFreq driver for your processor. Here is a list of processors that
-are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100,
-ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD
-mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm,
-Intel mobile PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4,
-Intel Xeon, Intel Pentium M (Centrino), National Semiconductors Geode GX,
-Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several
-"PowerBook" and "iBook2" and various processors on some ACPI 2.0-compatible
-systems (only if "ACPI Processor Performance States" are available to the
-ACPI/BIOS interface).
+are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, ARM-SA1110,
+AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD mobile Duron,
+AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, Intel mobile
+PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, Intel Xeon,
+Intel Pentium M (Centrino), National Semiconductors Geode GX, Transmeta Crusoe,
+VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several "PowerBook" and
+"iBook2" and various processors on some ACPI 2.0-compatible systems (only if
+"ACPI Processor Performance States" are available to the ACPI/BIOS interface).
</p>
<p>
@@ -1542,8 +1539,7 @@
<e>A:</e> Probably you have activated symmetric multiprocessing support
(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older
kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update
-your kernel as asked and check the current frequency with
-<c>x86info -mhz</c>.
+your kernel as asked and check the current frequency with <c>x86info -mhz</c>.
</p>
<p>
@@ -1553,11 +1549,11 @@
<p>
<e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower
-minimum frequency. Notice that throttling doesn't save much energy and is
-mainly used for thermal management (keeping your laptop cool and quiet). You
-can read the current throttling state with <c>cat
-/proc/acpi/processor/CPU/throttling</c> and change it with <c>echo -n "0:x" >
-/proc/acpi/processor/CPU/limit</c>, where x is one of the Tx states listed in
+minimum frequency. Notice that throttling doesn't save much energy and is mainly
+used for thermal management (keeping your laptop cool and quiet). You can read
+the current throttling state with <c>cat /proc/acpi/processor/CPU/throttling</c>
+and change it with <c>echo -n "0:x" > /proc/acpi/processor/CPU/limit</c>, where
+x is one of the Tx states listed in
<path>/proc/acpi/processor/CPU/throttling</path>.
</p>
@@ -1633,8 +1629,8 @@
<p>
<e>A:</e> If there is enough free space on your system, you can use the
-filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it
-as well. More information can be found in
+filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it as
+well. More information can be found in
<path>/usr/src/linux/Documentation/power/tuxonice.txt</path>.
</p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2008-01-31 23:38 Joshua Saddler
0 siblings, 0 replies; 20+ messages in thread
From: Joshua Saddler @ 2008-01-31 23:38 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 08/01/31 23:38:05
Modified: power-management-guide.xml
Log:
bring it a little more up to date. punt outdated Xfree86 references. ibm_acpi is now known as thinkpad_acpi. for xorg.conf, DPMS is no longer a boolean variable, and screen blank settings have been moved to a different section.
Revision Changes Path
1.35 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.35&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.35&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.34&r2=1.35
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- power-management-guide.xml 21 Jan 2008 12:15:56 -0000 1.34
+++ power-management-guide.xml 31 Jan 2008 23:38:05 -0000 1.35
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.34 2008/01/21 12:15:56 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.35 2008/01/31 23:38:05 nightmorph Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.38</version>
-<date>2008-01-21</date>
+<version>1.39</version>
+<date>2008-01-31</date>
<chapter>
<title>Introduction</title>
@@ -824,14 +824,12 @@
<path>/etc/X11/xorg.conf</path> similar to this:
</p>
-<pre caption="LCD suspend settings in X.org and XFree86">
-Section "ServerLayout"
- Identifier [...]
- [...]
- Option "BlankTime" "5" <comment># Blank the screen after 5 minutes (Fake)</comment>
- Option "StandbyTime" "10" <comment># Turn off screen after 10 minutes (DPMS)</comment>
- Option "SuspendTime" "20" <comment># Full suspend after 20 minutes</comment>
- Option "OffTime" "30" <comment># Turn off after half an hour</comment>
+<pre caption="LCD suspend settings in X.org">
+Section "ServerFlags"
+ Option "blank time" "5" <comment># Blank the screen after 5 minutes (Fake)</comment>
+ Option "standby time" "10" <comment># Turn off screen after 10 minutes (DPMS)</comment>
+ Option "suspend time" "20" <comment># Full suspend after 20 minutes</comment>
+ Option "off time" "30" <comment># Turn off after half an hour</comment>
[...]
EndSection
@@ -839,15 +837,11 @@
Section "Monitor"
Identifier [...]
- Option "DPMS" "true"
+ Option "DPMS"
[...]
EndSection
</pre>
-<p>
-This is the same for XFree86 and <path>/etc/X11/XF86Config</path>.
-</p>
-
</body>
</section>
<section>
@@ -860,27 +854,27 @@
battery mode and place it in your <c>battery</c> runlevel. The following script
should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the
appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops,
-install <c>sys-power/acpitool</c> and skip configuration of <c>ibm_acpi</c> as
-described below.
+install <c>sys-power/acpitool</c> and skip configuration of <c>thinkpad_acpi</c>
+(formerly called <c>ibm_acpi</c>) as described below.
</p>
<warn>
-Support for setting brightness is marked experimental in ibm-acpi. It accesses
+Support for setting brightness is marked experimental in thinkpad_acpi. It accesses
hardware directly and may cause severe harm to your system. Please read the
-<uri link="http://ibm-acpi.sourceforge.net/">ibm-acpi website</uri>
+<uri link="http://ibm-acpi.sourceforge.net/">thinkpad_acpi website</uri>
</warn>
<p>
-To be able to set the brightness level, the ibm_acpi module has to be loaded
+To be able to set the brightness level, the thinkpad_acpi module has to be loaded
with the experimental parameter.
</p>
-<pre caption="automatically loading the ibm_acpi module">
+<pre caption="automatically loading the thinkpad_acpi module">
<comment>(Please read the warnings above before doing this!)</comment>
-# <i>echo "options ibm_acpi experimental=1" >> /etc/modules.d/ibm_acpi</i>
+# <i>echo "options thinkpad_acpi experimental=1" >> /etc/modules.d/thinkpad_acpi</i>
# <i>/sbin/update-modules</i>
-# <i>echo ibm_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
-# <i>modprobe ibm_acpi</i>
+# <i>echo thinkpad_acpi >> /etc/modules.autoload.d/kernel-2.6</i>
+# <i>modprobe thinkpad_acpi</i>
</pre>
<p>
@@ -892,7 +886,7 @@
<pre caption="/etc/conf.d/lcd-brightness">
<comment># See /proc/acpi/ibm/brightness for available values</comment>
-<comment># Please read /usr/src/linux/Documentation/ibm-acpi.txt</comment>
+<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>
<comment># brightness level in ac mode. Default is 7.</comment>
BRIGHTNESS_AC=7
@@ -924,7 +918,7 @@
eend $?
else
ewarn "Setting LCD brightness is not supported."
- ewarn "For IBM Thinkpads, check that ibm_acpi is loaded into the kernel"
+ ewarn "For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel"
ewarn "For Toshiba laptops, you've got to install sys-power/acpitool"
fi
}
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-doc-cvs] cvs commit: power-management-guide.xml
@ 2008-05-23 20:34 Sven Vermeulen
0 siblings, 0 replies; 20+ messages in thread
From: Sven Vermeulen @ 2008-05-23 20:34 UTC (permalink / raw
To: gentoo-doc-cvs
swift 08/05/23 20:34:12
Modified: power-management-guide.xml
Log:
Coding style
Revision Changes Path
1.36 xml/htdocs/doc/en/power-management-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.36&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.36&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.35&r2=1.36
Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- power-management-guide.xml 31 Jan 2008 23:38:05 -0000 1.35
+++ power-management-guide.xml 23 May 2008 20:34:12 -0000 1.36
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.35 2008/01/31 23:38:05 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.36 2008/05/23 20:34:12 swift Exp $ -->
<guide link="/doc/en/power-management-guide.xml">
<title>Power Management Guide</title>
@@ -859,14 +859,15 @@
</p>
<warn>
-Support for setting brightness is marked experimental in thinkpad_acpi. It accesses
-hardware directly and may cause severe harm to your system. Please read the
-<uri link="http://ibm-acpi.sourceforge.net/">thinkpad_acpi website</uri>
+Support for setting brightness is marked experimental in thinkpad_acpi. It
+accesses hardware directly and may cause severe harm to your system. Please
+read the <uri link="http://ibm-acpi.sourceforge.net/">thinkpad_acpi
+website</uri>
</warn>
<p>
-To be able to set the brightness level, the thinkpad_acpi module has to be loaded
-with the experimental parameter.
+To be able to set the brightness level, the thinkpad_acpi module has to be
+loaded with the experimental parameter.
</p>
<pre caption="automatically loading the thinkpad_acpi module">
@@ -1325,11 +1326,12 @@
<p>
There are two different implementations for S4. The original one is swsusp,
-then there is the newer tuxonice (former suspend2) with a nicer interface (including fbsplash
-support). A <uri link="http://tuxonice.net/features.html#compare"> feature
-comparison</uri> is available at the <uri link="http://www.tuxonice.net">tuxonice
-Homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of swsusp,
-but it has been merged back.
+then there is the newer tuxonice (former suspend2) with a nicer interface
+(including fbsplash support). A <uri
+link="http://tuxonice.net/features.html#compare"> feature comparison</uri> is
+available at the <uri link="http://www.tuxonice.net">tuxonice Homepage</uri>.
+There used to be Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been
+merged back.
</p>
<p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2008-05-23 20:34 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-23 3:40 [gentoo-doc-cvs] cvs commit: power-management-guide.xml Josh Saddler
-- strict thread matches above, loose matches on Subject: below --
2008-05-23 20:34 Sven Vermeulen
2008-01-31 23:38 Joshua Saddler
2008-01-21 12:15 Jan Kundrat
2008-01-21 12:12 Jan Kundrat
2007-12-03 19:31 Sven Vermeulen
2007-10-03 17:27 Josh Saddler
2007-07-24 22:32 Josh Saddler
2007-07-08 17:51 Josh Saddler
2007-07-08 7:48 Josh Saddler
2007-05-30 19:09 Josh Saddler
2007-03-15 19:24 Josh Saddler
2007-02-20 17:44 Josh Saddler
2006-12-17 3:42 Josh Saddler
2006-08-17 0:45 Lukasz Damentko
2006-07-27 8:23 Lukasz Damentko
2006-07-27 8:13 Lukasz Damentko
2006-02-16 18:45 Josh Saddler
2006-02-12 11:53 Josh Saddler
2005-10-28 14:48 Stefano Rossi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox