I remember when Proton launched it was like magic playing games like Doom and Nier Automata straight from the Linux Steam client with excellent performance. I do not miss the days of having the Windows version of Steam installed separately.

  • Twospoons@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    19
    ·
    9 months ago

    If only Linux wouldn’t Bork my whole install when I try to switch to 144hz on my monitor.

    • atmur@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      16
      ·
      9 months ago

      That’s a weird one. I’ve been running a 165hz primary monitor and a 144hz secondary for a while on AMD, Nvidia, and Intel GPUs. I’ve never had any trouble with them.

      Were you using Wayland or X11?

      • Twospoons@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        9 months ago

        Honestly don’t remember which I was running. Was a new install of testing Endevour OS with an Nvidia card. Changed the refresh rate through the display settings to 144 and it went black and never came back. Fixed it back to 60 through cli boot eventually but it never liked changing it off that.

        • BURN@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          I can verify I’ve had this exact problem. Never found a solution. My Linux box has been changed to Manjaro so it’ll work now

    • hperrin@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      9 months ago

      Are you using some weird video setup? I’ve had some issues with DisplayLink but never anything worse than needing to reboot before it will work again.

    • rasensprenger@feddit.de
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      9 months ago

      Borking an entire install by pressing buttons on a monotor is pretty difficult. What exactly were you doing? Did you ask your OS’ community for support?

      • Twospoons@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        9 months ago

        All I did was on first install go to display settings and change to 144hz in the OS and screen then goes black and never came back. Force a shutdown and boots back to a black screen after login.

        I was eventually able to change things back to 60hz and working through booting to cli but 144 never wanted to work (am admittedly using Nvidia card).

        So not completely borked but not ideal at all.

        • rasensprenger@feddit.de
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          Ah yeah nvidia can be painful, especially if you want wayland. But this seems to be a simple modesetting issue, I’m sure there are some known workarounds. You can also report driver bugs directly to nvidia, but I don’t know if that will do much.

        • rasensprenger@feddit.de
          link
          fedilink
          arrow-up
          3
          ·
          9 months ago

          Well even if the user doesn’t really know what they’re doing, things shouldn’t easily break, that’s just bad.

          • be_excellent_to_each_other@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            9 months ago

            I’m not convinced this is a valid statement:

            If only Linux wouldn’t Bork my whole install when I try to switch to 144hz on my monitor.

            If he says his install is borked I believe him. If he says it’s “just” because he tried to switch to 144hz on his monitor, eh…

            Edit: Also sounds like nvidia binary blob driver. Odd to me that he didn’t get the “do you want to keep these settings” prompt, and that it didn’t revert when he didn’t click yes though.