@ibroughtashrubbery heard nothing of that sort. There are in-browser frontends like Piped and Invidious with it's numerous instances e.g. yewtu.be. I'm also seeing few Qt-based ytdl frontends in AUR, might be what you are looking for?
I think pcr 7+8 (for grub) or pcr 7+12 (for systemd-boot) should be okay. The more pcr you add, the higher likelihood you need to re-enroll after updates.
The reason why using your own keys can be a problem is if you exclude the Microsoft certificates, then oproms from graphics cards stop working. You have to add the Microsoft certs after using your own key for the top level platform key.
For Debian, if you use out of kernel modules like Nvidia, you have create signing keys and edit a config file so dkms to sign those modules for those modules to work with Secure Boot. Instructions are on the Debian wiki.
That just means the TPM will not auto unlock the encrypted disk. You would have to unlock with whatever LUKS password (or key file) you set for that drive. There is optionally a TPM master key you can export that similar to the Microsoft Bitlocker password (40 digit number iirc), that Lennart mentioned in his blog. If you deleted any other pass slots and do not have that TPM master key, you will not be able to unlock the LUKS drive.
If you look at that freedesktop manpage I linked, it states some of the PCR values and what each one measures. When you enroll a PCR, that value is stored in the TPM. If anything differs between the system and the TPM, the TPM will refuse to unlock that encrypted drive.
For example, PCR 0 measures your mother UEFI firmware. If you update the firmware, the TPM will not unlock your LUKS drive until you re-enroll the drive once again. Is is a personal choice, but enrolling certain PCR into the TPM can be more inconvenient.
It seems like you’re having a lot of issues – it really shouldn’t be working that way. Here’s how I do it on desktop; should work on the Deck.
Do a pacman -Syu as others have suggested before installing anything new.
From terminal (X used for AUR package name):
Install auracle with pacman -S auracle; it’s a utility to search and install from AUR easily.
auracle clone X will clone the project in the working directory.
auracle buildorder X will give you a list of dependencies needed to build it. If things say satisfied, you already have them.
install the dependencies with pacman -S. You can get fancy by echoing them to a file and using something like sed, or you can just type them manually.
cd into the directory you cloned and build the package with makepkg.
once done, hit up arrow until you see your installation line for those dependencies with pacman. Change that -S to a -Rs (remove them plus any dependencies installed with them).
install the package you just built with pacman -U name-of-package.zst.
profit
If this doesn’t work for you, check where it doesn’t work. It sounds like you may have an issue with pacman rather than the AUR.
Nvidia doesn’t make CPUs, which is what this headline is referring to. The headline is still a bit surprising because Intel’s Linux support is first-class, but yeah, there’s more than a million Steam Decks out there in the wild now, I imagine that accounts for a large chunk of this stat
For me, choosing AMD in my newest laptop over Intel boiled down to iGPU. In previous years I had an Intel with their iGPU, which was underwhelming. For the next one, I chose Intel with a discrete Nvidia card, which was a mistake due to a power drain, proprietary drivers, and all-around hustle. For the first time in decades, I chose AMD CPU, finally lifting away the resentment of anything ATI-related from decades ago. I must say that I am immensely happy with the choice, speed, reliability, power consumption, thermal control, and the iGPU (Rembrandt).
If you want to check that a machine you’re buying is compatible with Linux, a good place to start is to google how to install drivers for the computer’s components on Linux. Check the common problem areas (WiFi, graphics, sound, etc.) and see if you find lots of other people complaining about those components. If you find evidence that a driver is available, or you can’t seem to find any info either way, it’s probably fine.
I can’t really answer the question you had regarding this site you found, but that is my general strategy for checking Linux hardware compatibility.
Also make sure that the retailer you’re buying from has a reasonable returns policy, just in case you get it, install Linux (or run it from a live USB, to avoid wiping the disk before you know you’re good), and discover something doesn’t work.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.