Bug#521280: [Pkg-acpi-devel] Bug#521280: doesn't seem to affect thinkpad-acpi only
Hi, another thing that needs to be done is to start acpid with the `-n' option. Why? Please note that teh netlink interface is always used as a fallbac if the proc interface is not available. The -n option essantially is not a use netlink option but a do not use /proc option. Attached is a patch for the acpid source package that adds the necessary definitions to input_layer.c and sets the `-n' option in Thanks for the patch. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521280: [Pkg-acpi-devel] Bug#521280: doesn't seem to affect thinkpad-acpi only
On Mon, 9 Nov 2009 09:56:03 +0100 Michael Meskes mes...@debian.org wrote: Hi, another thing that needs to be done is to start acpid with the `-n' option. Why? Please note that teh netlink interface is always used as a fallbac if the proc interface is not available. The -n option essantially is not a use netlink option but a do not use /proc option. My mistake. I didn't realise I had /proc/acpi/event enabled on the machine I tried this. harry signature.asc Description: PGP signature
Bug#521280: doesn't seem to affect thinkpad-acpi only
tags 521280 + patch thanks Hi, another thing that needs to be done is to start acpid with the `-n' option. Attached is a patch for the acpid source package that adds the necessary definitions to input_layer.c and sets the `-n' option in acpid.default. Please apply this patch, as acpid is currently broken. Cheers, harry diff -urN a/debian/acpid.default b/debian/acpid.default --- a/debian/acpid.default 2009-11-08 17:17:37.0 +0100 +++ b/debian/acpid.default 2009-11-08 17:10:12.692962806 +0100 @@ -1,7 +1,7 @@ # Options to pass to acpid # # OPTIONS are appended to the acpid command-line -#OPTIONS= +OPTIONS=-n # Modules to load before starting acpid # diff -urN a/debian/patches/input_events.diff b/debian/patches/input_events.diff --- a/debian/patches/input_events.diff 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/input_events.diff 2009-11-08 17:06:37.816447496 +0100 @@ -0,0 +1,55 @@ +diff -ruN a/input_layer.c b/input_layer.c +--- a/input_layer.c 2009-10-20 18:17:28.135310348 +0200 b/input_layer.c 2009-10-20 18:32:04.907313692 +0200 +@@ -57,7 +57,50 @@ + {{{0,0}, EV_KEY, KEY_SUSPEND, 1}, + button/suspend SUSP 0080 }, + {{{0,0}, EV_SW, SW_LID, 1}, button/lid LID close}, +- {{{0,0}, EV_SW, SW_LID, 0}, button/lid LID open} ++ {{{0,0}, EV_SW, SW_LID, 0}, button/lid LID open}, ++ /* blue access IBM button on Thinkpad T42p*/ ++ {{{0,0}, EV_KEY, KEY_PROG1, 1}, button/prog1 PROG1 0080 }, ++ {{{0,0}, EV_KEY, KEY_VENDOR, 1}, ++ button/vendor VNDR 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F1, 1}, button/fnf1 FNF1 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F2, 1}, button/fnf2 FNF2 0080 }, ++ /* Fn-F2 produces KEY_BATTERY on Thinkpad T42p */ ++ {{{0,0}, EV_KEY, KEY_BATTERY, 1}, ++ button/battery BAT 0080 }, ++ {{{0,0}, EV_KEY, KEY_SCREENLOCK, 1}, ++ button/screenlock SCRLCK 0080 }, ++ {{{0,0}, EV_KEY, KEY_COFFEE, 1}, ++ button/coffee CFEE 0080 }, ++ {{{0,0}, EV_KEY, KEY_SLEEP, 1}, button/sleep SBTN 0080 }, ++ {{{0,0}, EV_KEY, KEY_WLAN, 1}, button/wlan WLAN 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F6, 1}, button/fnf6 FNF6 0080 }, ++ {{{0,0}, EV_KEY, KEY_SWITCHVIDEOMODE, 1}, ++ button/videomode VMOD 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F9, 1}, button/fnf9 FNF9 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F10, 1}, ++ button/fnf10 FNF10 0080 }, ++ {{{0,0}, EV_KEY, KEY_FN_F11, 1}, ++ button/fnf11 FNF11 0080 }, ++ /* Fn-F9 produces KEY_F24 on Thinkpad T42p */ ++ {{{0,0}, EV_KEY, KEY_F24, 1}, button/fnf24 FNF24 0080 }, ++ {{{0,0}, EV_MSC, 4, 12}, button/fnbs FNBS 0080 }, ++ {{{0,0}, EV_MSC, 4, 13}, button/fnins FNINS 0080 }, ++ {{{0,0}, EV_MSC, 4, 14}, button/fndel FNDEL 0080 }, ++ {{{0,0}, EV_MSC, 4, 18}, button/fnpgdown FNPGDOWN 0080 }, ++ {{{0,0}, EV_KEY, KEY_ZOOM, 1}, button/zoom ZOOM 0080 }, ++ {{{0,0}, EV_KEY, KEY_BRIGHTNESSDOWN, 1}, ++ button/brightnessdown BRTDN 0080 }, ++ {{{0,0}, EV_KEY, KEY_BRIGHTNESSUP, 1}, ++ button/brightnessup BRTUP 0080 }, ++ {{{0,0}, EV_KEY, KEY_KBDILLUMTOGGLE, 1}, ++ button/kbdillumtoggle KBILLUM 0080 }, ++ {{{0,0}, EV_KEY, KEY_VOLUMEDOWN, 1}, ++ button/volumedown VOLDN 0080 }, ++ {{{0,0}, EV_KEY, KEY_VOLUMEUP, 1}, ++ button/volumeup VOLUP 0080 }, ++ /* mute button produces KEY_MIN_INTERESTING on Thinkpad T42p */ ++ {{{0,0}, EV_KEY, KEY_MIN_INTERESTING, 1}, ++ button/mininteresting MININT 0080 } + }; + + /*--*/ diff -urN a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2009-11-08 17:17:37.0 +0100 +++ b/debian/patches/series 2009-11-08 17:07:06.117286756 +0100 @@ -1,3 +1,4 @@ event.c.diff netlink.diff +input_events.diff gcc44.diff signature.asc Description: PGP signature
Bug#521280: doesn't seem to affect thinkpad-acpi only
Hi, acpid in principle supports button events from the input layer. The problem is just, that the necessary events are not defined. This is from Debian's acpid (1.0.10-2) in file input_layer.c: static struct evtab_entry evtab[] = { {{{0,0}, EV_KEY, KEY_POWER, 1}, button/power PBTN 0080 }, {{{0,0}, EV_KEY, KEY_SLEEP, 1}, button/sleep SBTN 0080 }, {{{0,0}, EV_KEY, KEY_SUSPEND, 1}, button/suspend SUSP 0080 }, {{{0,0}, EV_SW, SW_LID, 1}, button/lid LID close}, {{{0,0}, EV_SW, SW_LID, 0}, button/lid LID open} }; I've recorded all the button events when the Fn key is pressed on my Thinkpad T42p and also merged events found in the version here: http://www.tedfelix.com/linux/acpid-netlink.html With these additions, acpid is able to listen to all Fn button events. So acpid should be patched to include these: static struct evtab_entry evtab[] = { {{{0,0}, EV_KEY, KEY_POWER, 1}, button/power PBTN 0080 }, {{{0,0}, EV_KEY, KEY_SLEEP, 1}, button/sleep SBTN 0080 }, {{{0,0}, EV_KEY, KEY_SUSPEND, 1}, button/suspend SUSP 0080 }, {{{0,0}, EV_SW, SW_LID, 1}, button/lid LID close}, {{{0,0}, EV_SW, SW_LID, 0}, button/lid LID open}, /* blue access IBM button on Thinkpad T42p*/ {{{0,0}, EV_KEY, KEY_PROG1, 1}, button/prog1 PROG1 0080 }, {{{0,0}, EV_KEY, KEY_VENDOR, 1}, button/vendor VNDR 0080 }, {{{0,0}, EV_KEY, KEY_FN_F1, 1}, button/fnf1 FNF1 0080 }, {{{0,0}, EV_KEY, KEY_FN_F2, 1}, button/fnf2 FNF2 0080 }, /* Fn-F2 produces KEY_BATTERY on Thinkpad T42p */ {{{0,0}, EV_KEY, KEY_BATTERY, 1}, button/battery BAT 0080 }, {{{0,0}, EV_KEY, KEY_SCREENLOCK, 1}, button/screenlock SCRLCK 0080 }, {{{0,0}, EV_KEY, KEY_COFFEE, 1}, button/coffee CFEE 0080 }, {{{0,0}, EV_KEY, KEY_SLEEP, 1}, button/sleep SBTN 0080 }, {{{0,0}, EV_KEY, KEY_WLAN, 1}, button/wlan WLAN 0080 }, {{{0,0}, EV_KEY, KEY_FN_F6, 1}, button/fnf6 FNF6 0080 }, {{{0,0}, EV_KEY, KEY_SWITCHVIDEOMODE, 1}, button/videomode VMOD 0080 }, {{{0,0}, EV_KEY, KEY_FN_F9, 1}, button/fnf9 FNF9 0080 }, {{{0,0}, EV_KEY, KEY_FN_F10, 1}, button/fnf10 FNF10 0080 }, {{{0,0}, EV_KEY, KEY_FN_F11, 1}, button/fnf11 FNF11 0080 }, /* Fn-F9 produces KEY_F24 on Thinkpad T42p */ {{{0,0}, EV_KEY, KEY_F24, 1}, button/fnf24 FNF24 0080 }, {{{0,0}, EV_KEY, KEY_SUSPEND, 1}, button/suspend SUSP 0080 }, {{{0,0}, EV_MSC, 4, 12}, button/fnbs FNBS 0080 }, {{{0,0}, EV_MSC, 4, 13}, button/fnins FNINS 0080 }, {{{0,0}, EV_MSC, 4, 14}, button/fndel FNDEL 0080 }, {{{0,0}, EV_MSC, 4, 18}, button/fnpgdown FNPGDOWN 0080 }, {{{0,0}, EV_KEY, KEY_ZOOM, 1}, button/zoom ZOOM 0080 }, {{{0,0}, EV_KEY, KEY_BRIGHTNESSDOWN, 1}, button/brightnessdown BRTDN 0080 }, {{{0,0}, EV_KEY, KEY_BRIGHTNESSUP, 1}, button/brightnessup BRTUP 0080 }, {{{0,0}, EV_KEY, KEY_KBDILLUMTOGGLE, 1}, button/kbdillumtoggle KBILLUM 0080 }, {{{0,0}, EV_KEY, KEY_VOLUMEDOWN, 1}, button/volumedown VOLDN 0080 }, {{{0,0}, EV_KEY, KEY_VOLUMEUP, 1}, button/volumeup VOLUP 0080 }, /* mute button produces KEY_MIN_INTERESTING on Thinkpad T42p */ {{{0,0}, EV_KEY, KEY_MIN_INTERESTING, 1}, button/mininteresting MININT 0080 } }; Other models might produce different events. They can all be found with `input-events' from the input-utils package. To find the device to listen on, call lsinput and look for the right one. For instance mine shows: # lsinput ... /dev/input/event6 bustype : BUS_HOST vendor : 0x1014 product : 0x5054 version : 16641 name: ThinkPad Extra Buttons phys: thinkpad_acpi/input0 bits ev : EV_SYN EV_KEY EV_MSC ... So I would call `input-events 6' Cheers, harry signature.asc Description: PGP signature
Bug#521280: doesn't seem to affect thinkpad-acpi only
Hi, I think an even better solution for button events would be for acpid to support arbitrary events. Details can be found in a bug report I created upstream: https://sourceforge.net/tracker/?func=detailaid=2881849group_id=33140atid=407344. Cheers, harry signature.asc Description: PGP signature
Bug#521280: doesn't seem to affect thinkpad-acpi only
Hi, I am having similar problems with this issue. We are running Lenny 5.0.2 on several dozen clients and have backported kernel 2.6.30 from unstable to get better hardware support. Now, since CONFIG_ACPI_PROC_EVENT has been disabled with 2.6.29 and above, the power button has stopped working on our desktop machines. As far as I have understood this issue, acpid is moving from the proc-interface to some hal/input-layer related model and thus the Debian kernel-team has dropped CONFIG_ACPI_PROC_EVENT. I have tested with both a machine running unstable with latest package base and our Lenny clients with just the backported kernel and old acpid. Can someone enlighten me how I can fix this ? Where should I watch for events generated by the power button now ? Adrian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org