How to configure acpid - Revision history

Nephros: /* Make the Microphone Mute button work */

2010-09-19T14:49:43Z

‎Make the Microphone Mute button work

Nephros: /* Added Microphone Mute */

2010-09-19T14:46:52Z

‎Added Microphone Mute

Marc-soft: explain why acpid logging is broken in debian and ubuntu

2009-11-30T04:27:57Z

explain why acpid logging is broken in debian and ubuntu

Tonko: /* Introduction */

2009-04-22T14:24:33Z

‎Introduction

Thjaeger: /* Sources of Information */

2008-11-24T09:12:04Z

‎Sources of Information

Kevmitch: /* Introduction */

2008-01-22T10:06:12Z

‎Introduction

Kevmitch: /* Introduction */

2008-01-21T08:22:04Z

‎Introduction

Vrossum at 14:32, 5 January 2008

2008-01-05T14:32:09Z

Vrossum: /* Troubleshooting */

2008-01-05T14:28:56Z

‎Troubleshooting

Csawtell: /* Event Script */

2007-09-02T19:28:07Z

‎Event Script

@@ Line 170: / Line 170: @@
 ==Make the Microphone Mute button work==
-There is ATM no special key with this functionality defined in X or anywhere else.
+There is ATM no special key with this functionality defined in X or HAL.
 The easiest way I have found is to do it via amixer.

@@ Line 168: / Line 168: @@
   event=ibm/hotkey HKEY 00000080 00001007
   action=/etc/acpi/switchdisplay.sh
 ==Troubleshooting==

@@ Line 3: / Line 3: @@
 Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}} in older versions of acpid and to {{path|/var/log/messages}}, and {{path|/var/log/syslog}} via the syslog interface in newer versions >~1.0.6.
-{{NOTE|Modern distributions no longer use acpid, and instead rely on HAL}}
+{{NOTE|Modern distributions no longer use acpid for power manager, and instead rely on HAL and pm-utils (but you can still use acpid for other hotkeys)}}
 ==Sources of Information==

@@ Line 2: / Line 2: @@
 ==Introduction==
 Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}} in older versions of acpid and to {{path|/var/log/messages}}, and {{path|/var/log/syslog}} via the syslog interface in newer versions >~1.0.6.
 ==Sources of Information==

@@ Line 8: / Line 8: @@
 *You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.
 *And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].
 ==Example: go to sleep on lid close==

@@ Line 1: / Line 1: @@
 __TOC__
 ==Introduction==
-Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.
+Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}} in older versions of acpid and to {{path|/var/log/messages}} via the syslog interface in newer versions >~1.0.6.
 ==Sources of Information==

@@ Line 152: / Line 152: @@
 ==Switch external display==
 Again make sure that
 With the newer versions of X, display switching can be done with xrandr.
+And /etc/acpi/events/displaybtn
 ==Troubleshooting==

@@ Line 148: / Line 148: @@
 An alternative is to call radeontool (if you have a radeon videocard only of course)
@@ Line 153: / Line 160: @@
 *If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.
 *For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].
 [[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]  [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]

@@ Line 28: / Line 28: @@
 dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.
-For the script you can use the <tt>hibernate</tt> script of [http://www.tuxonice.net/ Tux On Ice] (it is independent of the [[Tux on Ice | suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.
+For the script you can use the <tt>hibernate</tt> script of [http://www.tuxonice.net/ Tux On Ice] (it is independent of the [[ www.suspend2.net | suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.
 {{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}