It's rare, but when it happens it's indeed annoying.

Last night I ran the updates on my #ArchLinux system and noticing there was a new kernel version I shut down my machine instead of suspending it as usual.

This morning my OS wasn't booting.

I thought it was my fault and tried to revert some stuff I was trying by chrooting into my system from a usb.

No luck, until I tried to boot into the backup LTS kernel, and it worked.

Turns out the update broke something with the nvidia driver.

#linux

Now they fix it with an update to the nvidia driver, but this caused me a whole morning wasted trying to troubleshoot something that wasn't my fault.

I get why in corporate environments nobody uses Arch...it's great, but it can be a bit unpredictable with its rolling updates system.

Anyway, 99% of my headaches with my system are from my nvidia GPU and its lousy proprietary drivers.
I use the same exact configuration and software on my thinkpad and it is flawless, and smoother.

Not having to rely on Nvidia CUDA to do 3D renderings anymore gives me the freedom of using an AMD GPU, which is in my wishlist for my next upgrade.

@mauro
Same thing has happened to me a couple times on my ASUS laptop running Ubuntu 22.04. Might have been the amdgpu (laptop has both). The vendor drivers (AMD and Nvidia) are prone to this it seems to me.

@mauro This is why I really like running arch with btrfs and snapper. Snap-pac creates a btrfs snapshot whenever I install packages and updates, and I have it setup so I can boot into readonly snapshots, so at least I have a functional system even if there was an issue.

I had the same issue with nvidia for many years, which is why I switched to AMD and haven't looked back.