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.cafeEnglish
    0·
    25 days 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.

    • riquisimo@lemmy.dbzer0.comOPEnglish
      0·
      24 days ago

      So my solution was to switch to Wayland, and since the only officially-supported Wayland on Pop is their default GNOME, I learned how to name GNOME look more cinnamon-like.

      I’ve got new issues now, like occasionally one of my monitors will just freeze on wakeup and I’ll have to toggle it on and off in display settings but it’s easier than making a full jump to mint right now. (As that seems to be my best bet for stable cinnamon)

      • insomniac_lemon@lemmy.cafeEnglish
        1·
        1 day ago

        Hey, I updated recently and it seems like it’s now fixed for me on X with driver version 565.77 (not that it’s necessarily the exact fix version, and it may be a systemd fix too).