For context this ticket was only opened days ago.
Iām just seeing this now. This thread and this one here:
are absolutely wild. Imagine paying fat stacks of cash for a premium GPU(or more) only to get subpar support and no one knows whatās going on.
So over a month later, multiple people sitting with 10ās of thousands of pounds of hardware purchases and absolutely nothing from NVidia? honestly, probably would have been money better spent on hacked 5090s with more vram, probbaly get more supportā¦
I have been able to successfully enable MIG on a RTX PRO 6000 Max-Q GPU running VBIOS 98.02.6A.00.03 (this is the version that shipped with my devices).
I followed the directions at MIG User Guide ā NVIDIA Multi-Instance GPU User Guide r575 documentation and had to use the Display Mode Selector utility to switch the GPU into compute mode. (NOTE: This utility required me to disable Secure Boot for it to run on my Ubuntu 24.04 installation).
Thu Jul 31 07:36:05 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 575.57.08 Driver Version: 575.57.08 CUDA Version: 12.9 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA RTX PRO 6000 Blac... On | 00000000:01:00.0 Off | On |
| 30% 48C P8 15W / 300W | 32942MiB / 97887MiB | N/A Default |
| | | Enabled |
+-----------------------------------------+------------------------+----------------------+
| 1 NVIDIA RTX PRO 6000 Blac... On | 00000000:C1:00.0 Off | Off |
| 30% 44C P8 8W / 300W | 558MiB / 97887MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
| 2 NVIDIA RTX PRO 6000 Blac... On | 00000000:E1:00.0 On | Off |
| 30% 35C P8 18W / 600W | 590MiB / 97887MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| MIG devices: |
+------------------+----------------------------------+-----------+-----------------------+
| GPU GI CI MIG | Memory-Usage | Vol| Shared |
| ID ID Dev | BAR1-Usage | SM Unc| CE ENC DEC OFA JPG |
| | | ECC| |
|==================+==================================+===========+=======================|
| 0 0 0 0 | 32942MiB / 97251MiB |188 0 | 4 4 4 1 4 |
| | 4MiB / 131072MiB | | |
+------------------+----------------------------------+-----------+-----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 0 0 12124 C python3 32938MiB |
| 1 N/A N/A 12117 C python3 548MiB |
| 2 N/A N/A 12109 C python3 548MiB |
+-----------------------------------------------------------------------------------------+
@aplattner any news on this yet?
The team is putting together a set of instructions on what to do. Iāll let you know when I hear more.
For anyone experiencing this problem with the RTX PRO 6000 Blackwell product specifically, please reach out to your point of sale. They should be able to walk you through the process of getting this resolved.
@brandon_929, did you check this (from the Display Mode Selector tool User Guide) before running the Display Mode Selector tool?: āWARNING: Using the NVIDIA Display Mode Selector Tool on systems that have not passed vGPU software certification can cause the GPU PCle board and system to be permanently unusable.ā
Hello,
I am using an RTX PRO 6000 Blackwell Max-Q Workstation Edition (vBIOS 98.02.6A.00.03) on Ubuntu 22.04 bare-metal.
-
With
nvidia-driver-580-open, the GPU is detected and works normally, but MIG cannot be enabled (nvidia-smi -i 2 -mig 1ā āNot Supportedā). -
With the proprietary driver (580.82.09
.runpackage), the GPU is not recognized at all. Kernel logs show:
NVRM: The NVIDIA GPU 0000:ca:00.0 (PCI ID: 10de:2bb4)
NVRM: installed in this system requires use of the NVIDIA open kernel modules.
In the forum, the last advice was to āreach out to your point of saleā.
Could you please clarify:
-
Does this mean I need to RMA/replace the product, or is there a new vBIOS/driver update that will resolve this?
-
Why is this GPU limited to open kernel modules and not supported by the proprietary driver line?
-
Is MIG functionality expected to be enabled in an upcoming driver/vBIOS release, or is it a hardware limitation of this Max-Q model?
This would help us decide whether to wait for a fix or proceed with a replacement through our reseller.
Thank you.
As the error message you posted states, the proprietary drivers are deprecated and donāt support modern GPUs. You must use the open drivers.
I posted a message above that explains how to enable MIG on RTX PRO 6000 Max-Q GPUs. To summarize, to use MIG you must use the Display Mode Selector Tool to enable compute mode (and therefore disable the display outputs) on the GPUs.
Yes, I it is a scary sounding warning - but I have had no issues using the tool with RTX PRO 6000 Max-Q GPUs. Of course, keep in mind that if you disable the display outputs you will need another display adapter in order to connect a monitor to your PC.
When I ran sudo ./displaymodeselector āgpumode compute and selected my Pro 6000, ethernet stopped working. Whatās up with that? Had to revert back to graphics, I need my ethernet. lol
I was able to enable MIG. But, not worth losing ethernet.
I also would like to enable MIG on my Blackwell Workstation Max-Q verion, which came with a vBIOS version below the required version for this card (referring to the documentation).
I obtained two cards through the Nvidia GPU grant program (thanks for being funded! This is much appreciated), thus I donāt have a vendor to turn to, and I didnāt find any clear advise how to proceed. Is the displaymodeselector tool the one thing I need? Or is a vBIOS update required? Where can I get the tool for this?
Any hints are highly welcome. I consulted the documentation and several other threads in this forum, but a clear advise seems not to be around yet.
In fact, referring to the MIG installation documents at MIG User Guide ā NVIDIA Multi-Instance GPU User Guide r580 documentation I was able to confirm that the vBIOS of my cards is larger than the required minimum (I read other documentation before according to which this was not the case, but Iām unable to find it ā perhaps it has been corrected).
Thus, I obtained the Mode Selector tool from the website linked in the above document, followed the instructions therein and set my GPUs to Compute mode. From there, I continued with the setup steps to define the profiles I wanted, and without any further complications, my GPUs are now āmultipliedā into the setup I had in mind.
Noteworthy: Nvidia provided all assistance I needed along the way ā they are fast to react and well-meaning!
not sure if still relevant for this thread, but I posted some details in a different thread with this posting: RTX 6000 pro ws BIOS update to >= 98.02.55.00.00 how? - #25 by Frank_Quadro
for this ānewā feature (first time in a desktop type product), it needs a minimum driver version, and a different VBIOS version per version of the RTX PRO 6000 cards. (sadly the RTX PRO 6000 600W version had a few board shipped early withOUT the feature of MIG being enabled in VBIOS, so need a VBIOS update firstā¦)
to enable MIG, card must be changed in its āmodeā, which comes with a change in the BAR1 size.
MIG is only available AFTER these changes, on all 3 SKUs of the RTX PRO 6000. vGPU is only supported on the Server Edition of RTX PRO 6000ā¦
-Frank
Hi Frank, first of all thank you for the information.
I have a follow up question that has been puzzling me for month and kept me from using MIG. I have updated the VBIOS on my PNY Pro 6000 WS. Then I put the card into compute mode and installed the open-source compute driver. The driver letās me spawn MIG instances, however passing through MIG instances to virtual machines does not work because the MIG instances are not signed up in Linuxā MDEV subsystem.
I have heard that some people made it work by spawning MIG instances and then passing through the MDEV devices those create but I am unable to do so. It seems that both on RHEL based systems as well as on Fedora based systems, the driver does not sign up the card and neither the MIG instances with the MDEV subsystem.
Are there any additional requirements for this?
@marton3 @ALowlyConsumer @morgwai666
Have a look here: If not rugpull why rugpull shaped? Nvidia + MIG + gfx profile + RTX 6000 - GPU - Level1Techs Forums
Apparently we were rugpulled. @Frank_Quadro You have any news if this will be fixed for the Workstation Edition?
Additional mention to the above post for @colin88 and @BlueGoliath
Hi all, I lack expertise on Linux, but will ask around for inputā¦
In general, RTX PRO 5/6000 are the first gfx GPUs supporting MIG (despite that MIG is without gfx out support, and Linux onlyā¦), in previous generations, only the compute GPUs H/A100 supported MIG - these GPUs donāt have real gfx support.
And also: the only RTX RPO 6000 GPU to support vGPU, so the time sliced sharing of a GPU for multiple VMs/users, is the Server Edition!
My high level understanding is that RTX PRO 5/6000 MIG can be used with Linux, MIG instances can be passed through to Linux VMs, but no gfx out.
Only RTX PRO 6000 server edition would then be supported with vGPU on top of MIG instances passed through to Windows/Linux VMs, and then actually could be doing time sliced vGPU sharing to multiple VMs (on top of physical MIG āsharingā)ā¦
So wondering if RTX PRO 6000 Workstation and vGPU (driver) might be one source of the issues hereā¦
But like I said, no expert on Linux at all, will seek some helpā¦
-Frank

