From: <te...@cr...> - 2001-05-04 00:55:52
|
Greg, thanks for the tips. I've looked over everything and here's a little more info. I noticed 'glxinfo' and 'gears -info' giving an undefined symbol error the other night but was unable to include it in the first post because I was mailing the message elsewhere. BTW, there was an error in the first post, I'm running Kernel 2.4.2 not 4.0.2 :P. Anyway, here's a little more on the pesky undefined symbol message: glxinfo: error while loading shared libraries: /usr/lib/libGL.so.1: undefined symbol: grSstControl I checked to insure that the libGL.so.1 was the correct lib (or at least tried to). It was a Debian 2.3 package named 'xlibmesa' 4.0.3-1 (which is the package for XF86 4.0 if i'm not mistaken?) Additionally, /var/log/XFree86.0.log listed Direct rendering on TDFX to be disabled, but nothing more that I could see significant. It's also odd how the TDFX module doesn't allow 32 bpp for this Voodoo 5. The choices are 8, 16, and 24. I read in the users guide that 16 bpp would be suppoted for acceleration. Although, the card is 32 bpp capable and should run. /dev/agpgart doesn't exsist so that may be a problem? I'm thinking I should just use CVS to get the full DRI source and just compile. Possibly the Debian packages are wrong? I noticed that tdfx , tdfx_dri, nor tdfx_drv are listed in the 'lsmod' output. Are they supposed to be loaded as soon as X is loaded or only when accelerated support is needed? It appears that X loads the tdfx module but it just isn't listed in the 'lsmod' output. I hope that is enough information for the problem. I'm going to play around with updating the libs a few more times. I appreciate all the help. Bryan A. Hughes in...@cr... On Thu, 03 May 2001 14:28:59 -0600 Greg Woods <gs...@sp...> wrote: > "Bryan A. Hughes" wrote: > >Voodoo 5 5500 (AGP) for 3D > > Acceleration in XF86. Unfortunately, DRI appears to be disabled > when X > > is started because bus mastering is off. > > Bus mastering is (I'm told) a PCI concept. If you are using an AGP > card, > it is a no-op. I too ran into this, including the lack of success > with > "setpci", but this wasn't the problem. In my case it turned out to > be > some old Mesa libraries that were still being linked to. What does > "gears -info" show? How about running "ldd" on one of your binaries > that > you think should be using DRI? Looking in /var/log/XFree*.log can > also > be enlightening. > > --Greg > > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/lists/listinfo/dri-users |