• 4 Posts
  • 236 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
















    • For what I assume is a security precaution, SysRq is disabled by default in Fedora, and you need to go enable it if you want to be able to recover when shit like this happens - the link shows how, and explains what each letter does.
    • It’s honestly hard to say what caused it, but you could check your system logs and see what looks suspicious around the time of the crash. journalctl, dmesg and your steam logs (in ~/.steam/steam/logs usually) could be worth a look, or worth showing someone else at least if you aren’t sure whats going on in there.
    • I’d avoid actively trying to cause it, but if it happens again you handled it exactly how I’d try handle it. Having SysRq enabled would let r-e-i-s-u-b handle it more gracefully than a forced shutdown at least!



  • and a Nvidia 2080ti

    Do you know which Nvidia driver you’re using currently?

    There’s an established open-source Nouveau driver that Ubuntu & Mint probably defaulted to, a bleeding-edge open-source NVK driver that is still very early in it’s development, and a proprietary Nvidia driver that Nobara probably tried, as it’s kinda what you’d want for gaming.

    The other question would be if you’re using Wayland or X11 underneath your desktop environment?

    It should be listed in Settings > System > System Details, under the heading “Windowing System” if you’re using GNOME.

    Wayland has better multi-monitor support than X11, but the proprietary Nvidia driver has a few teething problems with Wayland at the moment - a new 555 beta driver update should be coming this week with proper fixes for the sync/screen-tearing issues people have been experiencing.