Bug 723720 - backlight for (ASUS G73SW notebook) keyboard cannot be set from keyboard
Summary: backlight for (ASUS G73SW notebook) keyboard cannot be set from keyboard
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-20 21:39 UTC by netbeans
Modified: 2011-08-30 11:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-30 11:08:30 UTC
Type: ---


Attachments (Terms of Use)

Description netbeans 2011-07-20 21:39:39 UTC
Description of problem:
keyboard background lights dont work ( not adjustable ) 

I have an ASUS G73SW notebook. The keyboard can be LED lite to various degrees of brightness. Under WIN 7, this feature does work. on linux, it plays dead.

The backlight for the screen is keyboard settable. The enable/disable wireless keys appears to work, but not always - not sure why.

There are other specialized keys, but I dont know how to match them up with some functionality.

Version-Release number of selected component (if applicable):


How reproducible:
so far always.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
I am not sure if this is a request for a new feature, or a bug, or a lack of understanding on how the keyboard works in getting notebook features to work.

Comment 1 Josh Boyer 2011-08-24 14:09:29 UTC
This looks like it might be supported in the upcoming 3.1 kernel with commits e9809c0b9670656855655d8ed6dc33718ec12ba2 and af965e973276b015d1b7d9ee78ed8d8df9d6bc98.

The latest kernel in updates-testing for Fedora 16 should have those commits.  We won't be backporting those to Fedora 14 due to the large gap in kernel versions and the relatively short lifetime left on that release.


Note You need to log in before you can comment on or make changes to this bug.