sort of makes one wonder how many whizz-bang hardware features get advertised that are little more than just software, but are oversold as unique physical engineering methods/techniques.
sort of makes one wonder how many whizz-bang hardware features get advertised that are little more than just software, but are oversold as unique physical engineering methods/techniques.
Same thing with Cisco switches for port-unlocks and Tesla cars (EAP and FSD are just software features, assuming you have HW2+, and rear heated seats are standard, just not activated unless you pay to enable it if you didn't get the cold-weather package when you ordered it).
I'm also unsure how much it really makes a difference in an electric motor compared to a combustion engine. Unless you're going to the track (or significantly breaking speed limits), you're only putting extra wear on the motors for 2-4 seconds at a time, which is all it takes to get to your 40-70 mph target speed.
https://hackaday.com/2013/11/04/manufacturer-crippled-flir-e...
Oscilloscopes are another product notorious for shipping same hardware with different jumpers/variables in the firmware.
https://tomverbeure.github.io/2020/06/27/In-the-Lab-Tektroni...
somewhat famous DS1052E 50 to 100MHz hack https://www.youtube.com/watch?v=LnhXfVYWYXE
DS2072A 70 to 300MHz https://hackaday.io/project/8115-rigol-ds2072a-upgrade-to-ds...
MSO5000 70 to 350 MHz https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso...
https://docs.nvidia.com/drive/drive_os_5.1.6.1L/nvvib_docs/i...
They've moved from keeping that sort of thing in EEPROM's to burnable fuses from what I understand, and I'm pretty sure what I'm aware of is pretty far behind state of the art.
If they've managed to set up the key management as well as they have and keep things hush-hushed enough to keep the nouveau folks obstructed, this seems either like an uncharacteristically careless mistake, or some seriously well executed malicious compliance from somebody.
Either way. I still find it irritating to the extreme that this type of thing only seems to happen to the detriment of users. Nvidia wins either way. Miners or gamers will buy out their cards.
My guess is this was accidentally on purpose (see also the recent shareholder lawsuit; Nvidia did win that one btw).
Source?
Never heard such a thing. Partners (MSI, ASUS, etc): absolutely. NVIDIA, I've never heard any evidence they sold directly to miners.
> My guess is this was accidentally on purpose (see also the recent shareholder lawsuit; Nvidia did win that one btw).
I think it's incredibly likely that we see this re-introduced on 3080 Ti or 3080 Super or whatever they call it which is about to be released, as well as with future generations of cards, which strongly argues against this being an "accidentally-on-purpose" thing.
People love to make up conspiracies about NVIDIA but all it takes is someone building a beta driver from a feature branch based on an old build that didn't have the mining brake yet, it's quite probable that this is just an accident. But it's NVIDIA and they're the only company people love to hate more than Apple.
People hate NVIDIA for releasing drivers that broke the mining brake, and they'll hate NVIDIA for reinstating the mining brake in the future. People get mad no matter what NVIDIA does.
I'm assuming he's referring to an RBS article which was mischaracterized by Barrons and then widely broadcast in the tech media... the RBS article looked at hashrate growth since launch and attempted to estimate the number of 30-series GPUs sold (the number they came up with was about 7% of gaming revenue). Barron's then took that number and trumpeted it as NVIDIA selling cards directly to miners when that's not what the original article said at all, they were just estimating how many cards ended up mining from any source, and it was sub-10% regardless.
But of course nobody actually went back and looked at the original article, and because it's NVIDIA everyone is completely willing to give full faith to any claims that make them look bad. Lie goes around the world before the truth has its pants on, etc.
But if there's an article I'm willing to read it.
Thank you for making me do a little leg work. Perhaps I should have done that in the first place.
https://twitter.com/dylan522p/status/1332502890104188929/pho...
I'll start to like nvidia when they provide anything remotely similar to the AMDGPU+Mesa experience on linux. Until then, hacking optimus and unstable kernel updates are the norm.
Yep. I have an old laptop with an Nvidia Quadro FX770M GPU that (hackintoshed) macOS sees as a Geforce 9600M GT and runs the included Geforce drivers quite happily on because the FX 770M so close kin with its consumer counterpart.
In fact, in a twist of irony for years the supposedly-more-stable Quadro Windows drivers had a power state bug with this card that would cause the laptop to bluescreen if the GPU tried to ramp down to an idle state. The only solution was to prevent the GPU from idling or to run a different OS with more generic drivers.
It was also before the era when PROM fuses were used to permanently disable hardware at the factory. So like, nowadays when you do something like flash Vega 56 with Vega 64 firmware, or flash 5700 with 5700XT firmware, it doesn't actually turn on any cores anymore, they're permanently disabled now. What changes is things like memory speed (Vega) or power limits (5700) that are used to artificially gimp the cards and increase the performance difference beyond the actual core count, as just disabling cores often doesn't give enough difference anymore to be marketable (Vega especially was very bottlenecked by other parts of the card other than the cores).
then there was 2003 Radeon 128MB 9500 to 9700 mod https://forum.beyond3d.com/threads/turn-your-radeon-9500-int...
One of the big differences is RAM.. the A6000 has 48GB, a 3090 only 24 (And the 3080 12). Also, the RAM in the A6000 is ECC, and of course in the consumer cards it isn't.
The A6000 also has ~10% more CUDA and Tensor cores.
So, no, it isn't just a different firmware.
When you look at the workstation cards that aren't top of the line, it's clear that they are nearly identical hardware to more mainstream consumer gaming GPUs, and the most significant hardware differences are usually smaller coolers on the workstation cards leading to lower clock speeds.
https://www.techpowerup.com/review/nvidia-geforce-rtx-3080-f...
This is the reason why DDR5 is so much faster despite using ECC effectively by default.
In the GPU space, this is why HBM2 memory doesn't really have a performance difference between ECC and non-ECC memory.
https://www.eevblog.com/forum/thermal-imaging/flir-e4-therma...
Which is a shame, because a GPU with FOSS firmware and comparable specs to the AMD/Nvidia hotness could use that software-driven flexibility to its advantage.
Then you notice the asterisk and realize it's just an accelerator (usually just a few instructions with some dedicated logic) and all the NN is still in software.
Isn't that the whole point? I was doing raytracing in the CPU in 2002 for a university project. Doesn't mean I could use it in a game.
With love,
USPTO