You are not logged in.
Good evening everyone!
Today I want to question you about handling ACPI events without acpid, but with bare system udev instead (writing rules).
I see that actually, when ACPI event occurs it first is hadled by udev (systemd-udevd process is spawned for a short time).
Basically speaking, is it possible to write udev rules for ACPI keys' events like lid opened/closed, power button, wlan key, mute and volume keys, brightness keys and monitor key?
Last edited by eruditorum (2013-02-16 11:06:57)
Offline
Yeah, there are examples of that. I think acpid just makes the task slightly easier.
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
Oh, I see that udev handles "power_supply" events ok (battery charge and discharge by 1%, AC on and off). But I see nothing for ACPI keys (lid, power button and all the others on the keyboard).
I have set "udev_log="debug"" in "udev.conf" file, but still I can't see them neither on system log nor on terminal with "udevadm monitor".
Where can I see them?
THANKS!
Last edited by eruditorum (2013-02-10 10:33:26)
Offline
Yeah, there are examples of that. I think acpid just makes the task slightly easier.
Man, I see nothing about ACPI keys in these examples, only other udev events. Thanks for the link however - now I know a bit more about what can be done with udev.
Offline
Unfortunately, I've had no luck in making udev respond to ACPI keys' events using udev rules. ((
Only AC on/off and battery charge reporting seem to work with rules.
Last edited by eruditorum (2013-02-12 15:24:57)
Offline