| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Arguably, a function called "reset" should put the backlight level and color in a known state. But what do bonw14, darp5, and oryp5 actually need to do for I2C when waking the CPU? Does kbled_reset need to be called at all? |
Sorry, something went wrong.
|
In my tinkering this appeares to break the system76-acpi-dkms module, making the LEDs unusable with the hardware controls inside Linux. If you remove the module they begin to work again. |
Sorry, something went wrong.
|
I may have spoken too soon... if I was wrong, I'll post about it again here...but seems my distro is not using the master branch. |
Sorry, something went wrong.
|
So it does not appear to be this commit, however the current master does seem to break things with the keyboard backlight controls when the acpi module is in use. |
Sorry, something went wrong.
Do not reset the keyboard backlight on CPU wake. This fixes keyboard backlight turning off and becoming white on wake from sleep. Signed-off-by: Tim Crawford <tcrawford@system76.com>
| Back | FazBrowse Home | New Git URL |
Do not reset the keyboard backlight on CPU wake. This fixes keyboard backlight turning off and becoming white on wake from sleep.
TODO: Fix for all kbled mechanisms.