From owner-freebsd-current@FreeBSD.ORG  Wed Dec  3 12:57:43 2003
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 CB1E016A4CE
	for <current@freebsd.org>; Wed,  3 Dec 2003 12:57:43 -0800 (PST)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 07E4543FDF
	for <current@freebsd.org>; Wed,  3 Dec 2003 12:57:43 -0800 (PST)
	(envelope-from nate@rootlabs.com)
Received: (qmail 21141 invoked by uid 1000); 3 Dec 2003 20:57:44 -0000
Date: Wed, 3 Dec 2003 12:57:44 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: Melvyn Sopacua <freebsd-current@webteckies.org>
In-Reply-To: <200312032131.15052.freebsd-current@webteckies.org>
Message-ID: <20031203125614.U21122@root.org>
References: <20031202143252.Y18107@root.org>
	<200312032131.15052.freebsd-current@webteckies.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Francisco Solsona <solsona@acm.org>
cc: current@freebsd.org
Subject: Re: ACPI problem, my VAIO won't come back from suspension
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: Wed, 03 Dec 2003 20:57:43 -0000

On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
> On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
> > Try other states (acpiconf -s 1, 2, 4).  If one works, use it.  If not,
> > try disabling acpi and using apm(4) to suspend and resume.
>
> Normally that would be grand, but now that I've not compiled acpi into the
> kernel, I have no /dev/apm anymore as well.

If you don't have acpi(4), then you need to add "device apm" to your
kernel to enable apm(4) support.

> Even with acpi, I never got a /dev/apmctl so apmd never worked. I've read
> through devfs(5)/(8), but as far as I understand, it is the driver's
> responsibility to create the device and even if you could do it in userland,
> than it will just be a non-configured device.

You can't use apmd with acpi(4).  It has /dev/acpictl.

-Nate