None
以上来自于谷歌翻译
以下为原文
Hi Shaun,
why should this be an issue with the NV drivers? lspci is a linux command and has nothing to do with NV drivers.
BTW it works fine for me with ESX 6.5. And for sure this command makes no difference if you installed vGPU manager or not.
In addition all Tesla M60s delivered since end of 2016 are already in Graphics mode. There are also other ways to check if the board is in Graphics mode:
https://virtuallyvisual.wordpress.com/2016/04/19/nvidia-m60-m6-problems-check-your-card-in-graphics-mode/
And here the documentation that states that the M60 should already be in Graphics mode:
http://images.nvidia.com/content/pdf/grid/guides/GRID-Quick-Start-Guide-August-2016.pdf
*snip*
NVIDIA Tesla M10 ships and support graphics mode only.
NVIDIA Tesla M60 ships in graphics mode but supports both graphics and compute modes.
*snip*
Hope this helps to clarify
regards Simon
None
以上来自于谷歌翻译
以下为原文
Hi Shaun,
why should this be an issue with the NV drivers? lspci is a linux command and has nothing to do with NV drivers.
BTW it works fine for me with ESX 6.5. And for sure this command makes no difference if you installed vGPU manager or not.
In addition all Tesla M60s delivered since end of 2016 are already in Graphics mode. There are also other ways to check if the board is in Graphics mode:
https://virtuallyvisual.wordpress.com/2016/04/19/nvidia-m60-m6-problems-check-your-card-in-graphics-mode/
And here the documentation that states that the M60 should already be in Graphics mode:
http://images.nvidia.com/content/pdf/grid/guides/GRID-Quick-Start-Guide-August-2016.pdf
*snip*
NVIDIA Tesla M10 ships and support graphics mode only.
NVIDIA Tesla M60 ships in graphics mode but supports both graphics and compute modes.
*snip*
Hope this helps to clarify
regards Simon
举报
