Created attachment 110136 [details] Example screen shot with artifacts Artifacts on the screen on notebook asus S301L. The laptop has a muxless video card. I use DRI_PRIME. $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x76 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 2 associated providers: 1 name:Intel Provider 1: id: 0x51 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 0 associated providers: 1 name:radeon DRI_PRIME=1 LD_LIBRARY_PATH=/opt/mesa-master/lib/ LD_PRELOAD=/opt/mesa-master/lib/dri/radeonsi_dri.so glxgears DRI_PRIME=1 LD_LIBRARY_PATH=/opt/mesa-master/lib/ LD_PRELOAD=/opt/mesa-master/lib/dri/radeonsi_dri.so amoeba Example screen shot as an attachment amoeba.jpg Uname: Linux mj 3.17-1-amd64 #1 SMP Debian 3.17-1~exp1 (2014-10-14) x86_64 GNU/Linux
Created attachment 110137 [details] dmidecode
Created attachment 110138 [details] lspci -v
Created attachment 110139 [details] dmesg
Created attachment 110140 [details] lspci (active radeon)
Created attachment 110143 [details] glxinfo
Created attachment 110144 [details] Example screen shot with artifacts
Does the v5 fix from bug 60879 help by any chance?
I applied the patch to the mesa https://bugs.freedesktop.org/attachment.cgi?id=106530 And applied https://bugs.freedesktop.org/attachment.cgi?id=98258 to radeon module no changes. The screen still "chess".
Do the artifacts still occur on current Mesa git?
Thanks, now OGL apps looks good.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.