-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Peter Suetterlin composed on 2018-12-14 17:34 (UTC):
Carlos E. R. wrote:
El 2018-12-13 a las 09:42 -0500, Felix Miata escribió:
Does it improve if you switch from intel to modesetting? All my intel GPUs that modesetting supports are using it. Last official update of xf86-video-intel was 3 summers ago.
I don't remember how to do that...
Reboot with a parameter?
If you look at /var/log/Xorg.0.log you'll see
[ 9.021] (==) Matched intel as autoconfigured driver 0 [ 9.021] (==) Matched modesetting as autoconfigured driver 1 [ 9.021] (==) Matched fbdev as autoconfigured driver 2 [ 9.021] (==) Matched vesa as autoconfigured driver 3
It just goes through the list until it finds one. So just uninstall the intel driver and it'll use modesetting.
Or, use /etc/X11/xorg.conf*, such as /etc/X11/xorg.conf.d/50-device.conf, to specify which driver to use. Removing the ancient xf86-video-intel package ultimately seems most sensible - no bandwidth wasted storing or updating unused software.
This is what I have done, remove the package. Easier, no config editing, leave to automatics. But first, as I had done an update, I tried to reproduce the issue, and yes, it did. Not in its worst manner, but yes, the artifacts are there. Then I removed the package and rebooted. I tried Amazon Prime Video with Chrome and it worked well, but I still need to go through Kodi, and an hibernation cycle to make sure, that will be later today. [...] Well, it is tomorrow now, and video seems to be working fine :-) - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlwWacMACgkQtTMYHG2NR9Wb3wCeLJ13sVGfLSkBD4hhawTrUz6F WIUAmQE6rp3E+dMgCLJvVUb15zYTjXU3 =ASq/ -----END PGP SIGNATURE-----