Announcement

Collapse
No announcement yet.

Power management not running after upgrade

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Power management not running after upgrade

    When running the energy saving configuration in system settings I got a message that said the Power Management configuration module could not be loaded.
    Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

    http://www.kubuntu.org/getkubuntu

    #2
    Originally posted by steve7233 View Post
    When running the energy saving configuration in system settings I got a message that said the Power Management configuration module could not be loaded.
    Are you referring to the KCM module or something like laptop-tools?

    Anyways, first step is to run
    Code:
    sudo apt-get update && sudo apt-get dist-upgrade
    . Will probably require logging out and in. If that doesn't help then we can start looking more specifically at the problem.

    Comment


      #3
      Originally posted by steve7233 View Post
      When running the energy saving configuration in system settings I got a message that said the Power Management configuration module could not be loaded.
      +1 for Kubuntu 13.10 64b

      [System Settings], [Power Management]:




      so, then [Startup and Shutdown], [Service Manager]:



      Any ideas?

      Comment


        #4
        Originally posted by teracow View Post
        +1 for Kubuntu 13.10 64b

        [System Settings], [Power Management]:




        so, then [Startup and Shutdown], [Service Manager]:



        Any ideas?
        Try the commands I recommended. Is this an upgraded install or fresh?

        Comment


          #5
          I fixed this by running recovery mode. Some things didn’t finish configuring at the last part of the upgrade. The Power management works now. How about my Kernal panic thread?
          Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

          http://www.kubuntu.org/getkubuntu

          Comment


            #6
            Originally posted by dmeyer View Post
            Try the commands I recommended. Is this an upgraded install or fresh?
            Those commands are run as part of my post-installation configuration. So, no change there.

            This is a fresh install.

            Comment


              #7
              Also, found this in dmesg output:
              Code:
              [    0.266381] ACPI: bus type PCI registered
              [    0.266383] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
              [    0.266423] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xec000000-0xefffffff] (base 0xec000000)
              [    0.266425] PCI: MMCONFIG at [mem 0xec000000-0xefffffff] reserved in E820
              [    0.268990] PCI: Using configuration type 1 for base access
              [    0.269690] bio: create slab <bio-0> at 0
              [    0.269805] ACPI: Added _OSI(Module Device)
              [    0.269806] ACPI: Added _OSI(Processor Device)
              [    0.269807] ACPI: Added _OSI(3.0 _SCP Extensions)
              [    0.269808] ACPI: Added _OSI(Processor Aggregator Device)
              [    0.270317] ACPI: EC: Look up EC in DSDT
              [    0.273074] ACPI BIOS Warning (bug): Incorrect checksum in table [TAMG] - 0x10, should be 0x0F (20130517/tbprint-204)
              [    0.273758] ACPI: Interpreter enabled
              [    0.273762] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
              [    0.273765] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
              [    0.273773] ACPI: (supports S0 S3 S4 S5)
              [    0.273774] ACPI: Using IOAPIC for interrupt routing
              [    0.273788] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
              [    0.273844] ACPI: No dock devices found.
              [    0.277060] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
              [    0.277064] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
              [    0.277065] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
              Not sure if it helps, though...

              Comment


                #8
                Originally posted by teracow View Post
                Also, found this in dmesg output:
                Code:
                [    0.266381] ACPI: bus type PCI registered
                [    0.266383] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
                [    0.266423] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xec000000-0xefffffff] (base 0xec000000)
                [    0.266425] PCI: MMCONFIG at [mem 0xec000000-0xefffffff] reserved in E820
                [    0.268990] PCI: Using configuration type 1 for base access
                [    0.269690] bio: create slab <bio-0> at 0
                [    0.269805] ACPI: Added _OSI(Module Device)
                [    0.269806] ACPI: Added _OSI(Processor Device)
                [    0.269807] ACPI: Added _OSI(3.0 _SCP Extensions)
                [    0.269808] ACPI: Added _OSI(Processor Aggregator Device)
                [    0.270317] ACPI: EC: Look up EC in DSDT
                [    0.273074] ACPI BIOS Warning (bug): Incorrect checksum in table [TAMG] - 0x10, should be 0x0F (20130517/tbprint-204)
                [    0.273758] ACPI: Interpreter enabled
                [    0.273762] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
                [    0.273765] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
                [    0.273773] ACPI: (supports S0 S3 S4 S5)
                [    0.273774] ACPI: Using IOAPIC for interrupt routing
                [    0.273788] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
                [    0.273844] ACPI: No dock devices found.
                [    0.277060] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
                [    0.277064] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
                [    0.277065] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
                Not sure if it helps, though...
                Hmm, this usually needs drilling down to fix but what I can recommend is adding "pcie_aspm=force" to your kernel boot options. It's not ideal but should work in most cases. Does this problem affect actual usage?

                Comment


                  #9
                  Originally posted by dmeyer View Post
                  Does this problem affect actual usage?
                  No, I don't usually leave this computer alone long enough for powersaving features to be useful. Just noticed the error when looking around and thought I should mention it.

                  I'll try your suggestion.
                  Last edited by teracow; Nov 07, 2013, 05:02 PM.

                  Comment


                    #10
                    Originally posted by teracow View Post
                    No, I don't usually leave this computer alone long enough for powersaving features to be useful. Just noticed the error when looking around and thought I should mention it.

                    I'll try your suggestion.
                    As a rule of thumb, you are almost inevitably going to get some ACPI warnings or errors. I get a few on my machine and it does not affect normal use. Even with these errors I get better battery life than under Win7 so it really is safe to ignore them. That said, the solution I passed onto you can - in some limited cases - have a few unintended consequences so I would rather just ignore the warnings and not try anything.

                    If you do feels your errors are impacting your use of the system feel free to let us know.

                    Comment


                      #11
                      Originally posted by dmeyer View Post
                      That said, the solution I passed onto you can - in some limited cases - have a few unintended consequences so I would rather just ignore the warnings and not try anything.
                      Okiedokie, I think I'll leave it alone then.

                      Thanks!

                      Comment

                      Working...
                      X