Difference between revisions of "Problem with LCD brightness buttons"

From ThinkWiki
Jump to: navigation, search
(Problems increasing brightness with newer Lenovo thinkpad (x60).)
 
(Affected Models)
Line 5: Line 5:
  
 
A recent change in one of the newer Lenovo bios updates for (at least for the x60) seems to have swaped the acpi keycode for increasing brightness with the acpi code for swaping displays (err... primary to external I believe).  
 
A recent change in one of the newer Lenovo bios updates for (at least for the x60) seems to have swaped the acpi keycode for increasing brightness with the acpi code for swaping displays (err... primary to external I believe).  
 +
 +
The undesireable behavior is that when trying to increase brightness, the display (for X) completely goes blank.
  
 
Bug reports:
 
Bug reports:
  
 
https://bugs.freedesktop.org/show_bug.cgi?id=9355
 
https://bugs.freedesktop.org/show_bug.cgi?id=9355
 +
 +
 +
Details:
 +
 +
* Doesn't happen if acpid isn't running.
 +
* Doesn't happen if you are in a vtty until all acpi events (will post the code with some logs later) are processed.
 +
* The behavior of the display going out and not coming back may be related to the i810 driver.
 +
 +
Tested on:
 +
* Fedora Core 6 (same behavior)
 +
* Kubuntu Edgy 6.10 (same behavior)

Revision as of 09:00, 3 January 2007

Affected Models

A recent change in one of the newer Lenovo bios updates for (at least for the x60) seems to have swaped the acpi keycode for increasing brightness with the acpi code for swaping displays (err... primary to external I believe).

The undesireable behavior is that when trying to increase brightness, the display (for X) completely goes blank.

Bug reports:

https://bugs.freedesktop.org/show_bug.cgi?id=9355


Details:

  • Doesn't happen if acpid isn't running.
  • Doesn't happen if you are in a vtty until all acpi events (will post the code with some logs later) are processed.
  • The behavior of the display going out and not coming back may be related to the i810 driver.

Tested on:

  • Fedora Core 6 (same behavior)
  • Kubuntu Edgy 6.10 (same behavior)