From owner-freebsd-acpi@FreeBSD.ORG Wed Jan 4 17:57:54 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B02616A41F; Wed, 4 Jan 2006 17:57:54 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE54243D45; Wed, 4 Jan 2006 17:57:52 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EuCtS-0001UC-00; Wed, 04 Jan 2006 18:57:50 +0100 Date: Wed, 4 Jan 2006 18:57:50 +0100 To: Ariff Abdullah Message-ID: <20060104175750.GM13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> <20060103185047.GH13887@poupinou.org> <20060104161842.GK13887@poupinou.org> <20060105005441.029835c1.ariff@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105005441.029835c1.ariff@FreeBSD.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@FreeBSD.org, freebsd-amd64@FreeBSD.org, lists@stringsutils.com Subject: Re: No APM yet for AMD? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:57:54 -0000 On Thu, Jan 05, 2006 at 12:54:41AM +0800, Ariff Abdullah wrote: > On Wed, 4 Jan 2006 17:18:42 +0100 > Bruno Ducrot wrote: > > On Wed, Jan 04, 2006 at 10:14:13AM -0500, Francisco Reyes wrote: > > > Bruno Ducrot writes: > > > > > > >>http://public.natserv.net/acpidump.txt > > > > > > > >Well could you try to add this to your /boot/loader.conf: > > > >hw.acpi.osname="Microsoft Windows NT" > > > > > > Done > > > > > > > > > >It's because I want to check what happens if the following ASL is > > > >triggered: > > > > > > > >If (LEqual (SizeOf (\_OS), 0x14)) > > > >{ > > > > BPOL (0x3C) > > > >} > > > > > > Second dump on the same location... different name > > > http://public.natserv.net/acpidump2.txt > > > > > > >That's look like a workaround for Windows NT and that seems to > > > >be related to batteries and AC adapter. > > > > > > Not sure what was supposed to happen after trying the change in > > > loader.conf, but I tried "sysctl -a |grep acpi.bat" and the > > > results are the same as before. > > > > > > hw.acpi.battery.life: -1 > > > hw.acpi.battery.time: -1 > > > hw.acpi.battery.state: 7 > > > hw.acpi.battery.units: 1 > > > hw.acpi.battery.info_expire: 5 > > > > It was a stupid idea, sorry. I will look a little bit more. I > > think I begin to understand what's wrong, but I need to look a > > little bit further. > > > > I also CC to freebsd-acpi@ with a reply-to accordingly. > > > Few acpi BIOSes does not support _BST (battery status) method, causing > that type of weird sysctl output (since it depends solely on _BST). > Your hope is to use acpiconf(8) i.e acpiconf -i . > Unfortunately, acpiconf itself does not display all possible > values. > > Try this patch against usr.sbin/acpi/acpiconf/acpiconf.c > > http://people.freebsd.org/~ariff/acpi/acpiconf.c.diff > > Hopefully you will have the proper output in terms of percentage. > You won't have advance battery status such as remaining time and few > others. This is a limitation for BIOSes without _BST. There is a broken _BST in that AML. I think I can fix it directly onto the DSDT, or maybe I will use a little workaround which will use a SM Bus to access the battery. In fact I'm wondering if Windows use such smart battery stuff instead even though the SMBus is not visible from the AML (or I really don't see how it can work under that OS. Really). > I believe Nate Lawson is the right person to comment on this. Indeed. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.