Hot dogs
Ugh, I got a fair return from buying to AMD right before Ryzen came out. I sold some of it and bought multiple different chip companies so now I have some AMD, some Intel, some NVDA. Oh well, it's not a huge amount but still sucks. I hope they can come back if only because AMD needs competition to keep them from becoming the evil that old Intel was. I was hoping Intel would also be a viable third GPU competitor, I like my Arc A770 for the price and I'm hoping they don't kill off the GPU division.
I don't disagree, but today the blame lies with CrowdStrike, not Windows. As much as I hate defending Windows.
Mozilla is a for-profit company and is bound to enshittify just like any other for-profit company. Tracking, ads, and a focus on unnecessary bullshit like Pocket and recommendations have long indicated that Mozilla doesn't give a shit about the user. They want to shove AI in the browser just like all the others. Unfortunately, the best browser is still Firefox, but at least use a privacy focused fork like LibreWolf that also strips Mozilla's other bullshit away rather than using Firefox straight up.
As a user and not as a government agent, why should I care? If anything, having a foreign government hoard my data and spy on me is better than the government that actually has jurisdiction over me. If I were posting things critical of my own government I would rather have a foreign government hoard that data than my own government. There's a lot more of a chance that US data hoarding leads to action against US citizens than Chinese data hoarding.
I don't see how this benefits average Americans in any way. This helps the government and corporations.
I don't really see why they would hire him to achieve this goal. He had already quit as maintainer. He was out of the picture unless he resigned specifically due to accepting an offer from NVIDIA, but if that was the case and they wanted Nouveau stopped then why is he now contributing a huge patchset? If they hired him and he quit nouveau they could've had him work on the proprietary driver or their own open out of tree kernel driver, but they specifically had him (or at least allowed him) to keep working on nouveau.
Also, if they really wanted to EEE nouveau into oblivion, they would need to get every single prominent nouveau, nova, and NVK developer on payroll simultaneously before they silence them all because once one gets silenced why would any of the others even consider an NVIDIA offer? Especially those already employed at Red Hat? It doesn't really make sense to me as an EEE tactic.
What has been apparent over the past few years is that NVIDIA seems to be relaxing their iron grip on their hardware. They were the only ones who could enable reclocking in such a way that it would be available to a theoretical open source driver and they did exactly that. They moved the functionality they wanted to keep hidden into firmware. They had to have known that doing this would enable nouveau to use it too.
Also, they're hopping on this bandwagon now that NVK is showing promise of being a truly viable gaming and general purpose use driver. Looking at the AMD side of things, they did the same thing back when they first started supporting Mesa directly. They released some documentation, let the community get a minimally viable driver working, and then poured official resources into making it better. I believe the same situation happened with the Freedreno driver, with Qualcomm eventually contributing patches officially. ARM also announced their support of the Panfrost driver for non-Android Linux use cases only after it had been functionally viable for some time. Maybe it's a case of "if you can't beat them, join them" but we've seen companies eventually start helping out on open drivers only after dragging their feet for years several times before.
I'm cautiously optimistic. While I could see NVIDIA hiring him to stifle nouveau development, it doesn't really seem worth it when he already quit as maintainer and Red Hat is already working on nova, a replacement for nouveau. I got into Linux with Ubuntu 6.06 and remember the situation then. NVIDIA and ATI both had proprietary drivers and little open source support, at least for their most recent chipsets of the time. I was planning on building a new PC and going with an NVIDIA card because ATI's drivers were the hottest of garbage and I had a dreadful experience going from a GeForce 4 MX420 to a Radeon X1600Pro. However, when AMD acquired ATI they released a bunch of documentation. They didn't immediately start paying people to write FOSS Radeon drivers, but the community (including third party commercial contributors) started writing drivers from these documents. Radeon support quickly got way better. Only after there was a good foundation in place do I remember seeing news about official AMD funded contributors to the Mesa drivers. I hope that's what we're now seeing with NVIDIA. They released "documentation" in the form of their open kernel modules for their proprietary userspace as well as reworking features into GSP to make them easier to access, and now that the community supported driver is maturing the see it viable enough to directly contribute to.
I think the same may have happened with Freedreno and Panfrost projects too.
This is my cautious optimism here. I hope they follow this path like the others and not use this to stifle the nouveau project. Besides, stifling one nouveau dev would mean no other nouveau/nova/mesa devs would accept future offers from them. They can't shut down the open driver at this point, and the GSP changes seem like they purposely enabled this work to begin with. They could've just kept the firmware locked down and nouveau would've stayed essentially dead indefinitely.
I think it's the other way around. NVIDIA's marketing name for render offloading (muxless) GPU laptops is NVIDIA Optimus so when the Mesa people were creating the open source version they called it PRIME.
Ooh, look at this beautiful vast open world! Let's go explo-YOU DIED
YOU DIED
YOU DIED
YOU DIED
The RGB control is a kernel problem not an OpenRGB problem (well, it might also be an OpenRGB problem if the card doesn't work in Windows either). The amdgpu kernel driver doesn't expose the i2c interfaces not associated with display connectors, so the i2c interface used for RGB is inaccessible and thus we can't control RGB on Linux. AMD's ADL on Windows exposes it just fine.
That said, I can't agree that NVIDIA just works. Their drivers are garbage to get installed and keep updated, especially when new kernels come out. Not to mention the terrible Wayland support and lack of Wayland VRR capability. I'm happy with my Arc A770 (whose RGB is controlled over USB and just works, but requires a motherboard header).
Debian has always had a primary focus on being open source and adhering to good open source principles. It's a rare trait in the modern Linux ecosystem sadly, with so many corporate distros just trying to make a buck. Arch seems pretty good about open principles as well. I'm always going to stick to community-powered distros over ones backed by corporations and I suggest everyone who cares about FOSS do the same.
You can view WiFi passwords for saved networks on pretty much every OS. There's no reason to be secretive about entering WiFi passwords, at least to the people whose devices you're entering the password on.