01 Sep 2018
I recently switched from MacOS to Linux for my personal/work machine. As much as I like my new laptop I really missed all the battery life that my previous Macbook Pro was capable of.
I decided to do something about it and improve battery life of my setup as much as I could. This post is part me saving it for future reference and part sharing it with you, the curious reader.
I have a System76’s Oryx Pro 4 (2018) with the following characteristics:
- CPU: Intel i7-8750H, 2.2 up to 4.1 GHz, 6 cores
- Display: 15.6” 1920x1080 144hz
- Discrete GPU: NVIDIA GeForce GTX 1060
- Memory: 32 GB dual-channel DDR4 @ 2400 MHz
- Storage: 500G Samsung NVME 970 EVO, 1TB Samsung SSD 860 EVO
- Communications: Gigabit Ethernet, Intel Wireless-AC WiFi, Bluetooth
- Camera: 1080p HD Webcam
- Battery: Embedded 4 Cells Polymer battery pack – 55Wh
And I run the following software (at the time of this writing):
System76 has their own Linux distribution Pop! OS. By default uses Gnome and comes preloaded with some good stuff and uses an older version of the kernel. It must be the LTS kernel since they have to support it and it would be crazy to support every version out there.
When I tested this machine with Pop OS! I got a discharge rate of about ~11-10W idle, just powertop running. I do not remember if I had the keyboard backlight on and what the screen backlight level was so it may not be a fair comparison but it’s a good baseline.
I use Archlinux and i3-gaps which are way lighter than Ubuntu (Pop! OS base) and Gnome. With my current setup I get ~8.5 W discharge rate while idling, just running powertop.
This is before I run anything related to power savings so it comes to show how much Linux has improved.
Power savings configuration
Kernel command line
I boot the kernel adding the following to the command line:
The interesting bit for our current discussion is the nowatchdog paramater which turns off lockup detectors in the kernel which saves a tiny fraction of power and performance.
Kernel module configuration
I have the following kernel module configuration file:
These are here for reference only and to show the concept of doing some research on what drivers your machine is using and what do they need to have increased power savings. You don’t want to copy these as-is because it may turn your machine unusable.
TLP – Linux Advanced Power Management
From their project page:
TLP brings you the benefits of advanced power management for Linux without the need to understand every technical detail. TLP comes with a default configuration already optimized for battery life, so you may just install and forget it. Nevertheless TLP is highly customizable to fulfil your specific requirements.
TLP is a daemon that turns on power saving flags in hardware, configures the CPU, configures kernel parameters, etc, that are good for power savings. As the project says, the defaults are pretty good but you can always tweak it a little bit more.
My own configuration:
There is some fine tweaking possible for newer CPUs with TLP to manage cpu power hints, pstates, turbo settings, etc. I don’t use them since I run System76’s system76-power(github) to handle the CPU profiles because it is easier.
fancontrol is a daemon, that as its name says, controls fans in your
computer. That is, if the computer maker decided to give you that power. In
Linux, such control is done through the PWM (Pulse Width Modulator) interface.
PWM allows you to control the power that goes into an electrical line (I am being intentionally simplistic here). If you have fan PWM lines available you can control how much power goes into them, and in turn, how fast they spin.
fancontrol is part of the
lm_sensors package in archlinux and ubuntu.
fancontrol is a tool to control a fan speed based on some temperature
thresholds. This is useful because usually the auto control in the fans is
overly aggressive, turning fans on very rapidly when the CPU activity increases
a tiny bit. And, the faster a fan spins, the more power it consumes.
You have to take several things into account here, the temperature limits of the hardware you want to control the fan of, the ambient temperature of where you live. Say, if the CPU wants to be at 30C by default but your ambient temperature is 40C those fans are going to spin forever. You want to be careful with this. You most likely don’t want to fry your electronics.
If you install the
lm_sensors package and run the sensors utility you can see
which hardware temperature monitors you have available and what are their
temperature limits. Plus, if you have fans around.
Mine looks like this:
Now, that is one I care about, the system76-isa-0000 has a fan for the CPU, and turns out it is very aggressive and since I live in a very warm place to begin with, I want to tone it down so I can save a bit of juice.
pwmconfig utility which will create an
/etc/fancontrol file which
looks like this:
(Don’t copy this. This is very hardware dependant, run pwmconfig)
fancontrol.service and voila.
Fans are now under control.
Linux thermal daemon (thermald) monitors and controls temperature in laptops, tablets PC with the latest Intel sandy bridge and latest Intel CPU releases. Once the system temperature reaches a certain threshold, the Linux daemon activates various cooling methods to try to cool the system.
Now, the difference between the fans and thermald is that thermald uses passive cooling methods built into these CPUs.
thermald is a last barrier. When the CPU is under heavy load and not even the
fan can keep it cool thermald uses several passive cooling features built into
newer cpus (Intel’s, not sure about AMD) to minimize power and temperature.
This is my current configuration:
Which pretty much means that if the CPU goes higher than 82C it should use all matters of passive cooling at its disposal to cool it down. I’ve tested this and it’s amazing how even using all the cores heavily it stays at 82C.
After you configure it you just enable the daemon and that’s it. It will do it’s thing when it must.
Note: This is experimental.
Undervolting is similar to overclocking, except instead of increasing speed, you are trying to keep your current speed by using less voltage.
This works because due to tiny differences in manufacturing processes CPU voltage and power specifications are not the same between units. They have ranges and tolerances. This is what lets you overclock and undervolt.
When a CPU maker builds a CPU they make sure to feed it voltage which can guarantee they meet the specified clock speed. But it is very likely any given CPU can work with less voltage and still work within the specified speeds and stability.
What this accomplishes for us is using less power to feed the CPU and that saves juice. Less voltage also mean less heat, which in turn means less fan noise and spinning, which also saves juice.
I use intel-undervolt to set the voltages, but there are other scripts and tools available.
You have to find the specific voltages and tolerances that your CPU can work with, you do this by decreasing the voltage just a tiny bit, do some heavy stress testing for a good chunk of time. If it works, you decrease it a bit more, and you continue doing it till you find a set of voltages that work for your machine.
This is how my (current)
/etc/intel-undervolt.conf looks like:
The reason the GPU is commented out is because apparently it is already
undervolted by quite a bit by default. I recommend you use
read to check your default values. You may find something you don’t want to
With all of this configuration, my idle power usage doesn’t really change very much. It starts showing when you actually put some load and start using the system. My overall battery life went from about ~4 hours to about ~5.5 hours. Which is pretty good. It still sucks compared with the MBP but this machine is a power house. I didn’t really expect to get 10 hours of battery with it.
Thermals improved quite a bit too, and that’s pretty important to me because I live in a very hot place.
That is it. If you have any suggestions how to improve this guide, or how to increase battery life please do share!