On 18/07/2023 05:25, David C. Rankin wrote:
All, Devs,
Was surprised yesterday to find that TLP was happily running on my laptop (with tlp frequency-info) while the service was not enabled. I stumbled upon it after pulling power to my laptop and happening to see the log messages telling me I need to enable it to have it available on boot and my needing to mask systemd-rfkill.service and systemd-rfkill.socket.
I'm not complaining, it's a good command line tool for power management, but didn't know how Leap was starting it since the service wasn't enabled.
Anybody have the Cliff's Notes version of how this works?
(I happily enable it and masked rfkill)
Can't really help with this, and not sure which Leap you're on, but just to say I had no idea what TLP was until I just did the Leap 15.4 -> 15.5 upgrade on my main laptop, and found there was a conflict between it and power-profiles-daemon. Unsure which one was the one to keep, and a search throwing up this page: https://www.reddit.com/r/openSUSE/comments/vqq5ex/the_latest_tlp_conflicts_w... I went with the latter. And curiously that seems to have resolved a long-standing problem with the battery/power management. Through the last couple of Leap releases my laptop battery would almost always throw a wobbly shortly after unplugging the power cable, and cause a suspend/shutdown with messages displaying suggesting I had some 'weird' power setup, even though all my settings in Plasma looked sensible to me. The battery reporting was all over the place and it didn't respect the limited charge settings I'd made in the BIOS. Now it's behaving normally, not charging until it gets below a certain level. I just don't know if TLP was something that was installed by default in the past, or that I'd read about somewhere previously and been convinced it should be installed on laptops. My system's clearly better off without it, but the above linked post suggests for some users it will be the opposite. Maybe in your case it's disabled because of this same potential conflict? gumb