Date: Wed, 24 Dec 2014 20:22:34 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-x11@freebsd.org Subject: Re: VESA X11 drivers non-functional after recent update Message-ID: <alpine.BSF.2.11.1412242017140.78400@wonkity.com> In-Reply-To: <20141224222025.GA7968@unixarea.DDR.dd> References: <F4B237B5-0400-4BD4-ADBB-1DC7F4E51E80@metricspace.net> <20141224222025.GA7968@unixarea.DDR.dd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Dec 2014, Matthias Apitz wrote: > El día Wednesday, December 24, 2014 a las 11:13:55AM -0500, Eric McCorkle escribió: > >> Hello, >> >> I have a laptop with an Optimus setup with haswell graphics and an nvidia card. As none of this is currently supported, I had been using the VESA drivers. However, the VESA driver no longer functions after I updated ports yesterday (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 "cannot read V_BIOS", neither device reports a bios segment, etc). >> >> Is there something I can do to restore the VESA drivers to a functioning state (or alternatively, any sort of development haswell driver I can use), or is the only option to revert the ports directory and rebuild everything? > > (Note: I do not have this problem and I can not help to solve it. I'm > only interested in your problem and its solution because I'm thinking to > acquire a netbook with haswell and do need the VESA driver too in this > case). > > I've checked the SVN > http://svnweb.freebsd.org/ports/head/UPDATING?view=log and the blog > pointed to by the information in UPDATING > http://blogs.freebsdish.org/graphics/2014/11/19/xserver-1-14-update-ready/ > I do not see any information about droping VESA support. The AIGLX default changed, though. Try Option "AIGLX" "Off" In the ServerLayout section. From owner-freebsd-x11@FreeBSD.ORG Thu Dec 25 16:37:52 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 8496F2D9 for <freebsd-x11@freebsd.org>; Thu, 25 Dec 2014 16:37:52 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id 53C9B1AA for <freebsd-x11@freebsd.org>; Thu, 25 Dec 2014 16:37:52 +0000 (UTC) Received: from [IPv6:2001:470:1f11:617:29d8:5ffb:f9ef:1d8d] (unknown [IPv6:2001:470:1f11:617:29d8:5ffb:f9ef:1d8d]) (using TLSv1.2 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 E3B1F19D6; Thu, 25 Dec 2014 16:32:01 +0000 (UTC) User-Agent: K-9 Mail for blackphone In-Reply-To: <alpine.BSF.2.11.1412242017140.78400@wonkity.com> References: <F4B237B5-0400-4BD4-ADBB-1DC7F4E51E80@metricspace.net> <20141224222025.GA7968@unixarea.DDR.dd> <alpine.BSF.2.11.1412242017140.78400@wonkity.com> MIME-Version: 1.0 Subject: Re: VESA X11 drivers non-functional after recent update From: Eric McCorkle <eric@metricspace.net> Date: Thu, 25 Dec 2014 11:32:00 -0500 To: Warren Block <wblock@wonkity.com>,Matthias Apitz <guru@unixarea.de> Message-ID: <E303C97D-FDD1-4424-8630-13F55A36638B@metricspace.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-x11@freebsd.org 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: Thu, 25 Dec 2014 16:37:52 -0000 I'm currently reverting everything (userland and ports) to the status of the repos on Oct 3 (when everything worked for me), in order to do a ZFS snapshot. I will then try updating again and try the AIGLX option. On December 24, 2014 10:22:34 PM EST, Warren Block <wblock@wonkity.com> wrote: >On Wed, 24 Dec 2014, Matthias Apitz wrote: > >> El dÃa Wednesday, December 24, 2014 a las 11:13:55AM -0500, Eric >McCorkle escribió: >> >>> Hello, >>> >>> I have a laptop with an Optimus setup with haswell graphics and an >nvidia card. As none of this is currently supported, I had been using >the VESA drivers. However, the VESA driver no longer functions after I >updated ports yesterday (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 "cannot read V_BIOS", neither device reports a bios >segment, etc). >>> >>> Is there something I can do to restore the VESA drivers to a >functioning state (or alternatively, any sort of development haswell >driver I can use), or is the only option to revert the ports directory >and rebuild everything? >> >> (Note: I do not have this problem and I can not help to solve it. I'm >> only interested in your problem and its solution because I'm thinking >to >> acquire a netbook with haswell and do need the VESA driver too in >this >> case). >> >> I've checked the SVN >> http://svnweb.freebsd.org/ports/head/UPDATING?view=log and the blog >> pointed to by the information in UPDATING >> >http://blogs.freebsdish.org/graphics/2014/11/19/xserver-1-14-update-ready/ >> I do not see any information about droping VESA support. > >The AIGLX default changed, though. Try > >Option "AIGLX" "Off" > >In the ServerLayout section. -- Sent from my Blackphone with K-9 Mail. Please excuse my brevity. From owner-freebsd-x11@FreeBSD.ORG Fri Dec 26 10:19:16 2014 Return-Path: <owner-freebsd-x11@FreeBSD.ORG> Delivered-To: x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A852B25E for <x11@FreeBSD.org>; Fri, 26 Dec 2014 10:19:16 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8FE64D6A for <x11@FreeBSD.org>; Fri, 26 Dec 2014 10:19:15 +0000 (UTC) Received: from AprilRyan.norad (dyndsl-037-138-232-119.ewe-ip-backbone.de [37.138.232.119]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 16E0888777 for <x11@FreeBSD.org>; Fri, 26 Dec 2014 11:12:12 +0100 (CET) Message-ID: <549D347C.7030305@freebsd.org> Date: Fri, 26 Dec 2014 11:12:12 +0100 From: Dominic Fandrey <kami@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: x11@FreeBSD.org Subject: graphics/dri missing dependency to multimedia/v4l_compat Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Fri, 26 Dec 2014 10:19:16 -0000 Updating DRI fails for me with: freebsd va_backend.h:33:10: fatal "error: 'linux/videodev2.h' file not found" Only after installing multimedia/v4l_compat did it compile. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1412242017140.78400>