7
Plasma, Wayland & NVIDIA Proprietary Drivers giving issues (lemmy.ca)
submitted 4 months ago* (last edited 3 months ago) by to c/kde@lemmy.ml
9 comments fedilink hide all child comments
 

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
[–] [S] 3 points 4 months ago (2 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 4 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •