[Bug 955176] Re: Brightness hotkeys misdetected on Eee Pc

[greg]

> The handlers that are probably deprecated are mostly those for ASUS and
> Toshiba hardware, which no one who works on this package has direct access
> to.

At least on Asus notebooks everything should be handled through the
kernel, with the asus-laptop module.

> Could you please run acpi_listen and show the actual ACPI events generated
> for each of these keys? This may be important later in case a different
> ASUS model isn't being handled correctly in the kernel yet.

The eeepc-laptop driver generates ATKD events in the range 0x20 to 0x2f,
depending on the current brightness, where 0x20 is the lowest setting
and 0x2f is the highest. For instance:

increment:
hotkey ATKD 0000002c 00000003
hotkey ATKD 0000002e 00000006

decrement:
hotkey ATKD 0000002c 00000004
hotkey ATKD 0000002a 00000004

This conflicts with the asus-brightness-down acpid event, which matches
all of these events, no matter if the brightness is actually incremented
or decremented.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to acpi-support in Ubuntu.
https://bugs.launchpad.net/bugs/955176

Title:
  Brightness hotkeys misdetected on Eee Pc

Status in “acpi-support” package in Ubuntu:
  Incomplete

Bug description:
  The acpid scripts that ship with acpi-support misdetect the brightness
  keys on the Eee PC 901 (and probably most other models, as the ACPI
  events are very similar). Both keys, brightness up and down, are
  detected as brightness down. On the other hand, brightness events are
  already handled by eeepc_laptop, so any additional handling by acpi-
  support is harmful and results in crazy behaviour if one presses the
  keys. Removing the acpi-support package solves the issue.

  But, the real WTF is, why does Ubuntu *still* ship acpi-support, and
  acpid? The hacky scripts it uses are largely outdated and cause more
  issues than they solve. ACPI events, bare for a few exceptions, are
  now handled either directly by the kernel input layer, or other
  subsystems, like UPower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/955176/+subscriptions