From: Chris S. <pen...@ya...> - 2001-02-28 03:18:59
|
Ok. I'm hoping I'm just missing something small here that someone might be able to point out to me... Running Kernel 2.4.1, XFree 4.0.2 Trying to get DRI running, went through the user guide/troubleshooting in full and got to the point that I could get "tdfx: direct rendering enabled" in my X log file, but when running glxinfo it was still using indirect, and UT in GL ran..well, it didn't really run.. So finally I had some time and did the full build of DRI from CVS, which went without a hitch. Kernel module was created. Followed the whole 'installing your new xserver' in the dri-compilation, and I'm now running the new DRI Xserver. I've made sure I'm using the freshly compiled tdfx kernel module. Everything looks proper. I'm right back where I started. glxinfo reports indirect, and my X log still states "direct rendering enabled". I have the DRI section in my XF86Config-4, so I know it's not a permissions issue. I'm going crazy! At this point my head is spinning from linux overload, so I'm not sure what I should include to best diagnose this problem. Rather than include everything, creating an extremely large email, I'll just leave it all out for now. Please help! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Darren P. <da...@fl...> - 2001-02-28 03:48:05
|
On Wednesday 28 February 2001 3:24 am, you wrote: > Ok. I'm hoping I'm just missing something small here that someone might > be able to point out to me... I was having similar problems. Have you tried turning LIBGL_DEBUG on? If you turn it on and then run glxinfo, it might give you some better idea of what is wrong. In my case it was a bad version of the glide library. You can get a version that works with DRI from the resource page http://dri.sourceforge.net/resources/resources.html (Thanks to Carlos Delgado for pointing that one out to me!) Hope this has been some help. Darren. > > Running Kernel 2.4.1, XFree 4.0.2 > > Trying to get DRI running, went through the user guide/troubleshooting > in full and got to the point that I could get "tdfx: direct rendering > enabled" in my X log file, but when running glxinfo it was still using > indirect, and UT in GL ran..well, it didn't really run.. > > So finally I had some time and did the full build of DRI from CVS, which > went without a hitch. Kernel module was created. Followed the whole > 'installing your new xserver' in the dri-compilation, and I'm now > running the new DRI Xserver. I've made sure I'm using the freshly > compiled tdfx kernel module. Everything looks proper. > > I'm right back where I started. glxinfo reports indirect, and my X log > still states "direct rendering enabled". I have the DRI section in my > XF86Config-4, so I know it's not a permissions issue. I'm going crazy! > > At this point my head is spinning from linux overload, so I'm not sure > what I should include to best diagnose this problem. Rather than > include everything, creating an extremely large email, I'll just leave > it all out for now. > > Please help! > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/lists/listinfo/dri-users |
From: Chris S. <pen...@ya...> - 2001-02-28 04:48:40
|
Ok. I set LIBGL_EXPORT=verbose And now when I run glxinfo i get: "libGL: trying /usr/X11R6/lib/modules/dri/tdfx_dri.so" twice. Still running indirect, still logging direct rendering enabled in my X log. I'm not sure why it's trying the modules from the X11R6 directory...after I compiled from CVS and enabled the new Xserver, I made sure to make the changes in my XF86Config to reference the new modules directory.... ?? Thanks! Chris Darren Poulson wrote: > On Wednesday 28 February 2001 3:24 am, you wrote: > >> Ok. I'm hoping I'm just missing something small here that someone might >> be able to point out to me... > > > I was having similar problems. Have you tried turning LIBGL_DEBUG on? > > If you turn it on and then run glxinfo, it might give you some better idea of > what is wrong. In my case it was a bad version of the glide library. You can > get a version that works with DRI from the resource page > > http://dri.sourceforge.net/resources/resources.html > > (Thanks to Carlos Delgado for pointing that one out to me!) > > Hope this has been some help. > > Darren. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Chris S. <pen...@ya...> - 2001-02-28 12:41:30
|
Yep, X11R6-DRI is listed at the top, X11R6 is second to last. And I made sure to run ldconfig after I changed this when switching X servers. I'd have no problem removing the previous X, as soon as I get this new one working properly (well, everything *is* working properly I suppose, except DRI.. =) Is there any other place I can look for errors? I know that tdfx_dri.so exists under the X11R6-DRI directory tree - why would it be trying for the old one? Chris Forge wrote: > Look to /etc/ld.so.conf and make sure /usr/X11R6-DRI/ is listed *before* > /usr/X11R6/. I just wipe out X and run the DRI version out of /usr/X11R6/, > which I'd thouroughly recommend, once you have a (reasonably) working DRI > setup. > > Rich 'Forge' Mingin > Open Source Advocate _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: James D S. <jst...@ro...> - 2001-02-28 14:30:25
|
I have an ati rage128 pro card, and am not sure I can be of much help since you have a different card. However, when I installed in /usr/X11R6-DRI and adjusted /etc/ld.so.conf and ran ldconfig, I noticed unexpected behavior. The libGL sym links in /usr/lib ended up pointing back to the wrong library (the non-DRI version), rather than the new one that was created for DRI. Perhaps something similar happened to you. To solve it, I moved the libGL libraries out of /usr/lib (and all the paths in /etc/ld.so.conf) and put them somewhere else until I knew everything was working (once everything is working, you could just delete them). You might also make sure the the Mesa libraries are not there, and if they are, move them too and have sym links to libGL in place of the actual libraries. This is what worked for me, maybe you can apply it to your 3dfx situation. Hope this helps, James |
From: Jules B. <ju...@je...> - 2001-02-28 14:38:18
|
On Wed, Feb 28, 2001 at 09:31:40AM -0500, James D Strandboge wrote: > I have an ati rage128 pro card, and am not sure I can be of much help > since you have a different card. However, when I installed in > /usr/X11R6-DRI and adjusted /etc/ld.so.conf and ran ldconfig, I noticed > unexpected behavior. The libGL sym links in /usr/lib ended up pointing > back to the wrong library (the non-DRI version), rather than the new one That's right, good point. The debian (possibly others too) version will always prioritise the one in /usr/lib. You either have to move it out the way, or copy the new ones into /usr/lib. Jules |