Hi Ryan,
I apologize for how we handle this situation with our partners… I’m surprised to read, PNY is not providing the VBIOS update routine for a PNY-sold GPU, so far I know they want to check SN, so they know its PNY who initially sold the GPU into the channel…
What region are you in, I ‘cover’ EMEA, maybe things are being handled different in the USA…?
Maybe RMA is the faster option for you to get an updated board…? Until we improve the process… :-(.
A more general statement or warning: Overall, for being able to use MIG (Linux only, no display out), first you need the proper VBIOS to include the MIG functionality, and 2nd, you need to change the GPU into ‘compute’ mode, using DisplayModeSelector tool. This will need to also increase the BAR1 (memory addresses) from this GPUs default of 256MB to 8GB. There are systems that do NOT deal well with an add-in card of this BAR1 size, and thus will not be able to detect and ‘talk’ to it anymore. That’s why the tool explicitly warns, and recommends to be used only on ‘known good’ systems, systems listed in our certified systems catalogue…
We know not all systems can be tested and approved, so there might be systems out there that do still work, specially when they support “resizable BAR” and its enabled, but we can’t guarantee…
So word of caution here, in case you don’t know for sure, your system works fine with add-in cards that request a large BAR1 region, ‘a lot’ of reserved memory addresses….
If you toggle your GPU into a large-BAR1 mode on a system that can’t cope with the request, after reboot, your GPU will no longer be found, thus system can’t talk to it, and you will need a capable system to be able to use the GPU again, and potentially revert the setting to “graphics" mode including ‘normal 256MB BAR1 size…
I know this doesn’t read ‘user-friendly’, but I take it as the effect of bringing datacenter type features into desktop/consumer type systems and usecases…
I keep pushing our BU for improving the whole situation for the future, until then, we might need to accept ‘tricky’ field updates and settings, or even RMAs as the faster route to solution…
Again, my apologies..
-Frank