Re: regression since 2.6.36: backlight in sony-laptop not working

Dmitry Torokhov
2010-11-17T07:12:13Z

On Wed, Nov 17, 2010 at 03:30:06PM +0900, Norbert Preining wrote:
> Hi Mattia, hi Dmitry,
>
> On Fr, 12 Nov 2010, Mattia Dongili wrote:
> > backlight (actually Fn+F[56]) is one of those keys the needs remapping
> > these days, i.e. if xev doesn't get any event in X then you may need
> > something like:
>
> Ok, I have now done the fllowing:
> - recompiled a input-kbd binary with a relaxed version check
> - if (EV_VERSION != version) {
> + if (EV_VERSION > version) {
> in input.c, line 104 of input-utils.
>
> - created a vaio-kbd from the output of input-kbd and changed the
> keys that hat keycode 470 and 471 (those shown in evtest 8)
> to key_brightness:
>
> $ diff -u <(./input-kbd 8) vaio-kbd
> --- /dev/fd/63 2010-11-17 15:24:32.023696588 +0900
> +++ vaio-kbd 2010-11-17 15:24:02.000000000 +0900
> @@ -13,8 +13,8 @@
> 0x0006 = 467 # KEY_FN_F2
> 0x0007 = 468 # KEY_FN_F3
> 0x0008 = 469 # KEY_FN_F4
> -0x0009 = 470 # KEY_FN_F5
> -0x000a = 471 # KEY_FN_F6
> +0x0009 = 224 # KEY_BRIGHTNESSDOWN
> +0x000a = 225 # KEY_BRIGHTNESSUP
> 0x000b = 472 # KEY_FN_F7
> 0x000c = 473 # KEY_FN_F8
> 0x000d = 474 # KEY_FN_F9
> $
>
> remember:
> evtest /dev/input/event8 reports code 470 and code 471 for the respective
> Fn-F5 and Fn-F6 combinations.
>
> > output to a file, edit it to change the keys you need remapped and run
> > `input-kbd -f <file> <devNo>`.
>
> Then I run
> $ ./input-kbd -f vaio-kbd 8
> /dev/input/event8
> map: 44 keys, size: 59/64
> parse error: /dev/input/event8

"Parse error" suggests issue with teh keymap file.

> $
> with the effect that still brigthness is not working.
>
> If someone can explain what is wrong here and how to get this fixed
> that would be nice, because up to now on the sony-vaio mailing list
> I heard many complains about disappearing brightness, I hope we can
> fix that.
>

I did compile input-utils from sid and after fixing up the version issue
I can change mappings on my AT keyboard. Could you try doing the same -
maybe the issue is with the sony-laptop driver (rather its irectaion
with the large scancode support) as well as with input-kbd utility.

Thanks.

--
Dmitry