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="[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 <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> -- [email protected] mailing list
