Arch Linux

batmanfeynman

Member

Registered: 2019-02-10

Posts: 9

Unkown keybinding for XF86MonBrightnessUp

There seems to be a keybinding in my system for XF86MonBrightnessUp  and XF86MonBrightnessDown on my arch install. I don't know where this is specified or how to control it. How do I go about finding this out?

Reddit  post   where i first asked the question. It has more details.

Last edited by batmanfeynman (2019-07-22 16:48:41)

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,645

Re: Unkown keybinding for XF86MonBrightnessUp

Please don't make us read a reddit thread for details. What window manager are you using, and what have you tried so far?

batmanfeynman

Member

Registered: 2019-02-10

Posts: 9

Re: Unkown keybinding for XF86MonBrightnessUp

Sorry I guess. Here are the details.

I am using i3-gaps . I had initially thought that the brightness key wasn't working, so I went about reading this . First I installed xorg-xbacklight (This was sometime ago , I believe al I did was install this).  Now, today I tried installing acpilight .  So i made a udev rule as suggested on that page .

Contents of /etc/udev/rules.d/90-backlight.rules

SUBSYSTEM=="backlight", ACTION=="add", \
  RUN+="/bin/chgrp video /sys/class/backlight/%k/brightness", \
  RUN+="/bin/chmod g+w /sys/class/backlight/%k/brightness"
SUBSYSTEM=="leds", ACTION=="add", KERNEL=="*::kbd_backlight", \
  RUN+="/bin/chgrp video /sys/class/leds/%k/brightness", \
  RUN+="/bin/chmod g+w /sys/class/leds/%k/brightness"

I rebooted my system, but, i still required root privileges to use acpilight. So I uninstalled acpilight and moved on to light. (I did not delete this udev rule until after making my reddit post). light works fine. So I try adding a bindsym line to my i3 config:

bindsym XF86MonBrightnessUp exec light -A 10
bindsym XF86MonBrightnessDown exec light -U 10

After restarting i3 and trying out the keys, I notice the screen flashes 2 times and wasn't incrementing the brightness as i had expected. I went to a another virtual console (without x server)and tried out the keys. By looking at light -G , I figured out that the  brightness keys were actually incrementing brightness by around one percent(This was a variable quantity).

Ouptut of xev as requested by a reddit user:

With i3 bindsym active

RRNotify event, serial 57, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property Backlight, timestamp 12235875, state NewValue

RRNotify event, serial 57, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property BACKLIGHT, timestamp 12235875, state NewValue

RRNotify event, serial 58, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property Backlight, timestamp 12235878, state NewValue

RRNotify event, serial 58, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property BACKLIGHT, timestamp 12235878, state NewValue

without i3 bindsym

RRNotify event, serial 85, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property Backlight, timestamp 12336167, state NewValue

RRNotify event, serial 85, synthetic NO, window 0x2400001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property BACKLIGHT, timestamp 12336167, state NewValue

That user did not reply and i don't know how to interpret this.

Also I tried deleting the udev rule I made earlier and rebooting, But the lower level keybinding still persists.

batmanfeynman

Member

Registered: 2019-02-10

Posts: 9

Re: Unkown keybinding for XF86MonBrightnessUp

This is the full output of xev when I press the brightness control button

MappingNotify event, serial 74, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

KeyPress event, serial 74, synthetic NO, window 0x2200001,
    root 0x1ae, subw 0x0, time 2884392, (2,820), root:(971,852),
    state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 74, synthetic NO, window 0x2200001,
    root 0x1ae, subw 0x0, time 2884392, (2,820), root:(971,852),
    state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

RRNotify event, serial 75, synthetic NO, window 0x2200001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property Backlight, timestamp 2884414, state NewValue

RRNotify event, serial 75, synthetic NO, window 0x2200001,
    subtype XRROutputPropertyChangeNotifyEvent
    output eDP1, property BACKLIGHT, timestamp 2884414, state NewValue

batmanfeynman

Member

Registered: 2019-02-10

Posts: 9

Re: Unkown keybinding for XF86MonBrightnessUp

dmesg prints this when i pres the brightness control keys

[ 3987.052604] atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 3987.052605] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 3987.190413] atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 3987.190414] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.

This doesn't happen when i press audio mute button for example ( The audio mute button press is picked up by xev)

Last edited by batmanfeynman (2019-07-23 03:51:39)

batmanfeynman

Member

Registered: 2019-02-10

Posts: 9

Re: Unkown keybinding for XF86MonBrightnessUp

I had the lockup issue. I added

acpi_osi=! acpi_osi="Windows 2009" 

to my kernel parameters to fix it.

I just found out that if I do not have these kernel parameters tge brightness key doesn't do anything (it still produces the dmesg ouput). But when i have this kernel parameter, that key messes with my brightness