cross-posted from: https://lemmy.dbzer0.com/post/30765479

I updated my graphics drivers from nvidia 470 to nvidia 560 due to issues running certain games. It’s fixed my gaming issue but reintroduced the problem that kept me from updating for so long.

After setting my computer to “suspend,” it wakes up to this screen on all monitors. I am unable to scroll up or type further commands, my only option is to reboot the machine.

  • My graphics card is: NVIDIA Corporation GP104 [GeForce GTX 1070]
  • Nvidia driver version: 560.35.03
  • My desktop environment is Cinnamon X11. (This does not occur on Wayland, but there is no Cinnamon Wayland.)

I can’t make heads or tails of this error screen. The best I can understand is the “Fixing recursive fault but reboot is required!” line. How can I get more information? Does anyone have any ideas on how I can fix this? Thanks in advance.

Edit: It seems important to mention this is happening only on X11 (Pop default and Cinnamon), and not on Pop!_OS on Wayland.

  • insomniac_lemon@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    1
    ·
    12 minutes ago

    I have the same issue on an Arch derivative with XFCE and a 1050Ti. From what I can find online this is related to a change with SystemD, though when I tried the suggested fixes they didn’t seem to work.

    It has been a while since this issue started and updates seem to have not fixed it (though I am not currently updated). Annoying especially as I used to use my computer to wake up.

  • 👍Maximum Derek👍
    link
    fedilink
    English
    arrow-up
    3
    ·
    19 days ago

    I don’t have a solution, but I have the same problem. I’ve been on the 470 drivers as a result.

    • riquisimo@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      19 days ago

      I would have stuck with 470, but modern games need the 500 drivers. I couldn’t get Metaphor ReFantazio working on 470, and I couldn’t get the latest Baldur’s Gate 3 patch working without updating either.

      470 is from 3 years ago at this point. There were going to be more problems moving forward if I didn’t update.

  • Telorand@reddthat.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    19 days ago

    I might be remembering wrong, but I think there was an issue with making a huge leap in the driver version, recently. Like, you would need to go to 550 first, then go to 555 or 560 (something like that).

    Maybe someone with a better memory can corroborate or correct me.