Yes! It would be amazing if we could finally apply vgpu on consumer cards and partition the GPU for virtual machines. It did work on older cards, but they closed that down - so you pay extra on...
Yes!
It would be amazing if we could finally apply vgpu on consumer cards and partition the GPU for virtual machines. It did work on older cards, but they closed that down - so you pay extra on enterprise cards.
If this would be possible, I would be very very happy.
I hope so. The tools are in beta so is hard to tell how things will turn out. However, I don’t expect much given the company’s history; these decisions are what placed the company where it stands...
I hope so. The tools are in beta so is hard to tell how things will turn out. However, I don’t expect much given the company’s history; these decisions are what placed the company where it stands today.
They have too much to lose and no competition to force them to open up their stack the way amd does.
What I find interesting is how long it took to find the solution. The "hack" is so simple that I wonder what other doors Nvidia kept open that no one considered to check as they seemed too...
What I find interesting is how long it took to find the solution. The "hack" is so simple that I wonder what other doors Nvidia kept open that no one considered to check as they seemed too obvious.
A simple patch of the flasher enables flashing of signed bioses to the GPUs. I wonder if they ever circumvent the cert validation on the cards.
Sadly you can't run enterprise bioses on consumer cards as the cards themselves reject booting it. But different BIOSes of the same model are now possible.
I remember some nvidia cert was leaked a while ago. Maybe that can be utilized to modify and unlock certain bios features.
The cat is out of the bag though. According to the dev, it's a very simple patch to the nvidia firmware patcher as NVidia has added some kind of "backdoor" itself for whatever reason. He basically...
The cat is out of the bag though. According to the dev, it's a very simple patch to the nvidia firmware patcher as NVidia has added some kind of "backdoor" itself for whatever reason.
He basically just enabled a hidden flag. The binary won't vanish. The only way to fix this is through a firmware patch on the cards I guess. I assume they added the backdoor for a certain reason - repairing/debugging or something similar so they might even wont.
I’m no expert but this tool would probably not change much. Unless mistaken, nouveau is an open source library that aims to provide simple, limited support (specifically operations that use gpu)....
I’m no expert but this tool would probably not change much. Unless mistaken, nouveau is an open source library that aims to provide simple, limited support (specifically operations that use gpu). Ignoring the fact that most end users in *nix platforms are tech savvy, I don’t see this affecting an open source driver such as this one unless these tools remain unpatched. And even then support would come in the form of a community or custom driver.
This is also a mod and based on the article it’s all in early/beta stages.
Nouveau is a perfectly competent driver. Nvidia gpus have arbitrary, manufacturer-enforced restrictions: they run with a very low clock rate unless told to do otherwise by the official driver. But...
Nouveau is a perfectly competent driver. Nvidia gpus have arbitrary, manufacturer-enforced restrictions: they run with a very low clock rate unless told to do otherwise by the official driver. But nouveau can't do this. The question asked by the parent is whether this work will lift that limitation, allowing nouveau to drive the gpu with reasonable performance.
I think the answer to that question is that if you flash your vBIOS to a better supported version that you find on your own on the internet with a 3rd party tool, then you may be able to get...
I think the answer to that question is that if you flash your vBIOS to a better supported version that you find on your own on the internet with a 3rd party tool, then you may be able to get better clock support with nouveau. This will never be officially supported by nouveau, they need to maintain their working relationship with NVIDIA and this would jeopardize it too much. Not that NVIDIA is doing much, but they're at least less toxic towards nouveau then they used to be.
Yeah I get what you both mean but I'm just not sure if the driver is ready to make use of this 'unlock' nor if adding support is feasible. I haven't used nouveau in a while but i do remember that...
Yeah I get what you both mean but I'm just not sure if the driver is ready to make use of this 'unlock' nor if adding support is feasible. I haven't used nouveau in a while but i do remember that the proprietary driver was recommended unless you strictly wanted foss.
If I'm interpreting you credent, it seems that this driver could be ready as is or with minimal changes. Whole be interesting if that's the case.
So I read the article and maybe I'm just being stupid here, but wasn't this already possible? Just a week ago I flashed another laptop's VBIOS on my Acer Swift X to raise my power limit targets...
So I read the article and maybe I'm just being stupid here, but wasn't this already possible? Just a week ago I flashed another laptop's VBIOS on my Acer Swift X to raise my power limit targets (35W->50W). What does this change? Is this bringing actual real control over VBIOS allowing modifications or is it the same old, same old?
Since we're talking about laptop power limits it sounds like you simply replaced the 35W TGP firmware with one that's 50W. All that's happened is your GPU's TDP was bumped to a level it could...
Since we're talking about laptop power limits it sounds like you simply replaced the 35W TGP firmware with one that's 50W. All that's happened is your GPU's TDP was bumped to a level it could always do, it was just a software switch to provide a certain level of performance -- in this case for the sake of battery life. You are not telling your 3050Ti to spoof an entirely different card.
With these two tools mentioned in the article it sounds like you can take a GeForce 970 and tell it that it's actually a Quadro M5000-class workstation GPU to unlock compatibility for professional software and workloads. All while appearing to be legitimate. Or you can load unauthorized, custom firmware and the signature checks performed on-GPU will be bypassed, rather than throwing an error and soft-locking your GPU (or whatever happens in that case). As mentioned in the article you can also circumvent Nvidia-mandated voltage controls by using custom firmware that again bypasses signature checks. It sounds like you can even flash a GPU to appear to be from another vendor, whatever benefits that may have.
Yes!
It would be amazing if we could finally apply vgpu on consumer cards and partition the GPU for virtual machines. It did work on older cards, but they closed that down - so you pay extra on enterprise cards.
If this would be possible, I would be very very happy.
I hope so. The tools are in beta so is hard to tell how things will turn out. However, I don’t expect much given the company’s history; these decisions are what placed the company where it stands today.
They have too much to lose and no competition to force them to open up their stack the way amd does.
What I find interesting is how long it took to find the solution. The "hack" is so simple that I wonder what other doors Nvidia kept open that no one considered to check as they seemed too obvious.
A simple patch of the flasher enables flashing of signed bioses to the GPUs. I wonder if they ever circumvent the cert validation on the cards.
Sadly you can't run enterprise bioses on consumer cards as the cards themselves reject booting it. But different BIOSes of the same model are now possible.
I remember some nvidia cert was leaked a while ago. Maybe that can be utilized to modify and unlock certain bios features.
I'm expecting a cease and desist letter in his inbox before the evening...
The cat is out of the bag though. According to the dev, it's a very simple patch to the nvidia firmware patcher as NVidia has added some kind of "backdoor" itself for whatever reason.
He basically just enabled a hidden flag. The binary won't vanish. The only way to fix this is through a firmware patch on the cards I guess. I assume they added the backdoor for a certain reason - repairing/debugging or something similar so they might even wont.
What does this mean for the Nouveau drivers?
I’m no expert but this tool would probably not change much. Unless mistaken, nouveau is an open source library that aims to provide simple, limited support (specifically operations that use gpu). Ignoring the fact that most end users in *nix platforms are tech savvy, I don’t see this affecting an open source driver such as this one unless these tools remain unpatched. And even then support would come in the form of a community or custom driver.
This is also a mod and based on the article it’s all in early/beta stages.
Nouveau is a perfectly competent driver. Nvidia gpus have arbitrary, manufacturer-enforced restrictions: they run with a very low clock rate unless told to do otherwise by the official driver. But nouveau can't do this. The question asked by the parent is whether this work will lift that limitation, allowing nouveau to drive the gpu with reasonable performance.
I think the answer to that question is that if you flash your vBIOS to a better supported version that you find on your own on the internet with a 3rd party tool, then you may be able to get better clock support with nouveau. This will never be officially supported by nouveau, they need to maintain their working relationship with NVIDIA and this would jeopardize it too much. Not that NVIDIA is doing much, but they're at least less toxic towards nouveau then they used to be.
Yeah I get what you both mean but I'm just not sure if the driver is ready to make use of this 'unlock' nor if adding support is feasible. I haven't used nouveau in a while but i do remember that the proprietary driver was recommended unless you strictly wanted foss.
If I'm interpreting you credent, it seems that this driver could be ready as is or with minimal changes. Whole be interesting if that's the case.
So I read the article and maybe I'm just being stupid here, but wasn't this already possible? Just a week ago I flashed another laptop's VBIOS on my Acer Swift X to raise my power limit targets (35W->50W). What does this change? Is this bringing actual real control over VBIOS allowing modifications or is it the same old, same old?
Since we're talking about laptop power limits it sounds like you simply replaced the 35W TGP firmware with one that's 50W. All that's happened is your GPU's TDP was bumped to a level it could always do, it was just a software switch to provide a certain level of performance -- in this case for the sake of battery life. You are not telling your 3050Ti to spoof an entirely different card.
With these two tools mentioned in the article it sounds like you can take a GeForce 970 and tell it that it's actually a Quadro M5000-class workstation GPU to unlock compatibility for professional software and workloads. All while appearing to be legitimate. Or you can load unauthorized, custom firmware and the signature checks performed on-GPU will be bypassed, rather than throwing an error and soft-locking your GPU (or whatever happens in that case). As mentioned in the article you can also circumvent Nvidia-mandated voltage controls by using custom firmware that again bypasses signature checks. It sounds like you can even flash a GPU to appear to be from another vendor, whatever benefits that may have.
So undervolting is going to be possible? That's fantastic news. Let's see where this goes... Thanks for the explanation :)