You are not logged in.
Pages: 1
After updating Arch Linux, the fn+f7 keyboard shortcut, which previously switched the screen backlight, does not work. Can I somehow get it back?
Offline
Try installing to linux-lts
Andrew
Offline
Which desktop environment you are using?
Offline
Is the key binding not triggering, or is the command itself not working? What command is that key triggering? Can you run it manually?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Try installing to linux-lts
Andrew
It not helped.
Offline
Which desktop environment you are using?
Xmonad
Offline
Is the key binding not triggering, or is the command itself not working? What command is that key triggering? Can you run it manually?
I think, command is not triggering, because I can create this keybinding in Xmonad. Initially, I don't set any keybinding, and this was working.
Offline
What xbindkeys say if you try using Fn+f7?
Last edited by Skunky (2019-02-12 15:56:37)
Offline
What xbindkeys say if you try using Fn+f7?
"Say"? It's "a program that allows to bind commands to certain keys or key combinations on the keyboard."
Offline
I just realized we may all be on the wrong track. There was no X11 level keybinding, this was a firmware action that has stopped working. You could add a key binding to Xmonad to run an xbacklight command (or to write directly to the relevant /sys/class/ file) and that would remedy the symptoms quite easily, but if you want to get to the bottom of the change in the default firmware handling of this we need to look in a different direction:
What is the hardware? When did this key stop working? Was there a kernel update that changed it? If so, does downgrading to the previous kernel make it work again?
For future reference, when you are responding to several posts at once, please consolidate your replies into a single post (rather than making many sequential posts).
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I just realized we may all be on the wrong track. There was no X11 level keybinding, this was a firmware action that has stopped working. You could add a key binding to Xmonad to run an xbacklight command (or to write directly to the relevant /sys/class/ file) and that would remedy the symptoms quite easily
I already did it.
What is the hardware?
Asus X540SA
When did this key stop working?
2019-02-08, seemingly
Was there a kernel update that changed it?
Yes. https://www.archlinux.org/packages/?sor … =&flagged=
If so, does downgrading to the previous kernel make it work again?
I installed LTS, and it not works (it worked previously)
Offline
Skunky wrote:What xbindkeys say if you try using Fn+f7?
"Say"? It's "a program that allows to bind commands to certain keys or key combinations on the keyboard."
You can do
xbindkeys -k
and check if the keyboard shortcut is working correctly.
For example Fn+F7 on my laptop equals to
XF86ScreenSaver
Last edited by Skunky (2019-02-13 01:55:00)
Offline
Using an lts kernel is not an ideal test. Can you get a kernel from your cache and/or the arch archive from before that date and test if using the older kernel is sufficient to restore the behavior?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Using an lts kernel is not an ideal test. Can you get a kernel from your cache and/or the arch archive from before that date and test if using the older kernel is sufficient to restore the behavior?
Switching to 4.19.8 linux and linux-headers fixes this problem. But I don't think it's a good solution
Offline
Nope, it's not a solution, but it's an excellent diagnostic as it confirms that it was a kernel change that affected how the firmware controls are handled. In otherwords, there's no reason to look into WM settings or xbindkeys information.
I can't dig into it now, but the next step would be to follow up on what changed between the two kernel versions. With luck the addition of the proper command line parameter to the kernel could get everything back in order.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I was having the same issue, adding 'acpi_backlight=vendor' as a kernel parameter fixed the issue, as suggested by Trilby
Offline
Pages: 1