Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Aug 2012 11:16:26 +0200
From:      Niclas Zeising <zeising@daemonic.se>
To:        Andreas Nilsson <andrnils@gmail.com>
Cc:        Dominic Fandrey <kamikaze@bsdforen.de>, freebsd-stable@freebsd.org
Subject:   Re: battery state
Message-ID:  <502B68EA.5040907@daemonic.se>
In-Reply-To: <CAPS9%2BSsgPHCr2_xaCF637vtj%2B%2BQx7i%2BtjE%2BwYTuotHLL3CWz0Q@mail.gmail.com>
References:  <502B5F7D.6000909@bsdforen.de> <CAPS9%2BSv7FgSN=CkNwhzTa_caHA5gVvGZD8HZZ548Qubp_SAF_g@mail.gmail.com> <502B61B8.4040304@bsdforen.de> <CAPS9%2BSsgPHCr2_xaCF637vtj%2B%2BQx7i%2BtjE%2BwYTuotHLL3CWz0Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-08-15 11:07, Andreas Nilsson wrote:
> On Wed, Aug 15, 2012 at 10:45 AM, Dominic Fandrey <kamikaze@bsdforen.de>wrote:
>> On 15/08/2012 10:40, Andreas Nilsson wrote:
>>> On Wed, Aug 15, 2012 at 10:36 AM, Dominic Fandrey <kamikaze@bsdforen.de
>>>> wrote:
>>>> For a while now "acpiconf -i0" always shows the battery state that
>>>> was correct when booting the system. It's never updated.
>>>>
>>> It wont solve the problem, but does the sysctl hw.acpi.battery.time update
>>> correctly?
>>>
>>
>> Thanks for the fast reply, right now it shows -1 (the system was plugged
>> in during boot).
>>
>> I just unplugged it and it still shows -1:
>>
>>> sysctl hw.acpi.battery
>>>
>> hw.acpi.battery.life: 99
>> hw.acpi.battery.time: -1
>> hw.acpi.battery.state: 0
>> hw.acpi.battery.units: 2
>> hw.acpi.battery.info_expire: 5
> 
> Sounds like there is some acpi-problem then. On my thinkpad it takes maybe
> five seconds for it to go from -1 to an estimate. Also
> hw.acpi.battery.state=0 for me equals "AC plugged in and battery full".

Just a short "aol".  I'm seeing the same issue, also on a HP laptop, a
HP 6910p with a Core2Duo 2.0GHz processor (can't remember the exact
model).  It has been this way for as long as I can remember (at least a
year), but I haven't checked into the matter more closely.  Are you
running the latest current?  I haven't updated in a while, so perhaps
the issue has been resolved...
Regards!
-- 
Niclas



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?502B68EA.5040907>