On Thu, 2009-03-19 at 22:32 -0500, Greg Rivers wrote: > On Thu, 19 Mar 2009, Robert Noland wrote: > > > On Thu, 2009-03-19 at 15:01 -0500, Greg Rivers wrote: > >> On Wed, 18 Mar 2009, Robert Noland wrote: > >> > >>> Ok, so it isn't the gart caching... Can you get me a pointer to a > >>> screenshot? > >>> > >> > >> fetch http://www.tharned.org/rv380-drm-issue.tbz > >> This archive contains various logs and system configuration files as well > >> as screen shot images. Look at the README file for a description of the > >> images. > >> > >> > >>> What is garbled exactly? Is the damage constrained to specific windows > >>> or it it the entire framebuffer? > >>> > >> > >> The entire frame buffer is garbled; switching to syscons and back seems to > >> change the way it's garbled. However, the interior of an xterm window is > >> never garbled. I'm running a dual-head configuration with the frame > >> buffer spanning both monitors. > > > > Ok, I thought that I had already fixed this up, but I missed this > > spot... Please try this patch. > > > > It's still garbled with this patch too. Any other ideas? Just let me > know when it's time for me to buy a different video card. :-)
So, what I noticed today is that the difference between your ok and garbled xorg.logs seems to be the ring pointer contents not being empty... I haven't really figured out why that is yet... robert. > -- > Greg Rivers -- Robert Noland <rnol...@freebsd.org> FreeBSD
signature.asc
Description: This is a digitally signed message part
