[SOLVED] Graphic bug with nvidia driver and linux 5.16

heybix · 2022-01-22 12:38:37

Hello,

I have graphic bug since I have installed linux 5.16.x: multicolored lines (aberrations) appear when I move my cursor and generally when anything moves on my screen.
If I use linux-lts kernel, the bug is already present, but disappears when I log out ang log in again.
I have strong feeling that the bug comes from nvidia drivers, no problem with nouveau. I have also tested version 510 of nvidia driver, but nothing changed.

The bug is present in X11 and Wayland session and also in GDM.

I use Gnome as desktop environment and nvidia drivers 495.46.

Does anyone have the same problem?

Last edited by heybix (2022-01-23 11:07:12)

seth · 2022-01-22 13:03:41

the bug is already present, but disappears when I log out ang log in again

https://wiki.archlinux.org/title/NVIDIA#Early_loading ?

Do you have an image of the artifacts?

heybix · 2022-01-22 13:34:21

Sorry, I have read the part you have linked, but I don't understand what an "image of artifact" means?

Long ago, I have added

MODULES=(i915 nvidia nvidia_modeset nvidia_uvm nvidia_drm)

to my /etc/mkinitpcio.conf file, in order to launch this kernel module early.

I never had problems until kernel 5.16. Now the bug appears.

I have tested commenting out this line, reloading configuration with

mkinitpcio -P

and rebooting, but the bug is always present.

seth · 2022-01-22 13:51:42

A photo that depicts the "multicolored lines"

initramfs as a guess based on the "fixed on next instance of GDM" condition.
But "i915 nvidia" sounds like this is an optimus system?? Are you actually running on the nvidia chip?

glxinfog -B
eglinfo | grep -i vendor

Is GDM configured to run on X11 or wayland?
Where are the outputs wired - the nvidia or intel chip?
(In doubt post the Xorg log)

heybix · 2022-01-22 14:43:20

Yes, this is an optimus system Intel/Nvidia.

GDM is running on Wayland.

I think the output are wired to the intel chip because the nvidia card activity is at 0% according to nvtop and the intel chip is active according to intel_gpu_top.

Image of the bug : https://i.ibb.co/CbV5c1Q/vlcsnap-2022-0 … 36s138.png
A video : https://drop.infini.fr/r/TYDp0_jNhr#luq … gt5/AZle8=

$ glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics (CML GT2) (0x9bc4)
    Version: 21.3.4
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.3.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.3.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

$ prime-run glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 5928 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 2060/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 495.46
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 495.46
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 495.46
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

$ eglinfo | grep -i vendor

EGL vendor string: NVIDIA
EGL vendor string: Mesa Project
EGL vendor string: Mesa Project
EGL vendor string: NVIDIA

Last edited by heybix (2022-01-22 15:11:01)

seth · 2022-01-22 14:58:03

The problem is then rather w/ the intel module.

Please
1. edit your post and use "code" tags rather than "quote" tags and replace the oversized image w/ a link (the board has a 250x250 limit)
2. Try to move GDM to Xorg (iirc optimus on gnome wayland is still not a thing anyway)
3. Post the xorg log
4. See
https://wiki.archlinux.org/title/Intel_ … nable_fbc)
https://wiki.archlinux.org/title/Intel_ … flickering
https://wiki.archlinux.org/title/Intel_ … RI3_issues
https://wiki.archlinux.org/title/Intel_ … ver_(i965)

heybix · 2022-01-23 10:49:28

Thanks! I have followed https://wiki.archlinux.org/title/Intel_ … flickering.
Adding

i915.enable_psr=0

in kernel parameters fixed the bug !

Arch Linux

#1 2022-01-22 12:38:37

[SOLVED] Graphic bug with nvidia driver and linux 5.16

#2 2022-01-22 13:03:41

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

#3 2022-01-22 13:34:21

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

#4 2022-01-22 13:51:42

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

#5 2022-01-22 14:43:20

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

#6 2022-01-22 14:58:03

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

#7 2022-01-23 10:49:28

Re: [SOLVED] Graphic bug with nvidia driver and linux 5.16

Board footer