LinuxQuestions.org - libGL is out of sync with DRI

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - libGL is out of sync with DRI - no direct rendering ATI m9 (https://www.linuxquestions.org/questions/slackware-14/libgl-is-out-of-sync-with-dri-no-direct-rendering-ati-m9-354172/)

libGL is out of sync with DRI - no direct rendering ATI m9

Hi all

I'm trying to get direct rendering on my laptop to work. It uses an ATI M9 card. In my Xorg.0.log everything looks fine:

Code:

(II) RADEON(0): Direct rendering enabled

However, glxinfo reports:

Code:

direct rendering: No

I'm following the DRI troubleshooting at freedesktop.org:
dri.freedesktop.org/wiki/DriTroubleshooting
I found, per their instructions, that:

Code:

libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r200_dri.so

libGL error: dlopen /usr/X11R6/lib/modules/dri/r200_dri.so failed (/usr/X11R6/lib/modules/dri/r200_dri.so: undefined symbol: _glapi_get_dispatch)

libGL error: unable to find driver: r200_dri.so

The advice is that I install my drivers and libgl from sources. How do I go about this? Or is there an update available for Slackware (using packages from current instead of 10.1)?

- Any help appreciated, thanks in advance

I think it is part if Mesa... compile Mesa

Re: libGL is out of sync with DRI - no direct rendering ATI m9

Did you try the official DRI snapshot for the R200 ? You need to download the latest common-*.tar.bz2 and r200-*.tar.bz2 archives, then you should extract each archive and run its install.sh script. In case of trouble, you could restore overwritten X.Org's files by reinstalling x/*.tgz packages.

-- LiNuCe

Just some update on the 'progress'

shashir's advice was to compile MESA, but this didn't make a difference. To top this off, I followed http://dri.freedesktop.org/wiki/Building to build X from CVS. This pretty much made
starting X impossible, but I can't remember the specifics...I reinstalled slackware's own X again real fast.

I followed LiNuCe's suggestion and installed the two archives. Now, the driver correctly finds my external monitor so I have a lovely mergedfb, which I was also trying to get to work. However, the dri has become worse. Loading the dri module form xorg.conf now causes X not to start at all...

Code:

Symbol noXFree86DRIExtension from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved!



  *** If unresolved symbols were reported above, they might not

  *** be the reason for the server aborting.



Fatal server error:

Caught signal 11.  Server aborting

Commenting out the DRI parts makes the server start, but no direct rendering of course. There are no errors being reported, and only warnings when the driver is looking for the vrefreshrange of the monitor.

Disabling the mergedfb to only load one monitor doesn't solve anything.

I also installed the archive http://dri.freedesktop.org/snapshots...x.i386.tar.bz2 but this didn't
make a difference.

I'm taking a small break from this all, as I'm already happy that mergedfb works nicely and I have exams coming up. When I get around to it, I'll try all this again, because I might have messed up a few things installing all the packages.

Thanks for the advice so far!

I had problem after problem getting direct rendering going for my notebook's Radeon IGP320, and initially you made a comment about glxinfo telling you it was disabled, but the Xorg log saying it had been enabled -- there's a beautiful page that helped me on the DRI site, but at some point I had the silliest problem of direct rendering only being available for root. Have you tried putting at the end of your xorg config file:
Section "DRI"
Mode 0666
EndSection
Just a quick suggestion; may be useless, may fix it all up for you. Been awhile, but I'm pretty sure I get similar symptoms without that in my xorg.conf

Yes, I tried that.

I've installed gentoo on the laptop, thinking that if I get used to compiling from source to get all the little tricks and treats to work, that will help out, and I guess it did because it works like a charm now. Pity about losing Slackware though, guess I'm just too lazy to really look into it...