Today’s CPUs usually expose some USB connections directly. Ryzen 7000 desktop CPUs expose 4 USB 3.2 Gen 2 directly on their on-package I/O die for example. So if you connect your USB drives directly to the ports your mainboard connects directly to the CPU, the chipset (“southbridge”) and any third-party USB controllers are out of the equation.

This is just information, I’m not advising to use USB for fixed storage.

“ASRock” and “ASRock Rack” are two different series of motherboards.

Here’s the QVL of one of their AM5 mainboards: https://www.asrockrack.com/general/productdetail.asp?Model=B650D4U-2L2T/BCM#Memory - it doesn’t limit these modules to specific CPUs. All CPUs with ECC compatibility also support these modules on this mainboard. Some of these Rack boards are over a year old, and they always had some ECC modules on their QVL. This - again - isn’t EPYC 4004 specific, they couldn’t have validated it with EPYC 4004 CPUs a year ago. In fact, their CPU support list doesn’t even list EPYC 4004 CPUs as of today, as they haven’t released a BIOS update adding (official) compatibility in for these CPUs (it will probably be released shortly though).

ASRock Rack AM4 mainboards also officially support ECC memory. So if you wanted verified ECC support on a comparatively cheap AMD platform you could’ve always gone for one of these boards with a regular Ryzen CPU (not an APU). The boards are a bit on the expensive side but if you want official support (for whatever reason you’d need that in a homelab environment) you can get it.

The server/workstation focused ASRock Rack AM5 mainboards list plenty of ECC modules in their QVL. The “gaming-focused” ASUS B650E-E I’m using even has two ECC modules listed in its QVL.

So you could’ve already gotten verified ECC support, the fact that the same CPUs now exist with a different (EPYC) branding doesn’t change that. Finding these mainboards isn’t particularly tricky either.

Could’ve just gotten a Ryzen then. These Epycs are essentially relabeled Ryzen CPUs.

Many boards support ECC even when not mentioned. Most ASUS and ASRock boards do for example.

PCIe is back- and forwards-compatible, so even an RTX 4090 would in theory work in a PCIe 2.0 x4 slot.

Now, PCIe 2.0 x4 is obviously really slow compared to what most current cards support (PCIe 4.0 x16), but I doubt transcoding is bandwidth sensitive on the PCIe link.

So pick pretty much any card, be wary though that some consumer-focused cards artificially limit the amount of concurrent transcoding sessions they support. Seems like Nvidia is limiting consumer cards to now 8 sessions, which is probably plenty.

Die sind extra für Selfies mit dem Spiegel gemacht.

Hier bitteschön, einmal für Linksfüßler und einmal für Rechtsfüßler:

Einen braun gefärbten Schimmel!

Was letzte Preis eins Pferd mit UPS Design?

Like others said an Intel CPU with iGPU, alternatively the cheapest Intel Arc GPU (A380?) supports the latest spec of Intel QSV as well.

I also recommend a stable/LTS distro like Debian or AlmaLinux (or other RHEL-based distros). Or just keep using Ubuntu Server LTS.

The OS packages being hopelessly outdated doesn’t really matter when you’re running most services inside containers.

Couldn’t agree more. Wireguard isn’t really hard once you understand the basics.

As others said, “Websocket Support” enables support for them and is required for some applications. “Cache Assets” caches (likely static) assets in the proxy so they don’t have to be loaded from the backend service - I’d leave this disabled unless the backend service is hosted on another network entirely, and even then only enable it if you know the implications. “Block Common Exploits” is a very primitive filter against SQL injection (and similar) attacks. It also blocks some user agents. I wouldn’t enable it as it won’t do much to block a dedicated attacker and some filters may falsely trigger in edge cases, causing errors.

Funktioniert bei mir.

I backup my /home folder on my PC to my NAS using restic (used to use borg, but restic is more flexible). I backup somewhat important data to an external SSD on a weekly basis and very important data to cloud storage on a nightly basis. I don’t backup my *arr media at all (unless you count the automated snapshots on my NAS), as it’s not really important to me and can simply be redownloaded in most cases.

So I don’t and wouldn’t apply the 321 rule to all data as it’s simply too expensive for the amount of data I have and it’d take months to upload with my non-fiber internet connection. But you should definitely apply it to data that’s important to you.

Der Kollege ist aus irgendeinem anderen Grund vermeintlich tot. Da hat der Jäger erstmal gar nichts mit zu tun. Jetzt fragst du deinen anderen Kollege, der Jäger ist, ob der Kollege wirklich tot ist. Statt das zu überprüfen, schießt der Jäger auf ihn, damit er danach sicher tot ist, falls er das noch nicht war.

Schwarzer Kunststoff mit einem silbernen Streifen. Der 7800 ist aber deutlich größer wenn mich nicht alles täuscht.

Die Urversion des 2600/VCS hat natürlich auf jeden Fall was. Ich habe aber oft auch für die neueren Varianten was übrig, bspw. eben Atari 2600 Jr., das Top Loader NES oder auch die PS One.

Der Jr. ist doch auch ein echter 2600. Eine PS2 Slim ist doch auch eine echte PS2.

Ich glaube es ist einfach cool, systemd uncool zu finden und niemand weiß (mehr) so recht, warum überhaupt.

Aber diejenigen wissen es sicher viel besser als die Entwicklungsteams großer Distributionen.