this post was submitted on 05 Jun 2026
7 points (100.0% liked)

KDE & Plasma users

3423 readers
27 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE's software runs on GNU/Linux, BSD and other operating systems, including Windows.

founded 6 years ago
MODERATORS
 

UPDATE: Long story short...I still have no clue. Unplugging my second monitor got the proprietary drivers working properly on KDE Neon, but not on any Arch based distro I tried. I tried kernels from 6.1 to 6.18, and drivers all the way from 470 (disaster) to 595, dkms and open. Followed all the advice on the Arch docs regarding power management, blacklisting, etc...

Soooo....I don't know. But I'm up and running with a single monitor on an Ubuntu based distro, which isn't ideal, but right now I'll take what I can get.

you are viewing a single comment's thread
view the rest of the comments
[–] wise123@sh.itjust.works 3 points 1 week ago* (last edited 1 week ago) (2 children)

First Never download and install nvidia drivers from their websites (unless you know what you are doing).

second glitching is a broad term what do you mean by glitching?

screen tear, artifacts, ghosting?????

We gonna need more data as in logs.

but i would recommend you follow proper steps from arch wiki.

But i know everybody dont like to read so this might help https://youtu.be/vrFPcCYUj2c (this is still sort of my polite way to say RTFM)

[–] Adderbox76@lemmy.ca 2 points 1 week ago (1 children)

Thanks for replying.

I do indeed know what I'm doing. This particular problem just has me stumped.

As I mentioned, I am working my way through the relevant parts of the Arch Wiki, because, as you say, I'm a person who tries to RTFM. I was posting here to see if anyone had some across some specific issue that I may have missed from a recent update in the last few months. Wasn't looking for a replacement to RTFM; was looking to see if there was something specific I might be missing.

As for logs: This is the link to the when the problem began, back when I was under the impression that it was a hardware problem (specifically the power supply) I know now that it's not a hardware issue, but the logs I posted in the comments still apply.

https://lemmy.ca/post/59824776

[–] wise123@sh.itjust.works 1 points 1 week ago (1 children)

hmm well i never had this specific issue and im not an expert in driver issue.

SO TL;DR I cant help you. sorry.

BUT (AND I KNOW IT SOUNDS DUMB or you might be doing it already)

I would recommend you do some A/B testing.

keep your setup the same and change only one thing at a time (like driver version, Wayland vs X11, kernel options, or compositor) so you can pinpoint exactly which change is causing the problem.

Maybe take a look into nvidia-{open,dkms,beta, etc} packages.

or something else entirely.

This might help you to at least get your system going so you can do your Video editing, graphic design, 3d modelling etc. If u want to get your system up and going right now(deadlines or something else) its not a bad idea to temporarily install windows and attack this problem later in free time with no pressure.

I hope you find a solution to the problem.

[–] Adderbox76@lemmy.ca 2 points 1 week ago

Worst case scenario is I end up reinstalling the X Display server for now. No real time constraint. Just annoying.

[–] eldavi@lemmy.ml 1 points 1 week ago (1 children)

First Never download and install nvidia drivers from their websites (unless you know what you are doing).

are they incorporated upstream now-a-days?

[–] Adderbox76@lemmy.ca 1 points 1 week ago (1 children)

I'm not at my desktop at the moment, but IIRC from putzing around last night trying various fixes, I believe the upstream built in prop drivers are at version 580 or something, while NVIDIA direct is at 595. Tried both. No joy.

[–] eldavi@lemmy.ml 1 points 1 week ago

go older until one works.