I’ve installed TLP on my Lenovo ThinkBook laptop and was wondering if there are additional steps I can take to extend the battery life when using the laptop unplugged.
Could you please share more tips and tricks for maximizing battery life on Linux laptops?
powertop is a cool tool that can analyze your machine and provide a list of suggested power optimizations
This is the way. You need to check whether CPU and package are mostly in the highest C-states they can be. If not, you’ve got a task or IO device causing a lot of wasted power.
not related to longer battery life per se, but suspend-then-hibernate is the number one improvement to my daily use. the laptop suspends normally and if not woken in an hour, it suspends to disk. upon wake it restores from the swap file/partition. zero battery drain when off, resume from hibernate is faster than cold boot. I can go days without a charger; the other day I’ve “woken” it after like 10 days and did a full system upgrade - the battery and everything else was how I left it. after I was done, just closed it and left it.
my laptop is my secondary workstation and it’s not rare that I don’t touch it for days. it sucks major balls when I have to urgently leave and find out it’s depleted.
with systemd-boot and a fast and seamless boot process, this is as close as it gets to stuff Macbooks had more than 10 years ago.
I’ve never had a laptop that hibernates correctly with Linux. Is it something I can achieve with more research or some laptops won’t hibernate anyway? I routinely have that shitty experience when I pick up my laptop to see it has no juice left although I didn’t use it and it was apparently asleep.
it is insanely cumbersome to achieve this, but it is doable and once set up, it runs like a dream. I’ve got it on a T480s (F40), T420s (Arch), MBP 2010 (Debian 12) and MBPr 2012 (F39), all with encrypted LVM + btrfs, some with a swap subvolume, some with a separate swap partition outside of LVM (waaay faster boot, no decrypt prompt - dreamboat!)
basically you have to allocate a swap file, subvolume, or partition that’s RAM * 1.5 (on account of zram) but don’t add it to fstab. then you have to dick around with systemd scripts that turn off zram and activate swap on suspend and do the reverse on resume. then, dracut or mkinitcpio have to be set up to use the resume funcionality (when coldbooting it looks for the resume swap file and if present restores this instead of booting). also, there’s adding kernel switches to systemd-boot or GRUB to utilise resume.
edit: oh yeah, also taming selinux to allow you to write to said swap.
now that would be just enabling hibernation, but I don’t like explicitly activating suspend or hibernate, I wan’t it to hibernate after I’ve left it in suspend for a while; I’ve set it to 60 mins. that way I don’t have to think about it, just use my laptop like it’s actually 2024.
also, since you’re now coldbooting several times per day, it’s essential that this process is as fast and jerkless as possible, hence systemd-boot with all pauses and timeouts set to zero.
the steps involved depend on your distro, I’ve made it work with Fedora, Arch and Debian. Here’s a good primer so take it from there and use the arch wiki and experiment.
I’m moderately capable but a bit of a noob and oddly enough have a t480 with Debian and been trying to get hibernate to work. Did you figure this out yourself or was there a guide you followed that you might be able to point me to?
If you’re running AMD, TLP won’t help as much as running a 6.6+ kernel with the proper amd-pstate kernel module running. 6.8 takes it even further.
Damn, I looked at this thread hoping to optimize my server idle power draw.
AMD 2700X, and Debian Bookworm kernel back ports just got to 6.6. Hopefully this doesn’t break my ZFS 😅
I too wanted to rock Debian with ZFS. Had to go Ubuntu due to better ZFS support.
I once just needed to take notes in a lecture so I didn’t start my X server and just wrote in vim in TTY.
For more power savings, you can undervolt your CPU if it supports it. On some CPUs, it can result in significant power savings.
Undervolting requires a lot of testing to make sure each core is stable under all conditions. There is no guarantee that a CPU will undervolt well though. Two identical CPUs can have significantly different results.