From owner-freebsd-questions@FreeBSD.ORG  Mon Jan  5 02:34:03 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@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 D6CD5FD1
 for <freebsd-questions@freebsd.org>; Mon,  5 Jan 2015 02:34:03 +0000 (UTC)
Received: from pandora.au.calorieking.net (mail.au.calorieking.net
 [115.70.179.114])
 (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 7B18811D4
 for <freebsd-questions@freebsd.org>; Mon,  5 Jan 2015 02:34:02 +0000 (UTC)
Received: from pandora.au.calorieking.net (localhost [127.0.0.1])
 by pandora.au.calorieking.net (Postfix) with ESMTP id 7FBD6C
 for <freebsd-questions@freebsd.org>; Mon,  5 Jan 2015 10:33:47 +0800 (WST)
X-Virus-Scanned: amavisd-new at calorieking.com
Received: from pandora.au.calorieking.net ([127.0.0.1])
 by pandora.au.calorieking.net (mail.au.calorieking.net [127.0.0.1])
 (amavisd-new, port 10024)
 with ESMTP id 9I3EGX6qJ8Fb for <freebsd-questions@freebsd.org>;
 Mon,  5 Jan 2015 10:33:47 +0800 (WST)
Received: from egeria.internal (egeria.internal [192.168.2.111])
 by pandora.au.calorieking.net (Postfix) with ESMTPSA id 306C2A
 for <freebsd-questions@freebsd.org>; Mon,  5 Jan 2015 10:33:47 +0800 (WST)
Message-ID: <54A9F80A.2010507@calorieking.com>
Date: Mon, 05 Jan 2015 10:33:46 +0800
From: Gregory Orange <gregory.orange@calorieking.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: Re: CURRENT: Intel Haswell KMS support?
References: <20141231203011.51831755.ohartman@zedat.fu-berlin.de>
 <20141231200235.GA3957@unixarea.DDR.dd>
 <20141231214835.0f46afc4.ohartman@zedat.fu-berlin.de>
 <54A52D47.10306@qeng-ho.org>
In-Reply-To: <54A52D47.10306@qeng-ho.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 02:34:03 -0000

Hi Arthur,

On 01/01/15 19:19, Arthur Chance wrote:
> This is being written on a machine with an Intel i7-4790K CPU (Devil's
> Canyon, i.e. Haswell) and a Dell U2711 2560x1440 monitor. The X VESA
> driver works fine for me at native resolution. OK, I'm not a gamer and I
> don't do anything that needs fast 3D, but it works well enough that my
> first thought after reading the original post was "Haswell graphics
> aren't supported???" because I'd completely forgotten I was using the
> VESA driver. Using a vt console rather than sc I have no problem
> dropping out of X back into console mode either.

I think this is the problem I'm facing - can you clarify and assist if 
possible? I have a Haswell i3 which runs X fine with vesa, but when I 
quit X, the machine crashes hard and requires holding the power button.

Cheers,
Greg.