From 9c6043f34f6c2b28b2dee79d3f68ac243d362d23 Mon Sep 17 00:00:00 2001 From: taradiddles Date: Fri, 25 Nov 2022 08:41:21 +0200 Subject: [PATCH] fix typo / rephrase --- docs/troubleshooting/intel-igfx-troubleshooting.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/troubleshooting/intel-igfx-troubleshooting.md b/docs/troubleshooting/intel-igfx-troubleshooting.md index de0a35e..7f89fce 100644 --- a/docs/troubleshooting/intel-igfx-troubleshooting.md +++ b/docs/troubleshooting/intel-igfx-troubleshooting.md @@ -24,11 +24,11 @@ If you are unsure as to which parameter works with your kernel, check whether your kernel log from your latest boot has a message containing "i915: unknown parameter". -## Fix tearing (glithes/artifacts/corruption/...) +## Fix tearing (glitches/artifacts/corruption/...) -By default Qubes OS uses the framebuffer/modesetting driver (`fbdev`). An issue -with `fbdev` is that without compositing VM windows exhibit graphical artefacts -(dom0 is unaffected). Workarounds: +By default Qubes OS uses `fbdev`, the framebuffer/modesetting driver. An issue +with is that without compositing VM windows exhibit graphical artefacts (dom0 is +unaffected). Workarounds: * enable compositing; it is enabled by default in XFCE (if it was disabled for some reason, re-enabling it is done in "Window Manager Tweaks"; restarting @@ -37,8 +37,8 @@ with `fbdev` is that without compositing VM windows exhibit graphical artefacts [faq](https://faq.i3wm.org/question/3279/do-i-need-a-composite-manager-compton.1.html) mentions using `compton`). - * or switch to the `intel` driver (**for some users the `intel` driver is - unstable, triggering random crashes from oopses to hard reboots !**). + * or switch to the `intel` driver (**Note - for some users the `intel` driver + is unstable, triggering random crashes/reboots !**). Create `/etc/X11/xorg.conf.d/20-intel.conf` and fill it with ```