Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, 2003-03-17 at 21:41, Martin Spott wrote: Michel D?nzer [EMAIL PROTECTED] wrote: BTW, are you actually using 4x transfer rate? If so, have you tried lowering it? I't like to note that the lockups I saw with FlightGear and Solace were completely independent from the AGP transfer rate of my Radeon7500. I did quite a few tests to be shure about it. The same applies for the Radeon9100 I tried today, With the older 4.3 DRM code I see hangs with FG at AGP 1x. With the newer one I see random memory corruption but no hangs. Neither of them are ideal 8) --- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, 2003-03-17 at 06:15, Jonathan Thambidurai wrote: On Sun, 2003-03-16 at 19:59, Michel Dänzer wrote: On Mon, 2003-03-17 at 01:36, Jonathan Thambidurai wrote: When playing Serious Sam: The Second Encounter, the game (and maybe the system, or just the input) locks up after starting a new game at the map screen when it finishes pre-caching. All the demos work fine. I will only have time to further investigate this over the weekend, but I wanted to let anyone that might have the game know about the problem. I have a 4x AGP Radeon Mobility 7500 with 16 MB of memory running the BTW, are you actually using 4x transfer rate? If so, have you tried lowering it? latest texmem-0-0-1 branch from DRI CVS. The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff Thanks for the response. After applying the patch, the problem was not fixed. Dang, I was starting to believe this was the magic one patch to fix them all. ;) One thing I have to add is that the system does not lock up. I can ssh in. The Xserver cannot be killed, however; even kill -9 has no effect; I can kill the game's process, however, and shutdown without problems (remotely). These may be symptoms of a graphics chip lockup. What happens after you kill the game? Does the X server start to hog the CPU? You could try to set the environment variables RADEON_NO_CODEGEN, RADEON_NO_VTXFMT and RADEON_TCL_FORCE_DISABLE in this order to successively disable driver features and see if that makes a difference. -- 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:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
Michel D?nzer [EMAIL PROTECTED] wrote: The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff If it does not work, try this one - I never experienced any Radeon-lockup since I recompiled the driver with the patch mentioned here: Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45 Log message: Fix recycle lockup (Michel Danzer) Modified files: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/: Tag: mesa-4-0-4-branch radeon_dri.c Revision ChangesPath 1.37.2.6 +1 -0 xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
Michel Dänzer wrote: On Mon, 2003-03-17 at 06:15, Jonathan Thambidurai wrote: On Sun, 2003-03-16 at 19:59, Michel Dänzer wrote: On Mon, 2003-03-17 at 01:36, Jonathan Thambidurai wrote: When playing Serious Sam: The Second Encounter, the game (and maybe the system, or just the input) locks up after starting a new game at the map screen when it finishes pre-caching. All the demos work fine. I will only have time to further investigate this over the weekend, but I wanted to let anyone that might have the game know about the problem. I have a 4x AGP Radeon Mobility 7500 with 16 MB of memory running the BTW, are you actually using 4x transfer rate? If so, have you tried lowering it? latest texmem-0-0-1 branch from DRI CVS. The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff Thanks for the response. After applying the patch, the problem was not fixed. Dang, I was starting to believe this was the magic one patch to fix them all. ;) Arguing against that is the fact that we needed some special magic in the enable() function for GL_TEXTURE_2D, etc. -- this hackery means that it cannot be complete as there must be other stuff than GL_TEXTURE_2D that also needs to be caught -- though hopefully in a more general way. Keith --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, 2003-03-17 at 14:11, Martin Spott wrote: Michel D?nzer [EMAIL PROTECTED] wrote: The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff If it does not work, try this one - I never experienced any Radeon-lockup since I recompiled the driver with the patch mentioned here: Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45 Log message: Fix recycle lockup (Michel Danzer) Modified files: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/: Tag: mesa-4-0-4-branch radeon_dri.c Revision ChangesPath 1.37.2.6 +1 -0 xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c That change only has an effect on a server reset, I have no idea why it would make a difference otherwise. -- 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:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, Mar 17, 2003 at 02:41:43PM +0100, Michel Dänzer wrote: On Mon, 2003-03-17 at 14:11, Martin Spott wrote: Michel D?nzer [EMAIL PROTECTED] wrote: Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45 Log message: Fix recycle lockup (Michel Danzer) Modified files: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/: Tag: mesa-4-0-4-branch radeon_dri.c Revision ChangesPath 1.37.2.6 +1 -0 xc/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c That change only has an effect on a server reset, I have no idea why it would make a difference otherwise. I don't know either _why_ it would - this is beyond my insight into the subject. On the other hand I know that it definitely improves stability of the server on my end, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
Michel D?nzer [EMAIL PROTECTED] wrote: You could try to set the environment variables RADEON_NO_CODEGEN, RADEON_NO_VTXFMT and RADEON_TCL_FORCE_DISABLE [...] BTW, I just aquired a Radeon9100 clone to see if serveral 'features' resemble the behaviour I'm used to see on my Radon7500. Infortunately they pretty much behave the same way: The card locks up under certain 'well known' conditions and FlightGear looks quite dark with TCL enabled. I'm now looking for a switch to disable TCL on the r200 based card but grepping the source code I did not find an equivalent to the above mentioned environment setting. Did I miss it ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
Martin Spott wrote: Michel D?nzer [EMAIL PROTECTED] wrote: You could try to set the environment variables RADEON_NO_CODEGEN, RADEON_NO_VTXFMT and RADEON_TCL_FORCE_DISABLE [...] BTW, I just aquired a Radeon9100 clone to see if serveral 'features' resemble the behaviour I'm used to see on my Radon7500. Infortunately they pretty much behave the same way: The card locks up under certain 'well known' conditions and FlightGear looks quite dark with TCL enabled. I'm now looking for a switch to disable TCL on the r200 based card but grepping the source code I did not find an equivalent to the above mentioned environment setting. R200_NO_TCL=1 should do the trick Did I miss it ? Martin. --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, 2003-03-17 at 08:13, Michel Dänzer wrote: BTW, are you actually using 4x transfer rate? If so, have you tried lowering it? Yes, I am using 4x AGP One thing I have to add is that the system does not lock up. I can ssh in. The Xserver cannot be killed, however; even kill -9 has no effect; I can kill the game's process, however, and shutdown without problems (remotely). These may be symptoms of a graphics chip lockup. What happens after you kill the game? Does the X server start to hog the CPU? I haven't had a chance to ssh in again and check CPU usage, but absolutely nothing happens to the screen or input when I kill the game. You could try to set the environment variables RADEON_NO_CODEGEN, RADEON_NO_VTXFMT and RADEON_TCL_FORCE_DISABLE in this order to successively disable driver features and see if that makes a difference. Thank you for these suggestions. I am happy to report that setting RADEON_TCL_FORCE_DISABLE allows the game to work perfectly (at least for the few minutes I played). I would have tried this earlier, but Quake III works for hours and hours with TCL enabled, and I therefore assumed that there was no problem with TCL. --Jonathan Thambidurai --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
Michel D?nzer [EMAIL PROTECTED] wrote: BTW, are you actually using 4x transfer rate? If so, have you tried lowering it? I't like to note that the lockups I saw with FlightGear and Solace were completely independent from the AGP transfer rate of my Radeon7500. I did quite a few tests to be shure about it. The same applies for the Radeon9100 I tried today, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Serious Sam: 2nd Edition crash
When playing Serious Sam: The Second Encounter, the game (and maybe the system, or just the input) locks up after starting a new game at the map screen when it finishes pre-caching. All the demos work fine. I will only have time to further investigate this over the weekend, but I wanted to let anyone that might have the game know about the problem. I have a 4x AGP Radeon Mobility 7500 with 16 MB of memory running the latest texmem-0-0-1 branch from DRI CVS. --Jonathan Thambidurai --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Mon, 2003-03-17 at 01:36, Jonathan Thambidurai wrote: When playing Serious Sam: The Second Encounter, the game (and maybe the system, or just the input) locks up after starting a new game at the map screen when it finishes pre-caching. All the demos work fine. I will only have time to further investigate this over the weekend, but I wanted to let anyone that might have the game know about the problem. I have a 4x AGP Radeon Mobility 7500 with 16 MB of memory running the latest texmem-0-0-1 branch from DRI CVS. The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff -- 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:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Serious Sam: 2nd Edition crash
On Sun, 2003-03-16 at 19:59, Michel Dänzer wrote: On Mon, 2003-03-17 at 01:36, Jonathan Thambidurai wrote: When playing Serious Sam: The Second Encounter, the game (and maybe the system, or just the input) locks up after starting a new game at the map screen when it finishes pre-caching. All the demos work fine. I will only have time to further investigate this over the weekend, but I wanted to let anyone that might have the game know about the problem. I have a 4x AGP Radeon Mobility 7500 with 16 MB of memory running the latest texmem-0-0-1 branch from DRI CVS. The texmem branch doesn't have the FlushVertices fix yet, which seems to help with a number of lockups. Try http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff Thanks for the response. After applying the patch, the problem was not fixed. I also want to make sure it is understood that the game runs fine if you start up a cooperative multiplayer game and play by yourself (and as I mentioned before, all the demos play perfectly). One thing I have to add is that the system does not lock up. I can ssh in. The Xserver cannot be killed, however; even kill -9 has no effect; I can kill the game's process, however, and shutdown without problems (remotely). --Jonathan Thambidurai --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
