VESA X11 drivers non-functional after recent update

[Eric McCorkle]

> On Dec 26, 2014, at 12:51, Warren Block <wblock at wonkity.com> wrote:
> 
>> On Fri, 26 Dec 2014, Matthias Apitz wrote:
>> 
>> 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.
>> 
> ...
>> 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:
> ...
>> 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.
> 
> 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:
> 
> 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 ran X successfully at some point between the firmware upgrade and upgrading ports (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 range 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 the water until the Haswell graphics support comes along...