Comment 7 for bug 281732

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote : Re: Mute button on thinkpad x200/x200s

hi!

I have just done the troubleshooting-checklist on https://wiki.ubuntu.com/Hotkeys/Troubleshooting !

1. run xev to test whether a keypress event is seen:
This gives no keypress event with thinkpad extrabuttons!

5. enumerate the available input devices as seen by hal:
hal-find-by-capability --capability input | xargs -n1 lshal -u

udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_4'
  button.has_state = true (bool)
  button.state.value = true (bool)
  button.type = 'radio' (string)
  info.addons.singleton = {'hald-addon-input'} (string list)
  info.callouts.add = {'hal-setup-keymap', 'debian-setup-keyboard'} (string list)
  info.capabilities = {'input', 'input.keys', 'input.switch', 'button', 'input.keymap'} (string list)
  info.category = 'input' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  info.product = 'ThinkPad Extra Buttons' (string)
  info.subsystem = 'input' (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_4' (string)
  input.device = '/dev/input/event10' (string)
  input.keymap.data = {'0x01:screenlock', '0x02:battery', '0x03:sleep', '0x04:radio', '0x06:switchvideomode', '0x07:f22', '0x08:f24', '0x0b:suspend', '0x0f:brightnessup', '0x10:brightnessdown', '0x11:kbdillumtoggle', '0x13:zoom', '0x14:volumeup', '0x15:volumedown', '0x16:mute', '0x17:prog1', 'e05d:menu'} (string list)
  input.product = 'ThinkPad Extra Buttons' (string)
  input.x11_driver = 'evdev' (string)
  input.xkb.layout = 'de' (string)
  input.xkb.model = 'pc105' (string)
  input.xkb.rules = 'evdev' (string)
  input.xkb.variant = 'nodeadkeys' (string)
  linux.device_file = '/dev/input/event10' (string)
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'input' (string)
  linux.sysfs_path = '/sys/devices/virtual/input/input10/event10' (string)

with "sudo input-events 10" and pressing the hotkey (mute button and volume up/down) there is also no event shown.

10. If the events are reported by more than one input device then report a kernel bug (Ubuntu linux package) because it should only send the event on one device.
11. if not found with input-events, use acpi_listen to determine whether the key is coming through as an ACPI event instead of a keypress

acpi_listen gives only an output pressing other thinkpad keys: (ThinkVantage, FN+F3, Brightness up/down,...)
ibm/hotkey HKEY 00000080 00001018
ibm/hotkey HKEY 00000080 00001003
ibm/hotkey HKEY 00000080 00001010
video LCD0 00000086 00000000
ibm/hotkey HKEY 00000080 00001011
video LCD0 00000087 00000000

13. if there is neither an ACPI event nor an input event, this is probably also a kernel bug, though probably harder to diagnose (WMI, perhaps?)

further information:

lshal |grep system.hardware
  system.hardware.primary_video.product = 10818 (0x2a42) (int)
  system.hardware.primary_video.vendor = 32902 (0x8086) (int)
  system.hardware.product = '2767B35' (string)
  system.hardware.serial = 'L3D9557' (string)
  system.hardware.uuid = 'B2999701-49A6-11CB-9FF6-9729DA065BC4' (string)
  system.hardware.vendor = 'LENOVO' (string)
  system.hardware.version = 'ThinkPad T400' (string)