170hx（any cmp hx card）can run higher and higher fp32 flops than before

[jetcat8848]

i tried mod a OpenCL benchmark（disable fma to prevent
OK，the moded OpenCL benchmark runs，and the 170hx fp32 flops increased to 6.285 Tflops，the original fp32 flops just only 0.395Tflops，6.285/0.395=16，so，i think the nvidia driver prevented gpu use full speed on FMA！

[jetcat8848]

10DE 20C2 the devicr ID is a CMP170HX mining card，i installed a nvidia gird A100-20C driver to run it！

[jetcat8848]

[bah86]

Do you have any idea how to disable fma in the driver?

[astronautduckpc]

Is this the same problem that the cmp70hx and cmp90hx have reduced performance? Described here in open sources

[jetcat8848]

您知道如何在驱动程序中禁用 fma 吗？

sorry!i have no idea....

[jetcat8848]

这与 cmp70hx 和 cmp90hx 性能下降的问题相同吗？此处在开源中进行了描述

yes!it is the same!nvidia use efuse to tag fma speed (reduce to: 1/8,1/16,1/32...1/2^n,n=1,2...5),and the nv driver knows how to running!

[astronautduckpc]

这与 cmp70hx и cmp90hx.

да! это то же самое! NVIDIA использует efuse для обозначения скорости fma (уменьшите до: 1/8,1/16,1/32...1/2^n,n=1,2...5), и драйвер nv знает, как работать!

and how to fix or work around this?)

[Skylord4321]

this is incredible information! so they used Efuse within the driver to hinder the mining card performance!

[InnovativeOSS117]

For info in Nvidia Drivers, there exists fuse definitions related to FMA speed reduction.
What is interesting is that there also exists fuses to override this speed reduction.

I see 2 approach: either find in driver where those fuses are read and patch the driver, but the problem is to locate where to find it.
Second is to fuse the override SM speed, but good luck finding the tool to fuse the chip.

[InnovativeOSS117]

Flashing an A100 bios results in the card not booting in secured mode, making it unusable. But:

• the memory size, SM, shaders stays the same
• the sub system ID changes depending on bios original card

Flashing a 10gb board with an 8gb bios changes :

• the ROPs number (from 160 to 128), meaning this is probably set up in the bios

[InnovativeOSS117]

All my tweakings lead me conclude that the patch is working well: the memory bandwidth limitation is lifted with the patch but the one thing missing is the WDDM (graphic) activation of the driver. The card stays in TCC (compute mode)
The previous method of modifying the register value "AdpaterType" from 2 to 0 crashes the driver.
The only thing I could find about it is in Chinese ebay a guy that managed to enable WDDM for a a100 that have the same core. **



**

[Demianvan]

@jetcat8848 Very interesting, I do some benchmarks with AIDA64 in my 90xh compared with 3070, and the results are very similar or superior inclusive in front 170HX. Can you share the results in GPGPU AIDA64 with your 170hx?

As you can see, 90HX (3080) and 3070 have almost same results (except FP32/16). The "Very Interesting Thing" its with FP64, that are Untouched, and same with all INT capabilities (mainly for mining algorithms).

cmp90hx_OC_gpgpu.txt

3070_OC_gpgpu.txt

Looks like operations are directly in math factor way, dependant from FP64:

RTX gaming FP32=(FP64x64)
CMP mining FP32=(FP64x2)

Really this looks as driver thing, and confirms the way of patch a math factor in a fuse definition. Unlock this thing, and this cards turns in the most reliable GPUs for training and executing LLMs/SD generators. And, maybe, we are approaching a TABOO about the FP16 1:1 limitation for artificially segment the market.

My full testings and overclock are detailed in this thread.
#45 (comment)

[tech-qroll]

Это действительно интересно. Спасибо за проделанную работу! Было бы круто сделать большую статью с подробным объяснением всего этого для новичков, тогда все смогут покупать шахтерские видеокарты, и наслаждаться производительностью)

[eastmoe]

With the help of Gemini, I tried to compile a llama.cpp with disabled fma support, which can consume more than 170W and get an inference speed of 40-50 tokens/s when running some LLM (tifa-7b-qwen2-v0.1.q6_k.gguf).