From owner-freebsd-x11@FreeBSD.ORG Sat Dec 27 14:56:37 2014 Return-Path: Delivered-To: freebsd-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 2B4F6438 for ; Sat, 27 Dec 2014 14:56:37 +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 E6BECBC0 for ; Sat, 27 Dec 2014 14:56:36 +0000 (UTC) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (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 B69221F7A; Sat, 27 Dec 2014 14:56:29 +0000 (UTC) References: <20141224222025.GA7968@unixarea.DDR.dd> <20141226160730.GA43649@unixarea.DDR.dd> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPad Mail (11B511) From: Eric McCorkle Subject: Re: VESA X11 drivers non-functional after recent update Date: Sat, 27 Dec 2014 09:56:30 -0500 To: Warren Block 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2014 14:56:37 -0000 > On Dec 26, 2014, at 12:51, Warren Block wrote: >=20 >> On Fri, 26 Dec 2014, Matthias Apitz wrote: >>=20 >> El d=C3=ADa Wednesday, December 24, 2014 a las 08:22:34PM -0700, Warren B= lock escribi=C3=B3: >>=20 >>>> (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 t= o >>>> acquire a netbook with haswell and do need the VESA driver too in this >>>> case). >>>>=20 >>>> I've checked the SVN >>>> http://svnweb.freebsd.org/ports/head/UPDATING?view=3Dlog and the blog >>>> pointed to by the information in UPDATING >>>> http://blogs.freebsdish.org/graphics/2014/11/19/xserver-1-14-update-rea= dy/ >>>> I do not see any information about droping VESA support. >>>=20 >>> The AIGLX default changed, though. Try >>>=20 >>> Option "AIGLX" "Off" >>>=20 >>> In the ServerLayout section. >>=20 > ... >> On my Acer Aspire D250 I was >> curious and just removed (renamed) the xorg.conf and it works fine too, >> i.e. it does not use the Intel driver, but VESA. As well the mouse works >> as expected. More, I do not even note a difference between running the >> Xorg with Intel ./. VESA. Interesting. >>=20 >> It just uses some default internal configuration, logged in >> /var/log/Xorg.0.log as: > ... >> Re/ your Option: One could construct from the lines above the 'internal' >> config as a file /etc/X11/xorg.conf and insert this special Option. >=20 > Even that much is not necessary. xorg.conf only needs to contain the non-= default values. So to disable AIGLX, the entire xorg.conf needs only: >=20 > Section "ServerLayout" > Option "AIGLX" "Off" > EndSection Bad news I'm afraid. The reversion didn't seem to work. Worth mentioning: I had upgraded my firmware, though I could have sworn I ra= n X successfully at some point between the firmware upgrade and upgrading po= rts (after which the problem appeared) Looking at the Xorg.0.log file, both video devices seem to have "BIOS @ ????= ????/65536", so perhaps the firmware upgrade is somehow screwing up bios ran= ge detection? SC pixel mode seems to work fine, though. Also, without an xorg.conf file, a warning "primary device is not PCI" shows= up, and the VESA drive fails to detect any devices. I really hope it's not the firmware like I suspect, otherwise I'm dead in th= e water until the Haswell graphics support comes along...=