os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clean up the acpi section a bit, removing references to disable acpi with

Browse source 
the acpiconf utility.  If I messed up the sgml, feel free to fix.
This commit is contained in:
Nate Lawson 2007-04-07 20:21:09 +00:00
parent 528e59f1d5
commit ce50266cf6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=29953
1 changed files with 38 additions and 31 deletions

69
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -2513,14 +2513,15 @@ kern.maxvnodes: 100000</programlisting>
<title>Power and Resource Management</title>
<para>It is very important to utilize hardware resources in an
<para>It is important to utilize hardware resources in an
efficient manner. Before <acronym>ACPI</acronym> was introduced,
it was very difficult and inflexible for operating systems to manage
it was difficult and inflexible for operating systems to manage
the power usage and thermal properties of a system. The hardware was
controlled by some sort of <acronym>BIOS</acronym> embedded
interface, such as <emphasis>Plug and Play BIOS (PNPBIOS)</emphasis>, or
<emphasis>Advanced Power Management (APM)</emphasis> and so on.
Power and Resource Management is one of the key components of a modern
managed by the <acronym>BIOS</acronym> and thus the user had less
control and visibility into the power management settings.
Some limited configurability was available via
<emphasis>Advanced Power Management (APM)</emphasis>.
Power and resource management is one of the key components of a modern
operating system. For example, you may want an operating system to
monitor system limits (and possibly alert you) in case your system
temperature increased unexpectedly.</para>
@ -2563,7 +2564,8 @@ kern.maxvnodes: 100000</programlisting>
activity. The APM BIOS is supplied by the (system) vendor and
it is specific to the hardware platform. An APM driver in the
OS mediates access to the <emphasis>APM Software Interface</emphasis>,
which allows management of power levels.</para>
which allows management of power levels. APM should still be used for
systems manufactured at or before the year 2000.</para>
<para>There are four major problems in APM. Firstly, power
management is done by the (vendor-specific) BIOS, and the OS
@ -2596,33 +2598,37 @@ kern.maxvnodes: 100000</programlisting>
<title>Configuring <acronym>ACPI</acronym></title>
<para>The <filename>acpi.ko</filename> driver is loaded by default
at start up by the &man.loader.8; and should <emphasis>not</emphasis>
be compiled into the kernel. The reasoning behind this is that modules
are easier to work with, say if switching to another <filename>acpi.ko</filename>
without doing a kernel rebuild. This has the advantage of making testing easier.
Another reason is that starting <acronym>ACPI</acronym> after a system has been
brought up is not too useful, and in some cases can be fatal. In doubt, just
disable <acronym>ACPI</acronym> all together. This driver should not and can not
be unloaded because the system bus uses it for various hardware interactions.
<acronym>ACPI</acronym> can be disabled with the &man.acpiconf.8; utility.
In fact most of the interaction with <acronym>ACPI</acronym> can be done via
&man.acpiconf.8;. Basically this means, if anything about <acronym>ACPI</acronym>
is in the &man.dmesg.8; output, then most likely it is already running.</para>
at start up by the &man.loader.8; and should <emphasis>not</emphasis>
be compiled into the kernel. The reasoning behind this is that modules
are easier to work with, say if switching to another
<filename>acpi.ko</filename> without doing a kernel rebuild.
This has the advantage of making testing easier.
Another reason is that starting <acronym>ACPI</acronym> after a
system has been brought up often doesn't work well.
If you are experiencing problems, you can disable <acronym>ACPI</acronym>
altogether. This driver should not and can not be unloaded because the
system bus uses it for various hardware interactions.
<acronym>ACPI</acronym> can be disabled by setting
<literal>hint.acpi.0.disabled="1"</literal> in
<filename>/boot/loader.conf</filename> or at the &man.loader.8; prompt.
</para>
<note><para><acronym>ACPI</acronym> and <acronym>APM</acronym> cannot coexist and
should be used separately. The last one to load will terminate if the driver
notices the other running.</para></note>
<note><para><acronym>ACPI</acronym> and <acronym>APM</acronym> cannot
coexist and should be used separately. The last one to load will
terminate if the driver notices the other running.</para></note>
<para>In the simplest form, <acronym>ACPI</acronym> can be used to put the
system into a sleep mode with &man.acpiconf.8;, the <option>-s</option>
flag, and a <literal>1-5</literal> option. Most users will only need
<literal>1</literal>. Option <literal>5</literal> will do a soft-off
which is the same action as:</para>
<para><acronym>ACPI</acronym> can be used to put the
system into a sleep mode with &man.acpiconf.8;, the <option>-s</option>
flag, and a <literal>1-5</literal> option. Most users will only need
<literal>1</literal> or <literal>3</literal> (suspend to RAM).
Option <literal>5</literal> will do a soft-off which is the same
action as:</para>
<screen>&prompt.root; <userinput>halt -p</userinput></screen>
<para>The other options are available. Check out the &man.acpiconf.8;
manual page for more information.</para>
<para>Other options are available via &man.sysctl.8;. Check out the
&man.acpi.4; and &man.acpiconf.8; manual pages for more information.
</para>
</sect2>
</sect1>
@ -2720,7 +2726,7 @@ kern.maxvnodes: 100000</programlisting>
very large. Generate a copy of your <acronym>ASL</acronym>
by running this command:</para>
<screen>&prompt.root; <userinput>acpidump -t -d &gt; <replaceable>name</replaceable>-<replaceable>system</replaceable>.asl</userinput></screen>
<screen>&prompt.root; <userinput>acpidump -dt &gt; <replaceable>name</replaceable>-<replaceable>system</replaceable>.asl</userinput></screen>
<para>(Substitute your login name for
<replaceable>name</replaceable> and manufacturer/model for
@ -2868,7 +2874,8 @@ hw.acpi.s4bios: 0</screen>
<filename>/etc/rc.suspend</filename> and
<filename>/etc/rc.resume</filename>. There is a
commented-out example for unloading and loading a driver. Try
setting <option>hw.acpi.reset_video</option> to zero (<literal>0</literal>) if
setting <option>hw.acpi.reset_video</option> to zero
(<literal>0</literal>) if
your display is messed up after resume. Try setting longer or
shorter values for <option>hw.acpi.sleep_delay</option> to see
if that helps.</para>