Comment 17 for bug 625770

2010/11/25 Martin Pitt <email address hidden>:
> Hm, no, this keymap problem isn't related to the kernel bug. Can you
> please try this manually:
>
> - find out the input device of the hotkeys module with
> /lib/udev/findkeyboards, i. e. "input/event6" (in
> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/627890/comments/15)

$ /lib/udev/findkeyboards
AT keyboard: input/event2
module: input/event3

> - run
>
>     sudo /lib/udev/keymap input/event6 0x00 brightnessdown 0x10
> brightnessup
>
>  (adapt input/event6 accordingly to the findkeyboards output)

(PROBLEM)
$ sudo /lib/udev/keymap input/event3 0x00 brightnessdown 0x10 brightnessup
EVIOCSKEYCODE: Invalid argument
setting scancode 0x 0 to key code 224 failed
EVIOCSKEYCODE: Invalid argument
setting scancode 0x10 to key code 225 failed

I'v also re-done the step to find the scan codes:

$ sudo /lib/udev/keymap -i input/event3
Press ESC to finish
scan code: 0x00 key code: fn_f5
scan code: 0x10 key code: fn_f6
scan code: 0x11 key code: fn_f5
scan code: 0x10 key code: fn_f6
scan code: 0x11 key code: fn_f5
scan code: 0x10 key code: fn_f6
scan code: 0x11 key code: fn_f5
scan code: 0x10 key code: fn_f6

But there is something strange: the first key that I press receives a
0x00 scan codes but the next times it is correctly recognized. It is
not related to the F5 key as you can see below:

$ sudo /lib/udev/keymap -i input/event3
Press ESC to finish
scan code: 0x00 key code: fn_f6
scan code: 0x11 key code: fn_f5
scan code: 0x10 key code: fn_f6
scan code: 0x11 key code: fn_f5
scan code: 0x10 key code: fn_f6

$ sudo /lib/udev/keymap -i input/event3
Press ESC to finish
scan code: 0x00 key code: fn_f9
scan code: 0x14 key code: fn_f10
scan code: 0x15 key code: fn_f9
scan code: 0x14 key code: fn_f10

Is it normal?

I've also tried the suggested command with the correct codes:
$ sudo /lib/udev/keymap input/event3 0x11 brightnessdown 0x10 brightnessup
EVIOCSKEYCODE: Invalid argument
setting scancode 0x11 to key code 224 failed
EVIOCSKEYCODE: Invalid argument
setting scancode 0x10 to key code 225 failed

Martin, please note that in my system I have the patch su suggested as
reported here: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/625770/comments/12