## Issue description - Keyboard RGB works fine in Windows (Aura etc). - On Linux: - No keyboard backlight at all in any state. - `asusctl -s` shows full TUF RGB support and 4-step brightness: - Supported Keyboard Brightness: \[Off, Low, Med, High\] - Supported Aura Modes: \[Static, Breathe, RainbowCycle, RainbowWave, Pulse\] - Supported Aura Power Zones: \[Keyboard\] - `asusctl -k High` runs without error but has no visual effect. - `asusctl aura static/breathe/rainbow-cycle/...` runs without error, no visual effect. ## Steps to reproduce No keyboard backlight in linux session ## What is the current bug behavior? No backlight ## What is the expected correct behavior? - Keyboard backlight should turn on and respond to asusctl (and ideally hotkeys / DE brightness controls). - From a user perspective, this looks identical to issue #578 (FA608WI) but on FA608WV; I’m happy to test patches or extra logging builds if needed. ## Relevant logs and/or screenshots # asusd log Relevant lines from `journalctl -u asusd -b`: \[INFO asusd\] Product family: ASUS TUF Gaming A16 \[INFO asusd\] Board name: FA608WV \[INFO rog_platform::platform\] Found platform support at "asus-nb-wmi" \[INFO asusd::aura_manager\] TUF laptop, try using sysfs backlight control \[INFO rog_platform::keyboard_led\] Found keyboard LED controls at "asus::kbd_backlight" \[INFO asusd::aura_types\] Found laptop aura type "tuf" \[INFO asusd::aura_types\] Found sysfs backlight control (Before I added FA608WV to aura_support.ron there was also: \[WARN rog_aura::aura_detection\] the aura_support.ron file has no entry for this model but that warning is gone after adding the entry.) # aura_support.ron entry Current entry I added for this board in `/usr/share/asusd/aura_support.ron`: ( device_name: "FA608WV", product_id: "", layout_name: "fa506i", basic_modes: \[Static, Breathe, RainbowCycle, RainbowWave, Pulse\], basic_zones: \[\], advanced_type: r#None, power_zones: \[Keyboard\], ), # Sysfs layout `/sys/class/leds/asus::kbd_backlight` exists and contains: - brightness - max_brightness - kbd_rgb_mode - kbd_rgb_mode_index - kbd_rgb_state - kbd_rgb_state_index - brightness_hw_changed, power, trigger, etc. `kbd_rgb_*` index files: `cat kbd_rgb_state_index` > cmd boot awake sleep keyboard `cat kbd_rgb_mode_index` > cmd mode red green blue speed Note: `kbd_rgb_state` and `kbd_rgb_mode` are write-only (Permission denied on read), which I understand is normal for some TUF ECs. # Direct EC/sysfs tests From a root shell: cd /sys/class/leds/asus::kbd_backlight 1) Enable all power states: echo "1 1 1 1 1" \> kbd_rgb_state echo "1 1 1 0 1" \> kbd_rgb_state (no errors) 2) Static colors: echo "1 0 255 255 255 0" \> kbd_rgb_mode # white echo "1 0 255 0 0 0" \> kbd_rgb_mode # red echo "1 0 0 255 0 0" \> kbd_rgb_mode # green echo "1 0 0 0 255 0" \> kbd_rgb_mode # blue (no errors) 3) Brightness: echo 3 \> brightness # max, 0-3 supported (no errors, but no visible backlight at any step) # asusctl usage Commands I tried (all run without error, but keyboard remains completely dark): ``` asusctl -k High asusctl aura static -c ffffff asusctl aura static -c 00ff00 asusctl aura breathe asusctl aura rainbow-cycle asusctl aura rainbow-wave asusctl aura pulse ``` I also tried `asusctl aura -n`/`-p` to cycle modes, no visible effect. Happy to provide: - `dmesg` snippets, - full `journalctl -u asusd -b`, - output of `/sys/devices/virtual/dmi/id/*`, - and anything else that helps reverse-engineer the EC behavior for FA608WV. ## System details # Laptop model ASUS TUF Gaming A16 (2024) Board name: FA608WV # OS / env - Distro: Arch Linux - Kernel: 6.17.8-arch1-1 - asusctl: asusctl-git (v6.1.20 as reported in CLI) - asusd: running as a systemd service