diff options
| author | Ivan Molodetskikh <yalterz@gmail.com> | 2024-06-26 11:24:01 +0400 |
|---|---|---|
| committer | Ivan Molodetskikh <yalterz@gmail.com> | 2024-06-28 10:39:35 +0400 |
| commit | 557702147553c56759139cffa45e293e784dbd91 (patch) | |
| tree | b800a98e20450bb585dc5507cc54c85f3e7e0ccf | |
| parent | 40aff3a094756b2cfa9c0ce48c1ab2be26b1f9ee (diff) | |
| download | niri-557702147553c56759139cffa45e293e784dbd91.tar.gz niri-557702147553c56759139cffa45e293e784dbd91.tar.bz2 niri-557702147553c56759139cffa45e293e784dbd91.zip | |
wiki: Mention wait for completion NVIDIA flickering workaround
| -rw-r--r-- | wiki/Getting-Started.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/wiki/Getting-Started.md b/wiki/Getting-Started.md index 02802955..bc1974b7 100644 --- a/wiki/Getting-Started.md +++ b/wiki/Getting-Started.md @@ -29,6 +29,14 @@ You can try the following: 1. Update NVIDIA drivers. You need a GPU and drivers recent enough to support GBM. 2. Make sure kernel modesetting is enabled. This usually involves adding `nvidia-drm.modeset=1` to the kernel command line. Find and follow a guide for your distribution. Guides from other Wayland compositors can help. +If niri runs but the screen flickers, try adding this into your niri config: + +``` +debug { + wait-for-frame-completion-before-queueing +} +``` + ### Asahi, ARM, and other kmsro devices On some of these systems, niri fails to correctly detect the primary render device. |