From owner-freebsd-current@FreeBSD.ORG  Tue Jan  6 15:11:25 2004
Return-Path: <owner-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 7092416A4CE
	for <current@freebsd.org>; Tue,  6 Jan 2004 15:11:25 -0800 (PST)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id B10AD43D4C
	for <current@freebsd.org>; Tue,  6 Jan 2004 15:11:23 -0800 (PST)
	(envelope-from nate@root.org)
Received: (qmail 27889 invoked by uid 1000); 6 Jan 2004 23:11:24 -0000
Date: Tue, 6 Jan 2004 15:11:24 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: Rob MacGregor <rob_macgregor@hotmail.com>
Message-ID: <20040106150228.M27817@root.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: FreeBSD 5.2-CURRENT on HP Omnibook 6000 - ACPI problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2004 23:11:25 -0000

> The problem is that with ACPI enabled the eject button on the docking
> station doesn't work.

When ACPI is running, the BIOS no longer runs things like the eject
button.  Since we haven't implemented eject support yet, it does nothing
if ACPI is running.  Either wait for eject support, which will be a while,
or disable acpi.

> I've disabled two ACPI methods:
>
> lid: Because the lid is normally shut - I don't want the system going into
> standby all the time

sysctl hw.acpi.lid_switch_state=NONE

> thermal: Because sometimes a wild temperature is reported, causing a
> poweroff.  Certainly I doubt the values reported (over 200 C) when this
> occurs

I don't see how this is possible since the code to do this is commented
out.  Is there any console message printed before it powers off?  It may
be the BIOS that does this if it's just a power off (no nice shutdown).

    sys/dev/acpica/acpi_thermal.c:   /* shutdown_nice(RB_POWEROFF);*/

> On a related question - is it possible to tune the ACPI events (as you
> can under Linux)?  I'd like to keep the thermal action, but set it to
> poweroff on 2 over-temperature events rather than one.

Since the above code is commented out, you can just use /etc/devd.conf to
look for Thermal events of type 0x80 and then call a script that evaluates
sysctl hw.acpi.tz0.temperature and then call halt -p if it exceeds some
value.  We pipe many ACPI events to usermode through devd(8).

-Nate