From f791325b90b46c64400ade7dc50d7d762d8e1b0d Mon Sep 17 00:00:00 2001 From: Marc Fonvieille Date: Sat, 7 Jun 2003 14:41:07 +0000 Subject: [PATCH] Enhance the "Debugging ACPI" section with a ACPI disabling part (it is not easy for the user to find how to disable the ACPI system). While I'm there, rename the section to "Debugging and Disabling ACPI". --- .../books/handbook/config/chapter.sgml | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml index e255b85bda..5d2add9690 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml @@ -2273,11 +2273,26 @@ kern.maxfiles: 2088 -> 5000 - Debugging <acronym>ACPI</acronym> + Debugging and Disabling <acronym>ACPI</acronym> Almost everything in ACPI is transparent, until it does not work. That is usually when you as a user will know there - is something not working properly. + is something not working properly. The &man.acpi.4; driver + supports many debugging options, it is even possible to + selectively disable some parts of the ACPI + system. For more information about debugging facilities, read + the &man.acpi.4; manual page. + + Sometimes for various reasons, the + acpi.ko module must be unloaded. This + can only be done at boot time by the &man.loader.8;. You can + type at &man.loader.8; prompt the command + unset acpi_load each time you boot the + system, or to stop the autoloading of the + &man.acpi.4; driver add the following line to the + /boot/loader.conf file: + + exec="unset acpi_load"