Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000
while my BIOS/UEFI reports a battery charge capacity of 92% for my
notebook-
battery, upower still reports a charge capacity of 100% (AFAIK
upower gets this
information from the kernel - I believe this to be a kernel ACPI
bug).
The kernel driver doesn't do anything very interesting so it's
actually
very likely a BIOS bug.
I checked the situation in Windows 7 over the last days and I don't see
the problem there. I can use the 'HP Support Assistant' in Windows to
check the battery capacity and status – it seems to be the same tool as
in the 'HP UEFI Support Environment'. The value 'Current' (in mAh)
accords to the values (in percentage of 'Full Charge Capacity') reported
by Windows.
This is why I don't think that this is a BIOS bug.
Can you send the contents of /sys/class/power_supply/BAT1/uevent so
we
at least know what the kernel is reporting?
stefan@rosa:~$ cat /sys/class/power_supply/BAT1/uevent
POWER_SUPPLY_NAME=BAT1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Unknown
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=11100000
POWER_SUPPLY_VOLTAGE_NOW=10872000
POWER_SUPPLY_POWER_NOW=14851000
POWER_SUPPLY_ENERGY_FULL_DESIGN=59940000
POWER_SUPPLY_ENERGY_FULL=59940000
POWER_SUPPLY_ENERGY_NOW=17982000
POWER_SUPPLY_MODEL_NAME=Venturi
POWER_SUPPLY_MANUFACTURER=13-17
POWER_SUPPLY_SERIAL_NUMBER=01317 01/24/2012
Regarding my original issue ('GNOME fails to execute action on critical
battery condition') I just want to add that there seem to be three
issues involved: one is really a BIOS bug (see the last comments of
#695634), one at least seems to be a UPower bug (see #6841869) and then
there's this one.
Stefan.
Reply to: