Re: [Dri-devel] Radeon lockups with Quake3
On Thu, Apr 12, 2001 at 08:56:12PM -0700, Simon Kirby wrote: I decided to upgrade to the newest (as of earlier today) DRI tree, along with 2.4.3-ac5. I was playing Quake3 again, and got a lockup which has never happened before: the monitor on my Radeon went blank, but Quake3 kept going (I could hear the sounds and still "t"alk and hear the transmission). Usually the sound will loop over and over and sysrq will either work or not work. This time everything worked except for the monitor, but it locked up as soon as I quit the game (blindly). The looping sound, blanked screen, and sysrq working case is exactly the one which I can reproduce faithfully with QuakeForge. I have not tried Q3A recently as I have no way of knowing exactly what it's doing whereas I obviously know QF pretty well.. I have been experiencing this combination of problems since 2.4.2. I currently use a slightly patched version of 2.4.3-ac4 (I've added lm-sensors and an updated bttv driver..) I've been temporarily out of commission for the past day or two, so I haven't tried -ac5 yet. Just so you know that the error is probably not a freak bug which only you have happen. Of course, it dies for me in seconds, not minutes. I'll see if I can produce your results under -ac5 in Q3A. If you have a Quake CD laying around (or don't mind tracking down the shareware pak file), could you give QuakeForge a shot? Perhaps something it does is killing it faster? I'm using the "quakeforge" CVS tree, usually the nq-glx target. It also happens with the qw-client-glx target. If I am real lucky, we are experiencing the same bug. -- Joseph Carter [EMAIL PROTECTED]Free software developer RFC 882 put the dot in .com, not Sun Microsystems -- Seen on Slashdot PGP signature
Re: [Dri-devel] Radeon lockups with Quake3
On Fri, Apr 13, 2001 at 01:32:39PM -0700, Simon Kirby wrote: I'm trying to compile the glx client but I'm not having much luck. Debian unstable. How are you compiling it over there? Okay, finally got qf-client-glx to compile (library conflicts with DRI tree). It starts up and runs, but I'm not able to find any multiplayer servers and it doesn't let me play single player. I'll search for some in xqf or something. However, in the mean time, there are some strange things happening. As soon as the client starts, my analog flatpanel starts to get all jittery -- pixels are all vibrating left and right. I can _sometimes_ see a single row of pixels jittering normally if the sync is misaligned, but quakeforge isn't even changing the resoution (1024x768) and it just suddenly starts going all funky. Each scanline is different, as if the horizontal sync is changing phase slightly. As soon as I quit, everything returns to normal. I just obscured the window trying to find a multiplayer server, and got a lock up. Sysrq worked, but my mouse was frozen. I hadn't even started playing yet. Trying again... Simon- [ Stormix Technologies Inc. ][ NetNation Communications Inc. ] [ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]] [ Opinions expressed are not necessarily those of my employers. ] ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon lockups with Quake3
On Fri, Apr 13, 2001 at 02:07:05PM -0700, Simon Kirby wrote: On Fri, Apr 13, 2001 at 01:32:39PM -0700, Simon Kirby wrote: I'm trying to compile the glx client but I'm not having much luck. Debian unstable. How are you compiling it over there? Okay, finally got qf-client-glx to compile (library conflicts with DRI tree). It starts up and runs, but I'm not able to find any multiplayer servers and it doesn't let me play single player. I'll search for some in xqf or something. However, in the mean time, there are some strange things happening. As soon as the client starts, my analog flatpanel starts to get all jittery -- pixels are all vibrating left and right. I can _sometimes_ see a single row of pixels jittering normally if the sync is misaligned, but quakeforge isn't even changing the resoution (1024x768) and it just suddenly starts going all funky. Each scanline is different, as if the horizontal sync is changing phase slightly. As soon as I quit, everything returns to normal. I just obscured the window trying to find a multiplayer server, and got a lock up. Sysrq worked, but my mouse was frozen. I hadn't even started playing yet. Trying again... Well, I compiled "nuq" instead (the single player version), and I just finished three levels without any problems (other than the weird pixel thing which doesn't happen in q3). I tried obscuring the window, changing virtual desktops, dragging everything over it, etc., and couldn't get it to lock up at all. Before, when I had my G200, I could cause a lockup with any GL program by dragging partially or fully obscuring the GL window. It seems that this isn't causing it, though, or something in the multiplayer client is. Simon- [ Stormix Technologies Inc. ][ NetNation Communications Inc. ] [ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]] [ Opinions expressed are not necessarily those of my employers. ] ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
