Sorry in advance if this is the wrong place to ask.

Hello, everyone. I’ve recently gotten back into NixOS and immediately noticed that NVIDIA is buggy. (no surprise there) I’ve searched far and wide and it seems that no one else has these bugs? (I am most likely wrong though) I’ve gone mad trying to fix these two.

Here’s some extra info:

This is not distro exclusive, i’ve tried on fresh installs too.

I am using 565 with an RTX 3060 gpu.

I am on wayland/hyprland.

Curiously enough, this doesn’t happen on native games such as Metro 2033 or HOI4, only on proton.

apologies for the shitty gameplay and recording, and thanks.

  • fxomt@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    50 minutes ago

    Well, i’m fucked. I think i’m going to have to return to windows.

    I’ve learned my lesson, NEVER buy nvidia.

    thanks for all the help everyone, and happy holidays :)

  • RedWeasel@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 hours ago

    Does hyprland support explicit sync at all? That sounds like the explicit sync issue that was fixed earlier this year.

    Edit: Could run waycheck and see if linux-drm-syncobj-v1 (explict sync) is listed. I looked for NixOS and it “should” be supported, but best to double check.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      Yup, explicit sync is implemented on Hyprland, i tried waycheck.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      15 hours ago

      lmao yeah, you get used to it eventually. I can’t play on 90 FOV anymore, it seems small now 😅

  • Malix@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    13 hours ago

    try disabling the gsp, helped a lot with weird stutters on my system (kde/plasma, wayland, 3090, 565 driver).

    IIRC it was just setting NVreg_EnableGpuFirmware=0 to nvidia module

    edit: only works for the regular nvidia driver, not for nvidia-open

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      13 hours ago

      I disabled it, but nothing changed (i used regular NVIDIA and made sure it was disabled, too), but thank you

      • Malix@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        13 hours ago

        probably asking the obvious, but you did the … whatever mkinitcpio does, after changing the module’s config? Totally derped with that myself and wondered why my new settings didn’t take x)

        • fxomt@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          12 hours ago

          I use nixos and it doesn’t use mkinitcpio. Rebuid, reboot, and it works. I also made sure I disabled the GSP using nvidia-smi, so I’m sure that it isn’t the problem.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      54 minutes ago

      Well fuck me, X11 doesn’t have this issue at all. but i use wayland because X11 has its own set of bugs that causes me headaches. It’s a lose-lose for me.

  • morbidcactus@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    13 hours ago

    I’ve got a 4070ti running most recent nvidia-open on arch and haven’t had that happen, but I don’t tend to run with vsync often.

    What proton version are you running this on? Had some weird almost microstutters in cutscenes playing DA:Veilguard through moonlight on my steamdeck. Swapping to experimental resolved that, think it was one version of proton-ge that I had the issue with.

    Do you have vrr enabled by any chance?

    Are you running through gamescope? Have had grief with gamescope and nvidia, but that was mostly with hdr.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      52 minutes ago

      Many old games have vsync enabled by default :/ happens with all proton versions (I use ge), don’t use vrr or gamescope, but I’ll try on experimental again JIC if I was wrong (god I hope, lol) thanks for the tip.

      edit: experimental didn’t work either :(

  • boegy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    14 hours ago

    I had this happen on Fedora with amd cards as well. At the time I was using riverwm which is based on wlroots. I tried a few other WMs that also used wlroots and had the same problem, so I think the issue is somehow related to wlroots but I don’t know enough about it to be sure.

    When I tried on KDE Plasma (Kwin) I had no issue. So you may want to try Plasma or Gnome and see if the issue persists.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      13 hours ago

      Tried plasma, the bug was “fixed”, but the performance was horrid.

      fyi, hyprland isn’t wlroots anymore, its standalone :)

      • boegy@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 hours ago

        ok, I haven’t used hyprland so I wasn’t sure. The wayland tiling WMs I tried all had the same problem so I don’t know what the underlying cause is. I personally don’t have performance issues on wayland plasma and I don’t have an nvidia card in a linux system so I can’t test it further. I hope you are able to figure it out.