Date: Fri, 26 Dec 2014 17:07:30 +0100 From: Matthias Apitz <guru@unixarea.de> To: Warren Block <wblock@wonkity.com> Cc: freebsd-x11@freebsd.org Subject: Re: VESA X11 drivers non-functional after recent update Message-ID: <20141226160730.GA43649@unixarea.DDR.dd> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
El día Wednesday, December 24, 2014 a las 08:22:34PM -0700, Warren Block escribió: > > (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. In the context of the Acer C720/C710 (see the other thread) I have read in the block that one can run Xorg even without any xorg.conf configuration and it defaults fine to VESA (something which is required at the moment for the haswell chipset). 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. It just uses some default internal configuration, logged in /var/log/Xorg.0.log as: [ 32542.188] (==) Using default built-in configuration (30 lines) [ 32542.188] (==) --- Start of built-in configuration --- [ 32542.188] Section "Device" [ 32542.188] Identifier "Builtin Default intel Device 0" [ 32542.188] Driver "intel" [ 32542.188] EndSection [ 32542.188] Section "Screen" [ 32542.188] Identifier "Builtin Default intel Screen 0" [ 32542.189] Device "Builtin Default intel Device 0" [ 32542.189] EndSection [ 32542.189] Section "Device" [ 32542.189] Identifier "Builtin Default vesa Device 0" [ 32542.189] Driver "vesa" [ 32542.189] EndSection [ 32542.189] Section "Screen" [ 32542.189] Identifier "Builtin Default vesa Screen 0" [ 32542.189] Device "Builtin Default vesa Device 0" [ 32542.189] EndSection [ 32542.189] Section "Device" [ 32542.189] Identifier "Builtin Default fbdev Device 0" [ 32542.189] Driver "fbdev" [ 32542.189] EndSection [ 32542.189] Section "Screen" [ 32542.189] Identifier "Builtin Default fbdev Screen 0" [ 32542.189] Device "Builtin Default fbdev Device 0" [ 32542.189] EndSection [ 32542.189] Section "ServerLayout" [ 32542.189] Identifier "Builtin Default Layout" [ 32542.189] Screen "Builtin Default intel Screen 0" [ 32542.189] Screen "Builtin Default vesa Screen 0" [ 32542.190] Screen "Builtin Default fbdev Screen 0" [ 32542.190] EndSection [ 32542.190] (==) --- End of built-in configuration --- 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. HIH matthias -- Matthias Apitz, guru@unixarea.de, http://www.unixarea.de/ +49-170-4527211 1989-2014: The Wall was torn down so that we go to war together again. El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141226160730.GA43649>