• AstroLightz@lemmy.world
    0·
    12 hours 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.

  • HouseWolf@pawb.socialEnglish
    0·
    13 hours ago

    I’ll assume op is an Nvidia user since the only times I’ve had driver issues after an update was the few months when I still had a GTX card.

    Switched to AMD and literally no issues the last 2 years.

    • programmerlexi@sh.itjust.works
      0·
      5 hours ago

      As an AMD user i would like to share a list of the problems i’ve had in the past month, which happen to be the only hardware related problems i’ve had on the system:

      • Hibernation suddenly stopped working, destroying my ZFS in the process (Hibernation has since been fixed)
      • amdgpu shat itself (no vulkan devices, no opengl context) (and for some programs fixed itself) (resolved after reboot)
      • Fans stopped following their given fan curve (resolved by fw update)
      • CPU stopped thermal throttling (resolved by microcode update)

      Other than these my system has worked perfectly fine.

      • Tavi@lemmy.blahaj.zoneEnglish
        0·
        1 hour ago

        hibernation has since been fixed

        Ongoing nightmare actually. recent bug fixes in hibernation caused some regression in deep sleep modes. Mostly fixable*.

    • Rekorse@sh.itjust.works
      0·
      13 hours ago

      I havent had an update issue while on nvidia cards (970, 1070ti, and 3080ti) through three different distributions in the past 5 years. I think this is just meant to be a funny meme about how things used to be.

      • mobyduck648@lemmy.world
        0·
        12 hours ago

        Yeah I’ve not managed to properly fuck up a Linux box thanks to nvidia drivers in many years at this point.

  • thezeesystem@piefed.blahaj.zoneEnglish
    0·
    14 hours 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·
      14 hours 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.

      • lost_faith@lemmy.ca
        0·
        8 hours 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·
        13 hours 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.

        • rtxn@lemmy.worldM
          0·
          11 hours ago

          It was, in fact, a thing as recently as 2010. I know because I remember having to delete PulseAudio’s config after every second boot on Ubuntu 10.04 otherwise I wouldn’t have any audio. You were spared from the worst, be thankful for that.

        • BradleyUffner@lemmy.worldEnglish
          0·
          13 hours ago

          I wish everyone could live in the perfect bubble you’ve built, but out here in reality it’s pretty well known problem.

      • thezeesystem@piefed.blahaj.zoneEnglish
        0·
        14 hours 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.

      • TrickDacy@lemmy.world
        0·
        12 hours 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·
          12 hours 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·
            12 hours ago

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

            • ozymandias117@lemmy.worldEnglish
              0·
              11 hours 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

    • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
      0·
      14 hours 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·
        12 hours 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.

      • alpine_jim@piefed.socialEnglish
        0·
        13 hours 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·
      16 hours ago

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

      i use arch btw.

  • CameronDev@programming.dev
    0·
    17 hours 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.

    • atomicbocks@sh.itjust.worksEnglish
      0·
      12 hours ago

      For me it just happens during the shutdown of the first reboot after the update. When it comes back up on the new software it works just fine.

    • fedditter@feddit.org
      0·
      15 hours ago

      Its just Microsoft AI propaganda to discredit Linux. Buy Microsoft Products!!1!! Where an update never breaks the system!!1!

  • rtxn@lemmy.worldM
    0·
    18 hours ago

    This update is weird, did they put AI in my kernel?

    (we got a new GEMINI episode before GTA 6)

    • 87Six@lemmy.zip
      0·
      15 hours ago

      Potatoes: WHERES THE FUCKING SOL

      Linux: WHERE’S MY FUCKING KERNEL UPDATE