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.
post
Is this some joke I have too many known-good btrfs snapshots to understand?
Its just Microsoft AI propaganda to discredit Linux. Buy Microsoft Products!!1!! Where an update never breaks the system!!1!
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.
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.
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.
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.
Skill issue, non-ironically.
Using linux makes you forget that drivers are even a thing.
Not if you use FIPS kernels. Nvidia makes sure of that.
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.
Usually I only remember to restart after an update because my USB drives stop working :D
I'd guess Arch or a derivative user?
i know i need to update nvidia drivers when my screen starts flickering :3
Ahem... nix fixes that
Nix fixes kernel updates? How? I know how it can be done on arch, but it's sort of hack.
If there is a broken kernel, you can just revert to the previous version of the system
the nix docs explain it well, but the tldr is by being clever ;)
itβs not one magic bullet
Snapshots in general IMO, like say cachyOS + limine + snapper
Snapper creates snapshots when updating, and if you ever get a bad boot, you shut off and pick an earlier snapshot in the initial boot menu. It's one of the options you can pick during the initial setup, if I recall correctly, so you don't need to set it up yourself and risk making mistakes
that sounds really funny, because here "nix" is a colloquial expression for "nothing"
i wouldn't know, im arch-based :3
Can't say I've experienced that. Is this one of those Arch things?
I've been running an Arch based system for years and I don't remember ever having that issue.
I've had more failed kernel updates on Ubuntu... though even that was years ago at this point.
i use arch btw.
This update is weird, did they put AI in my kernel?

(we got a new GEMINI episode before GTA 6)
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.
The only system updates that ever went wrong on my Nobara were borked because i ran out of space on /boot.
On a sidenote: seriously, why did Nobara 40 / Fedora 40 create the boot partition with a default size of 1GB? With Nvidia drivers this is not even enough for more than the rescue environment, the last 2 good configs and the new update, while also not limiting the amount of old configs to a sane amount. Can't even resize the partition outside of nuking the whole drive. Nowadays you can save space by not putting nvidia stuff on /boot as long as you are not using LUKS, but ...


top 50 comments