Mark Vojkovich <mvojkovi@xxxxxxxxxxx> writes: > That sounds like a driver issue. You might want to look through > the cvs history for suspicious changes. This one looks suspicious: > > http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/mga/mga_video.c.diff?r1=1.35&r2=1.36&sortby=date > > The description says: > > 85. Fix for Xv resolution loss problem with Matrox cards (Michael Lampe). > > but, if I recall correctly, some of the resolution loss issues > with Matrox cards were because the video scaler didn't have enough > bandwidth to display the full resolution. Reclaiming the resolution > in bandwidth challenging situations probably results in fifo underflows > which, at least on the NVIDIA cards that I'm familiar with, would > produce results like you are describing. I don't follow that at all. What do you mean by "resolution loss" and "reclaiming the resolution"? Looking at that change it seems like it just removed a bunch of functionality including the "accelerated 2x horizontal zoom" and didn't replace it at all. It also changed a couple magic constants. But I don't see how this code would make it work sometimes and not other times. Specifically how it would work fine for a while and then stop working completely. It seems more like a higher level state corruption. Like maybe it still things some other client is connected to the Xv port even though nothing is any more. Is there some way to query to see what X thinks is using the Xv scaler? Or whatever other state is being kept? xvinfo doesn't seem to change output at all when mplayer is running. -- greg _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
