Main Display Monitor Artifacting

smelvin · 2025-10-04 22:31:35

Hello!

I've had this problem for a bit, my main monitor will just artifact, mainly by showing a black screen, flashing a bunch of static, and cutting in and out.

I've tried:
Reseating my GPU
Reinstalling Arch
Reinstalling Display Drivers
Swapping ports on GPU
Swapping Monitor Ports

Specs:
GPU: NVIDIA RTX 3080
CPU: Core i7-12700k
Graphics Platform: Wayland
Display Driver: 580.82.09

I run a triple monitor set up, two of them connected to display port (including my main one), and one connected via HDMI.

It will load properly and get me to the log-in screen without this happening, but as soon as I log in the artifacts start happening.

If there is any more info that would help please let me know!

Also, I believe this isn't a hardware issue because I run a dual boot with Windows 11 64-bit, and it works just fine over there.

Last edited by smelvin (2025-10-04 22:34:26)

Scimmia · 2025-10-05 02:42:23

What "log-in screen"? What Wayland compositor? Which driver package, exactly?

smelvin · 2025-10-05 16:54:22

Scimmia wrote:

What "log-in screen"? What Wayland compositor? Which driver package, exactly?

Sorry about taking so long to respond,

The log-in screen is just the users screen where I choose my account and then log in from there, It's not the terminal log in screen, I think it's specifically the one Plasma provides.

My compositor is Plasma, and the specific package I'm using is just nvidia from the main package repository.

seth · 2025-10-05 20:51:14

think it's specifically the one Plasma provides.

plasma-meta will drag in sddm-kcm what will drag in sddm, but there's no plasma-provided DM

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and since SDDM defaults to X11, your Xorg log, https://wiki.archlinux.org/title/Xorg#General

smelvin · 2025-10-05 21:52:38

Please post your complete system journal for the boot:
and since SDDM defaults to X11, your Xorg log

here's those! System Journal and Xorg log

In the system journal near the end I unplugged my monitor so I could access the terminal without blindly figuring out where the window is.

Last edited by smelvin (2025-10-05 21:54:08)

seth · 2025-10-05 22:08:01

Hybrid, nvidia-open and stale intel, server eventually runs on the nvidia chip, but first

Oct 05 17:42:17 foodcity kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
Oct 05 17:42:17 foodcity systemd-networkd[619]: wlan0: Link UP
Oct 05 17:42:18 foodcity systemd-coredump[928]: Process 883 (Xorg) of user 0 dumped core.
                                                
                                                Stack trace of thread 883:
                                                #0  0x00007f7bb909894c n/a (libc.so.6 + 0x9894c)
                                                #1  0x00007f7bb903e410 raise (libc.so.6 + 0x3e410)
                                                #2  0x00007f7bb902557a abort (libc.so.6 + 0x2557a)
                                                #3  0x000055c3ba26607e OsAbort (/usr/lib/Xorg + 0x15f07e)
                                                #4  0x000055c3ba2733d0 FatalError (/usr/lib/Xorg + 0x16c3d0)
                                                #5  0x000055c3ba268573 n/a (/usr/lib/Xorg + 0x161573)
                                                #6  0x00007f7bb903e540 n/a (libc.so.6 + 0x3e540)
                                                #7  0x00007f7bb977056c n/a (modesetting_drv.so + 0x1256c)
                                                #8  0x000055c3ba28e3b1 InitOutput (/usr/lib/Xorg + 0x1873b1)
                                                #9  0x000055c3ba13a6a5 n/a (/usr/lib/Xorg + 0x336a5)
                                                #10 0x00007f7bb9027675 n/a (libc.so.6 + 0x27675)
                                                #11 0x00007f7bb9027729 __libc_start_main (libc.so.6 + 0x27729)
                                                #12 0x000055c3ba13bcd5 _start (/usr/lib/Xorg + 0x34cd5)
                                                ELF object binary architecture: AMD x86-64
Oct 05 17:42:18 foodcity systemd[1]: systemd-coredump@0-1-927_928-0.service: Deactivated successfully.
Oct 05 17:42:18 foodcity systemd[1]: systemd-coredump@0-1-927_928-0.service: Consumed 123ms CPU time, 87.1M memory peak.
Oct 05 17:42:18 foodcity sddm[881]: Failed to read display number from pipe
Oct 05 17:42:18 foodcity sddm[881]: Display server stopping...
Oct 05 17:42:18 foodcity sddm[881]: Attempt 1 starting the Display server on vt 2 failed

i915 is in the initramfs, nvidia isn't - I'd try to swap that (remove the kms hook and any explicit mention of the i915 module and add the nvidia ones, see https://wiki.archlinux.org/title/NVIDIA#Early_loading (tough you won't need nvidia_uvm) - be aware that this might blow up the initramfs considerably for the nvidia firmware.
Also/alternatively delay the SDDM start, see https://bbs.archlinux.org/viewtopic.php … 8#p2256418 (but you'll have to edit the sddm.service instead of the lightdm one)

smelvin · 2025-10-05 22:43:13

Okay, so I checked my conf for mkinit, and I didn't see any modules there. I removed kms from the hooks and added the nvidia modules and after regenerating the initramfs and restarting to test, my main monitor did not turn on. I had to unplug it and plug it back in to get it to work.

Here's the system log and here's the Xorg log.

Last edited by smelvin (2025-10-05 22:43:28)

seth · Yesterday 14:13:08

Status quo ante, except the initial X11 crash is now gone (likely because of the earlier nvidia load)
Do you get the same w/ the non-open nvidia kernel module and in doubt https://wiki.archlinux.org/title/NVIDIA … P_firmware (latter will not work w/ nvidia-open!)

Can you disable the IGP in the UEFI?
Makes me wonder whether you're running into some undue https://wiki.archlinux.org/title/PRIME#NVIDIA (since it's default for Ampere. You'd want to test to set this to an unconditional "On")

Arch Linux

#1 2025-10-04 22:31:35

Main Display Monitor Artifacting

#2 2025-10-05 02:42:23

Re: Main Display Monitor Artifacting

#3 2025-10-05 16:54:22

Re: Main Display Monitor Artifacting

#4 2025-10-05 20:51:14

Re: Main Display Monitor Artifacting

#5 2025-10-05 21:52:38

Re: Main Display Monitor Artifacting

#6 2025-10-05 22:08:01

Re: Main Display Monitor Artifacting

#7 2025-10-05 22:43:13

Re: Main Display Monitor Artifacting

#8 Yesterday 14:13:08

Re: Main Display Monitor Artifacting

Board footer