From owner-freebsd-current@FreeBSD.ORG Mon Jul 14 22:08:33 2003 Return-Path: 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 1A15037B401 for ; Mon, 14 Jul 2003 22:08:33 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B088643F85 for ; Mon, 14 Jul 2003 22:08:32 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id A411E72DD1; Mon, 14 Jul 2003 22:08:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 9EB7A72DD0; Mon, 14 Jul 2003 22:08:32 -0700 (PDT) Date: Mon, 14 Jul 2003 22:08:32 -0700 (PDT) From: Doug White To: Scott Robbins In-Reply-To: <20030715003319.GA20034@scottro11.homeunix.net> Message-ID: <20030714220622.M5937@carver.gumbysoft.com> References: <20030715003319.GA20034@scottro11.homeunix.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Trouble with ACPI and ASUS MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Jul 2003 05:08:33 -0000 On Mon, 14 Jul 2003, Scott Robbins wrote: > It didn't. For the heck of it, I then tried recompiling the kernel with > the device acpi put back in, despite the possible dangers, but it didn't > work either. kldstat shows that the acip module is loaded. The error > that I get is ACPI timed out. > > ACPI power-off failed - timeout > The operating system has halted > Press any key to reboot Is this the only time you have problems? If so, I'd count yourself awfully lucky. > Some googling has indicated that this problem might be confined to ASUS > boards, but I'm not sure. My IRC friend suggested that I post the > problem here and see if anyone had solutions. This isn't enough information. We'd also need to see the dmesg from the offending machine, with any and all ACPI error messages that may be printed. Using acpidump to extract the DSDT is also helpful in case someone asks for it. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org