

nvidia-smi -query-supported-clocks=timestamp,gpu_name,gpu_bus_id,gpu_serial,gpu_uuid,memory,graphics -format=csv

Using latest Nvidia driver version 375.20. Nvidia-smi shows G0’s power.draw only 64.26 W and m only 810 MHz. G1 worked fine all time (I think I even swapped cards, same).īut under Linux (I think I even swapped cards, same), Fedora 24 圆4, kernel 4.8.86_64,

When Chrome stopped and after 5 minutes wait, clock went up again. Well, apart from Google Chrome kills G0’s core clock from over 2000 to 1600. I have 2 Pascal GPUs under heavy load (MSI Afterburner says 80% power) : GTX1070 xtreme gaming (G0, PCIe x16, 4k video out) and GTX1070 g1 (G1, PCIe x4, unconnected) setup and they work fine in Windows 10 圆4 Nvidia driver 376.19, motherboard z170-HD3P.
