Typos fixing and a rewording.
This commit is contained in:
parent
603ee175ac
commit
fcc3f38a28
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15511
1 changed files with 4 additions and 4 deletions
|
@ -1713,13 +1713,13 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<sect2 id="acpi-config">
|
||||
<title>Configuring <acronym>ACPI</acronym></title>
|
||||
|
||||
<para>The <filename>acpi.ko</filename> driver is loaded by the
|
||||
at start up by &man.loader.8; by default and should <emphasis>not</emphasis>
|
||||
<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 to useful, and in some cases can be fatal. If in doubt, just
|
||||
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.
|
||||
|
@ -1746,7 +1746,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<sect2 id="acpi-debug">
|
||||
<title>Debugging <acronym>ACPI</acronym></title>
|
||||
|
||||
<para>Almost everything <acronym>ACPI</acronym> is transparent, until
|
||||
<para>Almost everything in <acronym>ACPI</acronym> is transparent, until
|
||||
it does not work. That is usually when you as a user will know there
|
||||
is something not working properly.</para>
|
||||
|
||||
|
|
Loading…
Reference in a new issue