Am 2004.10.12 03:37:05 +0200 schrieb(en) Ian Romanick: > I was trying to test the latest version of my ReadPixels work to make > sure I didn't break anything on big-endian. However, it seems someone > beat me to it in the Rage128 driver. :) In a nutshell, I can get one > frame of gears, and then the 3D engine is toast. After that frame is > drawn, gears is at 100% and X is unresponsive. When I kill gears, > everything goes back to semi-normal. If I run another 3D program, I get > an empty (just a frame!) window. > > Looking at the output from R128_DEBUG=all, it appears to be stuck in > r128EmitHwStateLocked. > > That single frame of gears is also wrong. The colors are pinks and > purples. I suspect this may just be a byte-ordering problem. I notice > that the driver wants to use BGRA for primary color, but I suspect the > hardware really wants ARGB. Ditto for secondary color / fog. > >
It might be unrelated (and just some other silly mistake/problem): Using my local version of radeon (r100) driver converted to "t_vertex" I discovered a similar problem recently. 1) running glxgears I get the "hang with only mousepointer moving" -> reboot needed. 2) setting tcl_mode=0 and running glxgears -> instant reboot 3) other software seems to work fine, for example q3 or the projtex test. 4) running glxgears with the "original" driver from mesa-cvs works. I have to check with an older version of mesa and modified radeon driver, but as I recall it did work well somewhen in the past. greetings, Andreas ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
