recent i965 bugs

[Richard Goedeken]

Yesterday I did some more testing on my platform.  I disabled AIGLX just to see 
what would happen, and I did encounter the error: "upload_depthbuffer: Assertion 
`0' failed." when running glxgears.

I also made a discovery regarding the source of a previous unexplained event. 
Before a few days ago, I always saw the "Unable to initialize TTM buffer 
manager" message when running an OpenGL program.  Then at some point in my 
building/testing process, this message went away and a couple of other behaviors 
also changed.  I couldn't understand why - I rebuilt all the driver components 
from git snapshots of several different dates over the past 2 months, but still 
the 'new' behaviors persisted.

After I disabled AIGLX I figured out what happened.  With my Fedora distro, the 
i965_dri.so library is stored in '/usr/lib64/dri'.  This is where it is loaded 
for AIGLX, and this location is logged in the X.org log file.  I naturally 
assumed that this is the driver that was being used for OGL applications. 
However Mesa (libGL.so) loads the DRI driver after program start (so it doesn't 
show up if you do 'ldd /usr/lib64/libGL.so.1.2') and it expects it to be in a 
different place: /usr/X11R6/lib/modules/dri.

So my theory is that previously, the direct rendering opengl programs were 
always using the (old) /usr/X11R6 driver with the TTM bufmgr error.  After 
deleting that directory, the applications started using the (newer) driver in 
/usr/lib64/dri, and that's when the behaviors changed.

I haven't tried doing anything with Compiz in a few months - I figured that if I 
can't get normal OpenGL programs running flawlessly then there's no point in 
playing with Compiz.  It did sort-of work with the original Fedora 8 drivers, 
but it wasn't stable.

Richard


Timo Jyrinki wrote:
> 2008/1/17, Richard Goedeken <SirRichard at fascinationsoftware.com>:
>> You're welcome; I'm glad to help.  I tested the tip tonight and the alpha bug is
>> fixed for me, but unfortunately I still had to revert commit d9edd8e9.  I'm
>> pretty sure its faster for me now than it was a few weeks ago, even though I'm
>> still getting the 'unable to initialize TTM' message.  Keep up the good work.
> 
> Nice to find people who have the same problem as I have. See the
> rapidly-getting-bloated bug #14314 [1] for my problem which is now
> actually four problems... see mainly my last comment, the summary is
> currently misleading. Reverting the d9edd8e9 commit gets normal 3D
> applications to work on my GMA X3000, but I still have problems with
> at least compiz, and also the original problem if I disable
> AIGLX&Composite. Plus the TTM not working.
> 
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=14314
> 
> Could you try if you can get Compiz to work on your setup?
> 
> -Timo
> 
>