ACPIBAT(4)

πŸ“¦
version 11.0 Β· 2 versions
, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is acpibat(4) from the Kernel Interfaces Manual, bestie β€” it’s literally the page for the ACPI Battery driver.

acpibat β€” ACPI Battery πŸŽ€

πŸŽ€ SYNOPSIS πŸŽ€

acpibat* at acpi?

✨ DESCRIPTION ✨

the acpibat driver supports ACPI batteries. no cap, that’s the whole vibe.

The battery status is made available through the envsys(4) API, and you can also display the battery information with the envstat(8) command:

$ envstat -d acpibat0
                         Current  CritMax  WarnMax  WarnMin  CritMin Unit
                present:      ON
         design voltage:  14.400                                        V
                voltage:  16.267                                        V
             design cap:  74.880                                       Wh
          last full cap:  48.260                                       Wh
                 charge:  47.910                      5.000%   0.414%  Wh (99.27%)
            charge rate:     N/A
         discharge rate:  16.641                                        W
               charging:     OFF
           charge state:  NORMAL

Depending on the battery, the unit of measurement for the capacity-related information is either watt-hour (Wh) or ampere-hour (Ah). From these, the charge is usually the most interesting value β€” main character energy, honestly β€” but it’s possible to derive useful information from the other values too. For example, when acpiacad(4) is disconnected, the discharge rate gives a coarse approximation of the current power consumption. The ratio between the design capacity and the last full capacity, on the other hand, reveals the overall health of deteriorating lithium-ion batteries. πŸ¦‹

πŸ¦‹ EVENTS πŸ¦‹

the acpibat driver is able to send events to the powerd(8) daemon when a capacity state has been changed. The new state will be reported as the fourth argument to the /etc/powerd/scripts/sensor_battery script. iykyk.

If a custom capacity limit was set via envstat(8), the acpibat driver will report a user-capacity event to the same script when the current capacity limit has been reached. periodt. πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

🌸 HISTORY 🌸

The acpibat driver appeared in NetBSD 1.6. a whole icon. πŸ‘‘

πŸ’€ BUGS πŸ’€

⚠️ real talk, bestie: the ACPI specifications make a distinction between β€œcontrol method batteries” and β€œsmart batteries”. The acpibat driver only supports control method batteries. Furthermore, acpibat does not yet support some additional battery information introduced in the ACPI 4.0 standard. not me fixing that today, but noted. 😭

brought to you by the source/version footer cuties: Debian, dated March 17, 2010, filed as ACPIBAT(4) β€” mwah πŸ’–πŸ«Ά

πŸ“¦ where this page comes from