http://bugzilla.opensuse.org/show_bug.cgi?id=907368 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrej.lazo@gmail.com, | |tiwai@suse.com Flags| |needinfo?(andrej.lazo@gmail | |.com) --- Comment #1 from Takashi Iwai --- To see whether it's a kernel issue, try the following: - Install evtest package - Go to Linux console (e.g. VT1), be root. - Run evtest /dev/input/by-path/platform-i8042-serio-0-event-kbd (the device path might be different, but you must have a similar one.) - Press brightness up/down key. If this shows the proper key events (KEY_BRIGHTNESSUP and KEY_BRIGHTNESSDOWN), then the kernel reports correctly. The problem is rather in the upper layer, either X or KDE. If the keys aren't reported, then it's a kernel problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 Andrej Lazo changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrej.lazo@gmail | |.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 Andrej Lazo changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrej.lazo@gmail | |.com) | --- Comment #4 from Andrej Lazo --- (In reply to Takashi Iwai from comment #3)

You must run evtest not on X but on Linux console (VT1 or else). Otherwise the key events are already grabbed before you see it on xev.

OK I did it it display "^@" but display is going darker - when I press fn key related to VolumeUp it display a lot, including Tag VolumeUp. ################# this is done on 13.1 as there is no response on 13.2 ################## -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #6 from Takashi Iwai --- Also, another thing to try is pass video.use_native_backlight=0 boot option. You might need to pass together with acpi_backlight=video boot option. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #8 from Andrej Lazo --- (In reply to Takashi Iwai from comment #5)

So the key isn't emitted through the normal PS2 unlike the recent HP machines. Try other /dev/input/event* files on openSUSE 13.1 kernel. One of them should correspond to the input device from the ACPI video driver.

Also, please give the hwinfo outputs running on both openSUSE 13.1 and 13.2 kernels. Attach the files to Bugzilla.

linux-avmf:~ # evtest /dev/input/event5 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0 Input device name: "Video Bus" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 224 (Brightness down) Event code 225 (Brightness up) Event code 227 (?) Event code 241 (?) Event code 242 (?) Event code 243 (?) Event code 244 (?) Event code 245 (?) Testing ... (interrupt to exit) Event: time 1417038101.228446, type 1 (Key), code 224 (Brightness down), value 1 Event: time 1417038101.228446, -------------- Report Sync ------------ Event: time 1417038101.228484, type 1 (Key), code 224 (Brightness down), value 0 Event: time 1417038101.228484, -------------- Report Sync ------------ Event: time 1417038102.344158, type 1 (Key), code 225 (Brightness up), value 1 Event: time 1417038102.344158, -------------- Report Sync ------------ Event: time 1417038102.344194, type 1 (Key), code 225 (Brightness up), value 0 Event: time 1417038102.344194, -------------- Report Sync ------------ ^C -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #10 from Takashi Iwai --- (In reply to Andrej Lazo from comment #8)

(In reply to Takashi Iwai from comment #5)

...

So the key isn't emitted through the normal PS2 unlike the recent HP machines. Try other /dev/input/event* files on openSUSE 13.1 kernel. One of them should correspond to the input device from the ACPI video driver.

Also, please give the hwinfo outputs running on both openSUSE 13.1 and 13.2 kernels. Attach the files to Bugzilla.

linux-avmf:~ # evtest /dev/input/event5 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0 Input device name: "Video Bus" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 224 (Brightness down) Event code 225 (Brightness up) Event code 227 (?) Event code 241 (?) Event code 242 (?) Event code 243 (?) Event code 244 (?) Event code 245 (?) Testing ... (interrupt to exit) Event: time 1417038101.228446, type 1 (Key), code 224 (Brightness down), value 1 Event: time 1417038101.228446, -------------- Report Sync ------------ Event: time 1417038101.228484, type 1 (Key), code 224 (Brightness down), value 0 Event: time 1417038101.228484, -------------- Report Sync ------------ Event: time 1417038102.344158, type 1 (Key), code 225 (Brightness up), value 1 Event: time 1417038102.344158, -------------- Report Sync ------------ Event: time 1417038102.344194, type 1 (Key), code 225 (Brightness up), value 0 Event: time 1417038102.344194, -------------- Report Sync ------------ ^C

So far, so good. Try similarly on openSUSE 13.2 kernel, too. No input device gives like this at all? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #12 from Andrej Lazo --- openSuSe 13.2 ###################### Event: time 1417110181.263377, -------------- SYN_REPORT ------------ vEvent: time 1417110181.363963, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f Event: time 1417110181.363963, type 1 (EV_KEY), code 47 (KEY_V), value 0 Event: time 1417110181.363963, -------------- SYN_REPORT ------------ Event: time 1417110184.508741, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1417110184.508741, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1 Event: time 1417110184.508741, -------------- SYN_REPORT ------------ Event: time 1417110184.515771, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1417110184.515771, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0 Event: time 1417110184.515771, -------------- SYN_REPORT ------------ Event: time 1417110185.611481, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1417110185.611481, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1 Event: time 1417110185.611481, -------------- SYN_REPORT ------------ Event: time 1417110185.619071, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1417110185.619071, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0 Event: time 1417110185.619071, -------------- SYN_REPORT ------------ Event: time 1417110203.270966, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d Event: time 1417110203.270966, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1417110203.270966, -------------- SYN_REPORT ------------ Event: time 1417110203.473532, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2e Event: time 1417110203.473532, type 1 (EV_KEY), code 46 (KEY_C), value 1 Event: time 1417110203.473532, -------------- SYN_REPORT ------------ ^C linux-b4vl:~ # evtest /dev/input/event11 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "HP WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 138 (KEY_HELP) Event code 141 (KEY_SETUP) Event code 148 (KEY_PROG1) Event code 153 (KEY_DIRECTION) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 226 (KEY_MEDIA) Event code 240 (KEY_UNKNOWN) Event code 358 (KEY_INFO) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Event type 5 (EV_SW) Event code 1 (SW_TABLET_MODE) Event code 5 (SW_DOCK) Properties: Testing ... (interrupt to exit) ############## no response to fn (f7/f8) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 Andrej Lazo changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrej.lazo@gmail | |.com) | --- Comment #14 from Andrej Lazo --- I've tested fn keys while install - and when kernel was loading they reacted. Now I'am able to change LCD brightness via battery monitor but not using fn keys. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #16 from Takashi Iwai --- (In reply to Andrej Lazo from comment #14)

I've tested fn keys while install - and when kernel was loading they reacted.

Now I'am able to change LCD brightness via battery monitor but not using fn keys.

It might be that some wrong keymap is applied for your device. You can try to remove /usr/lib/udev/hwdb.d/60-keyboard.hwdb and reboot. (Better to make a backup that file to restore later, of course.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #18 from Andrej Lazo --- moved ########## linux-b4vl:~ # ls /usr/lib/udev/hwdb.d/60-keyboard.hwdb ls: cannot access /usr/lib/udev/hwdb.d/60-keyboard.hwdb: No such file or directory also removed video.use_native_backlight=0 acpi_backlight=video fn keys still doesn't work -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #20 from Andrej Lazo --- (In reply to Takashi Iwai from comment #15)

WMI hotkey is an unlikely target. It might provide something about brightness but only for old models. The newer models should give the key either via ACPI video bus or the normal i8042 serial I/O (aka PS/2 port). On openSUSE 13.1, it looks like that the former one took. But the behavior depends on BIOS, i.e. ACPI OSI string may influence somehow, so it's not really sure.

Try to find out the event device for video bus, and check whether the key comes with it.

Also, check the value in /sys/module/video/parameters/brightness_switch_enabled. If it's N, try to turn it on: echo 1 > /sys/module/video/parameters/brightness_switch_enabled and retest.

do you mean this? ####################### linux-b4vl:~ # evtest /dev/input/event5 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0 Input device name: "Video Bus" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 227 (KEY_SWITCHVIDEOMODE) Event code 241 (KEY_VIDEO_NEXT) Event code 242 (KEY_VIDEO_PREV) Event code 243 (KEY_BRIGHTNESS_CYCLE) Event code 244 (KEY_BRIGHTNESS_ZERO) Event code 245 (KEY_DISPLAY_OFF) Properties: Testing ... (interrupt to exit) ########## doesn't register -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #22 from Takashi Iwai --- OK, then it's BIOS that has changed the behavior. Let's retry acpi_osi things. Pass acpi_osi="!Windows 2012" and give the dmesg output. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #24 from Andrej Lazo --- Created attachment 615289 --> http://bugzilla.opensuse.org/attachment.cgi?id=615289&action=edit dmesg -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #26 from Andrej Lazo --- (In reply to Takashi Iwai from comment #25)

You passed wrongly: pass acpi_osi="!Windows 2012"

I have tried. using Yast, edit grub and also during boot (e line) acpi_osi=""!Windows 2012"" acpi_osi=\"!Windows 2012\" ########################## tell me exactly what to do -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #28 from Andrej Lazo --- Created attachment 615292 --> http://bugzilla.opensuse.org/attachment.cgi?id=615292&action=edit dmesg 2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #30 from Andrej Lazo --- (In reply to Takashi Iwai from comment #29)

It's only for testing, so better to edit in GRUB menu than in YaST. Just pass: acpi_osi="!Windows 2012"

See that you gave the opening quote at the wrong place. Check dmesg output.

I did - that was the first dmesg ############################ when I entered acpi_osi="!Windows 2012" during boot - It later displayed "acpi_osi=!Windows 2012" in hwinfo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 --- Comment #32 from Andrej Lazo --- (In reply to Takashi Iwai from comment #31)

OK, then ACPI OSI doesn't matter for the behavior. Hmm...

We can at least narrow down the regression kernel. 3.13, 3.14 and 3.15 kernel packages are available at: http://download.opensuse.org/repositories/home:/tiwai:/kernel:/3.13/ http://download.opensuse.org/repositories/home:/tiwai:/kernel:/3.14/ http://download.opensuse.org/repositories/home:/tiwai:/kernel:/3.15/

3.12 kernel is found in Kernel:SLE12.

Check which one starts showing the wrong behavior. I guess it's relatively new.

I do that on monday -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=907368 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(andrej.lazo@gmail | |.com) -- You are receiving this mail because: You are on the CC list for the bug.