Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Dec 2014 09:56:30 -0500
From:      Eric McCorkle <eric@metricspace.net>
To:        Warren Block <wblock@wonkity.com>
Cc:        "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>
Subject:   Re: VESA X11 drivers non-functional after recent update
Message-ID:  <E64DDBE1-821F-4219-A560-18CF65B1DD0C@metricspace.net>
In-Reply-To: <alpine.BSF.2.11.1412261047430.60313@wonkity.com>
References:  <F4B237B5-0400-4BD4-ADBB-1DC7F4E51E80@metricspace.net> <20141224222025.GA7968@unixarea.DDR.dd> <alpine.BSF.2.11.1412242017140.78400@wonkity.com> <20141226160730.GA43649@unixarea.DDR.dd> <alpine.BSF.2.11.1412261047430.60313@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Dec 26, 2014, at 12:51, Warren Block <wblock@wonkity.com> 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...=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E64DDBE1-821F-4219-A560-18CF65B1DD0C>