From owner-freebsd-current@FreeBSD.ORG  Sat Sep 20 14:28:45 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@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 ESMTPS id 0ED65C96;
 Sat, 20 Sep 2014 14:28:45 +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 AF6FCDF;
 Sat, 20 Sep 2014 14:28:44 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.9/8.14.9) with ESMTP id s8KEShkj024685
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 20 Sep 2014 08:28:43 -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 s8KEShgc024682;
 Sat, 20 Sep 2014 08:28:43 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Sat, 20 Sep 2014 08:28:43 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Subject: Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't
 recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT
In-Reply-To: <20140920162548.0d793cb8.ohartman@zedat.fu-berlin.de>
Message-ID: <alpine.BSF.2.11.1409200827380.96859@wonkity.com>
References: <20140919201210.72650231.ohartman@zedat.fu-berlin.de>
 <alpine.BSF.2.11.1409200727510.96859@wonkity.com>
 <20140920161012.02844320.ohartman@zedat.fu-berlin.de>
 <20140920162548.0d793cb8.ohartman@zedat.fu-berlin.de>
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]); Sat, 20 Sep 2014 08:28:43 -0600 (MDT)
Cc: freebsd-x11@freebsd.org, FreeBSD CURRENT <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Sep 2014 14:28:45 -0000

On Sat, 20 Sep 2014, O. Hartmann wrote:
>>
>> The very same CURRENT (most recent as I built world on all system today) doesn't
>> recognize the Haswell's HD4600 iGPU (i5-4200M). So, it seems impossible to me that
>> people can report having this GPU working if even the most recent FreeBSD CURRENT
>> doesn't recognize it.
>
> Sorry, on the laptop in question the integrated HD4600 does show up as a vga0: device in
> the pciconf-listing (it is very early and I stoped looking at the very end ...).

At this point, it's worth trying the vesa driver, which should work on 
Haswell.