Re: incorrect battery reading, 0% all the time

> On my Dynabook Portege X40-J running OpenBSD 7.9, the battery report
> from `apm -v` always returns 0% despite the battery being fully
> charged and AC connected.
> AC/BAT state does change when AC is connected/disconnected, only the
> battery remains at 0%.
> 
> apm -v output
> (AC UNPLUGGED)
> Battery state: charging, 0% remaining, 0 minutes recharge time estimate
> AC adapter state: connected
> Performance adjustment mode: manual (2901 MHz)
> (AC PLUGGED)
> Battery state: CRITICAL, 0% remaining, 0 minutes life estimate
> AC adapter state: not connected
> Performance adjustment mode: auto (400 MHz)
> 
> There's nothing wrong with the battery physically, it reports
> correctly under Linux and holds charge well.

So what does it report under Linux?
(And other OSes, for that matter?)

> Attached is dmesg and sysctl output

sysctl hw would probably be enough for this :-)

> acpibat0 at acpi0: BAT1 model "G71C000MA210" serial 4266600 type LiON oem "BYD"

> hw.sensors.acpibat0.volt0=4266.60 VDC (voltage)
> hw.sensors.acpibat0.volt1=4266.60 VDC (current voltage)
> hw.sensors.acpibat0.power0=1804.16 W (rate)

Batteries differ in the semantics of what they report
- surely it's not 4 kV and 1.8kW; probably mili.

> hw.sensors.acpibat0.watthour0=1804.16 Wh (last full capacity)

It seems odd that this is exactly the same number
as the rate above in (mili)watts.

> hw.sensors.acpibat0.watthour1=3300.26 Wh (warning capacity)
> hw.sensors.acpibat0.watthour2=0.00 Wh (low capacity)
> hw.sensors.acpibat0.watthour3=3308.11 Wh (remaining capacity), WARNING
> hw.sensors.acpibat0.watthour4=1804.16 Wh (design capacity)

So 3308 Wh of the designed 1804 Wh remain?

I suspect the battery itself reporting something strange
- possibly linux's acpibat knows its quirks?

	Jan