On Sun, 2002-08-11 at 05:01, Brian T. Schellenberger wrote: > On Saturday 10 August 2002 04:47 pm, Michel D�nzer wrote: > | On Sat, 2002-08-10 at 04:44, Brian T. Schellenberger wrote: > | > First, thank you very much for responding! > | > > | > On Friday 09 August 2002 06:32 pm, Michel D�nzer wrote: > | > | On Wed, 2002-08-07 at 05:10, Brian T. Schellenberger wrote: > | > | > I've always had occaisonal problems with refreshes not properly > | > | > taking place, but since I've installed XFree86 4.2, it has gotten > | > | > much worse. > | > | > > | > | > If I invoke "xv", for example, on multiple pictures, then when I go > | > | > to the next picture it will very frequntly fail to properly refresh > | > | > the picture. For example, if the first picture is 200x200 and the > | > | > second is 400x200, then it will typically be the case that once I hit > | > | > the spacebar, I see the original picture on the left half of the xv > | > | > window and the right half of the new picture on the right half. > | > | > > | > | > The other program where I notice this frequently is vncviewer. It > | > | > has always had some noticable refresh problems, but they seem to be > | > | > markedly worse now. > | > | > | > | I assume Option "NoAccel" fixes the refresh problems? If so, try > | > | playing with the "XaaNo..." options described in the XF86Config-4 > | > | manpage to isolate an offending acceleration function. I'd guess the > | > | ones related to Pixmaps would be a good start. > | > > | > This is a very logical assumption. Unfortunately, it's not true. > | > > | > If I try setting NoAccel, the problem still occurs; it's not even > | > improved (that I can tell) by setting the option. > | > | Well, the CPU draws every single pixel without acceleration, so this > | sounds like a problem with the apps (unlikely I think), the hardware or > | maybe some kind of PCI configuration? > > The main application that's causing trouble being xv, which has been, to say > the least, *very* stable, I'm making the starting assumption that it's not an > application error, but of course it could be an error that is finally being > exposed. The problem definately got worse when I installed the 4.2 version > of XFree86, though, and I'm still using the same version of xv (of course, > since it hasn't changed in nearly a decade, I think), so X would seem to be > somehow involved. > > Also, I'm afraid that "PCI configuration" sounds dangerously close to hardware > to me, and I don't really even know what you mean by it. > > Would you care to elaborate?
I was thinking of something related to Write Combining or PCI latency... > PS: FWIW, the trick of "pre-reading" all the images (page forward and back in > xv) usually solves or at least greatly mitigates the problem. > > Also, an "xrefresh" always solves it, and is very fast if optimization is on; > I supposed I could always hack the xv code to force one after every image > change but this seems a little silly . . . ...indeed, and I wouldn't expect this to reliably help with a problem close to hardware. Just to get this straight, you aren't using any special options, are you? -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
