Re: [R300] gliding_penguin snapshot
> Vladimir Dergachev wrote: > >> >> Hi Adam, >> >> Could you remind me what video card you have ? And also any other >> details that might be relevant (like resolution, refresh rate, >> motherboard chipset, AGP mode, etc). >> >>thank you ! >> >> Vladimir Dergachev > > > I have a Radeon 9800 Pro (R350). I use a mergedfb desktop at > 2560x1024... I don't know the refresh rate offhand. It's a dual xeon > machine. I'm running AGP at 4x. > > Generally speaking, at that resolution, I'm able to play a couple > holes of neverputt before my machine locks up. Tuxracer and PPracer, on > the other hand, lockup immediately. Neverputt tends to lockup between > holes, or sometimes when I'm aiming my shot... When I start X with the > lower resolution, neverputt locks up almost immediately. Given this, > I'm assuming the lockups happen when the framerate is at it's highest. We could check the states that are different between rv350 and r300 on fgl. Im on irc in case you are interested... -- Aapo Tahkola --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Vladimir Dergachev wrote: I have a Radeon 9800 Pro (R350). I use a mergedfb desktop at 2560x1024... I don't know the refresh rate offhand. It's a dual xeon machine. I'm running AGP at 4x. Generally speaking, at that resolution, I'm able to play a couple holes of neverputt before my machine locks up. Tuxracer and PPracer, on the other hand, lockup immediately. Neverputt tends to lockup between holes, or sometimes when I'm aiming my shot... When I start X with the lower resolution, neverputt locks up almost immediately. Given this, I'm assuming the lockups happen when the framerate is at it's highest. Adam So I assume this doesn't help you track down what the problem might be... Could it be specific to the 9800? Is there anything else you'd suggest testing? No, no ideas yet. Have you tried the latest CVS ? In the hope that the bug got fixed :) I'll give it a shot in a minute. First I wanted to try setting AGPMode to 2x. Though this is what it shows up as in the Xorg log file, I still see the following line in my dmesg: agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: Putting AGP V3 device at :00:00.0 into 4x mode It's probably unrelated to the lockups I'm seeing, but thought I'd mention it :-) Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
I have a Radeon 9800 Pro (R350). I use a mergedfb desktop at 2560x1024... I don't know the refresh rate offhand. It's a dual xeon machine. I'm running AGP at 4x. Generally speaking, at that resolution, I'm able to play a couple holes of neverputt before my machine locks up. Tuxracer and PPracer, on the other hand, lockup immediately. Neverputt tends to lockup between holes, or sometimes when I'm aiming my shot... When I start X with the lower resolution, neverputt locks up almost immediately. Given this, I'm assuming the lockups happen when the framerate is at it's highest. Adam So I assume this doesn't help you track down what the problem might be... Could it be specific to the 9800? Is there anything else you'd suggest testing? No, no ideas yet. Have you tried the latest CVS ? In the hope that the bug got fixed :) best Vladimir Dergachev Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Adam K Kirchhoff wrote: Vladimir Dergachev wrote: Hi Adam, Could you remind me what video card you have ? And also any other details that might be relevant (like resolution, refresh rate, motherboard chipset, AGP mode, etc). thank you ! Vladimir Dergachev I have a Radeon 9800 Pro (R350). I use a mergedfb desktop at 2560x1024... I don't know the refresh rate offhand. It's a dual xeon machine. I'm running AGP at 4x. Generally speaking, at that resolution, I'm able to play a couple holes of neverputt before my machine locks up. Tuxracer and PPracer, on the other hand, lockup immediately. Neverputt tends to lockup between holes, or sometimes when I'm aiming my shot... When I start X with the lower resolution, neverputt locks up almost immediately. Given this, I'm assuming the lockups happen when the framerate is at it's highest. Adam So I assume this doesn't help you track down what the problem might be... Could it be specific to the 9800? Is there anything else you'd suggest testing? Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Vladimir Dergachev wrote: Hi Adam, Could you remind me what video card you have ? And also any other details that might be relevant (like resolution, refresh rate, motherboard chipset, AGP mode, etc). thank you ! Vladimir Dergachev I have a Radeon 9800 Pro (R350). I use a mergedfb desktop at 2560x1024... I don't know the refresh rate offhand. It's a dual xeon machine. I'm running AGP at 4x. Generally speaking, at that resolution, I'm able to play a couple holes of neverputt before my machine locks up. Tuxracer and PPracer, on the other hand, lockup immediately. Neverputt tends to lockup between holes, or sometimes when I'm aiming my shot... When I start X with the lower resolution, neverputt locks up almost immediately. Given this, I'm assuming the lockups happen when the framerate is at it's highest. Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. A less rigourous, but easier way is to launch "bare X" - put a single xterm line in your .xinitrc (or .xsession) and login. Then start the game from xterm window. If it does not lock up immediately, you can be reasonably sure that X does not mess with the hardware while the game is playing. best Vladimir Dergachev cu, Nicolai Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Hi Adam, Could you remind me what video card you have ? And also any other details that might be relevant (like resolution, refresh rate, motherboard chipset, AGP mode, etc). thank you ! Vladimir Dergachev On Sun, 6 Mar 2005, Adam K Kirchhoff wrote: Vladimir Dergachev wrote: I just tagged "gliding_penguin" snapshot of r300_driver. We have not had snapshot in a long time and it seemed appropriate to make one. You can get the code by checking out r300_driver module with tag "gliding_penguin" from CVS at http://r300.sf.net/ . Use a command like this: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 \ co -P -z3 -r gliding_penguin r300_driver Both Quake and PPRacer (Open Source continuation of TuxRacer) work, with many Quake levels rendering very well (and I have not played PPRacer long enough to tell whether there is one that is broken). Big thanks to everyone who contributed to the release and, in particular, to many people who test CVS code :) Also, I updated the author list in the r300_driver/README file, but omitted e-mails of people that were added. If you would like your e-mail to appear please edit the file to your liking. If you have committed code to r300_driver and do not appear in the author list, I apologize - please add yourself ! I made the list by looking through CVS logs, I might have missed someone. Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Nicolai Haehnle wrote: On Sunday 06 March 2005 14:15, Adam K Kirchhoff wrote: Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. cu, Nicolai Well, I've never build solo before, but I gave it a whirl. I edited the config file so it'd only build the r300 driver, but it errors out during the build process: CC="gcc" CXX="g++" ../../../bin/mklib -o GL -major 1 -minor 2 \ -install ../../../lib -lm -lpthread -ldl ../../../src/mesa/main/dispatch.o ../../../src/mesa/glapi/glapi.o ../../../src/mesa/glapi/glthread.o ../../../src/mesa/drivers/dri/common/glcontextmodes.o ../../../../drm/libdrm/xf86drm.o ../../../../drm/libdrm/xf86drmHash.o ../../../../drm/libdrm/xf86drmRandom.o miniglx.o miniglx_events.o ../../../src/mesa/x86/glapi_x86.o mklib: Making Linux shared library: libGL.so.1.2 ../../../src/mesa/x86/glapi_x86.o(.text+0x20): In function `glNewList': ../../../src/mesa/x86/glapi_x86.S:128: multiple definition of `glNewList' ../../../src/mesa/main/dispatch.o(.text+0x0):../../src/mesa/glapi/glapitemp.h:74: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x40): In function `glEndList': ../../../src/mesa/x86/glapi_x86.S:129: multiple definition of `glEndList' ../../../src/mesa/main/dispatch.o(.text+0x46):../../src/mesa/glapi/glapitemp.h:79: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x60): In function `glCallList': ../../../src/mesa/x86/glapi_x86.S:130: multiple definition of `glCallList' ../../../src/mesa/main/dispatch.o(.text+0x7e):../../src/mesa/glapi/glapitemp.h:84: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x80): In function `glCallLists': ../../../src/mesa/x86/glapi_x86.S:131: multiple definition of `glCallLists' ../../../src/mesa/main/dispatch.o(.text+0xbe):../../src/mesa/glapi/glapitemp.h:89: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0xa0): In function `glDeleteLists': ../../../src/mesa/x86/glapi_x86.S:132: multiple definition of `glDeleteLists' ../../../src/mesa/main/dispatch.o(.text+0x10c):../../src/mesa/glapi/glapitemp.h:94: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0xc0): In function `glGenLists': ../../../src/mesa/x86/glapi_x86.S:133: multiple definition of `glGenLists' And so on and so forth :-) Are there any instructions on building linux-solo-x86 that I should be aware of? Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
On Sunday 06 March 2005 14:15, Adam K Kirchhoff wrote: > Unfortunately, I'm still getting pretty constant lockups that seem to be > related to high framerates. From ppcracer with RADEON_DEBUG set to all: > > http://68.44.156.246/ppracer.txt.gz > > On the plus side, the texture problem that I had seen with > neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. cu, Nicolai > Adam pgpo4Bo89wFuG.pgp Description: PGP signature
Re: [R300] gliding_penguin snapshot
Vladimir Dergachev wrote: I just tagged "gliding_penguin" snapshot of r300_driver. We have not had snapshot in a long time and it seemed appropriate to make one. You can get the code by checking out r300_driver module with tag "gliding_penguin" from CVS at http://r300.sf.net/ . Use a command like this: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 \ co -P -z3 -r gliding_penguin r300_driver Both Quake and PPRacer (Open Source continuation of TuxRacer) work, with many Quake levels rendering very well (and I have not played PPRacer long enough to tell whether there is one that is broken). Big thanks to everyone who contributed to the release and, in particular, to many people who test CVS code :) Also, I updated the author list in the r300_driver/README file, but omitted e-mails of people that were added. If you would like your e-mail to appear please edit the file to your liking. If you have committed code to r300_driver and do not appear in the author list, I apologize - please add yourself ! I made the list by looking through CVS logs, I might have missed someone. Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. Adam --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[R300] gliding_penguin snapshot
I just tagged "gliding_penguin" snapshot of r300_driver. We have not had snapshot in a long time and it seemed appropriate to make one. You can get the code by checking out r300_driver module with tag "gliding_penguin" from CVS at http://r300.sf.net/ . Use a command like this: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 \ co -P -z3 -r gliding_penguin r300_driver Both Quake and PPRacer (Open Source continuation of TuxRacer) work, with many Quake levels rendering very well (and I have not played PPRacer long enough to tell whether there is one that is broken). Big thanks to everyone who contributed to the release and, in particular, to many people who test CVS code :) Also, I updated the author list in the r300_driver/README file, but omitted e-mails of people that were added. If you would like your e-mail to appear please edit the file to your liking. If you have committed code to r300_driver and do not appear in the author list, I apologize - please add yourself ! I made the list by looking through CVS logs, I might have missed someone. best Vladimir Dergachev --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
