In recent linux kernels, the /proc/acpi/event interface has been deprecated. The same information (and more) is available via netlink (a way for the kernel to communicate with userspace that is usually used for networking) and the input layer (mouse, keyboard, power button, etc...). This version of acpid supports netlink and the input layer.
Be sure to check the Resolved Issues section below to see if you are experiencing a problem that has been fixed.
acpid-2.0.2.tar.gz - Latest version with netlink and input layer support.
kacpimon - Kernel ACPI Monitor. This is now included in the acpid source, so there's no need to download this. It's a test program that connects to /proc/acpi/event, the input layer (/dev/input/event*), and netlink. It then displays any events it receives on the console. Be sure to run this as root. Kill acpid ("killall acpid") to make sure kacpimon can open /proc/acpi/event.
evtest - Vojtech Pavlik's input layer monitor tool.
acpid-2.0.1.tar.gz
acpid-2.0.0.tar.gz
acpid-1.0.10-netlink6.tar.gz
acpid-1.0.10-netlink5.tar.gz
acpid-1.0.10-netlink4.tar.bz2
acpid-1.0.10-netlink3.tar.bz2
acpid-1.0.10-netlink2.tar.bz2
acpid-1.0.8ted1.tar.bz2
acpid in the Debian Package Tracking System (PTS) - I've been working closely with Debian and have received a lot of excellent feedback. acpid 2.x would not be as stable as it is without Debian's help.
kacpimon in the Debian PTS
acpid in Fedora/Red Hat
acpid SourceForge Project - Covers up to 1.0.10 so far.
Fedora's acpid package - Still based on the 1.0.10 version. Not sure how to contact anyone or monitor bugs.
kacpimon has been added as a separate project in Debian, and I need to sync up with changes that are in there.
The acpi-support package in Debian has files that cause an endless loop condition. The following files should be removed from acpi-support:
Upstream has apparently removed these already, so they will be removed from Debian soon. See Debian 556261.
Debian 522756 (HIGH) - acpid crashes when an input layer device goes away. Mikhail Krivtsov has provided a patch to handle this. However, how do we discover the connection of new devices?
Vojtech Pavlik provided the following ideas 11/6/2009:
After a bit of poking around, I've decided to go with inotify(7) on /dev/input. It appears to work fine (for me). I'll be releasing soon...
Debian 521280 (MED) - acpid doesn't cover all the ThinkPad events. I knew this one was coming. My original stance on this was that we'll cover those that the original kernel thinkpad support covered. I'm not sure how many that actually was. Regardless, it looks like a more generic system might be a better idea. Maybe just put out the event numbers for those we don't recognize. Ugly, but it works. There's a nice huge list of events in this bug report to start with.
<- Back to my Linux page.
Copyright ©2009, Ted Felix. Disclaimer