From owner-freebsd-stable@FreeBSD.ORG Wed Aug 15 09:16:44 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 165FB106564A for ; Wed, 15 Aug 2012 09:16:44 +0000 (UTC) (envelope-from zeising@daemonic.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) by mx1.freebsd.org (Postfix) with ESMTP id 82F908FC16 for ; Wed, 15 Aug 2012 09:16:43 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 96932403DF for ; Wed, 15 Aug 2012 11:16:41 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 89213403D7; Wed, 15 Aug 2012 11:16:41 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (mx.daemonic.se [IPv6:2001:470:dca9:0:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 03D33403E9; Wed, 15 Aug 2012 11:16:38 +0200 (CEST) Received: from mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) by mx.daemonic.se (Postfix) with ESMTPS id 3WxlRT6C0xz8gtM; Wed, 15 Aug 2012 11:16:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mx.daemonic.se ([IPv6:2001:470:dca9:0:1::3]) (using TLS with cipher CAMELLIA256-SHA) by mailscanner.daemonic.se (mailscanner.daemonic.se [2001:470:dca9:0:1::6]) (amavisd-new, port 10025) with ESMTPS id IWFYog-n6ZLp; Wed, 15 Aug 2012 11:16:35 +0200 (CEST) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2001:470:dca9:0:1::4]) by mx.daemonic.se (Postfix) with ESMTPS id 3WxlRR4r8sz8gtL; Wed, 15 Aug 2012 11:16:35 +0200 (CEST) Received: from [IPv6:2001:470:dca9:1::4] (vivi.daemonic.se [IPv6:2001:470:dca9:1::4]) by mail.daemonic.se (Postfix) with ESMTPSA id 3WxlRR3tT3z9Ctj; Wed, 15 Aug 2012 11:16:35 +0200 (CEST) Message-ID: <502B68EA.5040907@daemonic.se> Date: Wed, 15 Aug 2012 11:16:26 +0200 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: Andreas Nilsson References: <502B5F7D.6000909@bsdforen.de> <502B61B8.4040304@bsdforen.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Dominic Fandrey , freebsd-stable@freebsd.org Subject: Re: battery state X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2012 09:16:44 -0000 On 2012-08-15 11:07, Andreas Nilsson wrote: > On Wed, Aug 15, 2012 at 10:45 AM, Dominic Fandrey wrote: >> On 15/08/2012 10:40, Andreas Nilsson wrote: >>> On Wed, Aug 15, 2012 at 10:36 AM, Dominic Fandrey >>> 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