Thread: Re: [tuxracer-main] 3Dfx Voodoo 2 with Tuxracer Question
Status: Beta
Brought to you by:
jfpatry
From: Michael P. <MPE...@pr...> - 2000-04-21 18:08:31
|
-----Original Message----- From: Steve Baker <sjb...@ai...> To: tux...@li... <tux...@li...> Date: Friday, April 21, 2000 10:44 AM Subject: Re: [tuxracer-main] 3Dfx Voodoo 2 with Tuxracer Question >> Michael Petnuch wrote: > >> Voodoo 2 - 12 mb > >> I have installed Mesa 3.1 from the source using ./configure, make, make strip, make intall, make check. > >OK - but did you make it in the manner specified for Voodoo-2? I havn't >built Mesa for Voodoo in a long while - but IIRC, you needed some kind of >special argument to ./configure ... but I forget. > >If you did then this should run the 'gears' demo in fullscreen mode: > > cd gdemos > su > setenv MESA_GLX_FX f > ./gears (hit ESC to exit) > >> Everything compiles fine with I am guessing support for my harware but this dosent seem to be the case! > >I don't think the configure script auto-detects what kind of hardware you have. > >> Ok after that I dowloaded the source of tuxracer data and the main. >> Compiled moved the data to where it needed to be and ran. It loaded >> up in a window and ran incredible slow, around 1.234 fps. > >Software rendering - obviously. :-( > >> So then I tried the the RPMS, but got the same results. >> Then I was reading somewhere to put this in bash_profile >> exprot MESA_GLX_FX=fullscreen > ^^^^^^ > I hope you actually typed 'export'! > >It's almost certainly a problem in your Mesa build. There are a couple >of possibilities: > >1) You have Mesa pre-installed by RedHat in some other directory which > is overriding the one you built for yourself. > > Do this: > > find . -name lib\*GL.so\* -print > > ...and email us back what you see. Better still, do an 'ls -l' for > each file it finds and email that too. > > >2) You compiled Mesa with the wrong options for 3Dfx - I don't know > exactly what the right options are - but I'm pretty sure the > default options are not right. > > >-- >Steve Baker http://web2.airmail.net/sjbaker1 >sjb...@ai... (home) http://www.woodsoup.org/~sbaker >sj...@ht... (work) > >_______________________________________________ >tuxracer-main mailing list >tux...@li... >http://lists.sourceforge.net/mailman/listinfo/tuxracer-main Printout for find. -name lib\*GL.so\* -print followed by the symbolic links for each: ./usr/lib/libGL.so -> libGL.so.1 ./usr/lib/libGl.so.1 -> libGl.so.1.2.030100 ./usr/lib/lbGL.so.1.2.030100 ./usr/X11R6/lib/libGL.so -> libGl.so.1.2.0 ./usr/X11R6/lib/libGL.so.1 -> libGL.so.1.2.0 ./usr/X11R6/lib/libGL.so.1.2.0 ./usr/local/lib/libGL.so.1.2.0 ./usr/local/lib/libGL.so.1 -> libGL.1.2.0 ./usr/local/lib/libGL.so -> libGL.1.2.0 ./usr/local/lib/libGL.so.1.2.030100 ./usr/local/lib/libMesaGL.so -> libGL.so ./root/Mesa-3.1/src/.libs/libGL.so.1.2.0 ./root/Mesa-3.1/src/.libs/libGL.so.1 -> libGL.so.1.2.0 ./root/Mesa-3.1/src/.libs/libGL.so -> libGL.so.1.2.0 ./root/Mesa-3.1/lib/libGL.so -> libGL.so.1 ./root/Mesa-3.1/lib/libGL.so.1 -> libGL.so.1.2.030100 ./root/Mesa-3.1/lib/libGL.so.1.2.030100 BTW I did type export not exprot in my .bash_profile |
From: Michael P. <MPE...@pr...> - 2000-04-21 20:57:55
|
-----Original Message----- From: Jasmin Patry <jf...@mu...> To: tux...@li... <tux...@li...> Date: Friday, April 21, 2000 3:13 PM Subject: Re: [tuxracer-main] 3Dfx Voodoo 2 with Tuxracer Question >On Fri, Apr 21, 2000 at 09:45:36AM -0500, Steve Baker wrote: >> > Michael Petnuch wrote: >> >> > Voodoo 2 - 12 mb >> >> > I have installed Mesa 3.1 from the source using ./configure, make, make strip, make intall, make check. >> >> OK - but did you make it in the manner specified for Voodoo-2? I havn't >> built Mesa for Voodoo in a long while - but IIRC, you needed some kind of >> special argument to ./configure ... but I forget. > >Yes, you definitely need to compile it specifically for your Voodoo >card. Before they switched to configure, you needed to do >'make linux-glide' or one of its variants. Check the docs. > >By default, Mesa will build with software rendering only. (configure can't >detect that you have a Voodoo card AFAIK.) > >HTH, >Jasmin > >-- >Jasmin Patry Master's Student, Dept. of Computer Science >jf...@cg... http://www.cgl.uwaterloo.ca/~jfpatry/ > > >_______________________________________________ >tuxracer-main mailing list >tux...@li... >http://lists.sourceforge.net/mailman/listinfo/tuxracer-main I recomplied Mesa and this time preformed make linux-glide as it said in the 3Dfx doc. Of course it still didn't work but i figured to try the demos once again and I noticed a little ting before the software rendered demo would come up. It said the MESA_GLX_FX=disable Well I said that dosent seem to be right so I tried export MESA_GLX_FX=enable ran the demos and of course I was greated by my 3Dfx logo and a fully harware enabled demos. Now I have to try tuxracer but it should work :-) Thank all of you! |
From: Evan R. <er...@ne...> - 2000-04-21 22:45:32
|
Hey all. I compiled the Utah GLX software against Mesa 3.1 source. I had actually already installed Mesa (I didn't read the Utah instructions properly - I couldn't, after reading them see a probelm with this). I added the items listed in the README to my XF86Config and also some instruction pertaining to Mach 64 there too. According to the README: The module entry should look like this: Section "Module" < possible other modules > Load "glx.so" EndSection The Rage Pro device section should look like this: Section "Device" Identifier "ATI|3D Rage Pro AGP 1X/2X" < other options > Option "no_font_cache" Option "no_pixmap_cache" EndSection This is what mine looklike: I added this (didn't have a module section before): Section "Module" Load "glx.so" EndSection And changed my device to this: # Device setup for OpenGL Section "Device" Identifier "ATI|3D Rage Pro AGP 1X/2X" Option "no_font_cache" Option "no_pixmap_cache" EndSection # Device configured by Xconfigurator: # Section "Device" # Identifier "ATY Mach64" # VendorName "Unknown" # BoardName "Unknown" # #VideoRam 6287 # # Insert Clocks lines here if appropriate # EndSection (you will see that I commented out the old one). Obviously I am still on software rendering because I get 0.0 FPS ;) I figure this must have something to do with the file. I tried the defaults from the glx.conf file (left it unedited) but was slow as all hell. So I then edited the crap out of it and uncommented option they reckoned would maximise performance. Still 0.0 FPS ;) I tried something that I saw on the list, that is EXPORT MESA_GLX_FX=enable but to no avail (thought it seems slightly faster, I am sure I am imagining it. Still very unplayable). Anyone around here with Utah GLX experience? As far as I know, that is how I get my Rage Pro in my iMac 233 to support 3D Accelleration. Utah install instructions didn't seem to mention any chip-specific instructions. Thanks Evan |
From: Jasmin P. <jf...@mu...> - 2000-04-21 23:11:37
|
On Sat, Apr 22, 2000 at 10:38:24AM +1200, Evan Read wrote: > > Hey all. > > I compiled the Utah GLX software against Mesa 3.1 source. I had actually > already installed Mesa (I didn't read the Utah instructions properly - I > couldn't, after reading them see a probelm with this). > > I added the items listed in the README to my XF86Config and also some > instruction pertaining to Mach 64 there too. According to the README: [snip] > > Obviously I am still on software rendering because I get 0.0 FPS ;) I > figure this must have something to do with the file. I tried the > defaults from the glx.conf file (left it unedited) but was slow as all > hell. So I then edited the crap out of it and uncommented option they > reckoned would maximise performance. Still 0.0 FPS ;) > > I tried something that I saw on the list, that is EXPORT > MESA_GLX_FX=enable but to no avail (thought it seems slightly faster, I am > sure I am imagining it. Still very unplayable). That environment variable is only used with 3dfx cards (hence the _FX). > Anyone around here with Utah GLX experience? As far as I know, that is > how I get my Rage Pro in my iMac 233 to support 3D Accelleration. Utah > install instructions didn't seem to mention any chip-specific > instructions. I haven't used Utah GLX (I have a Voodoo3). Have you tried the Mesa demos, or any other OpenGL software? Does the Rage Pro have direct rendering drivers? (A quick look at the utah-glx page seems to indicate that only the Matrox cards have direct rendering drivers at the moment). Indirect rendering is much, much slower than direct rendering (every OpenGL call must pass through the X server); if I run 'tuxracer -indirect' I get about 3-4 fps. Sorry that I can't be of more help. If you get better results, please let us know. Cheers, Jasmin -- Jasmin Patry Master's Student, Dept. of Computer Science jf...@cg... http://www.cgl.uwaterloo.ca/~jfpatry/ |
From: Steve B. <sjb...@ai...> - 2000-04-21 23:44:44
|
Evan Read wrote: > I tried something that I saw on the list, that is EXPORT > MESA_GLX_FX=enable but to no avail (thought it seems slightly faster, I am > sure I am imagining it. Still very unplayable). You are certainly imagining it - the 'FX' in MESA_GLX_FX is for '3DFX'... and it certainly won't change anything for a non-3Dfx card or for software rendering. > Anyone around here with Utah GLX experience? It's all pretty new - you *REALLY* need to take this over to the Utah GLX mailing list - which you can reach by going to http://sourceforge.net and searching for 'UTAH'. -- Steve Baker http://web2.airmail.net/sjbaker1 sjb...@ai... (home) http://www.woodsoup.org/~sbaker sj...@ht... (work) |
From: Steve B. <sjb...@ai...> - 2000-04-21 23:44:36
|
Michael Petnuch wrote: > Printout for find. -name lib\*GL.so\* -print followed by the symbolic links > for each: > > ./usr/lib/libGL.so -> libGL.so.1 > ./usr/lib/libGl.so.1 -> libGl.so.1.2.030100 > ./usr/lib/lbGL.so.1.2.030100 > ./usr/X11R6/lib/libGL.so -> libGl.so.1.2.0 > ./usr/X11R6/lib/libGL.so.1 -> libGL.so.1.2.0 > ./usr/X11R6/lib/libGL.so.1.2.0 > ./usr/local/lib/libGL.so.1.2.0 > ./usr/local/lib/libGL.so.1 -> libGL.1.2.0 > ./usr/local/lib/libGL.so -> libGL.1.2.0 > ./usr/local/lib/libGL.so.1.2.030100 > ./usr/local/lib/libMesaGL.so -> libGL.so > ./root/Mesa-3.1/src/.libs/libGL.so.1.2.0 > ./root/Mesa-3.1/src/.libs/libGL.so.1 -> libGL.so.1.2.0 > ./root/Mesa-3.1/src/.libs/libGL.so -> libGL.so.1.2.0 > ./root/Mesa-3.1/lib/libGL.so -> libGL.so.1 > ./root/Mesa-3.1/lib/libGL.so.1 -> libGL.so.1.2.030100 > ./root/Mesa-3.1/lib/libGL.so.1.2.030100 > > BTW I did type export not exprot in my .bash_profile YIKES! It looks like you have at least three copies of Mesa *installed* and another sitting in your build directory!! ...then you said... > I recomplied Mesa and this time preformed make linux-glide as it said in the > 3Dfx doc. Of course it still didn't work but i figured to try the demos > once again and I noticed a little ting before the software rendered demo > would come up. It said the MESA_GLX_FX=disable > Well I said that dosent seem to be right so I tried export > MESA_GLX_FX=enable > ran the demos and of course I was greated by my 3Dfx logo and a fully > harware enabled demos. Now I have to try tuxracer but it should work :-) Well, this may have worked for the demo's and might work OK for TuxRacer, but with all those other Mesa libraries floating around on your hard drive, you are likely to find problems with other OpenGL programs picking up the wrong Mesa version. I suggest you remove *ALL* of those libGL* and libMesaGL* files to avoid confusion. Then recompile in the way that finally got you hardware accelleration. Finally, create symbolic links from where ever Mesa finally installed itself to: /usr/lib/libGL.so /usr/lib/libGLU.so Those are the 'canonical' places for OpenGL to be installed. -- Steve Baker http://web2.airmail.net/sjbaker1 sjb...@ai... (home) http://www.woodsoup.org/~sbaker sj...@ht... (work) |