• OR3X@lemm.ee
    link
    fedilink
    arrow-up
    37
    ·
    2 days ago

    Reminds me of that time I updated my UEFI firmware which automatically re-enabled secure boot which caused my Nvidia driver to fail to load on boot because Nvidia doesn’t sign them so I was stuck with the noveau(spelling?) driver which would crash when I tried to log into my DE. What an adventure figuring that out was. Oh, and the cherry on top: updating the firmware didn’t fix the initial issue I was troubleshooting.

    • Acters@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      12 hours 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

    • BradleyUffner@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day 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.

      • OR3X@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        Exactly. I was about to rip my hair out before I thought to check my UEFI settings.