Open Rank-N-Tensor opened 2 years ago
Additionally, I found this warning in the TLP documentation.
i am running ubuntu 20.04.4 with the 5.13 kernel. It was only after the kernel update that this issue arose.
Thanks for sharing, have you tried the solution mentioned, or maybe a higher / lower kernel version? We will also test it to compare.
system freezes and reboots.
Does this happen to you?
Hi @slimbook, thanks for the prompt response. I did try the 5.11 kernel earlier, to no avail. My system (thankfully) does not freeze or reboot. although, earlier, the screen would become pixelated and i would be forced to shut down the laptop and restart it.
I havent implemented the solution as of now as im working some other sensitive projects and i am worried about unexpected behaviour. please advise(if you can) on how to work with DKMS and secure boot ( I am a beginner in this space).
I @Rank-N-Tensor, It's okey. Kernel 5.14 oem seems to work better with tlp and intel processors, lowering consumption, but we still need to do some research. I'm afraid I can't help you much with DKMS or Secureboot.
understood, thank you for your time.
I seem to be having the same issue, as described here. It doesn't matter what option I have select on menu the only thing it seems to be affecting is the backlight, and nothing else on the system, occasionally I get the battery meter to saying 6 Hours of battery life left, but it then goes back to the normal 2 hour left as if Slimbook Battery was not running. I have tried running it on Xubuntu 20.04.4, PopOS V21.10 and beta version of Ubuntu 22.04, but nothing seem to work.
DESCRIPTION As the aforementioned title suggests, slimbook is not affecting battery saving. the time remaining is still the save as without slimbook ( about 1.5-2 hours with full charge)
Evidence Steps to reproduce the behavior:
Ctrl+Alt+T
slimbookbattery
Desktop
Expected behavior earlier, it would show ~10hrs with Energy Saving Mode
Screenshots
Additional context TLP information:
slimbook terminal output
Additionally, as is evident from the screenshot. This unexpected behavior began when the quick select menu switched from "Energy Saving" +"Balanced" + "High Performance" to "Low"+"Medium"+"High".