It semi reliably kills pipewire and some sometimes USB drives won't mount after a kernel update if I don't restart.

Hasn't happened in a little while though

I feel like "everything breaks on linux" was created by Microsoft to sell windows lol

In fairness, you have to specifically run that, so you know you are doing a firmware update and that you should be careful.

I feel your pain.

I now keep my data backup separate to the OS backups, so a rollback might time travel me back 3 years, but my data's safe... elsewhere...

(Sure. I might still have to do a restore...)

Me too l, I only used Linux for 2 years and I never had any problems with driver after update or any problems in general really.

It's funny, cause i haven't had this happen on linux, but i've had both audio and network issues on windows 11

Sometimes both. I recently started using an old Macbook with Void, which they have notorious broadcom-wl, so I searched a lot and a got a micro network adapter. It was actually quite hard to find with a working driver because Realtek. Anyway this one I found seemed to had a dkms driver on Void repo, so I went with that.

The dkms driver gives bunch of errors for some reason. I didn't have time to debug it and just compiled from Github. Naturally I have to compile it every kernel update. I probably can add a hook for it but haven't done that yet because lazy.

Edit: Added a kernel hook. It's not harder than writing this comment. :)

I've had Windows kill itself by doing a BIOS update and deleting the bitlocker keys in the process, on a computer where bitlocker was automatically enabled by the OS without the user knowing, and of course, without any backups of the keys except on a Microsoft account that was only logged in on that computer (the user didn't know the password for the account either).

I know there's user error in there, but for an OS that caters to people who barely know how to use a computer, it seems like a terrible choice to do all that.

Yeah fuck them both then, dell think it's a good idea and microslop also think it's a good and allowed dell to do it

Luckily this time it didn't fry the bios chip, but I wasted 2 hours fucking around and waiting for dell diagnostic tool to complete

Unfortunately yeah, these things still happen with Linux. I love linux, and I don't use Windows, but all the "Linux never does anything wrong", or "works on my machine, it must be a skill issue" people don't realize how much that prevents people from moving over.

Linux is a looooooot better than it used to be, but pretending that problems don't exist, is how Linux, and the culture surrounding it, got such a bad reputaion for such a long time.

User is just lonely, this has nothing to do with anything they have experienced, and the screenshot is just a regular diagnostic

Wiped? What are you talking about? Could you explain what you're experiencing and on which distro

I've never had this happen and never heard of this happening.