Precisely this card pci:v000010DEd00001380sv00001458sd000036CAbc03sc00i00 we have in a short-list of simulated gpu.
That is why I asked for the Device ID (Vendor) 1380
It turns out that where the 740A returns a legacybranch property
{
"devid": "0x1292",
"name": "GeForce GT 740M",
"legacybranch": "470.xx",
"features": [
"hdmi4k",
"vdpaufeaturesetD"
]
},
The 750 has no legacybranch property in the json data file supplied by Nvidia.
{
"devid": "0x1380",
"name": "NVIDIA GeForce GTX 750 Ti",
"features": [
"hdmi4k",
"vdpaufeaturesetE"
]
},
Thus can hope for Nvidia to update their data file at some point - that would be number one - I am currently trying wrap my head around some way of reliably determine where a device without legacybranch property should be categorized - I have to dig deeper into the nvidia device detection function to figure that out.
Oh - I think I am on to something.. hang on…
This is a hair-pulling experience
Continuing the story with the 750Ti - it turns out that Nvidia has changed the properties for the device
From
"features": [
"hdmi4k",
"vdpaufeaturesetE"
]
To
{
"devid": "0x1380",
"name": "NVIDIA GeForce GTX 750 Ti",
"legacybranch": "580.xx",
"features": [
"kernelopen"
]
}
Which still doesn’t explain why the script returns unsupported - but know that I know where the kernelopen property comes from … the investigation is ongoing…