From owner-freebsd-acpi@FreeBSD.ORG Wed Feb 18 03:49:49 2015 Return-Path: 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 D728E1CD; Wed, 18 Feb 2015 03:49:49 +0000 (UTC) Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3AD2260; Wed, 18 Feb 2015 03:49:49 +0000 (UTC) Received: by padfa1 with SMTP id fa1so11392830pad.2; Tue, 17 Feb 2015 19:49:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=D8kzYOOSWv3UkIGK8eQU6dWzcx1MtMa4jaKMzcMDPE4=; b=bXA8+kXvvPdJO6Sk+32NdjsNZo1eniHC6fV+K6dmOrXUGObhFjdZn/u7tc2ObhGnJs EMec8lB1TXQaJeJCTXuiSn2ME4CVuErPboGha5CPJ73qzTglTS2j5LN+29OnZcYS1jg2 stgb/QtXVp29IUQPs3UCfqN2k1rx/hzX5mS/qEgFp8Uk66JvNu8xoV6dGsu1GNykbJyS e0Z1hc7cV0bPnUNZaiehM61gCGDY+tHYsD4FoEzuhiJs6h40pjH8SdiIbktMiTEj/VKI +WRXsoe/s/1DAyvVMxkhX83H/XZ33hjH6hRatsAjwLYPsneYICjxBvih/ZJon11VVqjK 7EBQ== MIME-Version: 1.0 X-Received: by 10.70.124.202 with SMTP id mk10mr44669269pdb.159.1424230922532; Tue, 17 Feb 2015 19:42:02 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.30.198 with HTTP; Tue, 17 Feb 2015 19:42:02 -0800 (PST) In-Reply-To: <201502171040.35416.jhb@freebsd.org> References: <54CA9529.1060903@att.net> <201502171040.35416.jhb@freebsd.org> Date: Tue, 17 Feb 2015 19:42:02 -0800 X-Google-Sender-Auth: 5Jy3AQt3kHrtKvYBhwse8Gegqvo Message-ID: Subject: Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1 From: Kevin Oberman To: John Baldwin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Anthony Jenkins , Mohammad Najafi , "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 03:49:50 -0000 On Tue, Feb 17, 2015 at 7:40 AM, John Baldwin wrote: > 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 > I suspected that was the case, but did not recall for sure. Thanks for the confirmation, though it does not help with the problem reported. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com