Date: Wed, 4 Jan 2006 18:57:50 +0100 From: Bruno Ducrot <ducrot@poupinou.org> To: Ariff Abdullah <ariff@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org, freebsd-amd64@FreeBSD.org, lists@stringsutils.com Subject: Re: No APM yet for AMD? Message-ID: <20060104175750.GM13887@poupinou.org> In-Reply-To: <20060105005441.029835c1.ariff@FreeBSD.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <cone.1135784510.758843.3324.1000@zoraida.natserv.net> <200512291412.19476.peter@wemm.org> <cone.1136052558.494842.28540.1000@zoraida.natserv.net> <20060103155509.GE13887@poupinou.org> <cone.1136308365.970162.45107.1000@zoraida.natserv.net> <20060103185047.GH13887@poupinou.org> <cone.1136387653.168993.62674.1000@zoraida.natserv.net> <20060104161842.GK13887@poupinou.org> <20060105005441.029835c1.ariff@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 05, 2006 at 12:54:41AM +0800, Ariff Abdullah wrote: > On Wed, 4 Jan 2006 17:18:42 +0100 > Bruno Ducrot <ducrot@poupinou.org> 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 <battery number>. > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060104175750.GM13887>