Arc support was added after release to Linux Kernel 6.2 and it’s steadily improved since. Older Linux distros, or “LTS” oriented distros that favour stability may still not have support for them. I know Unraid was very slow to pick up on it and I had to settle for passing the pcie device through to a VM to get it working. Intel is keen to made these viable though, and I love having the AV1 encoder from my A380.

That’s not an equivalency. From written paper to typewriters and then to computers, writing has remained a product of the author. A typewriter repair shop would transition from mechanical to electronic typewriters and potentially then to computer repair. This is because it supports an evolving technology.

An author cannot transition to becoming a machine, because they cannot author what they don’t write, but a publisher can continue to publish anything that would make them money. So when human experience is boiled down to nothing more than the probabalistic order of the words written by authors who gave no consent to have their work absorbed and mutilated by an LLM, the only winner is a publishing house seeking cheaper labour than the human.

That one sounds squarely on Nvidia. Any driver that uses undocumented workarounds to gain kernel level access or utilizes an access loophool for system hooks is a bad driver. I’d assume Debian, or likely more accurately the Linux kernel itself was updated following some matter of CVE that Nvidia was quietly abusing.

Frustrating, but a good example of why those kinds of proprietary drivers are such a nightmare. You really just don’t know what techniques they’re using.

Yeah, because at least a decent 3rd party might hand you documentation and have the sense to build something consistent or maintainable. AI has a limited context scope and frequently suffers a type of short term memory loss that results in repeated work or variations in work that confuse the end result.

Biggest difference is that wormhole will pass traffic between devices on different networks as long as both are routable. So it’s not limited to a local network connection.

Ah, I see where I got confused. Yeah, CGNAT isn’t very common around here. I don’t think I’ve ever run into an ISP that uses it. I can see how that complicates things.

You really don’t though. I use wireguard myself under the same scenario without issue. You just need to use some form of dynamic DNS to mitigate the potentially changing IP. Even if you’re using Tailscale you’ll still need to have something running a service all the time anyways, so may as well skip the proxy.