mirror of https://github.com/tLDP/LDP
removed the information about the acpi application and replaced it with generic 'get a monitoring program' note
This commit is contained in:
parent
7dab3ddb71
commit
fd422a16ce
|
@ -44,9 +44,9 @@
|
|||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v1.6</revnumber>
|
||||
<date>2004-07-21</date>
|
||||
<date>2004-07-23</date>
|
||||
<authorinitials>ejh</authorinitials>
|
||||
<revremark>Spelling mistakes fixed, converted the bibliography to nicer DocBook, added a glossary, and updated the information on the 2.6 kernel and random freezes.</revremark>
|
||||
<revremark>Spelling mistakes fixed, converted the bibliography, added a glossary, moved step-by-step instructions to procedures in examples, and updated the information on the 2.6 kernel and random freezes.</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>v1.5.1</revnumber>
|
||||
|
@ -460,7 +460,7 @@ directory for the newly patched kernel. You should create a backup of all import
|
|||
</sect2>
|
||||
|
||||
<sect2 id="kernelprep">
|
||||
<title>Download and Unpack the New Kernel</title>
|
||||
<title>Download and unpack the kernel source</title>
|
||||
|
||||
<sect3 id="requiredpackages">
|
||||
<title>Required packages</title>
|
||||
|
@ -804,42 +804,30 @@ dot-o) on a separate line. You can also try running
|
|||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="apm2acpi" xreflabel="Switching from APM to ACPI">
|
||||
|
||||
<sect1 id="usingacpi" xreflabel="Using ACPI">
|
||||
<?dbhtml filename="usingacpi.html"?>
|
||||
<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 a monitoring program. I personally use <application>wmacpi</application>. There are lots to choose from in <xref linkend="ref-software"/>.
|
||||
|
||||
<sect2 id="apm2acpi" xreflabel="Switching from APM to ACPI">
|
||||
<?dbhtml filename="apm2acpi.html"?>
|
||||
<title>Switching from APM to ACPI</title>
|
||||
<para>Do not let <application>apmd</application> and
|
||||
<application>acpid</application> run at the same time unless you REALLY know
|
||||
what you are doing. Debian will <emphasis>not</emphasis> make sure only one is running
|
||||
at a time. You will have to check.
|
||||
APM will try to put your system into S3. On the 2.4.x (and before) series
|
||||
kernels this will quite probably hang your machine. S3 is not supported
|
||||
at a time. You will have to check.</para>
|
||||
|
||||
<para>APM will try to put your system into S3. On the 2.4.x (and before) series
|
||||
kernels this will probably cause your machine to lock up. S3 is not supported
|
||||
until at least 2.5.x. Even the patch will not provide support for S3 in the
|
||||
2.4.x series kernels. I personally did an <command>apt-get remove apmd</command>
|
||||
to solve the hanging problem.</para>
|
||||
</sect1>
|
||||
2.4.x series kernels. I completely removed APM support from the kernel, and removed the <application>apmd</application> daemon from my system. On Debian this was as easy as <command>apt-get remove apmd</command>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect1 id="usingacpi" xreflabel="Using ACPI">
|
||||
<?dbhtml filename="usingacpi.html"?>
|
||||
<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
|
||||
<application>acpi</application> Debian package is only available in testing and is unstable. If
|
||||
you are running stable you will not be able to install it without playing
|
||||
around with apt and your <filename>list.sources</filename> file. You can probably
|
||||
also compile from source. If you do get <application>acpi</application>
|
||||
installed you can use it to monitor your system like this: <command>acpi
|
||||
<option>-V</option></command>. The output will tell you about your
|
||||
system. Mine looks like this:</para>
|
||||
<screen>
|
||||
Thermal 1: ok, 47.1 degrees C
|
||||
Thermal 2: ok, 45.1 degrees C
|
||||
AC Adapter 1: off-line <-- running off battery
|
||||
AC Adapter 1: on-line <-- running off AC power
|
||||
</screen>
|
||||
|
||||
<para>Unfortunately, the <option>-V</option> <quote>full version</quote> does not work for me.
|
||||
Fortunately I can still look in each of the acpi files individually for
|
||||
information about my system. Check in the <filename
|
||||
<para>You can also look in each of the ACPI files individually for
|
||||
information about your system. Look in the <filename
|
||||
class="directory">/proc/acpi</filename> directory
|
||||
for various things of importance. If I want to check my battery I read the
|
||||
following file like this: <command>cat
|
||||
|
@ -891,7 +879,8 @@ battery type: Lion
|
|||
OEM info: Acer
|
||||
</screen>
|
||||
|
||||
<para>You are smart people. You can probably figure it out from here. :)</para>
|
||||
<para>For more information on each of these files, please read <ulink url="http://acpi.sourceforge.net/documentation/index.html" />.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue