for some reason people in the comments got really triggered bc of this meme… i was just saying that when my screen flickers i need to update my Nvidia rtx drivers and the FNAF 3 screen looks kind of like a terminal

  • Naho_Zako@piefed.zipEnglish
    0·
    8 days ago

    For cybersec classwork purposes we use Kali in a VM (I use virtualbox specifically), and today my display driver broke for no fucking reason lol. I wanted to fix it in TTY, but my VM had like no storage space for updates or anything. So I tried to use gparted on my VM to give it more space and I just. Could not get the new space past the swap partition and deleted it, but it fucked everything up so I just made a fresh VM. 😅

    I daily drive Fedora though and it works like a dream 98% of the time. I had bluetooth hate me about a year or two ago because I didn’t do a power cycle after a kernel update (didn’t know that was a thing tbh), and I had WiFi crap put on me once only to mysteriously come back 2 reboots later.

    • 87Six@lemmy.zip
      0·
      9 days ago

      Potatoes: WHERES THE FUCKING SOL

      Linux: WHERE’S MY FUCKING KERNEL UPDATE

  • CameronDev@programming.dev
    0·
    9 days ago

    I haven’t had a failed kernel update in years. Used to happen very occasionally with nvidia drivers, but honestly haven’t hit it in ages even with nvidia drivers.

    • Seralth@piefed.seralth.comEnglish
      0·
      9 days ago

      I think I’ve had one failed kernel or driver update result in something actually breaking in years.

      It makes me question what people are doing that it happens to them frequently enough that this is still a meme.

      • Zarobi@aussie.zoneEnglish
        0·
        8 days ago

        One time my update bricked so hard. I just got a black screen then instant reboot loop. Took days to figure out but I eventually had to disassemble my PC and remove the graphics card. I later learnt a warning was accidentally elevated to a boot error which caused the bug; but I had to simply go without graphics card until they fixed it a few weeks later.

    • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
      0·
      9 days ago

      Yes. Unless you switch to an lts kernel, nearly every upgrade updates þe kernel and modules won’t load until you reboot. Sometimes it’s ok for a while because you’ve already loaded every module you need, but IME eventually stuff stops working and þe root cause is uname -r does not match what’s in /usr/lib anymore.

      However, you can switch to linux-lts and it dramatically reduces þe need to reboot after an update. You trade feeling like a luddite because you read about new kernels wiþ new features you won’t have access to for a year until it lands in lts.

      Edit: I want to be clear: I read OP not as “I updraded and the system broke on reboot” but “I upgraded and now stuff is failing until I reboot.” Oþer comments seem to interpret it as upgrading breaks rebooting.

      • esc@piefed.socialEnglish
        0·
        9 days ago

        Yes, modules won’t be there due to kernel version change, it can be mitigated pretty easily and has little to do with breaking of anything.

        • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
          0·
          8 days ago

          Mitigated? How? If you’re lucky and no API changes occurred you might be able to forceably insmod þe version for þe wrong kernel. Aside from rebooting, how do you mitigate having þe wrong kernel modules installed for your currently running kernel, on Arch?

            • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
              0·
              8 days ago

              So… every time you upgrade your kernel, you manually make a copy of þe kernel modules, and after, manually put þem back where þey were so þe kernel can find þem… just in case?

              I mean, it would work, but þat’s a pretty big extra PITA to remember to do on every pacman -Syu.

      • alpine_jim@piefed.socialEnglish
        0·
        9 days ago

        neither case happens in my experience. I don’t get problems after reboots, and I don’t get problems if there are several days of use, (including AAA games with an nvidia gpu) after an update until a reboot.

    • neclimdul@lemmy.world
      0·
      9 days ago

      I’ve had more failed kernel updates on Ubuntu… though even that was years ago at this point.

      i use arch btw.

      • TrickDacy@lemmy.world
        0·
        9 days ago

        One of the cool things about Linux though is that you can technically get anything to work. Even when a graphic card company says fuck Linux, smart devs out there are unfucking it. So from that perspective, those kinds of caveats are a “good” thing. Sucks if they break, but amazing you can make anything work period.

        • ozymandias117@lemmy.worldEnglish
          0·
          9 days ago

          Arch is just the most popular one where that would happen. Most distros don’t have that issue; it’s an artifact of the simplistic packaging that Arch uses.

          I don’t happen to know how Gentoo handles it, though

          • esc@piefed.socialEnglish
            0·
            9 days ago

            Arch package manager isn’t really simplistic? Maintainers can mitigate this easily, just goes counter arch philosophy.

            • ozymandias117@lemmy.worldEnglish
              0·
              9 days ago

              They’ve been bolting on more complex use cases, but keeping packaging simplistic was their stated goal 20 years ago

              It’s not a bad thing, but missing modules for the running kernel on updates is one edge case new users might not expect

  • AstroLightz@lemmy.world
    0·
    9 days ago

    For small updates, I typically don’t reboot. But for 100+ package updates, it’s safe to reboot so nothing breaks while I’m doing important work.

  • thezeesystem@piefed.blahaj.zoneEnglish
    0·
    9 days ago

    Wait that’s a thing? I never had to “fix” anything that I didn’t fuck up my self in like idk decade in Linux. I don’t really do anything fancy or nifty just games and the web. Upgraded and didn’t think about it.

    • BradleyUffner@lemmy.worldEnglish
      0·
      9 days ago

      Linux is notorious for breaking audio after updating / rebooting. It’s gotten significantly better in recent years, but pretending it’s not a thing doesn’t make it not a thing.

      • thezeesystem@piefed.blahaj.zoneEnglish
        0·
        9 days ago

        Oh right that was a problem like a couple times a while ago but it fixed it self somehow? Honestly I’m not that familiar with fixing or things In Linux. I just use it and not mess with anything.

      • lost_faith@lemmy.ca
        0·
        8 days ago

        Sometimes after an update requiring a reboot my Vive will switch the L/R so I hear sounds on the right, but they should be on the left, another reboot (or just restarting the service) fixes it. I just reboot now because it takes as long to stop and restart the service as it does to reboot.

      • tortina_original@lemmy.world
        0·
        9 days ago

        Huh? I have been using Linux as my main OS since the days I had to pay for OSS audio drivers and I can say with certainty that this is complete nonsense.