[–] [S] 1 point 4 months ago* (last edited 4 months ago) (2 children)

I cannot use it without killing the programs that uses the Nvidia driver first (Niri itself uses it for example), which defeats the purpose of suspend. Nice try though, thanks!

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago* (last edited 4 months ago) (2 children)

    From Void handbook:

    Only first generation Maxwell, Kepler, and some Tesla cards support manual reclocking. Cards past Turing (GTX 16xx) support automatic reclocking. Graphics cards starting with second generation Maxwell (GTX 9xx) do not support reclocking because the linux-firmware collection is missing signed firmware blobs needed to reclock these cards past their boot frequencies.

    So it seems there is no hope for my card for nouveau? The gaming performance is terrible because it cannot reclock once in the game apparently. One positive side, suspend works now. :`)

    Edit: It was worth the try but no joy. Went back to no suspend state. :) At least it was easy thanks to dracut.

    Edit 2: No wonder why I didn't have a good performance on Arch too. It's because Nvidia didn't provide blobs for my card. :(

    Well I say what Linus said to Nvidia.

    Thanks again though!

  • source
  • parent
  • context
  • [–] [S] 2 points 4 months ago (2 children)

    To be fair, I was eyeing 9060 xt for some time and cannot buy it anymore since the price doubled because of AI-bros. Otherwise, I plan to, just can't yet. Maybe 5 more years stuck on GTX 1080 at this point, don't know.

    And yeah, Nvidia drivers suck.

  • source
  • parent
  • context
  • [–] [S] 1 point 4 months ago* (last edited 4 months ago) (4 children)

    Mine is 1080 and already dropped to legacy driver.

    By the way, just installed nouveau and on my first try, got bunch of DATA_ERROR but it's fine now. Though haven't tried a game yet, will try soon and report back.

    While doing this, found out about this: nouveau doesn't have support for power management for some cards and apparently mine is one of them.

    Check your sudo dmesg | grep -i nouveau and if you see pmu: firmware unavailable that's why your suspend or hibernate don't work (mine probably won't too, will see).

    Thanks again. :)

  • source
  • parent
  • context
  • [–] [S] 2 points 4 months ago* (6 children)

    Hmm, some resource-heavy games there. Sounds promising. Last time when I try to play resource-heavy games, I was getting 30-40 FPS where I usually get at least 75. There were playable but not fun that way. By the way, just checked and last time I tried NVK was 2 years ago!? I guess I'll give it a shot again. Thanks for reminding me. <3

    I also have an issue with suspend/hibernate and the like. Machine just shuts off. I haven’t figured that out for myself.

    This doesn't sound good. So it's possible my problem won't go away with nouveau. :/

    Edit: Which distro are you using by the way?

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago (8 children)

    Huh, last time I tried NVK was more than 6 months ago apparently. I'm actually interested in open drivers because proprietary ones are pain. Anyway, can you explain more? What kind of games are you playing, for how long on nouveau? It might be improved since I last checked.

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago*

    Yeah, the Nvidia proc only has three states: suspend, hibernate, resume

    I tried changing chvt 63 into chvt 2 so I can see what happens on resume more directly. By the way I didn't even know 63rd terminal existed.

    I got errors like these, it goes further but basically:

    void login: [13986.648494] BUG: using __this_cpu_read() is preemptible [00000000] code: nvidia-sleep.sh/18289
    BUG: using smp_processor_id() in preemptible  [00000000] code: nvidia-sleep.sh/18289
    BUG: using __this_cpu_read() is preemptible [00000000] code: elogind-daemon/831
    BUG: using smp_processor_id() in preemptible  [00000000] code: elogind-daemon/831
    

    I cannot use journalctl because this is runit, can dmesg though. It seems this could be a driver bug but not sure.

  • source
  • parent
  • context
  • view more: ‹ prev next ›