From owner-freebsd-questions@FreeBSD.ORG Sat Jan 6 17:13:45 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2068C16A403 for ; Sat, 6 Jan 2007 17:13:45 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id ACB7613C44C for ; Sat, 6 Jan 2007 17:13:44 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so8226570nfc for ; Sat, 06 Jan 2007 09:13:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=RdYMr41oqoKqgwx3uVTg7I/MfA74HH1J9wafgw6j2yEFE2uNd5En4amGw1/MDYvuBIiVs/3w6SFFi66IJpgbMpC1rB7BHYbr6iL0XFyNmulZhdQPZYHMZ4wDGqK98csXv1vRopuDokELhclzC5b6wDkpDeCWwyR6mawL2GOtQtk= Received: by 10.82.152.16 with SMTP id z16mr1979627bud.1168103623624; Sat, 06 Jan 2007 09:13:43 -0800 (PST) Received: by 10.82.175.3 with HTTP; Sat, 6 Jan 2007 09:13:43 -0800 (PST) Message-ID: <539c60b90701060913r72ff843ao5e2924475e508c24@mail.gmail.com> Date: Sat, 6 Jan 2007 10:13:43 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "FreeBSD Users Questions" MIME-Version: 1.0 X-Google-Sender-Auth: d5f4e2f98ff671d1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: fix: acpiconf won't suspend X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 17:13:45 -0000 Previously, I had asked why acpiconf -s always failed with the output: "not ready yet". I never got a satisfying answer, but this morning, in a flash of insight, I ran "acpiconf -s&" - magic - the & makes it go. Of course, out of my three laptops I've bought 2 years apart (each), not a one will un-suspend correctly (all no ttys/xorg, just like the warning in the man/handbook states is typical), but maybe my discovery will help someone else. Anyone know if 6.2 or 7.x have made significant changes to acpi? Steve