[ltp] CALL FOR TESTING: thinkpad-acpi BETA release 0.14-20070708

[Henrique de Moraes Holschuh]

On Sun, 08 Jul 2007, U Kuehn wrote:
> just a random test point on my T41 (or problem report :)
> 
> I am currently running 2.6.21.5 with tux-on-ice 2.2.10.2 (formerly known
> as suspend2). I have ibm_acpi as a modules, loaded with
>                 modprobe ibm_acpi experimental=1 hotkey=enable,0x090c
> and
>                 # 0x080c is default, we want also
>                 # f9 for hibernate-reboot
>                 echo 0x090c > /proc/acpi/ibm/hotkey
>                 echo enable >/proc/acpi/ibm/hotkey
> to be sure. Normally, I get fn-f3, fn-f4, fn-f9, fn-f12 as events for
> acpid via /proc/acpi/event:
> event=(ibm/hotkey HKEY 00000080 00001003)
> event=(ibm/hotkey HKEY 00000080 00001004)
> event=(ibm/hotkey HKEY 00000080 00001009)
> event=(ibm/hotkey HKEY 00000080 0000100c)
> 
> When using your patch release 20070801 against 2.6.21.6 with tux-on-ice
> 2.2.10.2 under gnome (tpb, but no hal), I get nothing. No events, nothing.

Check if you are getting input layer events using input-events from
input-utils.  If you want the ACPI events, you need to either:

1. reprogram the keys you want ACPI events to KEY_UNKNOWN or KEY_RESERVED using input-kbd

or

2. you need to make sure *nothing* is helding the thinkpad-acpi input/event
devices open

or

3. you need to compile thinkpad-acpi with CONFIG_THINKPAD_ACPI_INPUT_ENABLED
*un*set (i.e. disabled).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh