Hi,
On Mon, May 28, 2001 at 01:36:57PM -0700, Joseph Carter wrote:
> > There is a 100% correlation between the graphics setup resulting in a
> > corrupt mode (top inch of the screen curving off to the right with the
> > default X weave background) and the lockup, but the lockup actually
> > happens after the corrupt mode has been initialised.
>
> I notice when crashes happen to me with Radeon (100% of the time using
> anything as complex as a game after a few seconds) the monitor often goes
> black and complains that the video signal being sent is outside
> recognizable parameters (as opposed to simply not present any longer.)
Indeed, I occassionally see the same effect.
> Given that you describe the monitor displaying funny things, I bet the
> monitor timing is affecting what you're seeing (and if my monitor is less
> tollerant, perhaps this is also what I'm seeing?)
Yes. However, it *never* happens on this box after X initialisation
has succeeded. Descent3 is unplayable on the Mesa-3.5 branch due to
bad rendering, but quake3 and tribes2 work flawlessly and indefinitely
once X gets itself started. I've had an X desktop up for about a week
quite happily on that board. Gears sits churning away at a merry
1400fps or so for as long as I want to let it run.
> I was hoping my problems were perhaps VIA-only issues. It would seem I'm
> wrong there.
I'm using VIA Irongate too.
--Stephen
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
