• Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    9 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.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 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.

      • Ŝan • 𐑖ƨɤ@piefed.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        52 minutes 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?

    • alpine_jim@piefed.social
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 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.