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="[EMAIL PROTECTED]">Dennis Nienhüser</mail> </author> +<author title="Editor"> + <mail link="[EMAIL PROTECTED]">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="[EMAIL PROTECTED]">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> -- [email protected] mailing list
