Jeff Hartmann wrote:
> Pat Ritchie wrote:
> > Hi,
> > I am having problems with quake3 with the DRI, about half the time I try
> > and start up the game it locks up my system (completely dead, can't even
> > telnet in). Once I get in the game it seems to run fine. Each time it
> > locked something different happened, once I just got a black screen,
> > once I got all kinds of wierd colors moving around all over the screen
> > and once I could still see my desktop.
> > I know that I have to turn off busmastering in Windows to prevent
> > lockups, could the same thing be happening here?
> > What else can I do to help debug this?
> > Here are my system specs:
> > K6-3 450
> > Asus P5A
> > 128mb RAM
> > G400 MAX
> > DRI Snapshot 20000510
> > Any help would be greatly appreciated.
> > Thanks,
> > Pat
> > _______________________________________________
> > Dri-devel mailing list
> > Dri-devel@...
> > http://lists.sourceforge.net/mailman/listinfo/dri-devel
> What kind of sound card do you have, and are you running w/ sound on? I
> know the VIA MVP3 chipsets have problems doing ISA dma and PCI dma
> concurrently, however most of the time these can be worked around.
> Also I would suggest that you use the current dri cvs, unless the date
> is Oct 5th instead of May 10th in your above Snapshot line.
Maybe I have the same problem on the machine at home.
(I don't quite know what MB I have, I might have to take the
Anyway, it's a 450 MHz PII, 256 Mb, G400 Max, SB128 PCI sound, PCI
I get a note about missing interrupt in /var/log/messages after
I reboot (I'll find the exact message when
I'm at home), but the interrupt for the graphics __IS__ enabled. The
interrupt is not shared with other devices according to
It works in 50% of the cases, when it doesn't work the whole machine
hangs. Pressing the reset button doesn't help, because when the machine
comes up again DRI still doesn't work. I'll have to completely switch it
and on again.
It sounds like a BIOS/Motherboard problem, but what can I do to
this? It would be nice to have a test for the graphics interrupt before
starting OpenGL programs so I could do a clean shutdown/switch off/on so
I don't have to wait for fsck each time...
A test-if-video-interrupt-failed-then-halt in /etc/rc.d/rc.local would
I never had any problems with Utah-GLX.
What can I do to investigate this further?
Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@... Homepage: http://www.crc.dk