From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 3 18:21:36 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 630D610656C3; Fri, 3 Sep 2010 18:21:34 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Ian Smith Date: Fri, 3 Sep 2010 14:21:24 -0400 User-Agent: KMail/1.6.2 References: <20100903135945.K32216@sola.nimnet.asn.au> In-Reply-To: <20100903135945.K32216@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009031421.26466.jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org Subject: Re: acpi shows wrong battery state (fwd) 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: Fri, 03 Sep 2010 18:21:36 -0000 On Friday 03 September 2010 01:32 am, Ian Smith wrote: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debu >g.html === > 11.16.5.1 _OS dependencies > > Some AML assumes the world consists of various Windows versions. > You can tell FreeBSD to claim it is any OS to see if this fixes > problems you may have. An easy way to override this is to set > hw.acpi.osname="Windows 2001" in /boot/loader.conf or other similar > strings you find in the ASL. === > > It may be worth trying setting hw.acpi.osname to "Linux", or to one > of the others mentioned in your ASL. You'll see a number of > conditional tests on 'OSYS' in there; I don't know just what they > do, but it can't hurt to experiment. > > Try 'Windows 2001' also; there are some tests in the > EmbeddedControl section mentioning an RFLG and VIST .. clearly the > latter refers to Vista, but Windows 2001 zeroes RFLG, otherwise > set. (just guessing!) hw.acpi.osname is for \_OS and it does NOT influence \_OSI at all. They have totally different semantics although MS is advocating \_OSI is some sort of improved version of \_OS, unfortunately. Some BIOSes use both \_OS and \_OSI (e.g., \_OS for old Windows and \_OSI for newer Windows). Because of this problem, ACPICA just matches any known Windows OSIs for maximum compatibility. :-( FYI, in the latest ACPICA in CURRENT, we can install or remove OSIs from OS but the FreeBSD part is yet to be implemented. Jung-uk Kim