On 2017/07/13 19:57, Mark Kettenis wrote: > > Date: Wed, 12 Jul 2017 13:11:25 +0100 > > From: Stuart Henderson <s...@spacehopper.org> > > > > On 2017/07/12 07:46, Paul de Weerd wrote: > > > Note that vncviewer was never really blazing fast, but at least it was > > > workable. Obviously, vncviewer is doing something weird because other > > > programs don't seem affected by whatever changed (I'm guessing it's > > > the switch to using the modesetting driver on my hardware). > > > > Confirmed here. Switching back to the intel driver fixes it: > > > > Section "Device" > > Identifier "Intel Graphics" > > Driver "intel" > > EndSection > > Is this regression important enough to hold off the commit of the > driver selection change until we have a better understanding of what > is going wrong here?
I don't think it's important enough to hold off at this point. We have a viable workaround for now, imho we should get more people running with modesetting to give us more experience with it. > And does this only affect Haswell or are others also affected? I don't have much of a range of hardware to test with, but I've just tried on an X201 (i7-620M - Ironlake), which is now using the modesetting driver by default too, and doesn't have a problem with vncviewer.
