From owner-freebsd-acpi@FreeBSD.ORG  Tue Feb 17 17:17:14 2015
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 379EF37A
 for <freebsd-acpi@freebsd.org>; Tue, 17 Feb 2015 17:17:14 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0E74A22A
 for <freebsd-acpi@freebsd.org>; Tue, 17 Feb 2015 17:17:14 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5152CB915;
 Tue, 17 Feb 2015 12:17:10 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-acpi@freebsd.org
Subject: Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1
Date: Tue, 17 Feb 2015 10:40:35 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; )
References: <CAJ42Rm1dcpnUsD_-cdB3upUjNm=Jw+1j9WOEmH_7vN5zA7zDfA@mail.gmail.com>
 <54CA9529.1060903@att.net>
 <CAN6yY1sOwmQby8dOx6qkQCXKekcWbdWBO+hgmKBrXNw2tx1tMQ@mail.gmail.com>
In-Reply-To: <CAN6yY1sOwmQby8dOx6qkQCXKekcWbdWBO+hgmKBrXNw2tx1tMQ@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <201502171040.35416.jhb@freebsd.org>
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Tue, 17 Feb 2015 12:17:12 -0500 (EST)
Cc: Anthony Jenkins <Anthony.B.Jenkins@att.net>,
 Mohammad Najafi <zapture@gmail.com>
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi/>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 17:17:14 -0000

On Friday, January 30, 2015 12:37:10 pm Kevin Oberman wrote:
> My experience is the opposite.  With KMS I could run with VESA and without
> it I needed to pull VESA from my kernel.
> 
> As of today I am running fine with KMS, i915, and vt(4) with a standard
> GENERIC 10-STABLE kernel. I was running KMS and vt(4) well before they were
> MFCed, so I don't remember when I stopped adding "nooptions VESA", but I
> definitely used to need it to make suspect/resume work and don't any longer.
> 
> In any case, trying  kernel without VESA is a good idea.

FYI, VESA only applies to sc(4).  It is ignored for vt(4).  That is why it 
"works" with vt(4).

-- 
John Baldwin