Date: Fri, 12 Dec 2014 10:21:59 -0500 From: John Baldwin <jhb@freebsd.org> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-acpi@freebsd.org Subject: Re: ENXIOing non-present battery Message-ID: <6449474.BnGsyZAKhP@ralph.baldwin.cx> In-Reply-To: <548A072D.7090304@freebsd.org> References: <54840781.70603@freebsd.org> <201412111408.50866.jhb@freebsd.org> <548A072D.7090304@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, December 11, 2014 01:05:49 PM Colin Percival wrote: > On 12/11/14 11:08, John Baldwin wrote: > > On Sunday, December 07, 2014 2:53:37 am Colin Percival wrote: > >> On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First > >> the battery which exists; and second, a "Not Present" battery with zeroed > >> statistics. FreeBSD, not realizing that this second battery is a complete > >> myth -- the E7440 only has one battery, and there is nowhere to add another > >> -- faithfully reports the data from ACPI to userland. > > > > Does setting hint.battery.1.disabled=1 work for you? > > That fixes the dev.battery sysctls and KDE's battery monitor. The > hw.acpi.battery.units sysctl still reports "2", and `acpiconf -i 1` > still reports the phantom battery; but I suppose those don't matter > much... Ok. That is the "generic" thing we already have in place to disable devices, so I'd probably prefer to use that as the known workaround rather than adding another knob. That said, it looks like we report the userland state of "not present" correctly. I wonder if the bug is in KDE itself and its FreeBSD-specific power management bits (rather than hald)? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6449474.BnGsyZAKhP>