• OR3X@lemm.ee
    30·
    4 months 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.

    • BradleyUffner@lemmy.worldEnglish
      2·
      4 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.

      • OR3X@lemm.ee
        1·
        4 months ago

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

    • Acters@lemmy.world
      1·
      4 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

    • Trail@lemmy.world
      121·
      4 months ago

      Yes. If I ever need something else because something unforeseen happened (which has not happened for years, and I use a non-default one), I can boot up from a live USB and fix things.

      I use arch btw.

      • daggermoon@lemmy.world
        5·
        4 months ago

        I also use Arch btw. I have an lts kernel installed just in case. Came in handy when the amdgpu driver was broken for a week. The screen was flashing on Wayland.

          • daggermoon@lemmy.world
            2·
            4 months ago

            On Arch it’s just linux-lts I think. 6.12 is the current version I believe. In any case, I only need to use it when something breaks which is rare.

    • megabat@lemm.ee
      2·
      4 months ago

      vmlinuz vmlinuz.old vmlinuz.old.old vmlinuz.old.old.old vmlinuz.borken

      I’m sure one of these boots and has a Nvidia module that matches user space!

  • bruhduh@lemmy.world
    4·
    4 months ago

    My laptop with arch was lying around untouched by 2 months and this shit happened too, after that i switched and daily drived opensuse tumbleweed for PCs and debian stable for servers for a year already

    • Rin@lemm.ee
      1·
      4 months ago

      sudo reboot now???

      tl;dr: Yes… sudo reboot now.

      from reboot docs:

      […] Otherwise this simply invokes the shutdown(8) tool with the appropriate arguments.

      The shutdown command looks like this:

      shutdown [OPTION]... TIME [MESSAGE] .

      Anything passed into reboot will just get passed along to shutdown, including the time parameter.

      TIME may have different formats, the most common is simply the word ‘now’ which will bring the system down immediately.

      “now” is a valid time for shutdown so it reboots the system asap.