From owner-freebsd-current@FreeBSD.ORG Wed Oct 1 16:38:51 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 5DFFA16A4B3 for ; Wed, 1 Oct 2003 16:38:51 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id A27D543FF3 for ; Wed, 1 Oct 2003 16:38:50 -0700 (PDT) (envelope-from bleez@comcast.net) Received: from gravy.homeunix.net ([68.81.196.221]) by comcast.net (rwcrmhc13) with ESMTP id <2003100123384801500osrl1e>; Wed, 1 Oct 2003 23:38:48 +0000 Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2]) by gravy.homeunix.net (8.12.10/8.12.10) with ESMTP id h91NclgQ000963; Wed, 1 Oct 2003 19:38:47 -0400 (EDT) (envelope-from bleez@comcast.net) Date: Wed, 1 Oct 2003 19:38:47 -0400 (EDT) From: Bryan Liesner To: Nate Lawson In-Reply-To: <20031001112435.C85421@root.org> Message-ID: <20031001193250.X945@gravy.homeunix.net> References: <20030930144703.W81965@root.org> <20030930220658.GA51513@lagash.satanosphere.com> <20031001170457.GA55275@lagash.satanosphere.com> <20031001112435.C85421@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Problem w/ ACPI in -CURRENT: Update 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: Wed, 01 Oct 2003 23:38:51 -0000 Now I'm having an issue with ACPI. I used to hit the power button and that would initiate a proper shutdown. Now it seems to do nothing, but when I reboot the system goes into a suspended state before completing the shutdown. The motherboard beeps three times, the screen goes blank, and will complete the shutdown after I hit the any key. The strange thing is that in the past, a user initiated suspend while the system is running would never blank the screen, but this suspend-before-shutdown does... What do you need from me to help resolve this?