The ACPI Driver Package
The ACPI Driver Package is a Platform Specific Driver (PSD) and related files and programs that use the ACPI in your computer’s Vendor Supplied Firmware (UEFI BIOS/Traditional BIOS/ACPI/etc.) to configure and operate your computer. The PSD supports ACPI version 2.0 through version 6.4
This project produces 5 files and a toolkit for program development:
- ACPI.PSD – the Platform Specific Driver that sets up and controls the hardware, and also implements the ACPI Component Architecture which is the interface to your computer’s ACPI. This is the main component of the ACPI Driver Package. ACPI.PSD normally goes in \OS2\BOOT.
- ACPI32.DLL – The interface between ACPI.PSD and other programs (like AcpiDaemon.exe) so that they can use the ACPI functions in the PSD. This DLL is not required for proper operation of ACPI.PSD, but most programs will not be able to use any ACPI services if you do not install it. ACPI32.DLL normally goes in \OS2\DLL.
- APM.ADD – An Advanced Power Management interface that emulates APM functions using ACPI. This driver is not required for proper operation of ACPI.PSD, but may be required for some older programs that use APM functions. APM.ADD normally goes in \OS2\BOOT.
- AcpiDaemon.EXE – A program that implements certain system functions like CPU throttling, power button handling, various events like lid open/close events, etc. This program is not required for proper operation of ACPI.PSD, but is required for proper operation of APM.ADD. AcpiDaemon.EXE requires ACPI32.DLL and normally goes in \OS2.
- ACPID.CFG – The configuration file for AcpiDaemon.exe. ACPID.CFG must go in the directory specified by the ETC environment variable.
- The toolkit – For developing programs that interface with ACPI.PSD
Please read the ReadMe and the PSD_EN.INF documentation that is included in the distribution before installing and using this software.
Before submitting a ticket, make sure you have read the Requirements, Limitations, and Problems page.
Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for the same problem already created.
- Please enter a useful description of the actual problem in the Summary.
- If you think your hardware information is useful, put that information in the Description, not in the Summary.
- Do not put the ACPI Driver Package version number in the Summary.
- Please only submit one issue on a ticket. Do not list several issues on a single ticket. Be clear and specific and include all information necessary to show that the problem is being caused by the ACPI Driver software. DO NOT just submit a “report” of your experience.
- Please do not post information about your system on someone else’s ticket. ACPI Driver issues are complex enough that even if you have the same system and the same symptoms, your problem may not be the same. So open your own ticket — don’t post on someone else’s. If the developer thinks they are related, then the developer will link the tickets together.
- Make sure you always attach a testlog log file to your ticket when you open it.
Application / Driver Developers
A toolkit is available for using ACPI services. Applications can link to acpi32.lib. The library and header files are included in the toolkit. Sample programs and documentation are provided as well.
You can download the latest toolkit here: acpi-toolkit
This entry last updated: by