Announcement

Collapse
No announcement yet.

Linux 3.2 Is Still Looking To Be Power Hungry

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 3.2 Is Still Looking To Be Power Hungry

    Phoronix: Linux 3.2 Is Still Looking To Be Power Hungry

    The PCI subsystem pull for the Linux 3.2 kernel was published on Friday evening. If you were hoping it would rework PCI-E ASPM (Active-State Power Management) to be more like the Windows implementation or for more PCI drivers to be setting the bits directly to support it (effectively white-listing drivers/hardware), it didn't happen yet...

    http://www.phoronix.com/vr.php?view=MTAwNzY

  • #2
    how to force it

    To set the boot option to save the power....

    Open up and edit "/etc/default/grub"

    Edit the following line to include "pcie_aspm=force" (stuff in quotes varies)
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=force"

    Then run "sudo update-grub" from the command line for the changes to take effect.

    Comment


    • #3
      Isn't this aspm bug the hardware lying to the os? Where the hardware says it can't use aspm, but would work if it was told to use it? I fail to see what else the kernel could do that would result in better behavior other than a list of hardware that says it doesn't workk but does anyways.

      Comment


      • #4
        the problem

        Ok. Here is the problem with the current behavior.
        1. All the motherboards for new laptops have power saving.
        2. Only 1 manufacture sometimes has aspm report correctly.

        So with the kernel switching from a default of on - if it isn't being reported - to off means that the power saving stops working for almost all laptops and netbooks in existence.

        Whats worse is that it is the major way to save power on a laptop. With it off, I loose half of my battery life (eee pc).

        Because of the change of the default behavior, linux is a very negative experience for those who try it out on a laptop. And if the person who is trying it out, doesn't frequent phoronix (not likely), won't know about the command line and config files that he/she has to manually edit to get their battery life back where it should be.

        Comment


        • #5
          so its not a kernel bug but a distri bug

          Why does the Distries nut just set this kernel-flag by default if there are only 5-10 notebooks out there who dont have this feature?

          Comment


          • #6
            Originally posted by blackiwid View Post
            Why does the Distries nut just set this kernel-flag by default if there are only 5-10 notebooks out there who dont have this feature?
            That's a possibility, too. Bottom line is that the community somehow has to find a way to deal with such nasty issues.

            This shows again how little hardware manufacturers care about Linux (hell, even on my modern Thinkpad the BIOS doesn't advertise ASPM properly). And this is important to note in the context of the Secure Boot discussions...

            Comment


            • #7
              Originally posted by not.sure View Post
              This shows again how little hardware manufacturers care about Linux (hell, even on my modern Thinkpad the BIOS doesn't advertise ASPM properly).
              hmm I have a new Thinkpad, too and also I have a old Samsung NC10 how can I look if its on or not or should I just look with some tool whats in ubuntu there powertop? and insert that kernel option and look again?

              whats the name of that tool again?

              Comment


              • #8
                Originally posted by blackiwid View Post
                hmm I have a new Thinkpad, too and also I have a old Samsung NC10 how can I look if its on or not or should I just look with some tool whats in ubuntu there powertop? and insert that kernel option and look again?

                whats the name of that tool again?
                Phoronix Test Suite can do the most accurate and reproducible job. Just sudo apt-get install phoronix-test-suite and then something like say MONITOR=sys.power phoronix-test-suite benchmark battery-power-usage or some similar test profile before and after, to get a real-world look and under the same load each time. The aforementioned command will show differences when idling, DPMS off, and then during video playback with MPlayer as some light workloads.
                Michael Larabel
                http://www.michaellarabel.com/

                Comment


                • #9
                  Originally posted by Michael View Post
                  Phoronix Test Suite can do the most accurate and reproducible job.

                  thx Michael will try it later or tomorow.

                  hmm someone (maybe me ^^) should write to ubuntuusers.de or ubuntu.com wiki a entry how to activate this and how to test this

                  Comment


                  • #10
                    Originally posted by ua=42 View Post
                    Ok. Here is the problem with the current behavior.
                    1. All the motherboards for new laptops have power saving.
                    2. Only 1 manufacture sometimes has aspm report correctly.

                    So with the kernel switching from a default of on - if it isn't being reported - to off means that the power saving stops working for almost all laptops and netbooks in existence.

                    Whats worse is that it is the major way to save power on a laptop. With it off, I loose half of my battery life (eee pc).

                    Because of the change of the default behavior, linux is a very negative experience for those who try it out on a laptop. And if the person who is trying it out, doesn't frequent phoronix (not likely), won't know about the command line and config files that he/she has to manually edit to get their battery life back where it should be.
                    Right but doesn't setting this to "on" when the hardware really doesn't support cause breakage? If it does, you have to remember that the linux kernel supports something like 15 years worth of hardware and the goal is for the hardware to work out of the box. You are barking up the wrong tree. Call your laptop's support line and request an update that correctly reports this.

                    Also you should take a look back to when ACPI replaced APM there were a lot of boards that needed/need all sorts of workaround because the DSDT tables are bad/incorrect. The vendors didn't seem to care much because their windows drivers knew better. The kernels stance then was "go talk to the vendor to get an update, or see this guide for fixing your dsdt table. We will not be adding workarounds to fix this".

                    Comment

                    Working...
                    X