[Dri-devel] UT2003 Hangs with Radeon 8500

2003-07-15 Thread Marci 
Hi all ,

I'm tring UT2003 with my Raddy 8500LE and lastest DRI Drivers , but I have problems. 

The game start correctly , and I can play for an undeterminated period of time that 
can be  30 seconds or a couple of minutes, after that period the system hangsand I can 
hear only the sound of the game. I can't reboot, the system is completely freezed . 
I've noticed that the time before hang increases if I set AGPSize to 64 MB and 
increases much more if I set X depth to 16bit , but at the end it Hangs anyway.

My system is :

Athlon 2400+

KT4 Ultra 

Hercules 3dProphet Radeon FDX 8500LE 64MB

I append my XF86Config , I've tried with all the options in the Devices section 
disabled

Thank you all

Bye

Marcello

 


XF86Config
Description: Binary data

Re: [Dri-devel] UT2003 Hangs with Radeon 8500

2003-07-15 Thread Dieter Nützel 
Am Dienstag, 15. Juli 2003 16:23 schrieb Marci:
 Hi all ,

 I'm tring UT2003 with my Raddy 8500LE and lastest DRI Drivers , but I have
 problems.

 The game start correctly , and I can play for an undeterminated period of
 time that can be  30 seconds or a couple of minutes, after that period the
 system hangsand I can hear only the sound of the game. I can't reboot, the
 system is completely freezed . I've noticed that the time before hang
 increases if I set AGPSize to 64 MB and increases much more if I set X
 depth to 16bit , but at the end it Hangs anyway.

Me too. For Ages.

It seems to be out of texture (AGP) memory (leak).
Lower depth and more AGPSize let it come up later.

Ian is working on that.

 My system is :

 Athlon 2400+

dual Athlon MP 1900+

 KT4 Ultra

AMD 760MPX (762/768)

 Hercules 3dProphet Radeon FDX 8500LE 64MB

PowerColor Vivo 8500 64 MB

 I append my XF86Config , I've tried with all the options in the Devices
 section disabled

Yes, change nothing.

Regards,
Dieter



---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing  more.
Download  eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-21 Thread Philip Armstrong 
On Thu, Feb 20, 2003 at 09:05:27PM -0500, Daniel Vogel wrote:
  There is no way in hell UT2k3 will run on MGA.  It *REQUIRES*
  ARB_texture_env_combine, which is not supported by that hardware.  Even
  if it didn't require that extension, good grief man, why torture
  yourself like that?!? :)
 
 FWIW, the Windows version of UT2003 even runs (badly) on Intel 810 and
 Voodoo Banshee cards :) A G400 actually performs better than a TNT2 due to
 the increased fillrate. (all D3D)

I've got a G400 MAX as well -- it does pretty well all things
considered when paired with a beefy enough processor to compensate for
the lack of TL. Twas briefly the fastest GPU around ISTR, til Nvidia
stole the crown with the GeForce...

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong 
This is pretty much a followup to Adam Kirchhoff's bug report.

Adam reported that UT2003 patch level 2186 failed with the latest dri
trunk on his Radeon 8500 and gave the traceback reported by UT2003.
I've noticed that more information is contained within
~/.ut2003/System/UT2003.log

Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
Debian unstable and the latest demo release of UT2003 (v2206 -- which
is purported to not need S3TC extensions), I get the following
traceback reported by UT2003:

phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.

Backtrace:
[ 1]  ./Core.so [0x40a0478a]
[ 2]  /lib/libpthread.so.0 [0x40d8775a]
[ 3]  /lib/libc.so.6 [0x40bb39d8]
[ 4]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f55bb9]
[ 5]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f3e4f1]
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
[ 7]  
/scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__22FOpenGLRenderInterface14EPrimitiveType+0x373)
[0x430b0aeb]
[ 8]  ./Engine.so(DrawSection__FP11UStaticMeshiP9UMaterialP16FRenderInterface+0x6f)
[0x403739d3]
[ 9]  
./Engine.so(RenderStaticMesh__FP13FDynamicActorP15FLevelSceneNodePt5TList1ZP13FDynamicLightPt5TList1ZP20FProjectorRenderInfoP16FRenderInterface+0x1ea2)
[0x40375fd2]
[10]  
./Engine.so(Render__13FDynamicActorP15FLevelSceneNodePt5TList1ZP13FDynamicLightPt5TList1ZP20FProjectorRenderInfoP16FRenderInterface+0x3a9)
[0x40340d4d]
[11]  ./Engine.so [0x40360c81]
[12]  ./Engine.so(RenderLevel__FP15FLevelSceneNodeP16FRenderInterface+0x22be)
[0x40365f02]
[13]  ./Engine.so(Render__15FLevelSceneNodeP16FRenderInterface+0x7a2)
[0x4034838a]
[14]  ./Engine.so(Render__16FPlayerSceneNodeP16FRenderInterface+0x330)
[0x4034d4ec]
[15]  ./Engine.so(Draw__11UGameEngineP9UViewportiPUcPi+0x848)
[0x402854d4]
[16]  /scratch/phil/ut2k3/demo/System/SDLDrv.so(Repaint__12USDLViewporti+0x33)
[0x4307193b]
[17]  /scratch/phil/ut2k3/demo/System/SDLDrv.so(Tick__10USDLClient+0x85)
[0x43070365]
[18]  ./Engine.so(Tick__11UGameEnginef+0x31bd) [0x4028c2e1]
[19]  ./ut2003-bin(SDL_SetVideoMode+0x969) [0x8051b1d]
[20]  ./ut2003-bin(main+0x328c) [0x8058b2c]
[21]  /lib/libc.so.6(__libc_start_main+0xdd) [0x40ba2a51]
[22]  ./ut2003-bin(GetFullName__C7UObjectPw+0x7d) [0x80512d1]
Signal: SIGSEGV [segmentation fault]
Aborting.

In ~/.ut2003/System/UT2003.log is the following:

[snip]
Init: Input system initialized for SDLViewport
Log: Enter SetRes: 800x600 Fullscreen 1
Log: OpenGL
Init: GL_VENDOR : VA Linux Systems Inc.
Init: GL_RENDERER   : Mesa DRI G400 20021125 AGP 4x x86/MMX/3DNow!/SSE
Init: GL_VERSION: 1.2 Mesa 5.0
Init: Device supports: GL
Init: Device supports: GL_EXT_bgra
Init: Device supports: GL_ARB_texture_compression
Init: Device supports: GL_ARB_multitexture
Init: C32 RGB888 Z24 S8
Init: WARNING: OpenGL renderer relies on DXTC/S3TC support for good performance.
Init: WARNING: no support for combine3/4 extensions - not all blend modes supported
Init: Game engine initialized
Log: Startup time: 3.831979 seconds
Log: Precaching: NvidiaLogo.LevelInfo0
Log: Allocating 32768 byte dynamic index buffer.
Log: Allocating 65536 byte dynamic vertex buffer.
Log: OpenGL Error: GL_INVALID_ENUM (UOpenGLRenderDevice::Unlock)
Log: Finished precaching geometry in 0.105 seconds
Exit: Exiting.
Log: Waiting for file streaming thread to finish...
Uninitialized: Name subsystem shut down
Uninitialized: Allocation checking disabled
Uninitialized: Log file closed, Thu Feb 20 20:31:18 2003

So it looks like the segfault is caused by the GL_INVALID_ENUM
error. Could this be down to ut2003 being compiled against an earlier
libGL? By comparison, the Return to Castle Wolfenstein demo works
fine.

I'll try twiddling some of the settings in the ut ini file to see if
it makes any difference...

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Brown 
On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
 Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
 Debian unstable and the latest demo release of UT2003 (v2206 -- which
 is purported to not need S3TC extensions), I get the following
 traceback reported by UT2003:
 
 phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
 Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.

???

This looks like you are using Xig libGL.so library. Deinstall Xig libs
before doing tests like this.




---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Leif Delgass 
On Thu, 20 Feb 2003, Leif Delgass wrote:

 On Thu, 20 Feb 2003, Philip Brown wrote:
 
  On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
   Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
   Debian unstable and the latest demo release of UT2003 (v2206 -- which
   is purported to not need S3TC extensions), I get the following
   traceback reported by UT2003:
   
   phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
   Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
  
  ???
  
  This looks like you are using Xig libGL.so library. Deinstall Xig libs
  before doing tests like this.
 
 No, that's ut2k3 looking for S3TC support.

Actually, I'm not sure it's S3TC.  There may be some other functionality
in that X extension that it looks for. In any case, that message just
means it couldn't find that X server extension.  I see that and I've never
had XiG drivers installed.

-- 
Leif Delgass 
http://www.retinalburn.net



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel 
 On Thu, 20 Feb 2003, Philip Brown wrote:
 
  On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
   Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
   Debian unstable and the latest demo release of UT2003 (v2206 -- which
   is purported to not need S3TC extensions), I get the following
   traceback reported by UT2003:
   
   phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
   Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
  
  ???
  
  This looks like you are using Xig libGL.so library. Deinstall Xig libs
  before doing tests like this.
 
 No, that's ut2k3 looking for S3TC support.

No.

BTW, the above warning message is harmless IIRC.

   [ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
   [ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
   22FOpenGLRenderInterface14EPrimitiveType+0x373)

Might be interesting to know why it crashes inside the driver :)

-- Daniel, Epic Games Inc.


---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong 
On Thu, Feb 20, 2003 at 02:25:16PM -0800, Philip Brown wrote:
 On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
  Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
  Debian unstable and the latest demo release of UT2003 (v2206 -- which
  is purported to not need S3TC extensions), I get the following
  traceback reported by UT2003:
  
  phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
  Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
 
 ???
 
 This looks like you are using Xig libGL.so library. Deinstall Xig libs
 before doing tests like this.

No, it's just UT2003 looking for that X server extension and not
finding it. I don't have any Xig libraries whatsoever.

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong 
On Thu, Feb 20, 2003 at 05:53:25PM -0500, Leif Delgass wrote:
 On Thu, 20 Feb 2003, Leif Delgass wrote:
  On Thu, 20 Feb 2003, Philip Brown wrote:
   On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
Debian unstable and the latest demo release of UT2003 (v2206 -- which
is purported to not need S3TC extensions), I get the following
traceback reported by UT2003:
phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
   This looks like you are using Xig libGL.so library. Deinstall Xig libs
   before doing tests like this.
  
  No, that's ut2k3 looking for S3TC support.
 
 Actually, I'm not sure it's S3TC.  There may be some other functionality
 in that X extension that it looks for. In any case, that message just
 means it couldn't find that X server extension.  I see that and I've never
 had XiG drivers installed.

No, it's not the S3TC stuff -- note the warnings in the logfile in my
original email warning that a lack of S3TC support will lead to
reduced performance.

Googling around reveals that UT2003 complains about missing
XiG-SUNDRY-NONSTANDARD extensions for other people and it appears
entirely benign.

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong 
On Thu, Feb 20, 2003 at 06:13:01PM -0500, Daniel Vogel wrote:
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
[ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
22FOpenGLRenderInterface14EPrimitiveType+0x373)
 
 Might be interesting to know why it crashes inside the driver :)

fwiw, here's the output from ut2003 if I set MESA_DEBUG and
LIBGL_DEBUG:

cpu vendor: AuthenticAMD
cpu name: AMD Duron(tm) Processor
MMX cpu detected.
3DNow! cpu detected.
Testing OS support for SSE... yes.
Testing OS support for SSE unmasked exceptions... SIGFPE, yes.
Tests of OS support for SSE passed.
SSE cpu detected.
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(param=GL_COMBINE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(param=GL_COMBINE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_ALPHA_SCALE)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_ALPHA_SCALE)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error:

RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Leif Delgass 
On Thu, 20 Feb 2003, Daniel Vogel wrote:

  On Thu, 20 Feb 2003, Philip Brown wrote:
  
   On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
Debian unstable and the latest demo release of UT2003 (v2206 -- which
is purported to not need S3TC extensions), I get the following
traceback reported by UT2003:

phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
   
   ???
   
   This looks like you are using Xig libGL.so library. Deinstall Xig libs
   before doing tests like this.
  
  No, that's ut2k3 looking for S3TC support.
 
 No.
 
 BTW, the above warning message is harmless IIRC.

Yeah, I realized my error just after posting it (see my reply to myself).  
;)
 
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
[ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
22FOpenGLRenderInterface14EPrimitiveType+0x373)
 
 Might be interesting to know why it crashes inside the driver :)

I agree. 

Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
supported in the MGA driver.  I see defines for what look like combiner
registers, but it's not implemented in the driver yet (I don't have
hardware docs myself so I don't know the specifics of what the cards can
do).  The INVALID_ENUMS here appear to be the result of that and a lack of
ARB_texture_cube_map (neither of which are in core OpenGL 1.2).  However,
the driver shouldn't cause a segfault even with a bad enum.  A trace from
gdb would be helpful, I think.

On the plus side, the R100 and R200 drivers now support
ATI_texture_env_combine3 and one bug that was causing vertex corruption in
the intro cinematic in the R100 driver was fixed.  However, there are
still vertex problems that appear to be in the R100 driver to track down.

I can't test R200, so I'm not sure what the status is there.

-- 
Leif Delgass 
http://www.retinalburn.net







---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel 
 Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
 supported in the MGA driver.  I see defines for what look like combiner

That's a no go as we rely on this extension. The game should probably assert
in this case.

-- Daniel, Epic Games Inc.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Ian Romanick 
Philip Armstrong wrote:

phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.

Ignore this.  This is UT2k3 trying to determine which way to do 
fullscreen.  Either the XFree86 way or the XiG way.

[ 4]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f55bb9]
[ 5]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f3e4f1]
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]


There is no way in hell UT2k3 will run on MGA.  It *REQUIRES* 
ARB_texture_env_combine, which is not supported by that hardware.  Even 
if it didn't require that extension, good grief man, why torture 
yourself like that?!? :)



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Ian Romanick 
Leif Delgass wrote:


Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
supported in the MGA driver.  I see defines for what look like combiner
registers, but it's not implemented in the driver yet (I don't have
hardware docs myself so I don't know the specifics of what the cards can
do).  The INVALID_ENUMS here appear to be the result of that and a lack of
ARB_texture_cube_map (neither of which are in core OpenGL 1.2).  However,
the driver shouldn't cause a segfault even with a bad enum.  A trace from
gdb would be helpful, I think.


Correct.  The combiner in the G400 family is strange.  I spent some time 
looking at the docs a few weeks ago.  It should be possible to implement 
most of ARB_texture_env_combine, but not everything.  Basically, there 
is a single multiplier and a single adder.  That means that 
GL_INTERPOLATE is right out.  Also, the first operand MUST come from the 
source texture.

It's pretty kooky, but I think we could get about 60% of 
ARB_texture_env_combine and about 40% of ATI_texture_env_combine3 (no 
joke!) hardware accelerated.  If anyone (esp. anyone that has that 
hardware) would be interested in working on implementing it, I'd love to 
discuss it.  I just don't think I'll have the spare time to put too much 
effort into it.

What would be REALLY nice is to have as much of these extensions as 
possible hardware accelerated on MGA, Rage 128, and i810, AND have the 
software fallbacks MMX optimized...I can dream. :)

On the plus side, the R100 and R200 drivers now support
ATI_texture_env_combine3 and one bug that was causing vertex corruption in
the intro cinematic in the R100 driver was fixed.  However, there are
still vertex problems that appear to be in the R100 driver to track down.

I can't test R200, so I'm not sure what the status is there.


Unfortunately, it's WORSE on R200.  Not only does it not render 
correctly, it hard locks the system.  I have to hit the reset button on 
the case. :(  I'm trying to get through some of my other duties so that 
I can spend a few cycles on this.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel 
 There is no way in hell UT2k3 will run on MGA.  It *REQUIRES*
 ARB_texture_env_combine, which is not supported by that hardware.  Even
 if it didn't require that extension, good grief man, why torture
 yourself like that?!? :)

FWIW, the Windows version of UT2003 even runs (badly) on Intel 810 and
Voodoo Banshee cards :) A G400 actually performs better than a TNT2 due to
the increased fillrate. (all D3D)

We scale back pretty well, though the OpenGL renderer never was written with
the intention to work on G400 cards. The D3D renderer jumps through quite
some hoops to deal with very old HW, disables certain features and
simplifies certain materials/ shaders to avoid driver/ HW bugs/ limitations.
I didn't bother doing that for the OpenGL renderer, which, FWIW, runs quite
well on Voodoo 4/5 cards on Windows.

As I've been seeing posts on /. about the topic: on Windows the OpenGL
renderer performs within 5-10% of the D3D renderer on ATI and NVIDIA cards
on the machines I tested. Sometimes it's faster, but most of the times its
slightly slower than the D3D renderer, which doesn't come as a big surprise
given the amount of tweaking the D3D codepath underwent on both our end and
the driver side.

-- Daniel, Epic Games Inc.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] UT2003

2003-02-05 Thread Ian Romanick 
Adam K Kirchhoff wrote:

FYI,

	With the latest patch to UT2003 (2186), and drivers from the
texmem branch as of this morning (for a Radeon 8500), ut2003 segfaults:

Backtrace:
[ 1]  ./Core.so [0x409f635a]
[ 2]  /lib/libpthread.so.0 [0x40d7275a]
[ 3]  /lib/libc.so.6 [0x40b9f898]
[ 4]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74419]
[ 5]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74966]
[ 6]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e7498a]
[ 7]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e59521]
[ 8]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e70614]
[ 9]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e309e8]
[10]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e24301]
[11]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43dbf587]
[12]
/usr/local/games/ut2003/System/OpenGLDrv.so(DrawPrimitive__22FOpenGLRender
Interface14EPrimitiveType+0x348) [0x42f49ac0]
[13]  ./Engine.so(Flush__11FCanvasUtil+0x1dc) [0x4035206c]
[14]  ./Engine.so(_._11FCanvasUtil+0x28) [0x40351dac]
[15]  ./Engine.so(Render__16FPlayerSceneNodeP16FRenderInterface+0x97a)
[0x403434
96]
[16]  ./Engine.so(Draw__11UGameEngineP9UViewportiPUcPi+0x840) [0x4027b304]
[17]
/usr/local/games/ut2003/System/SDLDrv.so(Repaint__12USDLViewporti+0x33) [0
x42f0a93b]
[18]  /usr/local/games/ut2003/System/SDLDrv.so(Tick__10USDLClient+0x85)
[0x42f09
365]
[19]  ./Engine.so(Tick__11UGameEnginef+0x31bd) [0x40282111]
[20]  ./ut2003-bin(SDL_SetVideoMode+0x969) [0x8051b1d]
[21]  ./ut2003-bin(main+0x328c) [0x8058b2c]
[22]  /lib/libc.so.6(__libc_start_main+0xdd) [0x40b8e9f1]
[23]  ./ut2003-bin(ValidateCDKey__Fv+0x4d) [0x80512d1]
Signal: SIGSEGV [segmentation fault]

Prior to this patch, the game would load, levels would load (of course,
they'd render completely wrong), and my machine would lock up eventually.
I'm not sure if I should consider this an improvement :-)


I (finally) have an 8500, but UT2k3 is still on the way.  Looking at 
this backtrace, I assume that you got this from a core file.  Can you 
run UT2k3 from inside gdb?  You'll have to be able to ssh/telnet into 
your box.  I've been trying to reproduce this problem with other 
programs, but I haven't had any luck.

Has anyone else seen this problem?



---
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] UT2003

2003-02-05 Thread Adam K Kirchhoff 

On Wed, 5 Feb 2003, Ian Romanick wrote:

 Adam K Kirchhoff wrote:
  FYI,
 
  With the latest patch to UT2003 (2186), and drivers from the
  texmem branch as of this morning (for a Radeon 8500), ut2003 segfaults:
 
  Backtrace:
  [ 1]  ./Core.so [0x409f635a]
  [ 2]  /lib/libpthread.so.0 [0x40d7275a]
  [ 3]  /lib/libc.so.6 [0x40b9f898]
  [ 4]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74419]
  [ 5]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74966]
  [ 6]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e7498a]
  [ 7]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e59521]
  [ 8]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e70614]
  [ 9]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e309e8]
  [10]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e24301]
  [11]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43dbf587]
  [12]
  /usr/local/games/ut2003/System/OpenGLDrv.so(DrawPrimitive__22FOpenGLRender
  Interface14EPrimitiveType+0x348) [0x42f49ac0]
  [13]  ./Engine.so(Flush__11FCanvasUtil+0x1dc) [0x4035206c]
  [14]  ./Engine.so(_._11FCanvasUtil+0x28) [0x40351dac]
  [15]  ./Engine.so(Render__16FPlayerSceneNodeP16FRenderInterface+0x97a)
  [0x403434
  96]
  [16]  ./Engine.so(Draw__11UGameEngineP9UViewportiPUcPi+0x840) [0x4027b304]
  [17]
  /usr/local/games/ut2003/System/SDLDrv.so(Repaint__12USDLViewporti+0x33) [0
  x42f0a93b]
  [18]  /usr/local/games/ut2003/System/SDLDrv.so(Tick__10USDLClient+0x85)
  [0x42f09
  365]
  [19]  ./Engine.so(Tick__11UGameEnginef+0x31bd) [0x40282111]
  [20]  ./ut2003-bin(SDL_SetVideoMode+0x969) [0x8051b1d]
  [21]  ./ut2003-bin(main+0x328c) [0x8058b2c]
  [22]  /lib/libc.so.6(__libc_start_main+0xdd) [0x40b8e9f1]
  [23]  ./ut2003-bin(ValidateCDKey__Fv+0x4d) [0x80512d1]
  Signal: SIGSEGV [segmentation fault]
 
  Prior to this patch, the game would load, levels would load (of course,
  they'd render completely wrong), and my machine would lock up eventually.
  I'm not sure if I should consider this an improvement :-)

 I (finally) have an 8500, but UT2k3 is still on the way.  Looking at
 this backtrace, I assume that you got this from a core file.

Actually, I didn't.  UT2003 prints all sorts of nice debugging info when
it crashes :-)

 Can you run UT2k3 from inside gdb?  You'll have to be able to ssh/telnet
 into your box.  I've been trying to reproduce this problem with other
 programs, but I haven't had any luck.

I think I can handle that sometime this week.

Adam



---
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] UT2003

2003-02-02 Thread Adam K Kirchhoff 

FYI,

With the latest patch to UT2003 (2186), and drivers from the
texmem branch as of this morning (for a Radeon 8500), ut2003 segfaults:

Backtrace:
[ 1]  ./Core.so [0x409f635a]
[ 2]  /lib/libpthread.so.0 [0x40d7275a]
[ 3]  /lib/libc.so.6 [0x40b9f898]
[ 4]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74419]
[ 5]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e74966]
[ 6]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e7498a]
[ 7]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e59521]
[ 8]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e70614]
[ 9]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e309e8]
[10]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43e24301]
[11]  /usr/X11R6/lib/modules/dri/r200_dri.so [0x43dbf587]
[12]
/usr/local/games/ut2003/System/OpenGLDrv.so(DrawPrimitive__22FOpenGLRender
Interface14EPrimitiveType+0x348) [0x42f49ac0]
[13]  ./Engine.so(Flush__11FCanvasUtil+0x1dc) [0x4035206c]
[14]  ./Engine.so(_._11FCanvasUtil+0x28) [0x40351dac]
[15]  ./Engine.so(Render__16FPlayerSceneNodeP16FRenderInterface+0x97a)
[0x403434
96]
[16]  ./Engine.so(Draw__11UGameEngineP9UViewportiPUcPi+0x840) [0x4027b304]
[17]
/usr/local/games/ut2003/System/SDLDrv.so(Repaint__12USDLViewporti+0x33) [0
x42f0a93b]
[18]  /usr/local/games/ut2003/System/SDLDrv.so(Tick__10USDLClient+0x85)
[0x42f09
365]
[19]  ./Engine.so(Tick__11UGameEnginef+0x31bd) [0x40282111]
[20]  ./ut2003-bin(SDL_SetVideoMode+0x969) [0x8051b1d]
[21]  ./ut2003-bin(main+0x328c) [0x8058b2c]
[22]  /lib/libc.so.6(__libc_start_main+0xdd) [0x40b8e9f1]
[23]  ./ut2003-bin(ValidateCDKey__Fv+0x4d) [0x80512d1]
Signal: SIGSEGV [segmentation fault]

Prior to this patch, the game would load, levels would load (of course,
they'd render completely wrong), and my machine would lock up eventually.
I'm not sure if I should consider this an improvement :-)

Adam




---
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