Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Jan 2015 15:20:20 +0800 (CST)
From:      Mary <>
Subject:   Attn:Purchasing IP65 SAA Down Light Easter Industries 1/4/2015 11:20:18 PM
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
From owner-freebsd-questions@FreeBSD.ORG  Mon Jan  5 08:35:52 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: from (
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by (Postfix) with ESMTPS id 345819E7
 for <>; Mon,  5 Jan 2015 08:35:52 +0000 (UTC)
Received: from ( [])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by (Postfix) with ESMTPS id C1BD339A7
 for <>; Mon,  5 Jan 2015 08:35:51 +0000 (UTC)
Received: from ( [])
 by (8.14.7/8.14.7) with ESMTP id
 t058ZbFV064666; Mon, 5 Jan 2015 08:35:38 GMT
Message-ID: <>
Date: Mon, 05 Jan 2015 08:35:37 +0000
From: Arthur Chance <>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Gregory Orange <>,
Subject: Re: CURRENT: Intel Haswell KMS support?
References: <>
 <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <>
List-Unsubscribe: <>, 
List-Archive: <>;
List-Post: <>
List-Help: <>
List-Subscribe: <>, 
X-List-Received-Date: Mon, 05 Jan 2015 08:35:52 -0000

On 05/01/2015 02:33, Gregory Orange wrote:
> 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.

The problem with sc and the new X system is that on return from X to 
console mode the sc driver can't regain control of the screen to display 
anything. It doesn't crash, but you get a black screen so you might 
think it's not responding. In fact, if you (carefully) type "shutdown -r 
now" (or any other command) it will respond. If that's what's happening, 
switching to the vt driver will help. If you're genuinely getting a 
crash though it's not an sc versus vt problem.

To use the vt driver on my system I have the following two lines in 


Try that (and reboot of course) and see what happens.

Those who do not learn from computing history are doomed to

Want to link to this message? Use this URL: <>