From owner-freebsd-x11@FreeBSD.ORG  Wed Aug 21 15:37:08 2013
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 97E9761B
 for <freebsd-x11@freebsd.org>; Wed, 21 Aug 2013 15:37:08 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6D47124C5
 for <freebsd-x11@freebsd.org>; Wed, 21 Aug 2013 15:37:07 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2271D2308C
 for <freebsd-x11@freebsd.org>; Wed, 21 Aug 2013 11:37:05 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute3.internal (MEProxy); Wed, 21 Aug 2013 11:37:06 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:subject:date:in-reply-to
 :references; s=smtpout; bh=QriCguRek+5osykY8Iv2m/D/COA=; b=PSmfb
 bEe3zVWVauC5OM5CbXZauJKIgH3MYlkl+j9FD1IPC6/HhWr+FcsKEdItmCLJKwJP
 v4j8CBNVWmORyTlzLkVqr5ZxiluPKpSLMc4qA8bSXMPwB1RXne2FoiZHZxle7o+h
 NpTzW0hr3QwFUzXgnNM/Y9VoFMA7BAlHuYZsA4=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 8CD80B02387; Wed, 21 Aug 2013 11:37:05 -0400 (EDT)
Message-Id: <1377099425.10745.12486709.048AEAE7@webmail.messagingengine.com>
X-Sasl-Enc: Ml5g0TUTk9O+3BkTtHOmS8Iig435iOigfjk+UvUbt3Ai 1377099425
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-x11@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-d009844e
Subject: Re: Problem with the most recent Intel driver
Date: Wed, 21 Aug 2013 10:37:05 -0500
In-Reply-To: <CAJCmFP_YnQqzN_ySqsqmp7D_qoyXv580dBwvWR37tUd=dACTAA@mail.gmail.com>
References: <CAJCmFP_YnQqzN_ySqsqmp7D_qoyXv580dBwvWR37tUd=dACTAA@mail.gmail.com>
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:37:08 -0000

Hi! 

I had to deal with this too, once, when I was doing a PC-BSD install on
a netbook with Intel graphics. I worked around it by hard-powering down
the machine after this part of the install, booting into single user
mode, and then somewhere in /var/ I believe is a dotfile (.something)
that either has info inside it or just the existence of the dotfile
determines which part of setup has been completed. Deleting this file
(or editing  -- can't remember) and rebooting continued to the next part
of setup.

Unfortunately there's not much that can be done to fix this until the VT
switching for the new DRI/KVM/Intel/whatever framework is finished. I
don't know if there is an ETA on this work, and it may not even show up
in FreeBSD 9.x. It would be nice if PC-BSD could detect you're using an
Intel driver and modify their install process slightly to eliminate the
need for a hack/workaround...