Novell LINUX ENTERPRISE SERVER 10 - INSTALLATION AND ADMINISTRATION 04-08-2006 Installation Manual page 525

system executes commands stored in the BIOS, the functionality depends on the BIOS
implementation. The tables ACPI can detect and load are reported in /var/log/boot
.msg. See Section 29.3.4, "Troubleshooting"
troubleshooting ACPI problems.
29.3.1 ACPI in Action
If the kernel detects an ACPI BIOS when the system is booted, ACPI is activated auto-
matically and APM is deactivated. The boot parameter acpi=force may be necessary
for some older machines. The computer must support ACPI 2.0 or later. Check the
kernel boot messages in /var/log/boot.msg to see if ACPI was activated.
Subsequently, a number of modules must be loaded. This is done by the start script of
acpid. If any of these modules cause problems, the respective module can be excluded
from loading or unloading in /etc/sysconfig/powersave/common. The system
log (/var/log/messages) contains the messages of the modules, enabling you to
see which components were detected.
/proc/acpi now contains a number of files that provide information about the system
state or can be used to change some of the states. Some features do not work yet because
they are still under development and the support of some functions largely depends on
the implementation of the manufacturer.
All files (except dsdt and fadt) can be read with cat. In some files, settings can be
modified with echo, for example, echo X > file to specify suitable values for
X. One possiblity for easy access to those values is the powersave command, which
acts as a front-end for the Powersave daemon. The following describes the most impor-
tant files:
/proc/acpi/info
General information about ACPI.
/proc/acpi/alarm
Here, specify when the system should wake from a sleep state. Currently, this feature
is not fully supported.
/proc/acpi/sleep
Provides information about possible sleep states.
(page 530) for more information about
Power Management 525