From owner-freebsd-questions@FreeBSD.ORG Mon Jan 5 08:51:09 2015 Return-Path: Delivered-To: freebsd-questions@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 9924ADE8 for ; Mon, 5 Jan 2015 08:51:09 +0000 (UTC) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33C603C2F for ; Mon, 5 Jan 2015 08:51:08 +0000 (UTC) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.14.7/8.14.7) with ESMTP id t058p4C4064683; Mon, 5 Jan 2015 08:51:04 GMT (envelope-from freebsd@qeng-ho.org) Message-ID: <54AA5078.7030403@qeng-ho.org> Date: Mon, 05 Jan 2015 08:51:04 +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: Matthias Apitz , Gregory Orange , freebsd-questions@freebsd.org Subject: Re: CURRENT: Intel Haswell KMS support? References: <20141231203011.51831755.ohartman@zedat.fu-berlin.de> <20141231200235.GA3957@unixarea.DDR.dd> <20141231214835.0f46afc4.ohartman@zedat.fu-berlin.de> <54A52D47.10306@qeng-ho.org> <54A9F80A.2010507@calorieking.com> <54AA4CD9.50808@qeng-ho.org> <20150105084400.GA2822@unixarea.DDR.dd> In-Reply-To: <20150105084400.GA2822@unixarea.DDR.dd> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org 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:51:09 -0000 On 05/01/2015 08:44, Matthias Apitz wrote: > El día Monday, January 05, 2015 a las 08:35:37AM +0000, Arthur Chance escribió: > >> To use the vt driver on my system I have the following two lines in >> /boot/loader.conf >> >> kern.vty=vt >> i915kms_load="YES" >> >> Try that (and reboot of course) and see what happens. > > Be carefully with the last line (i915kms_load="YES") and prepared to > boot from another media to reset it again, because some hardware does > not boot with this. Any idea what hardware triggers this? I've got an i7-4790K CPU on an Asus Z97-A mobo and that works OK for the record. -- Those who do not learn from computing history are doomed to GOTO 1