7900 XTX - random screen artifacts and issue

Hello all,

I’ve dug around to figure this out for a while but I’m at a loss. I just built a new PC (7950x3d based), and put my 7900 xtx in it.

I did a fresh install and everything is running fine, with the exception of the screen issues. I’m having random screen / application flickering; this seems most prevalent when I’m moving windows, or maximizing applications. For example, I maximize an app on one screen which causes my other screen to momentarily go to black. Or applications will randomly have a vertical slice ‘shifted’ up. Other times if I’m moving applications other background apps will flicker very quickly.

I’ve tried reinstalling mesa, checking and rechecking everything I can think of. Examining all bios settings… I’m at a loss. This card was fine in my previous setup (3900x based).

I’m primarily using the RT kernel, but the issue is there with the stock kernel too.

I found this:

Sep 11 14:53:54 user kwin_wayland[1649]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

inxi -Ga

Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: Sapphire NITRO+ driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
    process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-1, DP-2, HDMI-A-1, HDMI-A-2 empty: Writeback-1
    bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 9440x3960 display-ID: 0
  Monitor-1: DP-1 pos: bottom-r res: 3440x1440 size: N/A modes: N/A
  Monitor-2: DP-2 pos: top-right res: 3440x1440 size: N/A modes: N/A
  Monitor-3: HDMI-A-1 pos: bottom-l res: 3440x1440 size: N/A modes: N/A
  Monitor-4: HDMI-A-2 pos: middle-c res: 2560x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 18.1.8 DRM 3.57 6.10.2-rt14-arch1-2-rt) device-ID: 1002:744c
    memory: 23.44 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.295 layers: 4 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 XTX (RADV NAVI31) driver: mesa radv v: 24.2.2-arch1.1
    device-ID: 1002:744c surfaces: xcb,xlib,wayland


Any help or suggestions greatly appreciated!

Cheers
J1m

Can you share the output of pacman -Q | grep -E "mesa|radeon|amd"

Does it also happen under X11 or is it only Wayland?

Hi Dalto - thank you for the response.

Yes - it is happening on x11 too, one of the first things I did was try it there.

amd-ucode 20240909.552ed9b8-1
lib32-mesa 1:24.2.2-1
lib32-vulkan-radeon 1:24.2.2-1
libva-mesa-driver 1:24.2.2-1
mesa 1:24.2.2-1
mesa-utils 9.0.0-4
vulkan-radeon 1:24.2.2-1
xf86-video-amdgpu 23.0.0-2

I also have this in my logs but I am not seeing any of the issues you are so it may be unrelated.

I also have the same driver versions as you. My inxi looks more or less the same as well.

Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: XFX RX-79XMERCB9 driver: amdgpu v: kernel arch: RDNA-3 pcie:
    speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 off: DP-2
    empty: DP-3,Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: none
    empty: DP-4,HDMI-A-2,Writeback-2 bus-ID: 0e:00.0 chip-ID: 1002:164e
    class-ID: 0300 temp: 44.0 C
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1354x381mm (53.31x15.00")
    s-diag: 1407mm (55.38")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: left model: Dell S3220DGF
    serial: 81MVF43 res: 2560x1440 dpi: 93 size: 697x392mm (27.44x15.43")
    diag: 806mm (31.7") modes: max: 2560x1440 min: 720x400
  Monitor-2: DP-2 mapped: DisplayPort-1 note: disabled model: Dell S3220DGF
    serial: J4MVF43 res: 2560x1440 dpi: 93 size: 697x392mm (27.44x15.43")
    diag: 806mm (31.7") modes: max: 2560x1440 min: 720x400
  Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: primary,right
    model: Dell S3220DGF serial: 15LVF43 res: 2560x1440 dpi: 93
    size: 697x392mm (27.44x15.43") diag: 806mm (31.7") modes: max: 2560x1440
    min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast
    surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 18.1.8 DRM 3.57 6.10.7-1-cachyos) device-ID: 1002:744c
  API: Vulkan v: 1.3.295 layers: 4 surfaces: xcb,xlib device: 0
    type: discrete-gpu hw: amd driver: mesa radv device-ID: 1002:744c device: 1
    type: integrated-gpu hw: amd driver: mesa radv device-ID: 1002:164e

:thinking:

I’m considering a reinstall… but I really don’t need the hassle.

I would be pretty skeptical that a reinstall would solve that problem.

I know, I am too.

It’s driving me nuts though, and this card was 100% in my last build.

Have you updated the MB BIOS to the latest version and ensured the settings are sound?

Yep. BIOS is the latest version, gone through everything I can think of in there. No overclocking, etc. and PC is running great apart from those issues.

https://wiki.archlinux.org/title/AMDGPU#Screen_artifacts_and_frequency_problem

I also have hardware acceleration set and accelerated video decoding with an RX590 AMD.

[ricklinux@rick-ms7c37 ~]$ pacman -Q | grep -E "mesa|radeon|amd" 
amd-ucode 20240909.552ed9b8-1
lib32-libva-mesa-driver 1:24.2.2-1
lib32-mesa-vdpau 1:24.2.2-1
lib32-vulkan-radeon 1:24.2.2-1
libva-mesa-driver 1:24.2.2-1
mesa 1:24.2.2-1
mesa-utils 9.0.0-4
mesa-vdpau 1:24.2.2-1
vulkan-radeon 1:24.2.2-1
xf86-video-amdgpu 23.0.0-2

https://wiki.archlinux.org/title/AMDGPU

Not sure if this would help. Also posted about the screen artifacts.

Hi Rick

I actually found and read through that earlier tonight, but I’ve had the same issues with all screens set to 60hz… no change.

I did find this: https://www.reddit.com/r/archlinux/comments/1eaxjzo/linux_610_causes_screen_flicker_on_amd_gpus/

And also noticed these errors:

Sep 11 21:53:21 user kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Sep 11 21:53:21 user kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait

I hadn’t seen / found / noticed these before, but they were constant. My PC also crashed earlier while I was AFK, I noticed the fans running loud and it was unresponsive.

I did install the LTS kernel and the errors aren’t appearing any more, plus I haven’t had tearing or flickering issues since.

Seems to point to a kernel issue(?). and there is a patch referenced in the reddit article above, but my config doesn’t fit the >144Hz + HDR profile that was originally logged in the bug report.

Appreciate the help! I’ll probably stick with the LTS kernel and try newer ones as they appear.

J1m

2 Likes

Hello @j1m!

I’m sure you’ve already tested this, but can you disable Freesync on your monitors to test it with the normal kernel?

I had the same problem back then with Freesync where I got a black screen from time to time. Since then, at least for me, it hasn’t happened again.

3 Likes

Hi Shadow

No, I hadn’t checked freesync, but I knew it was off on two of the screens, and didnt realize it was an option on one of the other.

It’s off now, and I’ve installed the stock kernel and it appears to be resolved! so far at least!

Thank you!

2 Likes

Usually this only happens on Freesync with higher refresh/resolution rates. Thanks @shadow359 for your insight!

2 Likes

i just add this point : no Freesync from kernel 6.9 or more

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.