Arch Linux

kovac

Member

Registered: 2020-03-14

Posts: 41

[Solved] brightness ctl using brightness ctl buttons is not working

Hi,

I'm on a ThinkPad T490 and trying to control monitor brightness using brightnessctl (I would actually like to do this using xbacklight but when I try the command  `xbacklit -set 50` I get the error "No outputs have backlit property", hence I installed brightnessctl). I can adjust brightness from console using commands like `brightnessctl s +100`. However, when I try to use the F5 and F6 keys to adjust brightness, they are not working.

I have already created a .xbindkeysrc file in my home directory with

```
"brightnessctl s +100"
  XF86MonBrightnessUp
"brightnessctl s 100-"
  XF86MonBrightnessDown
```

When I check the key codes in .Xmodmap, I see the following:

```
keycode 232 = XF86MonBrightnessDown NoSymbol XF86MonBrightnessDown
keycode 233 = XF86MonBrightnessUp NoSymbol XF86MonBrightnessUp
```

When I check the scan codes with `showkey --scancodes` I see the message

```
kb model was ?UNKNOWN?
[if you are trying this under X, it might now work
since the X server is also reading /dev/console]
```

Then when I press the brightness down btn (without FnLock), I see the codes)

0xe0  0x4c  0xe0  0xcc

And with brightness up btn:

0xe0  0x54  0xe0  0xd4

Last edited by kovac (2021-04-04 11:16:58)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,527

Re: [Solved] brightness ctl using brightness ctl buttons is not working

[if you are trying this under X, it might now work
since the X server is also reading /dev/console]

Do the keys produce output on

xev -event keyboard

Also, sanity check: you are running the xbindkeys daemon and restarted it after the adjustment and did not just create some random file that won't do anything by itself?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

kovac

Member

Registered: 2020-03-14

Posts: 41

Re: [Solved] brightness ctl using brightness ctl buttons is not working

Thanks for your suggestion. It turned out that I hadn't installed the drivers. It's sorted now.