mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
a45983a7b4
commit
63b294fe2f
|
@ -31,7 +31,7 @@ custom kernels with Debian's kernel-package system</ulink></para>
|
||||||
|
|
||||||
]>
|
]>
|
||||||
|
|
||||||
<article>
|
<article id="index">
|
||||||
<articleinfo>
|
<articleinfo>
|
||||||
<title>ACPI: Advanced Configuration and Power Interface</title>
|
<title>ACPI: Advanced Configuration and Power Interface</title>
|
||||||
|
|
||||||
|
@ -87,10 +87,9 @@ custom kernels with Debian's kernel-package system</ulink></para>
|
||||||
<date>2003-06-12</date>
|
<date>2003-06-12</date>
|
||||||
</revision>
|
</revision>
|
||||||
</revhistory>
|
</revhistory>
|
||||||
|
|
||||||
</articleinfo>
|
</articleinfo>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="about">
|
||||||
<title>About this document</title>
|
<title>About this document</title>
|
||||||
<para>When I first started the switch from APM to ACPI I didn't realize the
|
<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
|
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>
|
</para></blockquote>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="aboutacpi">
|
||||||
<title>About ACPI</title>
|
<title>About ACPI</title>
|
||||||
|
|
||||||
<para>In the world of power management ACPI is relatively new to the game.
|
<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>
|
Mobile Guide</ulink>.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="apmtoacpi">
|
||||||
<title>Why switch?</title>
|
<title>Why switch?</title>
|
||||||
<para>Not all systems support both APM and ACPI. I switched because my
|
<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
|
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>
|
are <ulink url="http://acpi.sourceforge.net/documentation/blacklist.html">not supported</ulink>.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="dsdt">
|
||||||
<title>DSDT: Differentiated System Description Table</title>
|
<title>DSDT: Differentiated System Description Table</title>
|
||||||
<para>Thanks to <ulink url="http://www.vitavonni.de/">Erich</ulink> writing this section.</para>
|
<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>
|
bios, the kernel uses the compiled-in DSDT table. That's all.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="install">
|
||||||
<title>Installing from scratch</title>
|
<title>Installing from scratch</title>
|
||||||
<para>ACPI is constantly being revised. It is currently not available in
|
<para>ACPI is constantly being revised. It is currently not available in
|
||||||
the 2.4.x series kernels but will be released into the
|
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>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="backups">
|
||||||
<title>Backups</title>
|
<title>Backups</title>
|
||||||
<para>If you are already running a kernel that is the same version of the
|
<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
|
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>
|
</itemizedlist>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="requiredpackages">
|
||||||
<title>Required packages</title>
|
<title>Required packages</title>
|
||||||
<para>Since I was starting on a brand new machine, I'm pretty sure I have the
|
<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
|
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>
|
</itemizedlist>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="patch">
|
||||||
<title>Download and patch</title>
|
<title>Download and patch</title>
|
||||||
<para>Download a fresh kernel from <ulink
|
<para>Download a fresh kernel from <ulink
|
||||||
url="http://www.kernel.org">www.kernel.org</ulink>. You need to make sure you
|
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>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="kernelconfig">
|
||||||
<title>Configure the new kernel</title>
|
<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
|
<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
|
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>
|
<para>exit and save the new configuration</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="kernelcompile">
|
||||||
<title>Compile the new kernel</title>
|
<title>Compile the new kernel</title>
|
||||||
<para>If you have additional modules that are not part of the main source
|
<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
|
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;
|
&kernel-compile;
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="kernelinstall">
|
||||||
<title>Install the new kernel</title>
|
<title>Install the new kernel</title>
|
||||||
<para>I like to configure lilo on my own, but do whatever tickles your fancy.</para>
|
<para>I like to configure lilo on my own, but do whatever tickles your fancy.</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
@ -589,7 +588,7 @@ still think it's a good way to do things.</para></note>
|
||||||
&kernel-compile;
|
&kernel-compile;
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="finishinstall">
|
||||||
<title>Reboot and test</title>
|
<title>Reboot and test</title>
|
||||||
<para>At this point you should reboot your machine. When your system comes
|
<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
|
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>
|
give the correct version though, which is useful.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="loadmodules">
|
||||||
<title>Load related modules</title>
|
<title>Load related modules</title>
|
||||||
<para>If you compiled ACPI support in as "M"odules you'll probably need to
|
<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
|
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>
|
dot-o) on a separate line.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="daemons">
|
||||||
<title>Switching from APM to ACPI</title>
|
<title>Switching from APM to ACPI</title>
|
||||||
<para>Don't let apmd and acpid run at the same time unless you REALLY know
|
<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
|
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".
|
the line <option>Option "DPMS"</option> under Section "Monitor".
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="usingacpi">
|
||||||
<title>Using ACPI</title>
|
<title>Using ACPI</title>
|
||||||
<para>There are a few different applications/daemons you will want to install
|
<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
|
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>
|
</variablelist>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="thanks">
|
||||||
<title>Thanks</title>
|
<title>Thanks</title>
|
||||||
<para>Much thanks goes out to the following:</para>
|
<para>Much thanks goes out to the following:</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
@ -1102,7 +1099,7 @@ enthusiastic about learning DocBook</para></listitem>
|
||||||
<para>There is very little difference between The Debian Way and the
|
<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>
|
generic way. In fact it's probably only 10 or so lines of difference.</para>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="nodebcompile">
|
||||||
<title>Compile the kernel</title>
|
<title>Compile the kernel</title>
|
||||||
<para>The <quote>normal</quote> way of compiling a kernel does not use
|
<para>The <quote>normal</quote> way of compiling a kernel does not use
|
||||||
<command>make-kpkg</command>. Instead, it uses the following steps:</para>
|
<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>
|
</itemizedlist>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="nodebinstall">
|
||||||
<title>Install the new kernel</title>
|
<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
|
<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>
|
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>
|
</warning>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1 id="nodebsoftware">
|
||||||
<title>Software packages</title>
|
<title>Software packages</title>
|
||||||
<para>You can still use all of the software mentioned in this HOWTO even if
|
<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
|
you're not using Debian. Unfortunately it will take a little more effort on
|
||||||
|
|
Loading…
Reference in New Issue