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
