1 |
On Sun, Nov 21, 2010 at 12:43 AM, Paul Hartman |
2 |
<paul.hartman+gentoo@×××××.com> wrote: |
3 |
> On Wed, Nov 17, 2010 at 12:03 AM, Paul Hartman |
4 |
> <paul.hartman+gentoo@×××××.com> wrote: |
5 |
>> On Thu, Nov 11, 2010 at 1:11 PM, J. Roeleveld <joost@××××××××.org> wrote: |
6 |
>>> On Thursday 11 November 2010 18:07:35 Paul Hartman wrote: |
7 |
>>>> On Wed, Nov 10, 2010 at 12:05 PM, J. Roeleveld <joost@××××××××.org> wrote: |
8 |
>>>> > If the soldering isn't done correctly, the battery-pack can literally |
9 |
>>>> > explode when put under load. |
10 |
>>>> |
11 |
>>>> Yeah, I don't think the savings would be big enough to justify the risk. |
12 |
>>>> |
13 |
>>>> I found a replacement battery online for less than USD$30 so I ordered |
14 |
>>>> it. Hopefully it fits and holds a charge. :) |
15 |
>>> |
16 |
>>> Good luck :) |
17 |
>>> If laptops would work with the same LIPO-packs that are used for Remote |
18 |
>>> Control planes, then it would be cheaper and easier as the chargers used for |
19 |
>>> those are better then the stuff they stick in laptops. |
20 |
>>> |
21 |
>>> But that's wishfull thinking |
22 |
>> |
23 |
>> The replacement battery is good, it fits perfectly and holds over 90% |
24 |
>> of maximum rated charge. |
25 |
>> |
26 |
>> I booted from Sabayon KDE LiveCD and the battery meter works fine in |
27 |
>> there, so there must be something wrong in my config. I will dig |
28 |
>> deeper to try to identify the differences. |
29 |
>> |
30 |
>> Thanks for all suggestions. :) |
31 |
> |
32 |
> After a combination of kernel upgrade, BIOS downgrade (to fix an |
33 |
> unrelated bug with resuming from suspend), KDE upgrades, and of course |
34 |
> general "messing with stuff", now it is working most of the time. I |
35 |
> have an actual battery meter and power management works and I am |
36 |
> happy. |
37 |
> |
38 |
> I sometimes get ACPI/DSDT errors in dmesg from boot time, about |
39 |
> infinite loops in 3 places, and when this happens the battery is |
40 |
> either "not present" to ACPI or is present but the state never changes |
41 |
> (for example remaining capacity at boot time is 2048 and this will |
42 |
> remain to be the value even as battery is dying). This properly seems |
43 |
> to happen randomly, or maybe affected somehow by dual-booting into MS |
44 |
> Windows. I didn't think DSDT/ACPI changes by the OS were persistent? |
45 |
> Perhaps it's something to do with warm rebooting vs powering off and |
46 |
> back on. I will have to experiment with it some more to see if I can |
47 |
> break it :) |
48 |
> |
49 |
> A long time ago I tried to extract and repair my broken DSDT but it |
50 |
> was over my head. I don't understand why it doesn't always work but |
51 |
> for now things seem to be functioning properly when ACPI is okay at |
52 |
> boot time. |
53 |
|
54 |
Another follow-up. It seems to work normally until it gets this error, |
55 |
at which point batter monitor stops working. Sometimes this error |
56 |
happens right away, other times it works for hours and then breaks. I |
57 |
guess it's a DSDT problem: |
58 |
|
59 |
ACPI Error (psparse-0537): Method parse/execution failed |
60 |
[\_SB_.PCI0.PIB_.EC0_.SMRD] (Node ffff88007f826320), |
61 |
AE_AML_INFINITE_LOOP |
62 |
ACPI Error (psparse-0537): Method parse/execution failed |
63 |
[\_SB_.BAT1.CHBP] (Node ffff88007f81d0f0), AE_AML_INFINITE_LOOP |
64 |
ACPI Error (psparse-0537): Method parse/execution failed |
65 |
[\_SB_.PCI0.PIB_.EC0_.SMSL] (Node ffff88007f826398), |
66 |
AE_AML_INFINITE_LOOP |
67 |
ACPI Error (psparse-0537): Method parse/execution failed |
68 |
[\_SB_.PCI0.PIB_.EC0_._Q09] (Node ffff88007f826438), |
69 |
AE_AML_INFINITE_LOOP |
70 |
|
71 |
Does anyone here know about this kind of thing? I am not really sure |
72 |
what it means. I've decompiled my DSDT but really don't know anything |
73 |
about how to fix it. Maybe I need to find some ACPI mailing list. |
74 |
Thanks. |