Comment 41 for bug 1194563

Ok. I tried doing some bisections. Here are the following kernels I attempted (all were Lucid/10.04 kernels since that's the last time I had any accurate batter info).

2.6.38-10.44 (pae)- failed, unmet repositories - no battery, no networking)
2.6.32-53.115 (pae) - no battery detected, issued acpi command and got nothing (just returned the command prompt), no networking
2.6.32-38.83 (pae) - no battery detected, issued acpi command and got nothing (just returned the command prompt), no networking
2.6.32-34.74 (pae) - no battery detected, issued acpi command and got nothing (just returned the command prompt), no networking

Tried mainline builds:
2.6.32-02063242 - no battery detected, issued acpi command and got nothing (just returned the command prompt), no networking
2.6.33-02063305 - no battery detected, issued acpi command and got nothing (just returned the command prompt), no networking

All these were attempted with 12.04 so it could be the older kernel conflicting w/ 12.04 (especially with networking). I would've thought one would have at least detected the battery and assume when I had 10.04, one of these Kernel's would've been on the machine and working (ie when battery status worked). Hopefully, I did a decent job of the bisect.

If it helps, when I booted with the Mainline Builds, both (during the splash screen or just as it was going off) flashed an acpi error message with something about an error in region.SM00. I didn't catch the rest as it went off too fast.

If that doesn't help give any other clues, it look like I'll just have to get used to being careful when I'm on battery. But thanks for all the help and sorry for how long it took me to find time to do the bisection!