According to Phoronix and its creator, Michael Larabel, the great cause of the problem of energy consumption in kernel 2.6.38 is the change that was made in the call ASPM (Active-State Power Management) for PCI Express slots. |
The Active-State Power Management feature allows you to reduce power consumption by putting PCI Express links that are not in use in a power-saving state, making them less active over time. This is a common feature in laptops and other mobile devices used to extend the life of batteries.
Apparently, the cause of the problem with the latest Linux kernels is the misconfigured BIOSes, since many laptop manufacturers support ASPM but do not configure it correctly in the so-called Fixed ACPI Description Table, which is the one that "auto-configures" the BIOS during boot .
What is the solution? Simple.
1.- I opened a terminal and wrote:
gksu gedit / etc / default / grub
2.- Locate a line similar to the following:
GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash"
3.- Replace it with one like this:
GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash pcie_aspm = force"
4.- Save the changes and enter the following command in the terminal:
sudo update-grub
This enables ASPM no matter what the BIOS says, and tests show that this solution achieves remarkable power savings that significantly increase battery life.
Source: Phoronix & Very Linux
I imagine that this energy consumption is more critical in latop.
Great, but does it work for kernel 2.6.39?
I join the consultation of Martín. I have Debian Sid with kernel 2.6.39
is it still needed in kernel 2.6.39?
I did not notice any substantial difference.
I have an Inspiron 5110 core i7 and hybrid graphics.
I ask myself the same question, if it is a conflict problem between the misconfiguration of the BIOS and the ASPM of the kernel, what solution has been taken for the following versions?
Look, from what I understand it works on all kernels higher than 2.6.38, which are precisely the ones that have the problem. It would be a matter of testing and comparing. 🙂 Lastly, if it doesn't work, go back the steps and that's it.
Cheers!! Paul.
Battery consumption is an issue that goes quite unnoticed ... especially in netbooks (although not so in notebooks).
The only way to really see if there were changes is to use the Phoronix suite to run the necessary tests.
A hug! Paul.
None. The error is still there ... 🙁
So is…
Can't this "forced" be loaded automagically?
Of course, for that you have to follow the steps indicated in the post.
I have given "Like" instead of "Reply". 🙂
But that's not automagic, that's doing it yourself, what I mean is whether the distributions will add the parameter to avoid the problem in successive releases.
Excellent.
No idea ... I hope so. 🙂