thanks for a try, do not work for dell xps studio 1340.

Hi guys, I find someone post the method that replaces AppleACPIPlatform.kext from 10.6.7 to Lion with AppleACPIBatterManager.kext can show the battery info on the top bar, also I have tested it and it is true, but there is something with System profile shows.

Try to use VoodooBattery.kext instead AcpipBattery.kext, it looks like to work, even for the system profile.

Found this on another site I take no credit for the kext it works on my Asus G51 just thought I would pass it along

Indeed, using AppleACPIPlatform from SL it works fine.

VoodooBattery on Lion GM works just fine. You need to place kext in S/L/E not Extra

The _BIF method failure with 10.7 AppleACPIPlatform is due to aml parsing/executing differences vs the 10.6 version of AppleACPIPlatform. While rolling back the kext may work as a workaround, the real fix is to update your DSDT to address the _BIF method failure. A fix for the dell 1340 laptop, which can be used as an example for others:

http://www.insanelymac.com/forum/index.php...t&p=1736543

The meat of the fix is editing the battery status update methods to do 8 bit I/O instead of 16 bit.

It's a bit of a problem that VoodooBattery doesn't correctly report on the problem when the _BIF method exists but fails to execute properly. Right now it just fails silently which is lame. When the _BIF method fails to execute, the return status from the evaluateObject() call is kIOReturnError. In this case VoodooBattery should report the error, even when you're running the 'release' version not just the 'debug' version.

This post has been edited by bcc9: Aug 20 2011, 04:18 AM

In case nobody noticed Lion's ACPI CA version is 0x20100528 => 28 April 2010 =>Advanced Configuration and Power Interface Specification Revision 4.0a.
This mean any ACPI table that is not conform with that specification (latest, 5.0 is work on progress) will fail on Lion!

The bug mentioned by bcc9 is just one of the many we will fight to correct on our 1.0(Gigabyte), 2.0/2.0a(Asus and many other), or best case, 3.0 ACPI Tables.

I experienced several other bugs like with ACPIMonitor plugin, SMBus declaration and methods and so on.

So you know what to expect.

Great found!
I also notice that FADT table should be converted to ACPI4.0 else no battery (Snow 10.6.8)
Existing Chameleon do not do this.