Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, is this good or bad?

2001-04-01 Thread Chris Proctor
On Sat, Mar 31, 2001 at 08:33:24PM -0800, Joseph Carter wrote: > > Those numbers are probably fairly typical, if very poor compared to win32 > numbers. Glide 3 is not exactly fast in Linux unfortunately. As a > result, 3dfx cards with DRI yield rather disappointing results. Don't > take that

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, is this good or bad?

2001-04-01 Thread Nathan Hand
On Sun, Apr 01, 2001 at 07:40:40PM +1000, Chris Proctor wrote: > > I think these numbers are software rendering. On my machine > with a Voodoo3 2000 and a dual Pentium Pro 200 I get the following: > > DRI:85 fps (monitor rate) > LIBGL_ALWAYS_INDIRECT: 46 fps > FX_GL

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, is this goo

2001-04-01 Thread Kreuzritter2000
> On Sun, Apr 01, 2001 at 04:40:44AM +0200, Kreuzritter2000 wrote: >> Ok >> >> Now i benchmarkt my Voodoo3 2000 PCI card under XFree-DRI with >> gears. >> >> I get 125.623 frames/s. >> >> The tdfx driver was branch 3.0, dri-cvs from beginning of march. >> The computer is an Athlon 500 MHz 128 MB r

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, isthis good or bad?

2001-04-01 Thread Adam K Kirchhoff
> I was getting ~1400 fps with my Radeon on a 600MHz Duron (ASUS A7V, > KT133 chipset), even with AGP 1x. Something's going horribly wrong with > your system... Are you serious? In all the times I've pulled and tested CVS code, I've never gotten above 1000 fps with my Radeon 64 Meg DDR on my 7

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, isthis good or bad?

2001-04-01 Thread Gareth Hughes
Adam K Kirchhoff wrote: > > > I was getting ~1400 fps with my Radeon on a 600MHz Duron (ASUS A7V, > > KT133 chipset), even with AGP 1x. Something's going horribly wrong with > > your system... > > Are you serious? In all the times I've pulled and tested CVS code, I've > never gotten above 1000

[Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Pasi Kärkkäinen
Hello! Is anyone else getting this: /usr/lib/libGL.so: undefined reference to `va_start' /usr/lib/libGL.so: undefined reference to `va_end' collect2: ld returned 1 exit status While trying to link your own (SDL/OpenGL) app to libGL.so.. I'm using debian unstable and todays .deb's of dri. -

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, isthis good or bad?

2001-04-01 Thread Keith Whitwell
Adam K Kirchhoff wrote: > > > I was getting ~1400 fps with my Radeon on a 600MHz Duron (ASUS A7V, > > KT133 chipset), even with AGP 1x. Something's going horribly wrong with > > your system... > > Are you serious? In all the times I've pulled and tested CVS code, I've > never gotten above 1000

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, isthis goo

2001-04-01 Thread Kreuzritter2000
> Adam K Kirchhoff wrote: >> >> > I was getting ~1400 fps with my Radeon on a 600MHz Duron (ASUS A7V, >> > KT133 chipset), even with AGP 1x. Something's going horribly wrong >> > with >> > your system... >> >> Are you serious? In all the times I've pulled and tested CVS code, I've >> never gotte

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, isthis goo

2001-04-01 Thread Gareth Hughes
Kreuzritter2000 wrote: > > Am think i should also add something to my first post. > > I testet gears in a 1024*768 screen resolution with 16 bpp. > But i didn't changed the screen size of gears itself. > > So is that the reason? Should i start XFree in 640*480, or better 320*200 to get >1000 f

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, is this goo

2001-04-01 Thread Keith Whitwell
Kreuzritter2000 wrote: > > > On Sun, Apr 01, 2001 at 04:40:44AM +0200, Kreuzritter2000 wrote: > >> Ok > >> > >> Now i benchmarkt my Voodoo3 2000 PCI card under XFree-DRI with > >> gears. > >> > >> I get 125.623 frames/s. > >> > >> The tdfx driver was branch 3.0, dri-cvs from beginning of march. >

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Joseph Carter
On Sun, Apr 01, 2001 at 05:52:22PM +0300, Pasi K?rkk?inen wrote: > Is anyone else getting this: > > /usr/lib/libGL.so: undefined reference to `va_start' > /usr/lib/libGL.so: undefined reference to `va_end' > collect2: ld returned 1 exit status > > While trying to link your own (SDL/OpenGL) app t

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Pasi Kärkkäinen
On Sun, 1 Apr 2001, Joseph Carter wrote: > On Sun, Apr 01, 2001 at 05:52:22PM +0300, Pasi K?rkk?inen wrote: > > Is anyone else getting this: > > > > /usr/lib/libGL.so: undefined reference to `va_start' > > /usr/lib/libGL.so: undefined reference to `va_end' > > collect2: ld returned 1 exit status

Re: [Dri-devel] 125.624 frames/s in gears with Voodoo3 2000 PCI, is this goo

2001-04-01 Thread Kreuzritter2000
> > > On Sun, Apr 01, 2001 at 04:40:44AM +0200, Kreuzritter2000 wrote: > >> Ok > >> > >> Now i benchmarkt my Voodoo3 2000 PCI card under XFree-DRI with > >> gears. > >> > >> I get 125.623 frames/s. > >> > >> The tdfx driver was branch 3.0, dri-cvs from beginning of march. > >> The computer is an

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Zephaniah E\. Hull
On Sun, Apr 01, 2001 at 09:58:05AM -0700, Joseph Carter wrote: > On Sun, Apr 01, 2001 at 05:52:22PM +0300, Pasi K?rkk?inen wrote: > > Is anyone else getting this: > > > > /usr/lib/libGL.so: undefined reference to `va_start' > > /usr/lib/libGL.so: undefined reference to `va_end' > > collect2: ld r

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Zephaniah E\. Hull
On Sun, Apr 01, 2001 at 11:16:13AM -0700, Daryll Strauss wrote: > On Sun, Apr 01, 2001 at 02:07:36PM -0400, Zephaniah E. Hull wrote: > > > > Actually, the problem is that libGL itself was miscompiled, I'm working > > on tracking this down and properly fixing it. > > > Actually, after a little

[Dri-devel] Re: One more Broadcast 2000 problem..

2001-04-01 Thread Adam K Kirchhoff
On Sun, 1 Apr 2001, Leon van Stuivenberg wrote: > > Application transferred too few scanlines > > Could be stream corruption, but i'm not sure. i've seen this at this end > too at some point. if you have TRACKH and OUTPUTH in ~/.bcast/bcastrc, > what are they set to? > > Or try enabling debug

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Pasi Kärkkäinen
On Sun, 1 Apr 2001, Zephaniah E. Hull wrote: > On Sun, Apr 01, 2001 at 11:16:13AM -0700, Daryll Strauss wrote: > > On Sun, Apr 01, 2001 at 02:07:36PM -0400, Zephaniah E. Hull wrote: > > > > > > Actually, the problem is that libGL itself was miscompiled, I'm working > > > on tracking this down an

[Dri-devel] My apoligies...

2001-04-01 Thread Adam K Kirchhoff
My previous message went to the wrong mailing list. I'm quite sorry. Adam ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel

[Dri-devel] Re: [Dri-users] Mouse lag in Quake3

2001-04-01 Thread AMD-760MP
> On Sun, Apr 01, 2001 at 11:05:35AM -0600, [EMAIL PROTECTED] wrote: > > > This may or may not have anything to do with your situation, but I > > noticed a distinct improvement when I switched from using a serial mouse > > to using a PS/2 mouse. I got a lot more control and my skill level in > > q

[Dri-devel] Re: New Radeon problems... (still)

2001-04-01 Thread Adam K Kirchhoff
This isn't just limited to my Radeon, now, either. It's happening with my G400. I've attached the full log file from when I tried with my Radeon with a CVS pull from this afternoon. Anyone want to take a look and tell me what they think? After X locks, I can still move around with a serial co

Re: [Dri-devel] Linking problem with libGL.so in .deb's

2001-04-01 Thread Zephaniah E\. Hull
Yes, infact the new .debs are now up. Zephaniah E. Hull. On Sun, Apr 01, 2001 at 10:15:17PM +0300, Pasi K?rkk?inen wrote: > Is this patch going to be included in the next build? > > > - Pasi K?rkk?inen > >^ > . . >

Re: [Dri-devel] Re: New Radeon problems... (still)

2001-04-01 Thread Adam K Kirchhoff
OK... I just upgraded to 2.4.3, recompiled the DRM modules from DRI cvs, and it's working. Was something done to the CVS code to make it work with 2.4.3, and, if so, could it have had a negative impact on 2.4.2? Adam On Sun, 1 Apr 2001, Adam K Kirchhoff wrote: > > This isn't just limited to

[Dri-devel] Debian cvs and radeon == painfully slow

2001-04-01 Thread adam.edgar
I just installed the cvs debs from warp and have found the radeon performance to be awfull. My setup is as follows: Duron 650 256 MB Ram Radeon 32 MB ddr Debian Sid (Unstable) Linux 2.4.3(also tried 2.4.2-ac26) When I run q3 areana the opening sequence is p

Re: [Dri-devel] Debian cvs and radeon == painfully slow

2001-04-01 Thread Zephaniah E\. Hull
On Sun, Apr 01, 2001 at 05:52:54PM -0500, adam.edgar wrote: > I just installed the cvs debs from warp and have found the radeon performance > to be awfull. My setup is as follows: > Duron 650 > 256 MB Ram > Radeon 32 MB ddr > Debian Sid (Unstable) > Linux 2.4.3(also

RE: [Dri-devel] Debian cvs and radeon == painfully slow

2001-04-01 Thread adoniz
Adam your problem is shown in these lines from Q3: Using XFree86-VidModeExtension Version 2.0 XF86DGA Mouse (Version 2.0) initialized XFree86-VidModeExtension Activated at 640x480 Using 8/8/8 Color bits, 24 depth, 0 stencil display. GL_RENDERER: Mesa GLX Indirect Initializing OpenGL extensions .

[Dri-devel] Re: Inline assembly question

2001-04-01 Thread Mike A. Harris
On Sat, 31 Mar 2001, Greg Hughes wrote: >Inline assembly experts, > >I've been palying with RedHat 7.1 Beta. This ships with gcc 2.96.77, >which is much better than the 2.96 bundled with RedHat 7.0. This >compiler can build the xc tree from the trunk, but it chokes trying to >build the mesa-3-5

Re: [Dri-devel] Re: [Dri-users] Mouse lag in Quake3

2001-04-01 Thread Joseph Carter
Ack, I gotta get in on this too... On Sun, Apr 01, 2001 at 07:03:40PM -0400, AMD-760MP wrote: > > To further perpetuate this insanely off-topic thread, using a USB mouse > gets finer control. I'm not sure about lag, but there's certainly a lot > more precision. As a matter of fact, when I switc