linrunner / tlp-doc Goto Github PK

When upgrading Fedora to a new version (in my case 35->36) it asks to check the TLP Repository GPG key. It is missing for Fedora 37 (just released) on https://linrunner.de/tlp/installation/fedora.html#fingerprints . Can you add it?

The reason for this issue is an ambiguity in the documentation about the compatibility between TLP & auto-cpufreq

During my researches about how to get the most out of the battery on my Linux laptop, I came across two great projects: TLP and auto-cpufreq. But, diving into the two projects, I realized that the possibility of running them in tandem was very ambiguous.
I'm not sure if this is the appropriate place to ask about this, but I haven't found any good answers anywhere else (even on the auto-cpufreq Discord server, where I met other users with the same goal).

In the TLP docs, it says:

auto-cpufreq: only impacts CPU settings that are not active in TLP’s default configuration. There will be no conflict as long as these remain deactivated.

But in the default config of TLP(UI), I see those CPU-related parameters enabled by default:

• CPU_ENERGY_PERF_POLICY_ON_AC
• CPU_ENERGY_PERF_POLICY_ON_BAT

I frankly don’t know what those settings do, but it seems to me that this has an influence on CPU behavior that could conflict with auto-cpufreq.

So I was wondering if it would be possible to clarify this point in the documentation, because I sincerely believe that it would be a huge gain for the whole Linux community to be able to use these two great tools in a complementary way.

TL;DR
It would be great to

• provide more information to the end user regarding the compatibility with auto-cpufreq

Alternatives I've considered
I've considered using TLP's CPU management features, but they require more advanced technical skills and manual configuration, and I'm afraid of damaging my hardware by fiddling with it.
On the other hand, I've considered uninstalling TLP, but I think it's a shame to part with the multitude of features TLP offers.

Additional context
Here's the initial post I made on the endeavourOS forum:
https://forum.endeavouros.com/t/tlp-auto-cpufreq-compatibllity/50431

This issue is a duplicate of TLP#724, but it seems that this issue has been hidden by GitHub (maybe because this is a new GitHub account).

This page has:

Charging starts upon connecting AC power, but only if the battery charge level is below the start threshold (START_CHARGE_TRESH_BATx); it will not charge when the level is above the start threshold

Charging stops when reaching the stop threshold (STOP_CHARGE_TRESH_BATx)

But later the page says:

START_CHARGE_THRESH_BAT0=75
STOP_CHARGE_THRESH_BAT0=100

And I think it is the spelling in this latter case - i.e. 'THRESH', with an 'H' - that is correct. Worryingly, though, with neither spelling ('TRESH' or 'THRESH') does tlp display an error when it (tlp) is run in a terminal.

Hi,

in installation/arch.rst, could it be that there is a bullet point missing for acpi_call (withouth -lts)?

Hi! Could you please update the repo to make it work under Fedora rawhide? i forced the repo to work and I can report tlp works in rawhide with no issues for me.

Hi there, Acer Nitro 5 has 80% battery limit officially on windows through Acer Care Center App, could you make it possible on Linux

I can't find anywhere that references what TLP stand for, if anything.