Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-04 Thread Branden Robinson
On Wed, Mar 03, 2004 at 12:52:04PM -0800, Chris Ruvolo wrote:
 On Wed, Mar 03, 2004 at 08:29:49AM -0800, cruvolo wrote:
  On Wed, Mar 03, 2004 at 01:47:15PM +0100, Michel D?nzer wrote:
   According to Mike, the real test would be 'real' OpenGL apps like Quake,
   does it pass that?
  
  Quake1, Quake2 and Q3A all work.  Tested for several minutes of play and
  demo playback.
 
 I may have spoken too soon.  Subsequently, X crashed with a SIGSEGV upon
 starting Quake.  It is certainly intermittent.  I didn't have this problem
 with 4.2.1.
 
 Would a stack trace be helpful?  I'll try installing the -dbg package when I
 get home from work.

Yes, a stack trace would be helpful.

-- 
G. Branden Robinson|  When dogma enters the brain, all
Debian GNU/Linux   |  intellectual activity ceases.
[EMAIL PROTECTED] |  -- Robert Anton Wilson
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Re: Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-03 Thread Chris Ruvolo
retitle 234388 xserver-xfree86: [tdfx] want DRI support above 1024x768 on 16MB 
Voodoo Banshee rev 3 and Voodoo3 rev 1

--

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Mar 01, 2004 at 01:51:08PM +0100, Michel D?nzer wrote:
 This is due to the patch 035_tdfx_disable_dri_on_16mb_with_highres.diff,
 which contains the comment:

Michel, thanks for the pointer to this patch.  I have made a build without
this patch, and it is functioning normally on my Voodoo3 rev 1.  DRI is
working with an X res of 1600x1200.  I am able to change VTs and am able to
change X resolutions without issue.  I do not use a framebuffer console.

I'm also changing the title to reflect that this is not exclusive to the
Banshee:

xserver-xfree86: [tdfx] want DRI support above 1024x768 on 16MB
Voodoo Banshee rev 3 and Voodoo3 rev 1

If anyone else is having the same problem, feel free to try my build.
It is versioned as 4.3.0-3.0.tdfx:

deb http://chris.ruvolo.net/debian/ xfree86-tdfx/binary-i386/
deb-src http://chris.ruvolo.net/debian/ xfree86-tdfx/source/

Thanks,
- -Chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARX78KO6EG1hc77ERAkZtAKCcYVoB0+ZBLZrEHnEz4J0b/wag7gCZAcpG
PWo1RImfvjlfUu592VHohFY=
=/N8I
-END PGP SIGNATURE-



Processed: Re: Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-03 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 234388 xserver-xfree86: [tdfx] want DRI support above 1024x768 on 
 16MB Voodoo Banshee rev 3 and Voodoo3 rev 1
Bug#234388: xserver-xfree86: [tdfx] want DRI support at 1280x960 on Voodoo 
Banshee rev 3
Changed Bug title.

 --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-03 Thread Chris Ruvolo
On Wed, Mar 03, 2004 at 01:47:15PM +0100, Michel D?nzer wrote:
 According to Mike, the real test would be 'real' OpenGL apps like Quake,
 does it pass that?

Quake1, Quake2 and Q3A all work.  Tested for several minutes of play and
demo playback.

-Chris


signature.asc
Description: Digital signature


Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-03 Thread Mike A. Harris
On Wed, 3 Mar 2004, Michel [ISO-8859-1] D�nzer wrote:

 On Mon, Mar 01, 2004 at 01:51:08PM +0100, Michel D?nzer wrote:
  This is due to the patch 035_tdfx_disable_dri_on_16mb_with_highres.diff,
  which contains the comment:
 
 Michel, thanks for the pointer to this patch.  I have made a build without
 this patch, and it is functioning normally on my Voodoo3 rev 1.  DRI is
 working with an X res of 1600x1200.  I am able to change VTs and am able to
 change X resolutions without issue.

According to Mike, the real test would be 'real' OpenGL apps like Quake,
does it pass that?

Right, running glxgears or some simple cheesy app is not enough.  
You must POUND the hell out of the driver with an intensive 3D 
application, such as Quake III or something else intensive.  It 
may take anywhere from a few seconds to 30-45 minutes for the 
crash to occur, so this isn't the type of problem that someone 
can configure the driver to use 1600x1200, fire it up for 10 
seconds, run glxgears and say hmm, well it works for me.






Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-03 Thread Chris Ruvolo
On Wed, Mar 03, 2004 at 08:29:49AM -0800, cruvolo wrote:
 On Wed, Mar 03, 2004 at 01:47:15PM +0100, Michel D?nzer wrote:
  According to Mike, the real test would be 'real' OpenGL apps like Quake,
  does it pass that?
 
 Quake1, Quake2 and Q3A all work.  Tested for several minutes of play and
 demo playback.

I may have spoken too soon.  Subsequently, X crashed with a SIGSEGV upon
starting Quake.  It is certainly intermittent.  I didn't have this problem
with 4.2.1.

Would a stack trace be helpful?  I'll try installing the -dbg package when I
get home from work.

-Chris


signature.asc
Description: Digital signature


Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-02 Thread Michel Dänzer
On Mon, 2004-03-01 at 13:51, Michel Dänzer wrote:
 
/* Disable DRI if using a 16Mb card with virtual resolution higher
 than
 * 1024x768 because DRI does not have enough memory available for
 textures
 * at higher resolutions, and will not operate correctly.
 */
 
 See also http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=38717 .
 
 Now, this is an odd explanation; 16 MB should be plenty enough for the
 DRI at say 1280x1024x16. Mike, do you have a better explanation for this
 limit?

The note about tdfx in the Texture management section on
http://dri.sourceforge.net/cgi-bin/moin.cgi/MesaDriver might explain. A
better solution might still be possible, but likely not trivially.


-- 
Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer




Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-02 Thread Mike A. Harris
On Mon, 1 Mar 2004, Michel [ISO-8859-1] D�nzer wrote:

  It looks to me like the error message you're complaining of was not
  added in 4.3.0.
 
 I don't see anything that is obviously causing this to be triggered.
 However, I am unsure about how this code fits in the wider implementation.

This is due to the patch 035_tdfx_disable_dri_on_16mb_with_highres.diff,
which contains the comment:

   /* Disable DRI if using a 16Mb card with virtual resolution higher
than
* 1024x768 because DRI does not have enough memory available for
textures
* at higher resolutions, and will not operate correctly.
*/

See also http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=38717 .

Now, this is an odd explanation; 16 MB should be plenty enough for the
DRI at say 1280x1024x16. Mike, do you have a better explanation for this
limit?

It's been quite a long time now since I created that patch.  I 
was receiving bug reports of DRI enabled tdfx configurations 
crashing randomly when running 3D software, usually video games.  
The problem didn't usually occur instantly, but would occur over 
a short period of time, and usually only with rather 3D intensive 
games like Quake III and the like.

When the games were played at a lower resolution, the problems 
went away.  Research into the problem, discovered that it was due 
to the majority of the video memory being given to the 
framebuffer, and starving texture memory.  I do not remember the 
gory details, but it should be in dri-devel archives from 1.5-2 
years ago.

At the time, people proposed that the problem could be solved by 
modifying the tdfx code to work better in low memory (read as 
high-resolution) situations.  I don't believe anyone ever cared 
enough about the problem to do that work though, or if it did get 
done, it certainly has slipped past me unnoticed.  ;o)

For our (Red Hat) purposes however, I was more concerned with 
desktop stability than the ability of 3Dfx hardware users to play 
Quake III at high resolution and crash their machine.  My 
solution was to patch our driver to disable configurations known 
to cause crashes or other instabilities in certain circumstances, 
and to remove the patch should the real problem ever be fixed in 
upstream sources down the line.  The patch remains in my current 
rpm packages for 4.3.0, and I believe many other distributions 
have borrowed the patch also to prevent the instability problems.

Has the tdfx driver been fixed so that memory starvation isn't an 
issue any more?  If so, it's probably a good idea to drop this 
patch nowadays.  I don't have time to do a runtime test 
personally and bash the driver with some intense 3D.  Could 
someone else do that perhaps?


-- 
Mike A. Harris





Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-02 Thread Mike Mestnik
There was talk in the DRI weekly meating about tdfx.  There is definatly
interested non-DRI developers, however motivation is the biggest thing
holding tdfx back.  Alan Cox has reportedly been working on the voodoo 12
series drivers.  If there is consumer intrest then programers might be
more likely to acctualy do the work.  I know I get a jolt when sombody
says tuxnes is the best emulator thay could find.

--- Mike A. Harris [EMAIL PROTECTED] wrote:
 On Mon, 1 Mar 2004, Michel [ISO-8859-1] Dänzer wrote:
 
   It looks to me like the error message you're complaining of was not
   added in 4.3.0.
  
  I don't see anything that is obviously causing this to be triggered.
  However, I am unsure about how this code fits in the wider
 implementation.
 
 This is due to the patch
 035_tdfx_disable_dri_on_16mb_with_highres.diff,
 which contains the comment:
 
/* Disable DRI if using a 16Mb card with virtual resolution higher
 than
 * 1024x768 because DRI does not have enough memory available for
 textures
 * at higher resolutions, and will not operate correctly.
 */
 
 See also http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=38717 .
 
 Now, this is an odd explanation; 16 MB should be plenty enough for the
 DRI at say 1280x1024x16. Mike, do you have a better explanation for
 this
 limit?
 
 It's been quite a long time now since I created that patch.  I 
 was receiving bug reports of DRI enabled tdfx configurations 
 crashing randomly when running 3D software, usually video games.  
 The problem didn't usually occur instantly, but would occur over 
 a short period of time, and usually only with rather 3D intensive 
 games like Quake III and the like.
 
 When the games were played at a lower resolution, the problems 
 went away.  Research into the problem, discovered that it was due 
 to the majority of the video memory being given to the 
 framebuffer, and starving texture memory.  I do not remember the 
 gory details, but it should be in dri-devel archives from 1.5-2 
 years ago.
 
 At the time, people proposed that the problem could be solved by 
 modifying the tdfx code to work better in low memory (read as 
 high-resolution) situations.  I don't believe anyone ever cared 
 enough about the problem to do that work though, or if it did get 
 done, it certainly has slipped past me unnoticed.  ;o)
 
 For our (Red Hat) purposes however, I was more concerned with 
 desktop stability than the ability of 3Dfx hardware users to play 
 Quake III at high resolution and crash their machine.  My 
 solution was to patch our driver to disable configurations known 
 to cause crashes or other instabilities in certain circumstances, 
 and to remove the patch should the real problem ever be fixed in 
 upstream sources down the line.  The patch remains in my current 
 rpm packages for 4.3.0, and I believe many other distributions 
 have borrowed the patch also to prevent the instability problems.
 
 Has the tdfx driver been fixed so that memory starvation isn't an 
 issue any more?  If so, it's probably a good idea to drop this 
 patch nowadays.  I don't have time to do a runtime test 
 personally and bash the driver with some intense 3D.  Could 
 someone else do that perhaps?
 
 
 -- 
 Mike A. Harris
 
 
 


__
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com




Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-01 Thread Chris Ruvolo
On Tue, Feb 24, 2004 at 02:43:08AM -0500, Branden Robinson wrote:
XFree86 refuses to use DRI at resolutions higher than 1024x768 on a
3dfx Voodoo Banshee and complains with this message on the logs:
  
(WW) TDFX(0): [dri] To use DRI, with a 16Mb Voodoo 3 or Banshee card,
you must invoke the server using a maximum resolution of 1024x768 or 
  lower.
  
I think this behaviour is not justified by any technical reason,
 
 This seems a hasty conclusion to reach if you're not very familiar with the
 driver code and the video hardware.

Branden, I am seeing this too.  The important point here is that this is a
regression from 4.2.1, where the hardware is capable of DRI within an X
session of 1600x1200.  Note that the resolution in question here is not the
resolution of the GLX graphic, but the resolution of the X display.  That
is, the accelerated graphic I had working was at 640x480 and would appear
windowed or fullscreen via DGA.

Now glxinfo with LIBGL_DEBUG=verbose is reporting:

libGL error: XF86DRIQueryDirectRenderingCapable failed

 Perhaps you could review the changes made to the tdfx driver between
 XFree86 4.2.1 and 4.3.0 (the tdfx driver has not, to date, been changed
 on xf-4_3-branch).
 
 It looks to me like the error message you're complaining of was not
 added in 4.3.0.

I don't see anything that is obviously causing this to be triggered.
However, I am unsure about how this code fits in the wider implementation.

-Chris


signature.asc
Description: Digital signature


Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-03-01 Thread Michel Dänzer
On Mon, 2004-03-01 at 10:55, Chris Ruvolo wrote:
 On Tue, Feb 24, 2004 at 02:43:08AM -0500, Branden Robinson wrote:
 
  It looks to me like the error message you're complaining of was not
  added in 4.3.0.
 
 I don't see anything that is obviously causing this to be triggered.
 However, I am unsure about how this code fits in the wider implementation.

This is due to the patch 035_tdfx_disable_dri_on_16mb_with_highres.diff,
which contains the comment:

   /* Disable DRI if using a 16Mb card with virtual resolution higher
than
* 1024x768 because DRI does not have enough memory available for
textures
* at higher resolutions, and will not operate correctly.
*/

See also http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=38717 .

Now, this is an odd explanation; 16 MB should be plenty enough for the
DRI at say 1280x1024x16. Mike, do you have a better explanation for this
limit?


-- 
Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer




Re: Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-02-26 Thread Christian Guggenberger
On Thu, 2004-02-26 at 20:17, Branden Robinson wrote:
 On Wed, Feb 25, 2004 at 11:27:47PM +0100, Rieker Flaik wrote:
  Claudio Martins wrote:
  
 (WW) TDFX(0):Tondri] To use DRI, with a 16Mb Voodoo 3 or Banshee card,
 you must invoke the server using a maximum resolution of 1024x768 or
 lower.
  
  Yes, I have the same errormessage. So I changed back to 1024x768 and in 
  /var/log/XFree86.0.log it's said that DRI has been loaded.
  (II) Loading extension XFree86-DRI
  (II) TDFX(0): [DRI] installation complete
  (==) TDFX(0): Direct rendering enabled
  (==) RandR enabled
  
  But when I tried to play Descent2 with OpenGL there was no
  Hardwareacceleration.
  $ glxinfo
  direct rendering: No
 
 You're probably seeing Debian Bug #229984 (plus 6 duplicate bugs).
 
  So how do I get back my good old ability to run 3d-Hardwareaccelerated
  games?
 
 Downgrade to xlibmesa-dri 4.3.0-0pre1v5, or wait for xlibmesa-dri
 4.3.0-3 (well, probably -- no i386 user has yet reported to me that the
 fix actually works).

okay, let me be the first to do so:
Yes, the fix (000_stolen_from_Mesa_CVS.diff ) does indeed work!

thanks.
Christian





Re: Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-02-25 Thread Rieker Flaik
Claudio Martins wrote:

   (WW) TDFX(0):Tondri] To use DRI, with a 16Mb Voodoo 3 or Banshee card,
   you must invoke the server using a maximum resolution of 1024x768 or
   lower.

Yes, I have the same errormessage. So I changed back to 1024x768 and in 
/var/log/XFree86.0.log it's said that DRI has been loaded.
(II) Loading extension XFree86-DRI
(II) TDFX(0): [DRI] installation complete
(==) TDFX(0): Direct rendering enabled
(==) RandR enabled

But when I tried to play Descent2 with OpenGL there was no
Hardwareacceleration.
$ glxinfo
direct rendering: No

So how do I get back my good old ability to run 3d-Hardwareaccelerated
games?


regards



Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-02-24 Thread Branden Robinson
On Mon, Feb 23, 2004 at 03:47:23PM +, Claudio Martins wrote:
 Package: xserver-xfree86
 Version: 4.3.0-2
 Severity: important
 Tags: sid
 
 
   XFree86 refuses to use DRI at resolutions higher than 1024x768 on a
   3dfx Voodoo Banshee and complains with this message on the logs:
 
   (WW) TDFX(0): [dri] To use DRI, with a 16Mb Voodoo 3 or Banshee card,
   you must invoke the server using a maximum resolution of 1024x768 or lower.
 
   I think this behaviour is not justified by any technical reason,

This seems a hasty conclusion to reach if you're not very familiar with the
driver code and the video hardware.

 nor does it make any sense, since this card has functioned correctly
 using DRI and OpenGL at resolutions as high as 1280x960, up to XFree86
 version 4.2.x.  Even if running certain OpenGL apps at 1280x960 would
 be too slow (like quake3), switching to lower res. modes like 1024x768
 or 800x600 used to work okay, but now with this version the X server
 simply refuses to use DRI and the kernel doesn't even automatically
 load the drm module like it used to.

Perhaps you could review the changes made to the tdfx driver between
XFree86 4.2.1 and 4.3.0 (the tdfx driver has not, to date, been changed
on xf-4_3-branch).

It looks to me like the error message you're complaining of was not
added in 4.3.0.

xfree86/cvs/HEAD/xc % cvs diff -u -r xf-4_2_1 -r xf-4_3_0 
programs/Xserver/hw/xfree86/drivers/tdfx
Index: programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -u -r1.21 -r1.22
--- programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile  21 May 2001 21:43:55 
-  1.21
+++ programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile  17 Feb 2003 17:06:44 
-  1.22
@@ -1,4 +1,4 @@
-XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v 1.21 
2001/05/21 21:43:55 dawes Exp $
+XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/Imakefile,v 1.22 
2003/02/17 17:06:44 dawes Exp $
 XCOMM
 XCOMM This is the Imakefile for the TDFX driver.  
 XCOMM 
@@ -36,7 +36,7 @@
   -I$(XF86SRC)/xaa -I$(XF86SRC)/rac -I$(XF86SRC)/int10 \
-I$(SERVERSRC)/fb -I$(XF86SRC)/xaa -I$(XF86SRC)/ramdac \
   -I$(XF86SRC)/vgahw -I$(XF86SRC)/ddc -I$(XF86SRC)/i2c \
-   -I$(XF86SRC)/ddc -I$(XF86OSSRC)/vbe -I$(SERVERSRC)/Xext \
+   -I$(XF86SRC)/ddc -I$(XF86SRC)/vbe -I$(SERVERSRC)/Xext \
-I$(FONTINCSRC) -I$(SERVERSRC)/include -I$(XINCLUDESRC) \
   -I$(EXTINCSRC) -I$(SERVERSRC)/render \
   $(DRIINCLUDES)
Index: programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v
retrieving revision 1.25
retrieving revision 1.27
diff -u -u -r1.25 -r1.27
--- programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h 18 Aug 2001 02:51:13 
-  1.25
+++ programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h 17 Oct 2002 01:02:08 
-  1.27
@@ -5,7 +5,7 @@
 
Copyright: 1998,1999
 */
-/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v 1.25 
2001/08/18 02:51:13 dawes Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx.h,v 1.27 
2002/10/17 01:02:08 dawes Exp $ */
 
 #ifndef _TDFX_H_
 #define _TDFX_H_
@@ -138,7 +138,7 @@
   unsigned char *MMIOBase[MAXCHIPS];
   unsigned char *FbBase;
   unsigned char *myFbBase;
-  unsigned int PIOBase[MAXCHIPS];
+  IOADDRESS PIOBase[MAXCHIPS];
   long FbMapSize;
   int pixelFormat;
   int stride;
@@ -219,6 +219,8 @@
   int videoKey;
   void (*VideoTimerCallback)(ScrnInfoPtr, Time);
   FBLinearPtr overlayBuffer;
+  FBLinearPtr overlayBuffer2;  /* for double-buffering */
+  int whichOverlayBuffer;  /* flip-flop */
   FBAreaPtr textureBuffer;
   Bool TextureXvideo;
   XF86VideoAdaptorPtr overlayAdaptor;
Index: programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v
retrieving revision 1.23
retrieving revision 1.25
diff -u -u -r1.23 -r1.25
--- programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c 21 May 2001 21:43:55 
-  1.23
+++ programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c 8 Feb 2003 21:26:59 
-   1.25
@@ -1,4 +1,4 @@
-/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v 1.23 
2001/05/21 21:43:55 dawes Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/tdfx/tdfx_dri.c,v 1.25 
2003/02/08 21:26:59 dawes Exp $ */
 
 #include xf86.h
 #include xf86_OSproc.h
@@ -195,7 +195,7 @@
else
  pConfigs[i].doubleBuffer = FALSE;
pConfigs[i].stereo = FALSE;
-   pConfigs[i].bufferSize = 16;
+   pConfigs[i].bufferSize = (pScrn-bitsPerPixel==32) ? 32 : 24;

Bug#234388: xserver-xfree86: [tdfx] X server refuses to use DRI at 1280x960 resolution

2004-02-23 Thread Claudio Martins
Package: xserver-xfree86
Version: 4.3.0-2
Severity: important
Tags: sid


  XFree86 refuses to use DRI at resolutions higher than 1024x768 on a
  3dfx Voodoo Banshee and complains with this message on the logs:

  (WW) TDFX(0): [dri] To use DRI, with a 16Mb Voodoo 3 or Banshee card,
  you must invoke the server using a maximum resolution of 1024x768 or lower.

  I think this behaviour is not justified by any technical reason, nor
does it make any sense, since this card has functioned correctly using DRI 
and OpenGL at resolutions as high as 1280x960, up to XFree86 version 4.2.x. 
Even if running certain OpenGL apps at 1280x960 would be too slow 
(like quake3), switching to lower res. modes like 1024x768 or 800x600 used
to work okay, but now with this version the X server simply refuses to use 
DRI and the kernel doesn't even automatically load the drm module like it
used to.


Thanks for your attention

Best regards

C. Martins


-- Package-specific info:
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo Banshee (rev 
03)
01:00.0 Class 0300: 121a:0003 (rev 03)

# XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config manual page.
# (Type man XF86Config at the shell prompt.)

Section Files
#   FontPathunix/:7100# local font server
# if the local font server has problems, we can fall back on these
#FontPath/usr/share/fonts/truetype
FontPath/usr/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/lib/X11/fonts/Type1
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/75dpi
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/share/fonts/truetype/openoffice
FontPath/usr/lib/X11/fonts/cyrillic
EndSection

Section ServerFlags
EndSection

Section Module
Loadddc
LoadGLcore
Loaddbe
Loaddri
Loadextmod
Loadglx
Loadpex5
Loadrecord
Loadxie
Loadbitmap
Loadfreetype
Loadspeedo
Loadtype1
Loadvbe
Loadint10
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc101
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  ImPS/2
#   Option  Emulate3Buttons   true
Option  Buttons   5
Option  ZAxisMapping  4 5
EndSection

Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEventstrue
Option  Device/dev/psaux
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
Option  ZAxisMapping  4 5
EndSection

Section Device
Identifier  Generic Video Card
Driver  tdfx
Option  UseFBDev  true
EndSection

Section Monitor
Identifier  Generic Monitor
HorizSync   30-96
VertRefresh 50-160
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  Generic Video Card
Monitor Generic Monitor
DefaultDepth16
SubSection Display
Depth   1
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   4
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   8
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   15
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   16
Modes   1280x960 1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   24
Modes   1024x768 800x600 640x480
EndSubSection
EndSection

Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
InputDevice Generic Keyboard
InputDevice Configured Mouse
#