NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: acpibat0 issue
RVP <rvp%SDF.ORG@localhost> wrote:
> On Fri, 15 Nov 2024, beaker wrote:
> > <snip>
> > After the AC is connected -- momentarilly -- the envstat(8) output
> > is correct and I can divide "charge" by "last full cap" to get the
> > current charge:
> >
> > --
> > $ envstat -d acpibat0
> > present: TRUE
> > design voltage: 10.800 V
> > voltage: 10.800 V
> > design cap: 47.520 Wh
> > last full cap: 26.373 Wh
> > charge: 26.110 Wh (99.00%)
> > charge rate: 6.058 W
> > discharge rate: N/A
> > charging: TRUE
> > charge state: NORMAL
>
> I'm not surprised by this behaviour if your battery now only has half its
> original capacity...
>
> > Here's is the battery-related info from dmesg(8) _before_ toggling
> > the AC adapter:
> > --
> > $ dmesg | grep bat
> > [ 1.029262] acpibat0 at acpi0 (BAT0, PNP0C0A-1): ACPI Battery
> > [ 1.950617] acpibat0: autoconfiguration error: failed to evaluate _STA: AE_NO_MEMORY
> > --
>
> This looks like a BIOS error. See if there's an updated BIOS.
>
> > Unfortunately I don't know how to interpret this autoconfig error.
> >
> > Once AC adapter is toggled I see this:
> > ..
> > [ 32.489257] acpibat0: normal capacity on 'charge state'
> >
> > I also noticed that there is no "bat0" entries for 'sysctl hw.acpi.'
> > though I don't know if there ought to be.
> >
> > I'm wondering if there's anything I might try to correct this issue
> > and/or possible work-arounds if not actualyl fixable?
> >
>
> I would recommend you a) get a new battery and b) update your firmware.
Out of curiosity I swapped in LMDE6 (Mint, Debian ed.) and ACPI works just fine,
no weirdness at all. Suggests it's a problem with NetBSD's ACPI implementation
which I'd guess is old and dated. Not a huge issue on such an old laptop but
still, maybe worth freshening the code?
Home |
Main Index |
Thread Index |
Old Index