From owner-freebsd-questions@FreeBSD.ORG  Tue Jul 22 10:54:33 2014
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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1698CE12
 for <freebsd-questions@freebsd.org>; Tue, 22 Jul 2014 10:54:33 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id B792226DF
 for <freebsd-questions@freebsd.org>; Tue, 22 Jul 2014 10:54:32 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.9/8.14.9) with ESMTP id s6MAsSud095780
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 22 Jul 2014 04:54:28 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s6MAsSUQ095777;
 Tue, 22 Jul 2014 04:54:28 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Tue, 22 Jul 2014 04:54:28 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: David Benfell <benfell@parts-unknown.org>
Subject: Re: About the black screen (Otherwise solved) Re: All of a sudden,
 problems with X
In-Reply-To: <20140722060749.5487612C10D1@mail.parts-unknown.org>
Message-ID: <alpine.BSF.2.11.1407220452330.93805@wonkity.com>
References: <20140722024643.GA29536@munich.parts-unknown.org>
 <20140722051423.0cf369b9.freebsd@edvax.de>
 <20140722040440.GA16353@munich.parts-unknown.org>
 <20140722061900.008b35db.freebsd@edvax.de>
 <20140722060749.5487612C10D1@mail.parts-unknown.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Tue, 22 Jul 2014 04:54:28 -0600 (MDT)
Cc: Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18
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: Tue, 22 Jul 2014 10:54:33 -0000

On Mon, 21 Jul 2014, David Benfell wrote:

> There is a note in UPDATING (did I read it beforehand? Of course not.) about 
> some video chips--including Intel, which mine is--that says that 
> Ctrl/Alt/F[n] won't work. Apparently X isn't cleaning up after itself 
> correctly when exiting either.
>
> So the message here seems to be, once you start X, you'd better be happy with 
> it. Because you might not be leaving (short of a reboot).
>
> But what this also suggests is that, should I need it, the Xorg.conf.new I 
> generated might actually be okay. Because it's the exit that's screwed up 
> rather than anything to do with the configuration.

The vt(4) console driver included with 10-stable and 9-stable solves 
this: https://wiki.freebsd.org/Newcons