On Tue, 1 Jan 2002, Derrik Pates wrote:
> On Tue, 1 Jan 2002, Steven Walter wrote:
>
> > I'm having a problem with playing Return to Castle Wolfenstein, both
> > with single-player under winex and the multiplayer native binary.
>
> I have seen the same sort of symptoms trying to play Win32 GL games via
> Wine (Alice, Quake 2). On exit, it locks X up pretty badly. It'll get out
> of the program and get the desktop redisplayed, but the console is locked.
> (Last time I tried it, I didn't have anything connected network-wise to
> try connecting in, but Alt-SysRq-{S,U,B} cleanly reboots the system, so
> the kernel was at least still responding.) I have a Voodoo5 AGP and
> XFree86 4.1.0 binaries from Debian on the system in question.
I have similar problems on my P3/933 box with a Voodoo5 PCI. They occur
most frequently in the game Tribes2, crashing after a period of time
ranging from 5 minutes to 6 hours (my guess is that the crash time is
inversely related to the time X has been up). Occasionally, it also
crashes in Quake3 or RTCW. I've got some more information as to
mitigating circumstances, etc.; to summarize:
- This happens in mesa-3-5-branch, mesa-4-0-branch, and X 4.1.0, with
kernels ranging from 2.4.9 to 2.5.0 (and possibly before that).
- Crashes occur in the following pattern:
1. The currently displayed image freezes on the screen; the
currently-playing sound loops.
2. I kill X with Alt+SysRq+K. The sound stops, and if it's been crashed
for a non-trivial amount of time, the video and sound from the past few
seconds that it's been frozen seem to "unspool" (looking like the game was
in fast-forward). The image does not disappear.
3. I blindly switch to a text console (with the standard Alt-Ctrl-fu) and
give X a Ctrl+C for good measure (X has chosen not to die on more than one
occasion). The image still remains, and utilities like mode3 and
vga_reset don't get rid of it.
4. I restart X (with "startx"). At this point, one of 3 things happen:
a) X restarts fine, but if I close it (intentionally or otherwise), I have
to blindly restart it;
b) The left 8 or so pixels from the image are repeated across the screen,
necessitating a forced reboot with Alt+SysRq+{SUB};
c) The image stays there, and necessitates the removal of the power plug
from the computer (Alt+SysRq, the power button, and traditional reboots
don't work).
5. After this happens about (inf+1) times (it's happened 3 times in the
past 72 hours; once, it ruined 3 weeks up), I decide to chuck my V5 into
my other box and pick up a card from the Great Satan of Video Hardware.
- No error messages are outputted to the logs of X, the kernel, or the
game in question.
- This is not a problem on Windows or with other video cards (to the best
of my knowledge, neither Radeons nor GeForce*'s experience this).
I hope that now that the problem is out in the open, the Linux Voodoo4/5
community can see a fix in an expedited manner; I know I'd prefer not to
have to throw an overpriced OS on the box that I'm putting the card in. --
Colin
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
