When I began having issues with choppiness a few months back, I thought I had troubleshot all software possibilities, which led me to conclude that it was a hardware issue.

I tested every piece of removable hardware (graphics card, power supply, etc…) and determined after all of that, that it must be the processor itself, and so bought myself a new (to me) computer.

After reinstalling everything, this new computer is doing the same thing, and I realized that there was one very important thing that I never originally checked…the compositor.

And it seems that, somehow, that is the issue, but I’ll be darned if I’ve been able to figure out how to fix it.

Tried on 3 different distros (Manjaro, CachyOS, Neon)

Somewhere between Wayland, Plasma 6, and the NVIDIA Proprietary drivers, things are glitching out. Everything works fine under Nouveau, but of course that keeps me from being able to do more heavy lifting like Blender, Resolve, etc…

Tried the Proprietary drivers both from within the distros themselves and directly downloading and installing the drivers from the NVIDIA website.

Back when the trouble first began and I was working under the assumption that it was a hardware issue, I tried multiple power supply units to no effect. I then tried using an older NVIDIA card which gave the same issue (Nouveau Good/Proprietary Bad). Reset and later replaced the RAM.

While I slowly work my way through the Arch pages regarding NVIDIA drivers, I figure I may as well ask if anyone has had success fixing glitches between Wayland, Plasma, and NVIDIA. Research says that such glitches are apparently pretty common with the newer versions of plasma. Looking for any tricks I may not have found yet.

Thanks

Edited - And no, switching to AMD just isn’t in the cards right now. I barely had enough scraped together to get a used desktop off of Ebay. There no chance I’ll be able to afford an AMD GPU equivalent to my GTX 3060.

  • wise123@sh.itjust.worksEnglish
    3·
    3 days ago

    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)

    • Hemingways_Shotgun@lemmy.caOPEnglish
      2·
      3 days ago

      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.worksEnglish
        1·
        3 days ago

        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.

        • Hemingways_Shotgun@lemmy.caOPEnglish
          2·
          3 days ago

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

    • eldavi@lemmy.mlEnglish
      1·
      3 days ago

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

      are they incorporated upstream now-a-days?

      • Hemingways_Shotgun@lemmy.caOPEnglish
        1·
        3 days ago

        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.

  • RedWeasel@lemmy.worldEnglish
    1·
    3 days ago

    Do you have any usb devices or other hardware attached? Do you have any background scripts running? Try running without those installed. if possible. If you copied your home directory, try a clean user.

    For example, I have an external light meter I made from instructions online and the script for it was accessing the brightness of the monitor with ddcutil and causing a similar spike. I rewrote it to use kscreen-doctor.