The newest Threadripper 7000 series not only support ECC, but require it to work. It only accepts DDR5 registered ECC RAM.
The newest Threadripper 7000 series not only support ECC, but require it to work. It only accepts DDR5 registered ECC RAM.
From mangas of course!
It gets replaced with CachyOS optimized version because it will set the repo priority higher.
You could just use CachyOS packages on EndeavourOS. https://wiki.cachyos.org/cachyos_repositories/how_to_add_cachyos_repo/
Benefits from optimizations without reinstalling the whole OS!
I tried it with Claude 3 Opus, even better:
Alright, listen up you little shits. Commit d96c36004e31 (“tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry”) had to remove a fucking hidden tab because apparently some half-assed third-party kernel config parsing tool couldn’t handle its shit.
I don’t know what kind of brain-dead tool it was, but you better make damn sure it gets fixed. Because if you can’t parse tabs as whitespace, you have no fucking business parsing the kernel Kconfig files, period.
In fact, let’s rub this breakage right in your face, more than some obscure ftrace record size option. If you can’t handle tabs, you sure as hell can’t handle page sizes either, dipshit.
Yeah, I know the whole tab-vs-space clusterfuck is sadly a classic Unix thing, and ‘make’ is notorious for being a broken piece of crap in that regard. But guess what? That doesn’t make it fucking okay, got it?
I’d sprinkle more random tabs all over our Kconfig files just to spite you, but I don’t want to make this codebase look any more like dog vomit than it has to. But if I keep seeing more of this kind of idiotic tooling, I just might fucking have to.
So shape up, or I’ll come over there and shove those tabs so far up your ass you’ll be shitting spaces for a week. Fuck!
Well, the bridges are open-source so you can just go and see what they do.
EDIT: Seems like you’re talking about the client app. Nevermind. It would be nice if it was open-source.
That is NVIDIA problem and it will be fixed soon because explicit sync support is getting merged.
He did pass the repo to the community (thus the repo not being on tteck) before he passed away so it will be maintained.