Closed m5x closed 5 years ago
I've tried other two OSes on different machine (Ubuntu 19.04, Clear Linux 31130) and cannot reproduce this issue on any of them. I guess it looks like I've encountered some rare and probably installation-specific behavior, overlooked something etc.
OS: Ubuntu 18.04.3 LTS, kernel 5.0.21 GPU: water-cooled stock Vega 64
It looks like
rocm-smi --setmlevel ...
does not have any effect on my Vega 64 GPU. It executes successfully and it can be verified both byrocm-smi
and/sys/kernel/debug/dri/1/amdgpu_pm_info
that the desired memory clock has been successfully set but there is no effect at all on hashing speed of a memory intensive algorithm. It stays the same no matter what value from allowed range (167-1500Mhz) is set.I am just missing something obvious out or is setting memory clock on Vega 64 not supported yet (but supported enough that it does not give any error and sys interface reports expected values)?