From owner-freebsd-current Mon Jan 27 12:36:19 2003 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 D0D9437B401 for ; Mon, 27 Jan 2003 12:36:18 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 17AA743F13 for ; Mon, 27 Jan 2003 12:36:18 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 86362 invoked by uid 1000); 27 Jan 2003 20:36:18 -0000 Date: Mon, 27 Jan 2003 12:36:18 -0800 (PST) From: Nate Lawson To: Bryan Liesner Cc: current@freebsd.org Subject: Re: follow up on acpi issue In-Reply-To: <20030125135410.Q557@gravy.kishka.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 25 Jan 2003, Bryan Liesner wrote: > Thanks, Nate. When you suggested that I remove the apm stuff fron the > kernel, you meant ALL of the apm stuff, didn't you :) . I took a > second look and found I still had viapm and its requirements still in > the config file. The system boots fine now with acpi. > > By the way, the system didn't hang as I claimed in my earlier mail. I > was able to telnet in... Having acpi and viapm had the side effect of > making the console go away. viapm is VIA power management, not an apm system. It's interesting that it made your console go away. I'm sending this back to -current to see if anyone has ideas what might be wrong with viapm. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message