ROGauracore keyboard backlight fails

For years I have been running the rogauaracore, also in the AUR, without any issue, to get keyboard backlight control on my ROG G531gt. After last update the keyboard backlighting disappears as soon as I get to the lightdm login screen. Sending the rogauracore command like
sudo rogauracore single_static 0000ff
will flash the blue behind the keys, but it again disappears immediately.
I have tried on the Zen kernel, that I normally run, and the LTS. Same result.
I am running XFCE. Using the keyboard’s own hot keys(Fn+arrow up), XFCE will show the OSD of keyboard lighting up to full brightness, but that doesn’t change anything; there’s still no backlight.
I have also reinstalled from git, and re-compiled rogauaracore. And tried the AUR version.
Any ideas?

Maybe hardware issue. Did you try on windows?

1 Like

Yes, no issue. The keyboard light is active from boot, through until lightdm kicks in.

downgrade the package, did you ask on the AUR page?

I had been using the git package compiled, and that hasn’t changed in 2 years. I still recompiled, without error, and as stated it works albeit very briefly.
There has to be something new in the services area, or lightdm, that is clobbering the backlighting.
I couldn’t see anything relevant in the journal.

maybe you can use the journalctl -f command and watch if something gets printed when you send that rogauracore command

1 Like

Good idea, but unfortunately, nothing useful:

Sep 17 21:03:40 onyx sudo[3885]:     onyx : TTY=pts/1 ; PWD=/home/onyx ; USER=root ; COMMAND=/home/onyx/rogauracore/rogauracore multi_static 000055 0000cc 0000aa 000099
Sep 17 21:03:40 onyx sudo[3885]: pam_unix(sudo:session): session opened for user root(uid=0) by onyx(uid=1000)
Sep 17 21:03:41 onyx sudo[3885]: pam_unix(sudo:session): session closed for user root

Does that command have some verbose output with something like -v or --verbose?

1 Like
sudo rogauracore -v single_breathing 00ff00 ffffff 1
parse color 00ff00
interpreted color 0 255 0
parse color ffffff
interpreted color 255 255 255
parse speed 1
args:
color1 0 255 0
color2 255 255 255
color3 0 0 16
color4 0 0 0
speed 1
single_breathing
constructed 1 messages:
message 0: 5d b3 00 01 00 ff 00 e1 00 01 ff ff ff 00 00 00 00 
Initialising libusb
Initialised libusb.
Found 5 USB devices.
Checking device 1d6b:0003, address 1
Checking device 0b05:1866, address 3
Found ROG Aura Core keyboard.
Opened USB device.
Auto detach kernel mode set.
Claimed interface 0.

No errors according to the application.

Well then, write on the AUR page and/or open an issue on github. Post this output too.

1 Like

Thanks. Will do.

Did you try these from the github page?

If your keyboard does not respond to rogauracore, it may help to send an initialisation message to the keyboard to "wake it up":

sudo rogauracore initialize_keyboard
If your keyboard remains dark, its brightness might have defaulted to 0. Try:

sudo rogauracore brightness 3
1 Like

Must be from older app, those commands fail. But thanks, will keep digging.

Look through the journal see if you notice something around when the lightdm loads journalctl -b -0

1 Like

Got it!! This post gave me a clue:

There’s an app called asusctl in the system also. I removed it, and I’m back to running.
Thanks for the help.

Don’t forget to mention this on the AUR page, maybe they will add it as a dependency.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.