rolling release (for gaming)

Seriously… after all these years without some pesky version upgrade screwing things up I couldn’t bring myself to install a non-rolling distro on any device I actively use.

And I only recently learned that a separate vimdiff command exists (not that it makes a difference over vim -d)…

Arch live ISO gives you arch-chroot which does all the binds automatically

That isn’t neccessary. nvidia-open automatically replaced nvidia (same for nvidia-open-dkms, nvidia-open-utils etc) when 590 hit and installing any of those nvidia-580xx packages will ask to remove them because they conflict.

It should be illegal to use pacman without pacman-contrib installed for checkupdates (no risk of partial upgrades) and for comparing and merging .pacnew-files with pacdiff…

While the distinction can be important, the snapshots from right before the update are exactly what you want in this case over some actual but always somewhat outdated real backup

“Doesn’t help” is a bit unspecific for an actual answer.

I simply installed nvidia-580xx-dkms and nvidia-580xx-utils and that was all. If you did not already use the dkms-driver package before you of course also need <your kernel>-headers and dkms (but the latter should be pulled as a dependency for nvidia-580xx-dkms anyway)…

Which automatically asks for the removal of nvidia-open (the standard package for the base linux kernel) or nvidia-open-dkms and nvidia-open-utils that replaced the earlier nvidia, nvidia-dkms, nvidia-utils packages when 590 hit.

PS: If you still have stuff using 32bit add (you might have guessed the scheme by now…) lib32-nvidia-580xx-utils to replace lib32-nvidia-open-utils

nvidia was automatically replaced with nvidia-open (also nvidia-open-lts, nvidia-open-dkms etc).

Simply installing nvidia-580xx-dkms, nvidia-580xx-utils (and lib32-nvidia-580xx-utils because Steam still needs all that 32bit stuff), which automatically removes the 590-open stuff because of conflicts, should be all you need to do.

PS: And of course your kernel’s header package if you did not use dkms before… (dkms should be pulled as a dependency automatically)

Your browser should normally handle that.

But you can also replace that string with ‘+’: https://en.wikipedia.org/wiki/Loss_(Ctrl+Alt+Del)

There is a fuse driver to directly mount it using the google API…

https://github.com/astrada/google-drive-ocamlfuse

That’s okay. Thanks to their insane pricing caused by covid, followed by more insane pricing caused by the AI bubble, many people are still running cards not getting any new drivers anyway.

Back then it was for many simply the first rolling distro they tried… to suddenly realize that without tedious (and rarely unproblematic) release upgrades the reasons for a new install (thus trying out yet another distro) also vanished.

In reality all those older relatives are rather easy. They don’t have a clue what they use anyway and they usually are also using their devices so little that they are not conditioned to expect all the (often questionable) Windows design decisions either.

So there is really no reason to overthink it. Install whatever Linux distribution you are most used to operating in case they actually need support. Most of the time they won’t because unlike Windows it does not just break randomly or simply slows down to a crawl with accumulated bloat over time.

…and all of them are using base 10.

That would be alot of work (and some space) but should be doable.

But just for your personal access to the wiki archwiki-offline and arch-wiki-search already exist (in the AUR).

“It works on my system” vs. “I bricked my device because the basic functionality to replace the pre-installed keys was broken or some idiot vendor had signed his hardware with that MS key” is still bad, even when it runs for the vast majority only using their system with pre-installed keys (those are not actually the ones needing the security and it really is just a marketing gimmick) while just a small minority aiming for security gets screwed by shitty implementations.

Realistically older generations didn’t get new stuff in updated drivers for quite some time anyway, so yeah… Doesn’t matter much.

Honestly, if I had a newer card I would be more concerned about that general shift to open source drivers at the moment as they are still far from comparable performance-wise.

You speak about the design of TPMs. I speak about the actual reality of mediocre and sometimes defective hardware and the even worse and often defective software implementations (often already on the bios/UEFI level) used in conjunction.

Sadly that’s not even close to the same thing, in parts because a certain “PoS company” plays a huge part in it.

Or to stick with your picture: Your argument is as sane as supporting any vaccine, no matter its effectiveness, because vaccines in general are a very good thing. Fortunately there are national health offices evaluating effectiveness and benefit/drawback comparisons for vaccines. Unfortunately the “same” evaluation for hardware is done by big tech under the premise of how to make the most money.

If you dislike TPMs on face value it’s because you also don’t understand the science behind how it works

No, i don’t “dislike” anything. I simply talked about practical reality instead of theoretic ideal.

HSMs are a key component of modern enterprise security.

I feel like you would not believe the real amount of shitty enterprise security were the pinnacle of TPM use is requiring active Secure Boot (with pre-installed MS keys of course) and managing their Office365 licensing…

You are confusing “what it should do” with “what it does”. Vendors are trying to save money like everyone else and will regularly provide defective hardware or software implementations that were never properly tested for any actual functionality beyond said “MS marketing gimmick”