Power Mangement Issues on daru2

Bug #130739 reported by Trey Brown
12
Affects Status Importance Assigned to Milestone
System76
Confirmed
Medium
Unassigned
System76 Driver
In Progress
Medium
Unassigned
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Randomly does not recognize the battery charge, or when it is (un)plugged into A/C.

Tags: daru2
Revision history for this message
Trey Brown (trey.brown) wrote :
Revision history for this message
Thomas Aaron (tom-system76) wrote :

Confirmed.

It took me a while, but I was finally able to duplicate the problem.
Three Observation:

1. I've noticed that on my daru2, the icon does not start switching between a/c and battery until the battery is fully charged. Once it starts, though, it will not stop, even after the battery has discharged a bit.

2. The applet seems to correctly detect whether A/C or battery is being detected until it starts acting up. It is, however, very slow in showing a change in state. Sometimes it can take up to 30 seconds.

3. There is often a discrepancy in the readings of the applet and the readings of $acpi.

Revision history for this message
Thomas Aaron (tom-system76) wrote :

I obtained the latest BIOS update from the manufacturer.
It is still in the beta stage.

Applying the beta did not fix the problem.

Revision history for this message
Trey Brown (trey.brown) wrote :

Any update from the manufacturer?

Revision history for this message
Thomas Aaron (tom-system76) wrote : Re: [Bug 130739] Re: Power Mangement Issues on daru2

Yes. They sent me a beta bios upgrade that did not work.
So, we're exploring gnome-power-manager right now.

----- Original Message -----
From: "Trey" <email address hidden>
To: <email address hidden>
Sent: Thursday, August 16, 2007 12:14:19 PM (GMT-0700) America/Denver
Subject: [Bug 130739] Re: Power Mangement Issues on daru2

Any update from the manufacturer?

--
Power Mangement Issues on daru2
https://bugs.launchpad.net/bugs/130739
You received this bug notification because you are a member of System76
Bugs, which is the bug contact for System76.

Revision history for this message
Trey Brown (trey.brown) wrote :

Doesn't know if this helps or changes anything, but, out of curiosity I took out the battery when it was plugged in. Power management did not recognize that the battery had been removed. I left it out for a good 30 min or so to give it time to update if it was just changing slow.

Changed in system76:
importance: Undecided → Medium
status: New → Confirmed
Changed in system76-driver:
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

This same problem is occurring on my Darter running Gutsy. It happens with both the GNOME power manager and the KDE power manager. My power manager issue seems to be an ACPI issue for sure, and not a power-manager frontend problem. I did post this bug to the Ubuntu Kernel ACPI team with a plethora of debugging information. Below is a link to the bug I posted.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/139701

Revision history for this message
Chris Strelioff (chris-strelioff) wrote :

I have similar behavior on a brand new darter ultra. See the attached power history screen shot. Note: the a/c is connected during this whole time.

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

Setting this bug as affecting linux-souce-2.6.24 in Ubuntu since it is still an issue in Hardy.

Changed in linux-source-2.6.24:
status: New → Confirmed
Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

The bug that Michael reported [1] has more information that kernel acpi developers can use and is has been set to Triaged and Medium with the acpi team assigned. That is probably the bug we should watch. I will leave it up to the Sys76 people if they want to mark this bug a duplicate of Michael's. If we aren't going to mark it a duplicate I will remove the "linux" package from the list of affected packages on this bug (just so they don't have duplicate bugs in their records).

Tom/Carl, if there is any other information you could add to that bug to help the acpi team out I'm sure they would appreciate it.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/139701

Changed in linux:
importance: Undecided → Medium
Revision history for this message
Thomas Aaron (tom-system76) wrote :

Several power management problems are solved by using 64-bit Ubuntu on the DarU2 / MS-1221.
1. Under 32-bit Ubuntu, the machine would literally shut off while trying to resume from S-1 suspend. Under 64-bit, S-1 suspend works perfectly.
2. Under 32-bit the screen would alternately dim and brighten as the machine was failing to accurately determine if it was on A/C or Battery power. Under 64-bit Ubuntu, this is also fixed.

From here on out, we will participate in this bug report...
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/139701

Let me know what other info I can provide.

Revision history for this message
Thomas Aaron (tom-system76) wrote :

Sorry, I misspoke.

1. Under 32-bit Ubuntu, the machine would literally shut off while trying to resume from S-1 suspend. Under 64-bit, S-1 suspend works perfectly.

2. The lcd brightening/dimming issue is caused by number 3 below, which is still present in 64-bit.

3. Power monitor readings are eratic. The machine can't tell if it is on A/C or battery power. Most of the time, running 'acpi -b' at the command line
will give different results than reported by the battery applet.

4. I'v also observed that this problem occurs once the battery has been charged to 100%. Before that, it seems to be pretty stable.

Revision history for this message
Thomas Aaron (tom-system76) wrote :

A work-around for this bug has been discovered. Placing....

ec_intr=0

...as a kernel option allows power management to behave properly in 64-bit Ubuntu,
which has been confirmed by in-house testing.

Some posts on our forums indicate that it works in 32-bit Ubuntu as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.