search

JafarAkhondali / acer-predator-turbo-and-rgb-keyboard-linux-module

Linux kernel module to support Turbo mode and RGB Keyboard for Acer Predator notebook series
GNU General Public License v3.0
342 stars 59 forks source link

Acer Nitro 5 AN515-45 issues #63

Closed AngryMandragora closed 1 year ago

AngryMandragora commented 1 year ago

Hello, I installed the kernel module, signed it, enrolled it etc. At first everything worked, except the static mode, which caused the lights to go off. Then when I played around a little and pressed the backlight button on the keyboard (Fn+F9 and F10), the screen brightness went down to 0% and the keyboard stopped working. After a reboot it works again, but now the keyboard is just dark and running the commands doesn't do anything. I booted to a live USB and then shut the computer down, after starting it again the keyboard lighting is working again, but now I can't change it. The kernel module is installed and the program runs without any error messages, but nothing happens.

AngryMandragora commented 1 year ago

After playing around even more with it, I followed the advice on this link: https://github.com/JafarAkhondali/acer-predator-turbo-and-rgb-keyboard-linux-module/issues/4 (uninstall, remove, reinstall). After this I have the same experience: all the fancy wave/breathe/etc effects work, EXCEPT the static one. (I did not dare to press the backlight button again, it's getting late and I'm happy it's working at least a bit. All I want is change the keyboard color from red to blue, any ideas? (And I would like to keep using secure boot as well.)

AngryMandragora commented 1 year ago

Found an undocumented solution: setting the speed to 0 for breath mode actually makes it static and it works: ./facer_rgb.py -m 1 -cR 0 -cB 255 -cG 230 -s0

AngryMandragora commented 1 year ago

Looks like the Fn+F10 issue persists even after removing the kernel module and uninstalling the service, so it doesn't seem to be related to this project. I will close this issue, though the static mode issue is still there, but that can be solved with a workaround.