From owner-freebsd-x11@FreeBSD.ORG  Wed Dec 24 16:13:54 2014
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@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 8FCCB10B;
 Wed, 24 Dec 2014 16:13:54 +0000 (UTC)
Received: from mail.metricspace.net
 (207-172-209-89.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com
 [207.172.209.89])
 by mx1.freebsd.org (Postfix) with ESMTP id 68F4526B8;
 Wed, 24 Dec 2014 16:13:53 +0000 (UTC)
Received: from [172.16.0.68] (unknown [172.16.0.68])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate) (Authenticated sender: eric)
 by mail.metricspace.net (Postfix) with ESMTPSA id 01A8B171C;
 Wed, 24 Dec 2014 16:13:52 +0000 (UTC)
Subject: VESA X11 drivers non-functional after recent update
From: Eric McCorkle <eric@metricspace.net>
Content-Type: text/plain;
	charset=us-ascii
X-Mailer: iPad Mail (11B511)
Message-Id: <F4B237B5-0400-4BD4-ADBB-1DC7F4E51E80@metricspace.net>
Date: Wed, 24 Dec 2014 11:13:55 -0500
To: freebsd-mobile@freebsd.org,
 "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.18-1
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, 24 Dec 2014 16:13:54 -0000

Hello,

I have a laptop with an Optimus setup with haswell graphics and an nvidia ca=
rd.  As none of this is currently supported, I had been using the VESA drive=
rs.  However, the VESA driver no longer functions after I updated ports yest=
erday (most likely connected to the removal of old x11).

I don't have the specific error message as I'm typing this on another device=
, but it seems that the driver can't access the bios (messages include "cann=
ot read V_BIOS", neither device reports a bios segment, etc).

Is there something I can do to restore the VESA drivers to a functioning sta=
te (or alternatively, any sort of development haswell driver I can use), or i=
s the only option to revert the ports directory and rebuild everything?=