Andy Dustman wrote: > I managed to get the r200 driver working again by doing a complete CVS > install. Some notes: > > * The card does now seem to generate interrupts at about the same > frequency as the current mode's vertical refresh. > > * Surprisingly (for me, at least), glxgears is now running at about > 2000+ fps and consuming about 70% CPU. I expected a lower frame rate > (equal to vertical refresh) and minimal CPU usage, but my expectations > may be unrealistic. > > * Quake3 still crashes after a few minutes, but with an error I haven't > seen before: > > r200WaitForFrameCompletion: drmRadeonIrqWait: -16 > > It did this on two separate occasions. Machine locks up, although I > believe on one occassion SysRq still worked. > > * Setting R200_DEBUG=sanity and running glxgears *immediately* locks the > machine hard with no output.
Hmm. What happens if you pipe the output to a file? Keith ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
