I've been doing some investigation and have discovered the following. If I perform these commands the back-light changes:
echo 0 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 1 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 2 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
Also there is a script called /etc/acpi/asus-keyboard-backlight.sh
I thought maybe this script wasn't being called and remapped the keys to the script and it still would not work. So I manually entered each script line and tested which worked fine accept I couldn't test this line:
if [ "$1" = down ]; then
I assume the $1 variable is only passed when called by the keyboard handler or is it possible this is the problem? How do I discover if this is being passed? How do I figured out if the script is even being called by the keyboard handler?
I have enough information now to make a workaround but would like to see this fixed in future versions.
I've been doing some investigation and have discovered the following. If I perform these commands the back-light changes:
echo 0 | sudo tee /sys/class/ leds/asus: :kbd_backlight/ brightness leds/asus: :kbd_backlight/ brightness leds/asus: :kbd_backlight/ brightness leds/asus: :kbd_backlight/ brightness
echo 1 | sudo tee /sys/class/
echo 2 | sudo tee /sys/class/
echo 3 | sudo tee /sys/class/
Also there is a script called /etc/acpi/ asus-keyboard- backlight. sh
I thought maybe this script wasn't being called and remapped the keys to the script and it still would not work. So I manually entered each script line and tested which worked fine accept I couldn't test this line:
if [ "$1" = down ]; then
I assume the $1 variable is only passed when called by the keyboard handler or is it possible this is the problem? How do I discover if this is being passed? How do I figured out if the script is even being called by the keyboard handler?
I have enough information now to make a workaround but would like to see this fixed in future versions.