This document answers frequently asked questions and provides solutions / workarounds for common problems.
TLP packages for new distribution versions appear in due time for the release. If you want to use TLP with alpha or beta releases, download the packages for the predecessor and install them manually with the package manager.
Yes. Using another tool simultaneously means that TLP's settings get overwritten by the other tools settings (and vice versa), so actual power saving gets unpredictable.
thermald: thermald's purpose is to limit power dissipation before the laptop's temperature gets critical. TLP enables power saving features globally to optimize battery power especially in idle and low workload situations. TLP does not conflict with thermald.
Powertop: please refer to the corresponding section.
Depends on the setting. TLP
"Conflict possible" means that the setting configured in TLP may get overwritten by the desktop's setting (and vice versa). System stability issues are not to be expected from those conflicts.
TLP runs on every laptop brand. A few features are available on IBM/Lenovo ThinkPads only.
Yes, of course.
The Linux kernel has accumulated many power saving features over the years, but only a minority is enabled by default. It seems to be really hard for the kernel developers to fully debug power saving on all possible hardware, so power saving stays disabled for the majority of drivers and it's up to the user to enable it.
Conclusion: a userspace tool like TLP is still needed to enable power saving globally.
No. It is not effective to run a power management tool inside a virtual machine (guest). Install TLP in the host operating system instead.
No. Package managers take care not to replace a user edited configuration file without explicit confirmation and create a backup copy too.
Not necessarily. TLP is always backwards compatible to existing configuration files. New features get reasonable default settings when not declared in the configuration file.
However package installation does not merge a new feature's settings. So if you want to change the default, you need to:
Possibly. There is no support however.
You may try to install the source tarball from GitHub:
Hint: check Makefile options to customize 'make install' to your distribution's requirements.
When encountering problems with the sound output on battery, for example clicking noises, try to disable audio power save completely:
See TLP Configuration.
The APM setting for battery mode
corresponds to the Ubuntu default and should cause no problems. Unfortunately drive manufacturers interpret the APM levels quite spaciously to save power.
Solution: try values > 128. See TLP Configuration.
Stopping the system disk for extended periods of time is unlikely to work, because applications and system daemons wake up the disk frequently. There is no real solution for this other than changing many applications and daemons.
To spin down after 1 minute (= 12 · 5 seconds) idle time use:
See TLP Configuration.
TLP applies configured APM levels and spin down timeouts upon every change of power source and upon suspend/resume. Writing the settings inevitably spins up the disk. To prevent this behaviour either disable the settings completely by commenting all of them (with a leading '#') or use the special value "keep" for the specific disk.
See TLP Configuration.
The Crucial M4 reduces performance according to the APM level. You may disable APM with
Affected hardware: ThinkPad T60 and T420 users reported this.
Solution:
Possible causes are:
SL/Edge models for instance.
At the time of writing this functionality is tested with ThinkPads only.
This is caused by the radeon driver's power management. To disable the setting either use
or
depending on your card/kernel. Refer to TLP Configuration for details.
Affected hardware: a Lenovo Ideapad 300 (Intel / Radeon hybrid graphics) user reported this issue.
Solution: disable DPM by commenting the configuration line:
Laptops with Optimus hybrid graphics contain two graphics units: one from Intel on the processor die ("integrated", iGPU) and one from Nvidia ("discrete", dGPU). Linux uses the Intel unit by default, but at the same time the unused Nvidia unit is enabled and uses a lot of battery power because no driver is loaded.
TLP can't do anything about this – Possible solutions are:
Exclude the dGPU from runtime power management.
TLP 1.0 and higher: blacklist the driver(s)
TLP 0.9 and before: blacklist the device
Hint: to check whether "01:00.0" matches your Nvidia dGPU, use
Refer to TLP Configuration too.
Exclude the dGPU from runtime power management, see the previous section.
Most likely it doesn't. All USB input devices (usbhid) are excluded from autosuspend by default.
Refer to bluetooth.
No. TLP's default configuration is based on the same policy as powertop's recommendations. Refer to the following sections for details and exceptions.
Powertop in interactive mode has no impact on TLP's function.
Explanation: powertop isn't a power management tool but merely an analysis tool. You can use powertop to view estimates about your power usage before or after installation of TLP, but TLP determines the best defaults for your system regardless of whether or not powertop is installed. On the other hand, attempting to apply powertop's --auto-tune settings on each boot will conflict with TLP.
Important: TLP applies maximum power savings on battery power only, so unplug AC power before checking with powertop.
Not all suggestions from Powertop make sense or are safe to implement:
Powertop insists on a value of 1500 centisecs, whereas TLP's defaults are 1500 on ac and 6000 on battery power. If you incline towards powertop's opinion then change the setting to:
Some laptops refuse ALPM for particular SATA links. It is impossible to change from max_performance to min_power. One cause may be an open link to the docking stations drive bay (when not docked).
Workaround for X-Series ThinkPads: enter BIOS setup. Go to "Security → IO Port Access" and change Ultrabay access to "disabled". Saves approx. 0.4 W.
For some wifi cards – for instance the Intel 3945abg – the Linux kernel does not support wifi power save.
TLP intentionally exempts input (usbhid) and WWAN (3G/UMTS, 4G/LTE) devices from autosuspend.
Input devices may be whitelisted (USB_WHITELIST, refer to USB); to enable autosuspend for WWAN devices use:
It is impossible to measure the power consumption of individual laptop components. Therefore the readings in "Device stats" column "Power est." are rough estimations that are obviously wrong and should be ignored.
tlp-stat -p may show values that do not reflect configuration, frequent example is the scaling governor.
There are several possible causes:
Some distributions use dedicated scripts to select a scaling governor during system start.
Solution: disable the scripts as follows:
Revert change with:
Revert change with:
Your mileage may vary. Check your distribution's documentation.
Solution: tlp-stat -p shows the correct values for your CPU. Example:
Since kernel 3.9 the new scaling driver intel_pstate is available and enabled by default on Intel Sandy Bridge (or newer) hardware. intel_pstate supports the governors powersave (recommended default) and performance only, ondemand is gone.
Depending on the distribution your mileage may vary:
Cause: kernel driver does not implement power saving properly.
Solution: disable power saving on battery
Cause: conflict with NetworkManager.
Solution: remove the file /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf.
Cause: most internal laptop bluetooth devices and all external bluetooth dongles are USB devices. Some do not implement autosuspend mode properly, giving trouble to connected devices or preventing discovery or pairing.
Solutions
TLP 1.0 and newer: configure USB_BLACKLIST_BTUSB=1.
TLP 0.9 and before: identify the USB bluetooth device with
Add it to USB_BLACKLIST.
Apply the new setting with
Cause: the XFCE Desktop uses the Blueman bluetooth applet, which enables bluetooth when started.
Solution: you have to remove the bluetooth applet from autostart or uninstall the package blueman. Alternatively you may patch the blueman-applet (see LP #908375).
Cause: conflict with other settings, i.e. DEVICES_TO_DISABLE/ENABLE_ON_... .
Solution: don't use RESTORE_DEVICE_STATE_ON_STARTUP=1 and DEVICES_TO_DISABLE/ENABLE_ON_... simultaneously.
Cause: systemd 209 (or higher) implements its own radio state restore scheme (systemd-rfkill.service, see TLP Configuration).
Solution: use either RESTORE_DEVICE_STATE_ON_STARTUP=1 or systemd's approach but not both.
Cause: some cards do not work reliable with USB autosuspend mode enabled, so by default TLP doesn't apply USB autosuspend for most integrated WWAN cards.
Solution: force USB autosupend for WWAN with
Refer to TLP Configuration.
Yes. The service units are critical for TLP's operation:
Solution: add the mei_me module to RUNTIME_PM_DRIVER_BLACKLIST.
Affected hardware: HP laptops (based on user feedback)
Solution: deactivate Wake-on-LAN in the BIOS.
Symptom: laptop shuts down spontaneously when changing to battery power.
Affected hardware: an Acer Aspire V5-591G user with kernel 4.4 reported this issue.
Solution: disable audio power saving.
Affected hardware: a Dell XPS user with Kernel 4.4 reported this issue.
Solution: enable Wake-on-LAN
Symptom: journal shows the message
Solution: none. This is not an error.
Explanation: during system startup multiple instances of tlp may get started concurrently by tlp.service and power source events (udevd). Because only one instance is needed to apply the settings, all other instances terminate with exit code 4.
ThinkPad battery features means battery charge thresholds and the possibility to discharge or recalibrate the battery when AC is connected.
Disclaimer:
Note: newer ThinkPad models may not need charge thresholds due to dualmode battery firmware – refer to Lenovo Forums and Lenovo Support.
Factory settings for ThinkPad battery thresholds are as follows: when plugged in the battery starts charging at 96%, and stops at 100%. These settings are optimized for maximum runtime, but having a battery hold a lot of power will decrease its capacity over the years. To alleviate this problem, the start/stop charge thresholds can be adjusted – at the cost of a more or less reduced battery runtime.
It all depends on how you use your laptop, or more precisely, on the minimal runtime you're ready to accept when you're on the road. In the end, it all comes down to a runtime vs. lifespan trade-off.
If the laptop is plugged most of the time and rarely unplugged, maximizing battery lifetime at the cost of a greatly reduced runtime may be acceptable, with values like starting charge at 40% and stopping at 50%.
On the contrary, if you use it unplugged most of the time, starting charge at 85% and stopping at 90% would allow for a much longer runtime and still give a lifespan benefit over the factory settings.
(Source: Lenovo Forums)
Default TLP settings (only if you uncomment the relevant lines) are slightly more protective regarding lifespan, with 75%/80% start/stop charge thresholds.
Please consider that the start threshold is the critical constraint for runtime, because it defines the lowest charge level that can occur while plugged.
Also, don't forget that TLP provides a command (tlp fullcharge) to fully charge the battery, when you need to temporarily maximize runtime (for example in case of a trip).
Check the bottom of tlp-stat's output, section "Suggestions", for the following lines
and install the required module package as explained in Installation for your distribution.
Most ThinkPad models need only one of the above kernel modules. You may check the output of tlp-stat -b for lines like
and remove the unnecessary module package (tpacpi-bat means acpi-call). However, it doesn't hurt to keep both.
Possible causes are:
Battery charge thresholds and recalibration work with ThinkPads only (see above).
Symptom: tlp-stat -b shows
or
Solution: see Which kernel module?
It may be necessary to rebuild the kernel modules (as root):
Symptom (Ubuntu): package install shows
Solution: install package linux-generic-headers.
Symptom (Ubuntu 16.04.2 HWE kernel 4.8): package install shows
Solution: either enable the TLP PPA (see Installation) and update your packages (recommended) or download version 0.42-1 from Yakkety and install it manually.
Symptom: tlp-stat -b shows
Solution: try to load manually with
and check tp-smapi Troubleshooting for a solution matching the error message or use adequate forums to resolve your issue with tp-smapi.
Hints:
Symptom: tlp-stat -b shows
Solution: try to load manually with
and use adequate forums to resolve your issue with acpi-call.
Note: you must disable Secure Boot otherwise acpi-call will refuse to load.
tp-smapi doesn't support start threshold and recalibration on Sandy Bridge generation ThinkPads. Symptoms are:
tlp-stat -b shows
tlp setcharge or fullcharge shows the message
tlp discharge or recalibrate show the message
Solution: TLP automatically uses tpacpi-bat when the kernel module acpi-call is available, see Which kernel module?
Solution: TLP automatically uses tpacpi-bat when the kernel module acpi-call is available, see Which kernel module?
These models are neither supported by tp-smapi nor by tpacpi-bat. Please refrain from opening issues for this.
By removing (and re-inserting) the battery the charge thresholds are reset to factory settings (96 / 100%) for some models. To restore TLP's settings the following two steps are needed:
or use
See Change Battery Charge Thresholds.
Possible causes are:
After changes to the configuration it is necessary to reboot. Alternatively use
or
to activate the thresholds.
On these models the threshold values shown by tlp-stat -b do not correspond to the written values. For example the setting START_CHARGE_THRESH_BATx=75 / STOP_CHARGE_THRESH_BATx=80 shows 75 / 74. The described behavior is caused by the firmware (UEFI/BIOS), not by TLP. Nonetheless the charge thresholds work as configured.
Affected models: X240, Yoga 12 (based on user feedback)
Workaround: activating a new start threshold may require to discharge the battery below the old start threshold after writing the new threshold, e.g. via tlp setcharge or reboot (see Issue #173).
Symptom: some users report severely reduced battery capacity or sudden drops of charge level from around 30 % to zero when employing charge thresholds.
Probable cause: conflict with dualmode battery firmware.
Solution: remove battery thresholds completely or use only the start threshold; then recalibrate battery once.
Note: this is a software only issue, no harm is done to the battery.
All existing panel applets use the standard kernel interface which doesn't give the charge state correctly as soon as charge thresholds intervene. In this situation tlp-stat -b shows "Unknown (threshold effective)" for /sys/class/power_supply/BATx/status. There is no solution at the moment.
In contrast, for ThinkPad models supporting tp-smapi tlp-stat -b shows the correct state below /sys/devices/platform/smapi/BATx/.
Yes. The charging process is not controlled by software, but by hardware. TLP just writes the thresholds to the hardware registers (via tp-smapi or tpacpi-bat). Once stored in the hardware the charge thresholds stay effective permanently. See below for removal.
The start charge threshold ensures that the battery is not recharged immediately after every short discharge process. The charging process starts only when the previous discharge was below the value of START_CHARGE_THRESH_BATx.
No. Otherwise they would be callled dis-charge thresholds.
No. Discharging the battery can be prevented only by connecting the power supply or switching off your ThinkPad.
Remove the charge thresholds from the configuration by inserting a leading '#'
and use
to immediately activate the factory settings 96 / 100%.
Most probable cause: battery is defect – and was it even before the recalibration attempt.
Cycle count is a ThinkPad battery function and available for models supporting tp-smapi only; refer to Which kernel module?
Symptom: some USB devices – scanners for example – do not work reliable when TLP activates USB autosuspend mode.
Solution: lookup the corresponding USB device ID with lsusb, add it to USB_BLACKLIST and reconnect the device.
Hint: TLP automatically excludes all input devices (HID) like keyboards and mice from USB autosuspend. You do not need to enter those in USB_BLACKLIST.
Solution: lookup the smartphone's USB device ID with lsusb, add it to USB_BLACKLIST and reconnect the smartphone.
Currently the command checks the kernel log for errors possibly caused by the settings for SATA ALPM.
TLP's default setting on battery
is optimimized for maximum power saving. Try to use less aggressive values:
or
or disable the setting completely – see SATA ALPM.
Don't forget to reboot before checking again.
The same applies to SATA_LINKPWR_ON_AC if you changed the default setting.
Note: the difference in power consumption between min_power and max_performance may amount to more than 1 W depending on your hardware.
Candidates:
© 2016, linrunner. Licensed under the CC BY-NC-SA.