Bug 758307 - Keyboard backlight keys do not work in Asus G73Sw laptop
Summary: Keyboard backlight keys do not work in Asus G73Sw laptop
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
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-11-29 16:48 UTC by Rudd-O DragonFear
Modified: 2012-03-01 16:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 16:34:24 UTC
Type: ---


Attachments (Terms of Use)

Description Rudd-O DragonFear 2011-11-29 16:48:46 UTC
Description of problem:

Function keys Fn+F3 and Fn+F4 (XF86KbdBrightnessDown/Up) do not change the keyboard backlight intensity.  Key to turn off keyboard backlight (keycode 248, upper left corner on keyboard) powers off the backlight, but doesn't power it back on.

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

Latest stable update

How reproducible:

Always

The kernel DOES support the backlight in the keyboard as an LED class driver -- but the Asus WMI kernel module does not associate it with the keyboard keys.

cat g73-keyblight 
#!/bin/sh

set -e

current=`cat /sys/class/leds/asus::kbd_backlight/brightness`
echo "current light level: $current"

if [ -n "$1" ]
then                                                                                                    
    current=$(($current $1))                                                                            
    echo "new light level: $current"                                                                    
    echo $current > /sys/class/leds/asus::kbd_backlight/brightness                                      
fi                                                                                                      
 
I can provide all the info you need.

Comment 1 Josh Boyer 2012-03-01 15:35:12 UTC
You didn't mention which kernel has this issue.  Based on the date, I'm going to guess it's a 3.1 based kernel.

Do the 3.2.7 or newer kernels help this at all?

Comment 2 Rudd-O DragonFear 2012-03-01 15:49:39 UTC
All the kernels, even 3.3-rc4 (my current kernel), have this issue.

Comment 3 Rudd-O DragonFear 2012-03-01 15:53:59 UTC
The keypresses are detected correctly... it's just that they do nothing.  They have no effect:

KeyPress event, serial 38, synthetic NO, window 0x7c00001,
    root 0x163, subw 0x0, time 335211652, (79,64), root:(79,960),
    state 0x10, keycode 238 (keysym 0x1008ff05, XF86KbdBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x7c00001,
    root 0x163, subw 0x0, time 335211652, (79,64), root:(79,960),
    state 0x10, keycode 238 (keysym 0x1008ff05, XF86KbdBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x7c00001,
    root 0x163, subw 0x0, time 335213754, (79,64), root:(79,960),
    state 0x10, keycode 237 (keysym 0x1008ff06, XF86KbdBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x7c00001,
    root 0x163, subw 0x0, time 335213754, (79,64), root:(79,960),
    state 0x10, keycode 237 (keysym 0x1008ff06, XF86KbdBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Comment 4 Rudd-O DragonFear 2012-03-01 15:55:54 UTC
This is not a kernel issue, apologies for my retardedness:

https://bugs.kde.org/show_bug.cgi?id=288179

Comment 5 Josh Boyer 2012-03-01 16:34:24 UTC
(In reply to comment #4)
> This is not a kernel issue, apologies for my retardedness:

No problem.  We all make mistakes sometimes.


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