• Naho_Zako@piefed.zip
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    6 hours 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.

  • HouseWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    48
    arrow-down
    1
    ·
    19 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.

    • JayDee@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      6 hours ago

      Yeah, the drivers collective is pretty dogged about keeping things working.

      GPU drivers are hella difficult to not cause breakage on, I expect. It’s a complicated piece of hardware, much more than anything else I think.

    • programmerlexi@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      11 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.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        7 hours 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
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      18 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
        link
        fedilink
        arrow-up
        6
        ·
        17 hours ago

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

  • CameronDev@programming.dev
    link
    fedilink
    arrow-up
    70
    ·
    22 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.

    • fedditter@feddit.org
      link
      fedilink
      arrow-up
      22
      arrow-down
      2
      ·
      21 hours ago

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

    • atomicbocks@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      18 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.

      • TrickDacy@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        4
        ·
        17 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.

  • AstroLightz@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    17 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.

  • thezeesystem@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    9
    ·
    20 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.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      11
      ·
      19 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.

      • tortina_original@lemmy.world
        link
        fedilink
        arrow-up
        16
        arrow-down
        2
        ·
        19 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.

        • Aeder@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          7 hours ago

          I’ve only remember ever having audio dissappear during the really early Ubuntu days (We are talking like version 7 or 8). Now if you told me Linux has issues with audio crackling due to apps requesting absurd audio parameters, then yeah, that was a more recent and persistent issue that only recently seems to have gone away.

        • Err(()).unwrap()@lemmy.worldM
          link
          fedilink
          arrow-up
          3
          ·
          16 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.world
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          5
          ·
          edit-2
          18 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.

      • lost_faith@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        13 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.

      • thezeesystem@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        19 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.