LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2003-07-08 18:04:20 +00:00
parent a45983a7b4
commit 63b294fe2f
1 changed files with 20 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
LDP/howto/docbook/ACPI-HOWTO.xml
View File

@ -31,7 +31,7 @@ custom kernels with Debian&apos;s kernel-package system</ulink></para>
]>
<article>
<article id="index">
<articleinfo>
<title>ACPI: Advanced Configuration and Power Interface</title>
@ -87,10 +87,9 @@ custom kernels with Debian&apos;s kernel-package system</ulink></para>
<date>2003-06-12</date>
</revision>
</revhistory>
</articleinfo>
<sect1>
<sect1 id="about">
<title>About this document</title>
<para>When I first started the switch from APM to ACPI I didn't realize the
kernel needed to be patched. My problem (insanely loud fan) was fixed just
@ -120,7 +119,7 @@ of doing things. There is also generic information in the
</para></blockquote>
</sect1>
<sect1>
<sect1 id="aboutacpi">
<title>About ACPI</title>
<para>In the world of power management ACPI is relatively new to the game.
@ -174,7 +173,7 @@ url="http://tuxmobil.org/Mobile-Guide.db/mobile-guide-p2c1-hardware-in-detail.ht
Mobile Guide</ulink>.</para>
</sect1>
<sect1>
<sect1 id="apmtoacpi">
<title>Why switch?</title>
<para>Not all systems support both APM and ACPI. I switched because my
system only supported ACPI. Pretty easy decision really. If you're switching
@ -190,7 +189,7 @@ the list if you've installed ACPI! They also have a list of machines that
are <ulink url="http://acpi.sourceforge.net/documentation/blacklist.html">not supported</ulink>.</para>
</sect1>
<sect1>
<sect1 id="dsdt">
<title>DSDT: Differentiated System Description Table</title>
<para>Thanks to <ulink url="http://www.vitavonni.de/">Erich</ulink> writing this section.</para>
@ -210,7 +209,7 @@ This override is quite easy: instead of loading the DSDT table from
bios, the kernel uses the compiled-in DSDT table. That's all.</para>
</sect1>
<sect1>
<sect1 id="install">
<title>Installing from scratch</title>
<para>ACPI is constantly being revised. It is currently not available in
the 2.4.x series kernels but will be released into the
@ -286,7 +285,7 @@ with them. Please don't email me asking about them, ask maxx instead.</para>
</sect2>
</sect1>
<sect1>
<sect1 id="backups">
<title>Backups</title>
<para>If you are already running a kernel that is the same version of the
one you are about to patch I recommend creating a fresh
@ -304,7 +303,7 @@ directory for the newly patched kernel. Remember that backups are
</itemizedlist>
</sect1>
<sect1>
<sect1 id="requiredpackages">
<title>Required packages</title>
<para>Since I was starting on a brand new machine, I'm pretty sure I have the
full list of required packages to make this whole patch go smoothly. Here's
@ -320,7 +319,7 @@ the list all in one go:</para>
</itemizedlist>
</sect1>
<sect1>
<sect1 id="patch">
<title>Download and patch</title>
<para>Download a fresh kernel from <ulink
url="http://www.kernel.org">www.kernel.org</ulink>. You need to make sure you
@ -454,7 +453,7 @@ look for the absence of errors.)</para>
</sect2>
</sect1>
<sect1>
<sect1 id="kernelconfig">
<title>Configure the new kernel</title>
<para>Now instead of using <command>make <parameter>menuconfig</parameter></command>, I have a godsend of an option. Check
this out: copy your current <filename>.config</filename> file into
@ -511,7 +510,7 @@ and make sure you have your APM (the old stuff) turned off. Under
<para>exit and save the new configuration</para>
</sect1>
<sect1>
<sect1 id="kernelcompile">
<title>Compile the new kernel</title>
<para>If you have additional modules that are not part of the main source
tree, you will need to add modules_image when you make your Debian
@ -552,7 +551,7 @@ still think it's a good way to do things.</para></note>
&kernel-compile;
</sect1>
<sect1>
<sect1 id="kernelinstall">
<title>Install the new kernel</title>
<para>I like to configure lilo on my own, but do whatever tickles your fancy.</para>
<itemizedlist>
@ -589,7 +588,7 @@ still think it's a good way to do things.</para></note>
&kernel-compile;
</sect1>
<sect1>
<sect1 id="finishinstall">
<title>Reboot and test</title>
<para>At this point you should reboot your machine. When your system comes
back up (assuming of course that everything went well and you still have a
@ -620,7 +619,7 @@ says that S3 is a supported state, but we already know it's not. It does
give the correct version though, which is useful.</para>
</sect1>
<sect1>
<sect1 id="loadmodules">
<title>Load related modules</title>
<para>If you compiled ACPI support in as "M"odules you'll probably need to
load the modules by hand. You'll need to hunt around a bit to see what
@ -689,7 +688,7 @@ file just create a new one and add each module name (remember, no
dot-o) on a separate line.</para>
</sect1>
<sect1>
<sect1 id="daemons">
<title>Switching from APM to ACPI</title>
<para>Don't let apmd and acpid run at the same time unless you REALLY know
what you're doing. Debian will <emphasis>not</emphasis> make sure only one is running
@ -714,11 +713,9 @@ two things:</para>
the line <option>Option "DPMS"</option> under Section "Monitor".
</para></listitem>
</itemizedlist>
</sect1>
<sect1>
<sect1 id="usingacpi">
<title>Using ACPI</title>
<para>There are a few different applications/daemons you will want to install
on your system: <application>acpid</application> (the daemon that will control your hardware states), and <application>acpi</application> (the interface to monitor events and states) are the base install. The
@ -1057,7 +1054,7 @@ generally getting ACPI up and running.</para>
</variablelist>
</sect1>
<sect1>
<sect1 id="thanks">
<title>Thanks</title>
<para>Much thanks goes out to the following:</para>
<itemizedlist>
@ -1102,7 +1099,7 @@ enthusiastic about learning DocBook</para></listitem>
<para>There is very little difference between The Debian Way and the
generic way. In fact it's probably only 10 or so lines of difference.</para>
<sect1>
<sect1 id="nodebcompile">
<title>Compile the kernel</title>
<para>The <quote>normal</quote> way of compiling a kernel does not use
<command>make-kpkg</command>. Instead, it uses the following steps:</para>
@ -1133,7 +1130,7 @@ generic way. In fact it's probably only 10 or so lines of difference.</para>
</itemizedlist>
</sect1>
<sect1>
<sect1 id="nodebinstall">
<title>Install the new kernel</title>
<para>In <citetitle>The Debian Way</citetitle>, you create a deb file which contains information about where the kernel is (and makes the kernel and yada-yada). In the <quote>normal</quote> way, you put things where they need to be right away. You need to install your modules and then configure lilo to point to the new kernel and then run
lilo. If you are not doing things <citetitle>The Debian Way</citetitle> your <quote>install</quote> will look like this:</para>
@ -1175,7 +1172,7 @@ lilo. If you are not doing things <citetitle>The Debian Way</citetitle> your <qu
</warning>
</sect1>
<sect1>
<sect1 id="nodebsoftware">
<title>Software packages</title>
<para>You can still use all of the software mentioned in this HOWTO even if
you're not using Debian. Unfortunately it will take a little more effort on