From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 07:34:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E089316A41F; Tue, 26 Jul 2005 07:34:57 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4420643D45; Tue, 26 Jul 2005 07:34:56 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6Q7Ypbv060754; Tue, 26 Jul 2005 09:34:52 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6Q7Ypnl044739; Tue, 26 Jul 2005 09:34:51 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6Q7YpLD044738; Tue, 26 Jul 2005 09:34:51 +0200 (CEST) (envelope-from wb) Date: Tue, 26 Jul 2005 09:34:51 +0200 From: Wilko Bulte To: Nate Lawson Message-ID: <20050726073451.GA44706@freebie.xs4all.nl> References: <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050725184101.GA41023@freebie.xs4all.nl> <42E5CA9E.6080309@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E5CA9E.6080309@root.org> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 07:34:58 -0000 On Mon, Jul 25, 2005 at 10:31:10PM -0700, Nate Lawson wrote.. > Wilko Bulte wrote: > >>>On Sun, 24 Jul 2005 17:15:12 -0700 > >>>Nate Lawson wrote: > >>Please try this patch with 7-current and report its output both on and > >>off power. It prints out more debugging info each time the battery is > >>read. > > > > > >On an Compaq EVO N160, on AC power > >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > >batt pass2: min 0 total_min 0 total_cap 0 > >ichss0: transition to 1 failed > > This is a separate issue, you should disable ichss: > hint.ichss.0.disabled="1" > > It appears your chipset does not actually support it. I think bruno@ > has a patch for doing more detailed checking for systems that actually > support it. > > >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > >batt pass2: min 0 total_min 0 total_cap 0 > >ichss0: transition to 1 failed > > > >APM version: 1.2 > >APM Management: Enabled > >AC Line status: on-line > >Battery Status: charging > >Remaining battery life: 0% > >Remaining battery time: 0:00:00 > >Number of batteries: 1 > >Battery 0: > > Battery Status: charging > > Remaining battery life: 0% > > Remaining battery time: 0:00:00 > > This is strange behavior. Your system is never reporting the current > battery capacity (cap = 0) even though it reports a reasonable battery > status (charging). Yep. It has always been this way. > >Unplugging AC power: > > > >batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 > >batt pass2: min 166 total_min 166 total_cap 0 > > > > > >wb@chuck ~: apm > >APM version: 1.2 > >APM Management: Enabled > >AC Line status: off-line > >Battery Status: low > >Remaining battery life: 0% > >Remaining battery time: 2:31:00 > >Number of batteries: 1 > >Battery 0: > > Battery Status: low > > Remaining battery life: 0% > > Remaining battery time: 2:31:00 > > Again, it does not report a valid cap off power but does report a valid > rate of use. > > Did you always have this behavior or was this introduced by my commit? Been there since a long time. -- Wilko Bulte wilko@FreeBSD.org