[Dri-devel] Mach64 driver on Compaq Armada M300
First of all, congratulations for the new drivers for ATI Mach64 and for the support of more and more video cards, even older ones... Still, I could not successfully use DRM and 3D acceleration on my AGP-disabled 4MB Mach64 card, using the Debian-package xserver-xfree86-dri-mach64. Even in the 16bit 640*480 and 16bit 800*600 modes, the only ones that fit in the cards tiny memory, I got the following PCI setbus error : (II) ATI(0): [drm] SAREA 2200+1208: 3408 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmGetBusid returned '' (II) ATI(0): [drm] drmSetBusid failed (7, PCI:0:5:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed I don't know enough about PCI to conclude... but I hope there is a cure! Here is an extract of my PCI bus info (Compaq Armada M300): 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) 00:04.0 CardBus bridge: Texas Instruments PCI1211 00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro (rev dc) 00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) Thanks for your help. Sincerely, Albert Cohen -- Albert Cohenhttp://www-rocq.inria.fr/~acohen INRIA Rocquencourt, BP 105, 78153 Le Chesnay, France --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver on Compaq Armada M300
On Mit, 2003-02-05 at 17:50, Albert Cohen wrote: (II) ATI(0): [drm] drmSetBusid failed (7, PCI:0:5:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed This has been discussed several times here: you need to make sure the DRM is built with the same compiler as the kernel. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Mach64 driver performance
I just did an informal real world benchmark on the Mach64 driver 20020704. Bzflag runs fine without any texturing, but with all other options except smoothing. That one knocked performance down horribly, too. In relatively simple worlds with all but the two mentioned settings at max, I was getting 17-18 FPS. Knock quality down and I got 22. Is texturing and smoothing slow because it's implemented in software or because I have too little memory left over for textures? I've got 8M of video memory and I'm running at 1024x768x16. As is, it's playable. :) Thanks. :) Cheers, David --- This sf.net email is sponsored by:ThinkGeek We have stuff for geeks like you. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver performance
On Sun, 7 Jul 2002, David Willmore wrote: I just did an informal real world benchmark on the Mach64 driver 20020704. Bzflag runs fine without any texturing, but with all other options except smoothing. That one knocked performance down horribly, too. In relatively simple worlds with all but the two mentioned settings at max, I was getting 17-18 FPS. Knock quality down and I got 22. Is texturing and smoothing slow because it's implemented in software or because I have too little memory left over for textures? I've got 8M of video memory and I'm running at 1024x768x16. Any anti-aliasing (point, line, or polygon) causes software fallback. Some texture environments like GL_BLEND are also software fallbacks (not to be confused with alpha blending with the framebuffer). I have the same amount of mem and use the same resolution as you. Memory shouldn't be a problem unless the texture demands of the app are very large. If textures cause massive slowdown, then the app is probably using a texture environment that's a fallback. Often in that case, there will be a slowdown only in certain areas of the world where the fallback textures are visible, or when certain transparency effects are used. At some point I could try to put all this down in a little chart of what works and doesn't work and what is done in software for mach64. -- Leif Delgass http://www.retinalburn.net --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver performance
On Mon, 8 Jul 2002, Leif Delgass wrote: On Sun, 7 Jul 2002, David Willmore wrote: I just did an informal real world benchmark on the Mach64 driver 20020704. Bzflag runs fine without any texturing, but with all other options except smoothing. That one knocked performance down horribly, too. In relatively simple worlds with all but the two mentioned settings at max, I was getting 17-18 FPS. Knock quality down and I got 22. Is texturing and smoothing slow because it's implemented in software or because I have too little memory left over for textures? I've got 8M of video memory and I'm running at 1024x768x16. Any anti-aliasing (point, line, or polygon) causes software fallback. Some texture environments like GL_BLEND are also software fallbacks (not to be confused with alpha blending with the framebuffer). I have the same amount of mem and use the same resolution as you. Memory shouldn't be a problem unless the texture demands of the app are very large. I should clarify: the texture mem available is currently determined by the max resolution configured and the AGP size (if it's an AGP card, of course), but you'll get better framerates by setting games to use a resolution lower than 1024x768. I tend to stick to 640x480 or maybe 800x600 for games, but my desktop is 1024x768. If textures cause massive slowdown, then the app is probably using a texture environment that's a fallback. Often in that case, there will be a slowdown only in certain areas of the world where the fallback textures are visible, or when certain transparency effects are used. At some point I could try to put all this down in a little chart of what works and doesn't work and what is done in software for mach64. -- Leif Delgass http://www.retinalburn.net --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
Any info (or references to documents in XFree tree) would be highly appreciated... Finally, I managed to get and build (and even run) mach64 branch. Thanks to everyone who helped me. Now I use not Jose's binaries but the ones built on my own system. Nothing has changed (what a surprize!:) on my desktop: - 3D works faster than usual - No fog in the tunnel demoapp. - Textures have major problems (for example, on celestia) - 2D works rather slow (comparing to ATI drivers by V. Dergachev) :((( But I noticed the tree is not updating for weeks (the last file is dated 28.10). It seems, the development stopped again... :) :( Cheers, Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On 2001.12.10 23:17 Sergey V. Udaltsov wrote: Try the tunnel demo. For me it went from 0.7fps to 25fps. For me, numbers are similar. Though, there are problems with fog: tunnel cannot turn it on (in fact, nothing happens on f - the fog is always off). For pre-pre-pre-alpha, this is not crucual though... Just one question to gurus: I'm no guru, but this is what I've know from a thread in this list at the time I was also trying to build the mach64 branch myself, about a month ago. Suppose, I took mach64-0-0-2-bramch tag. Are these actions correct: 1. Set in config/cf/site.def #define ProjectRoot /usr/X11R6-DRI 2. Do make World 3. Do make install Is it everything I need? How I can ask compiler use existing XFree headers and libraries? How I can build the kernel modules? Not really. Before you 'make install' you must make a mirror with symbolic link of your existing /usr/X11R6 to /usr/X11R6-DRI using the 'lndir' command for that: mkdir /usr/X11R6-DRI lndir /usr/X11R6 /usr/X11R6-DRI Setting the ProjectRoot in /usr/X11R6-DRI isn't even necessary since is the default already. If you have RedHat 7.x you also have to add the patch that is attached because of a problem in the gcc-2.96 code optimization leading to modules that can't be loaded by the X server. The kernel modules are built and installed at the same time. Any info (or references to documents in XFree tree) would be highly appreciated... Sorry, I was so dumb I could not find the answers at dri.sourceforge.net. Unfortunatly the only reference is the DRI Compilation Guide which has not been updated recently to include this. Someone really should do that because there has been a lot of people trying to test the cvs tree (especially the mach64 branch). Cheers, Sergey Regards, Jose Fonseca *** xc.old/xc/config/cf/host.def Tue Dec 4 17:14:35 2001 --- xc/xc/config/cf/host.def Tue Dec 4 17:15:45 2001 *** *** 16,19 --- 16,24 #endif + #define NeedModuleRanlib YES + #define ModuleCFlags $(CDEBUGFLAGS) $(CCOPTIONS) -fno-merge-constants \ + $(THREAD_CFLAGS) $(ALLDEFINES) + #define ModuleRanlibCmd RanlibCmd + #define BuildXFree86ConfigTools NO
Re: [Dri-devel] Mach64 driver
mkdir /usr/X11R6-DRI lndir /usr/X11R6 /usr/X11R6-DRI It's already done, thanks to binaries you gave me:) Setting the ProjectRoot in /usr/X11R6-DRI isn't even necessary since is the default already. Really? In which file? site.def contains ProjectRoot /usr/X11R6 but host.def contains /usr/X11R6-DRI. Which one is really used? If you have RedHat 7.x you also have to add the patch that is attached because of a problem in the gcc-2.96 code optimization leading to modules that can't be loaded by the X server. Thanks. Unfortunatly the only reference is the DRI Compilation Guide which has not been updated recently to include this. Someone really should do that because there has been a lot of people trying to test the cvs tree (especially the mach64 branch). Probably I'll be able to write little 10 lines HOWTO and post it here. When I finish the process...:) Cheers, Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On Tue, 2001-12-11 at 10:54, Michael Thaler wrote: On Mon, Dec 10, 2001 at 03:09:35PM +, Jose Fonseca wrote: I don't know what particular version of XFree 4.10 you have used but you must also install the X server from the mach64 build tree. The usual way is to 'lndir' your /usr/X11R6/ dir to /usr/X11R6-DRI/ and then 'make install'. This way you avoid file duplication. O.K. I tried to compile it and got a lot of errors. What I did was: mkdir DRI-CVS cd DRI-CVS/ cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co xc cd xc cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri update -P -d -r mach64-0-0-2-branch I don't know much about cvs but usually I just do: cvs -z3 [EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I don't know if updating a branch after checking out the trunk you get everything all right. Perhaps some one in the list could enlighten this... ln -s xc XFree40 mkdir build cd build lndir -silent -ignorelinks ../XFree40 cd ~/DRI-CVS/build/xc/ make World World.LOG I think I did everything like described in the compilation guide but I go a lot of errors. It seems I do something terribly wrong. I got the following errors: /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status You should have included the command that generated this error. Anyway something wrong must have happened before when building Xext. The rest of the errors are the consequence of this one... + rm -f libGL.so.1 + ln -s libGL.so.1.2 libGL.so.1 + rm -f ../../../exports/lib/libGL.so.1 + cd ../../../exports/lib + ln -s ../../lib/GL/GL/libGL.so.1 . rm -f libGL.so.1.2 mv -f libGL.so.1.2~ libGL.so.1.2 mv: cannot stat `libGL.so.1.2~': No such file or directory make[5]: *** [libGL.so.1.2] Error 1 make[5]: Target `all' not remade because of errors. make[5]: Leaving directory `/home/michi/DRI-CVS/build/xc/lib/GL/GL' making all in lib/GL/mesa/src/OSmesa... /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status + rm -f libOSMesa.so.3 + ln -s libOSMesa.so.3.3 libOSMesa.so.3 + rm -f ../../../../../exports/lib/libOSMesa.so.3 + cd ../../../../../exports/lib + ln -s ../../lib/GL/mesa/src/OSmesa/libOSMesa.so.3 . rm -f libOSMesa.so.3.3 mv -f libOSMesa.so.3.3~ libOSMesa.so.3.3 mv: cannot stat `libOSMesa.so.3.3~': No such file or directory make[5]: *** [libOSMesa.so.3.3] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status + rm -f libOSMesa.so.3 + ln -s libOSMesa.so.3.3 libOSMesa.so.3 + rm -f ../../../../../exports/lib/libOSMesa.so.3 + cd ../../../../../exports/lib + ln -s ../../lib/GL/mesa/src/OSmesa/libOSMesa.so.3 . rm -f libOSMesa.so.3.3 mv -f libOSMesa.so.3.3~ libOSMesa.so.3.3 mv: cannot stat `libOSMesa.so.3.3~': No such file or directory make[5]: *** [libOSMesa.so.3.3] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [gamma_dri.so] Error 1 make[6]: Target `all' not remade because of errors. make[6]: Target `all' not remade because of errors. make[6]: Leaving directory `/home/michi/DRI-CVS/build/xc/lib/GL/mesa/src/drv/gamma' /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [mach64_dri.so] Error 1 usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [mga_dri.so] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [i810_dri.so] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [r128_dri.so] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [radeon_dri.so] Error 1 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[6]: *** [sis_dri.so] Error 1 Yesterday I build everything from the mach64-0-0-1-branch and I did not get this errors. Anyone has a hint what I am doing wrong here? Have I forgot something? You forgot to CC the dri-devel ML. :) Greetings, Michael Regards, Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On Tue, 2001-12-11 at 10:45, Sergey V. Udaltsov wrote: mkdir /usr/X11R6-DRI lndir /usr/X11R6 /usr/X11R6-DRI It's already done, thanks to binaries you gave me:) Setting the ProjectRoot in /usr/X11R6-DRI isn't even necessary since is the default already. Really? In which file? site.def contains ProjectRoot /usr/X11R6 but host.def contains /usr/X11R6-DRI. Which one is really used? host.def has precedence. It's included before the conditional definition of ProjectRoot in site.def If you have RedHat 7.x you also have to add the patch that is attached because of a problem in the gcc-2.96 code optimization leading to modules that can't be loaded by the X server. Thanks. Unfortunatly the only reference is the DRI Compilation Guide which has not been updated recently to include this. Someone really should do that because there has been a lot of people trying to test the cvs tree (especially the mach64 branch). Probably I'll be able to write little 10 lines HOWTO and post it here. When I finish the process...:) Cheers, Sergey Regards, Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On Tue, Dec 11, 2001 at 11:52:59AM +, Jose Fonseca wrote: cvs -z3 [EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I don't have a login so I can only download as an anonymous user. I followed the instructions of the compilation guide but I am not familiar with CVS so maybe something went wrong. I don't know if updating a branch after checking out the trunk you get everything all right. Perhaps some one in the list could enlighten this... I am not sure, either. The command provided by the CVS webpage on dri.sourceforge.net did not work. I had to change the order of the options. Maybe this is wrong. You should have included the command that generated this error. Anyway something wrong must have happened before when building Xext. The rest of the errors are the consequence of this one... Sorry, you are right. make[5]: Entering directory `/home/michi/DRI-CVS/build/xc/lib/GL/GL' rm -f libGL.so.1.2~ + cd . + gcc -o ./libGL.so.1.2~ -shared -Wl,-soname,libGL.so.1 ../../../lib/GL/glx/clientattrib.o ../../../lib/GL/glx/compsize.o ../../../lib/GL/glx/dispatch.o ../../../lib/GL/glx/eval.o ../../../lib/GL/glx/glapinoop.o ../../../lib/GL/glx/glapi.o ../../../lib/GL/glx/glapi_x86.o ../../../lib/GL/glx/glthread.o ../../../lib/GL/glx/glxcmds.o ../../../lib/GL/glx/glxext.o ../../../lib/GL/glx/g_render.o ../../../lib/GL/glx/g_single.o ../../../lib/GL/glx/g_vendpriv.o ../../../lib/GL/glx/indirect_init.o ../../../lib/GL/glx/pixel.o ../../../lib/GL/glx/pixelstore.o ../../../lib/GL/glx/render2.o ../../../lib/GL/glx/renderpix.o ../../../lib/GL/glx/single2.o ../../../lib/GL/glx/singlepix.o ../../../lib/GL/glx/vertarr.o ../../../lib/GL/glx/xfont.o ../../../lib/GL/dri/XF86dri.o ../../../lib/GL/dri/dri_glx.o -lpthread -L../../../exports/lib -L/usr/X11R6-DRI/lib -lXext -lX11 -ldl -lc /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status + rm -f libGL.so.1 + ln -s libGL.so.1.2 libGL.so.1 + rm -f ../../../exports/lib/libGL.so.1 + cd ../../../exports/lib + ln -s ../../lib/GL/GL/libGL.so.1 . rm -f libGL.so.1.2 mv -f libGL.so.1.2~ libGL.so.1.2 mv: cannot stat `libGL.so.1.2~': No such file or directory make[5]: *** [libGL.so.1.2] Error 1 You forgot to CC the dri-devel ML. :) Already done;-) It would be nice if someone writes a little guide how to compile the Mach64 drivers. As soon as I get it working myself I will write a litte doc how I have done it. But I am not an expert in these things;-) Thanks, Michael ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On Tue, 2001-12-11 at 12:14, Michael Thaler wrote: On Tue, Dec 11, 2001 at 11:52:59AM +, Jose Fonseca wrote: cvs -z3 [EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I don't have a login so I can only download as an anonymous user. I followed the instructions of the compilation guide but I am not familiar with CVS so maybe something went wrong. Me neither. That's not a problem, just login as anonymous: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login Press enter for password and then cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I don't know if updating a branch after checking out the trunk you get everything all right. Perhaps some one in the list could enlighten this... I am not sure, either. The command provided by the CVS webpage on dri.sourceforge.net did not work. I had to change the order of the options. Maybe this is wrong. You should have included the command that generated this error. Anyway something wrong must have happened before when building Xext. The rest of the errors are the consequence of this one... Sorry, you are right. make[5]: Entering directory `/home/michi/DRI-CVS/build/xc/lib/GL/GL' rm -f libGL.so.1.2~ + cd . + gcc -o ./libGL.so.1.2~ -shared -Wl,-soname,libGL.so.1 ../../../lib/GL/glx/clientattrib.o ../../../lib/GL/glx/compsize.o ../../../lib/GL/glx/dispatch.o ../../../lib/GL/glx/eval.o ../../../lib/GL/glx/glapinoop.o ../../../lib/GL/glx/glapi.o ../../../lib/GL/glx/glapi_x86.o ../../../lib/GL/glx/glthread.o ../../../lib/GL/glx/glxcmds.o ../../../lib/GL/glx/glxext.o ../../../lib/GL/glx/g_render.o ../../../lib/GL/glx/g_single.o ../../../lib/GL/glx/g_vendpriv.o ../../../lib/GL/glx/indirect_init.o ../../../lib/GL/glx/pixel.o ../../../lib/GL/glx/pixelstore.o ../../../lib/GL/glx/render2.o ../../../lib/GL/glx/renderpix.o ../../../lib/GL/glx/single2.o ../../../lib/GL/glx/singlepix.o ../../../lib/GL/glx/vertarr.o ../../../lib/GL/glx/xfont.o ../../../lib/GL/dri/XF86dri.o ../../../lib/GL/dri/dri_glx.o -lpthread -L../../../exports/lib -L/usr/X11R6-DRI/lib -lXext -lX11 -ldl -lc /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status + rm -f libGL.so.1 + ln -s libGL.so.1.2 libGL.so.1 + rm -f ../../../exports/lib/libGL.so.1 + cd ../../../exports/lib + ln -s ../../lib/GL/GL/libGL.so.1 . rm -f libGL.so.1.2 mv -f libGL.so.1.2~ libGL.so.1.2 mv: cannot stat `libGL.so.1.2~': No such file or directory make[5]: *** [libGL.so.1.2] Error 1 I've checked and Xext is not built after all. It must be already available. For that you need to make the 'lndir' stuff _before_ building so that the linker finds it (note the -L/usr/X11R6-DRI/lib in the command line). You forgot to CC the dri-devel ML. :) Already done;-) It would be nice if someone writes a little guide how to compile the Mach64 drivers. As soon as I get it working myself I will write a litte doc how I have done it. But I am not an expert in these things;-) I agree. Thanks, Michael Regards, Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
On Tue, Dec 11, 2001 at 12:45:59PM +, Jose Fonseca wrote: Me neither. That's not a problem, just login as anonymous: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login Press enter for password and then cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I start to feel really stupid. I tryed it again and again I got errors. I followed your instructions and did: mkdir DRI-CVS cd DRI-CVS cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc ln -s xc XFree40 mkdir build cd build lndir -silent -ignorelinks ../XFree40 cd ~/DRI-CVS/build/xc/ make World World.LOG + gcc -o ./libGL.so.1.2~ -shared -Wl,-soname,libGL.so.1 ../../../lib/GL/glx/clientattrib.o ../../../lib/GL/glx/compsize.o ../../../lib/GL/glx/dispatch.o ../../../lib/GL/glx/eval.o ../../../lib/GL/glx/glapinoop.o ../../../lib/GL/glx/glapi.o ../../../lib/GL/glx/glapi_x86.o ../../../lib/GL/glx/glthread.o ../../../lib/GL/glx/glxcmds.o ../../../lib/GL/glx/glxext.o ../../../lib/GL/glx/g_render.o ../../../lib/GL/glx/g_single.o ../../../lib/GL/glx/g_vendpriv.o ../../../lib/GL/glx/indirect_init.o ../../../lib/GL/glx/pixel.o ../../../lib/GL/glx/pixelstore.o ../../../lib/GL/glx/render2.o ../../../lib/GL/glx/renderpix.o ../../../lib/GL/glx/single2.o ../../../lib/GL/glx/singlepix.o ../../../lib/GL/glx/vertarr.o ../../../lib/GL/glx/xfont.o ../../../lib/GL/dri/XF86dri.o ../../../lib/GL/dri/dri_glx.o -lpthread -L../../../exports/lib -L/usr/X11R6-DRI/lib -lXext -lX11 -ldl -lc /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status + rm -f libGL.so.1 + ln -s libGL.so.1.2 libGL.so.1 + rm -f ../../../exports/lib/libGL.so.1 + cd ../../../exports/lib + ln -s ../../lib/GL/GL/libGL.so.1 . rm -f libGL.so.1.2 mv -f libGL.so.1.2~ libGL.so.1.2 mv: cannot stat `libGL.so.1.2~': No such file or directory make[5]: *** [libGL.so.1.2] Error 1 I've checked and Xext is not built after all. It must be already available. For that you need to make the 'lndir' stuff _before_ building so that the linker finds it (note the -L/usr/X11R6-DRI/lib in the command line). How do I have to do that? I don't think that lndir'ing from /usr/X11R6 to /usr/X11R6-DRI will do any good. As soon as I managed to compile this I will write a short compilation guide because I think the compilation guide on the webpage is really outdated and there are probably a lot of people who want to get the mach64 working. Thanks for your help, Michael ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
El Mar 11 Dic 2001 15:51, Michael Thaler escribió: On Tue, Dec 11, 2001 at 12:45:59PM +, Jose Fonseca wrote: Me neither. That's not a problem, just login as anonymous: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login Press enter for password and then cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc I start to feel really stupid. I tryed it again and again I got errors. I followed your instructions and did: mkdir DRI-CVS cd DRI-CVS cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r mach64-0-0-2-branch xc ln -s xc XFree40 mkdir build cd build lndir -silent -ignorelinks ../XFree40 cd ~/DRI-CVS/build/xc/ make World World.LOG + gcc -o ./libGL.so.1.2~ -shared -Wl,-soname,libGL.so.1 ../../../lib/GL/glx/clientattrib.o ../../../lib/GL/glx/compsize.o ../../../lib/GL/glx/dispatch.o ../../../lib/GL/glx/eval.o ../../../lib/GL/glx/glapinoop.o ../../../lib/GL/glx/glapi.o ../../../lib/GL/glx/glapi_x86.o ../../../lib/GL/glx/glthread.o ../../../lib/GL/glx/glxcmds.o ../../../lib/GL/glx/glxext.o ../../../lib/GL/glx/g_render.o ../../../lib/GL/glx/g_single.o ../../../lib/GL/glx/g_vendpriv.o ../../../lib/GL/glx/indirect_init.o ../../../lib/GL/glx/pixel.o ../../../lib/GL/glx/pixelstore.o ../../../lib/GL/glx/render2.o ../../../lib/GL/glx/renderpix.o ../../../lib/GL/glx/single2.o ../../../lib/GL/glx/singlepix.o ../../../lib/GL/glx/vertarr.o ../../../lib/GL/glx/xfont.o ../../../lib/GL/dri/XF86dri.o ../../../lib/GL/dri/dri_glx.o -lpthread -L../../../exports/lib -L/usr/X11R6-DRI/lib -lXext -lX11 -ldl -lc /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status + rm -f libGL.so.1 + ln -s libGL.so.1.2 libGL.so.1 + rm -f ../../../exports/lib/libGL.so.1 + cd ../../../exports/lib + ln -s ../../lib/GL/GL/libGL.so.1 . rm -f libGL.so.1.2 mv -f libGL.so.1.2~ libGL.so.1.2 mv: cannot stat `libGL.so.1.2~': No such file or directory make[5]: *** [libGL.so.1.2] Error 1 I've checked and Xext is not built after all. It must be already available. For that you need to make the 'lndir' stuff _before_ building so that the linker finds it (note the -L/usr/X11R6-DRI/lib in the command line). How do I have to do that? I don't think that lndir'ing from /usr/X11R6 to /usr/X11R6-DRI will do any good. Xext is not builded in the DRI compilation process. This is because the dri trunk (branch) is a stripped-out version of the XFree source code. This is because you MUST lndir your existing XFree distro files to the /usr/X11R6-DRI directory, where DRI compilation is trying to find the libs, as you can read in the line: ... -L/usr/X11R6-DRI/lib -lXext ... So, the first thing that you have to do is check if there is a libXext.so.* in your /usr/X11R6-DRI/lib. If you have that library there, I don't understand your problem, and in the other case, you know what to do now. As soon as I managed to compile this I will write a short compilation guide because I think the compilation guide on the webpage is really outdated and there are probably a lot of people who want to get the mach64 working. I think that compiling the mach64 branch is as difficult as compiling another branch or the trunk. All of them are stripped-source versions (I'm not sure now about the mach64-0-0-1, perhaps this was a complete X source tree ) and you need an starting XFree install. Best regards. -- M. Teira ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Mach64 driver
Hello, I downloaded the trunk and the mach64 branch from CVS. I compiled everything with make world and loaded the mach64 module into the kernel. I used XFree 4.10 from debian unstable to test the driver. First I ran glxgears with the libGL that came with debian. I got: 525 frames in 5.0 seconds = 105.000 FPS 629 frames in 5.0 seconds = 125.800 FPS 621 frames in 5.0 seconds = 124.200 FPS After that I copied the libGL from ~/DRI-CVS/build/xc/lib/GL/ to /usr/lib/ and I got 725 frames in 5.0 seconds = 145.000 FPS 600 frames in 5.0 seconds = 120.000 FPS 700 frames in 5.0 seconds = 140.000 FPS 600 frames in 5.0 seconds = 120.000 FPS 700 frames in 5.0 seconds = 140.000 FPS My machine is a PIII-650 with ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) It's an slight improvement, but not very much. I was also wondering that my mouse pointer behaves like the computer needs a lot of cpu power. When I rum glxinfo X crashes, also when I run quake. Do I have to use the newly compiled X server to really run gl apps? I looked at the XFree log file and it only tells that the server aborted, no reasons. Greetings, Michael ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 driver
Hi, On Mon, 2001-12-10 at 14:44, Michael Thaler wrote: Hello, I downloaded the trunk and the mach64 branch from CVS. I compiled everything with make world and loaded the mach64 module into the kernel. I used XFree 4.10 from debian unstable to test the driver. I don't know what particular version of XFree 4.10 you have used but you must also install the X server from the mach64 build tree. The usual way is to 'lndir' your /usr/X11R6/ dir to /usr/X11R6-DRI/ and then 'make install'. This way you avoid file duplication. After you must start the X server in /usr/X11R6-DRI/bin. See the DRI Compilation Guide for more information about how to do this. First I ran glxgears with the libGL that came with debian. I got: 525 frames in 5.0 seconds = 105.000 FPS 629 frames in 5.0 seconds = 125.800 FPS 621 frames in 5.0 seconds = 124.200 FPS After that I copied the libGL from ~/DRI-CVS/build/xc/lib/GL/ to /usr/lib/ and I got 725 frames in 5.0 seconds = 145.000 FPS 600 frames in 5.0 seconds = 120.000 FPS 700 frames in 5.0 seconds = 140.000 FPS 600 frames in 5.0 seconds = 120.000 FPS 700 frames in 5.0 seconds = 140.000 FPS My machine is a PIII-650 with ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) It's an slight improvement, but not very much. I was also wondering that my mouse pointer behaves like the computer needs a lot of cpu power. When I rum glxinfo X crashes, also when I run quake. Do I have to use the newly compiled X server to really run gl apps? I looked at the XFree log file and it only tells that the server aborted, no reasons. Yes you need, as said above, and that is the most probable cause for all these strange behaviors that you've noticed. Greetings, Michael Regards, Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
