-
-
Save ps1dr3x/b15c62eafb388ddf8bb7d3896d1a1cee to your computer and use it in GitHub Desktop.
| # "input0::scrolllock" might be different (?) | |
| # On | |
| sudo sh -c 'echo 1 > /sys/class/leds/input0::scrolllock/brightness' | |
| # Off | |
| # sudo sh -c 'echo 0 > /sys/class/leds/input0::scrolllock/brightness' |
I also have the same problem.. It gets overwrite to 0 again after I changed it to 1, so the keyboard just blinks.
Hmm.. Maybe you have a daemon or something else running and rewriting the value @aevim @Tryware, maybe you could try to monitor the i/o operations on that path. I guess the behavior of this operation is also dependent on the keyboard's hardware, firmware and drivers. I changed keyboard and I don't need this workaround anymore, but in my case for example I had to put that in a 5 seconds cronjob because for some reasons the value was rewritten to 0 every time I was pressing the CapsLock key (but only in that case as far as I remember).
how to learn the input device?
I've made a Systemd task to detect and force the LEDs to turn on periodically.
There's the repository
@Magnitudexx The brightness file just rewrites the value inside, it doesn't matters if you try changing it with echo or directly with a text editor. I don't know what's preventing it to change tho.