• BradleyUffner@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      5 months ago

      Ugh, I just went through the same thing last week. Let’s just say that checking if secure boot had been turned back on was NOT one of the first 500 things that came to mind during troubleshooting.

    • Acters@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      I know this is a day old and most people who would have seen this already have moved on, but this is a simple fix. In fact if you have secure boot enabled, the Nvidia driver installation will detect it and start the signing process. If you don’t have secure boot enabled, then it will skip it. I think having secure boot enabled and properly signing your drivers is good to not end up in that situation again. Though I understand how annoying it can be too. Sigh