That BAT0/uevent output is very interesting. It shows that whatever values we see in FreeBSD are the same in Linux too:
See the MIN_DESIGN_VOLTAGE which is 122V on Linux also.
The VOLTAGE_NOW value is missing entirely--on FreeBSD volatage is shown as Unknown.
The MODEL_NAME is blank--same as FreeBSD.
Compare with the output on my ASUS X202E laptop:
$ uname -a
Linux X202E 5.0.0-38-generic #41-Ubuntu SMP Tue Dec 3 00:27:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ cat /sys/class/power_supply/BAT0/uevent
POWER_SUPPLY_NAME=BAT0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=7400000
POWER_SUPPLY_VOLTAGE_NOW=7400000
POWER_SUPPLY_POWER_NOW=0
POWER_SUPPLY_ENERGY_FULL_DESIGN=38006000
POWER_SUPPLY_ENERGY_FULL=22177000
POWER_SUPPLY_ENERGY_NOW=21637000
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_CAPACITY_LEVEL=Normal
POWER_SUPPLY_MODEL_NAME=X202-51
POWER_SUPPLY_MANUFACTURER=ASUSTek
POWER_SUPPLY_SERIAL_NUMBER=
Note that VOLTAGE_MIN_DESIGN is a sane value: 7.4V, and VOLTAGE_NOW is available.
hd_scania And yes what you’ve needed was logged from FreeBSD 12.1-RELEASE
Good. Keep it at 12.1-RELEASE.
hd_scania But why on Linux NO ACPI bugs or power hw ones
No idea, but, the similarity in battery status outputs on Linux and FreeBSD leads me to ask this question:
Is FreeBSD-12.1-RELEASE stable in the system console?
What I mean to ask is: if you don't start GUI, and leave the laptop in console mode, can you keep working like that? Or, does the laptop reboot or crash after some time, because the system detected a low battery power situation?
PS. This selective output is not what I want:
sudo dmesg|grep -Eie 'power|bat|acpi|apic|energy'
I want the all of the output:
sudo dmesg > /tmp/dmesg.txt
Same on FreeBSD. Post entire output.
