Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v7.2 (Windows/Linux)
@Claymore, few questions:
1) -cclock: you wrote "you can overclock only", but it seems not to be true for, at least, Windows and Polaris. My 470x can be underclocked (GPU set to 1150 for all states).
2) Any chance to support -cclock and -mclock on Linux for amdgpu-pro drivers (for Polaris)? It is not said "unsupported on Linux", but does not work for me (mem can't be set to 1950 using this).
3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers?
4) Are older cards like 7950/7970 supported using amdgpu-pro drivers on Linux?
5) There is an issue on Windows when used -*clock commands: they are applied at some init stage, but for my 470x it instantly changes hashrates only for the card with monitor connected. I can stop and resume other cards for changes to take effect (and show correct/new hashrate), but probably makes sense to fix it somehow, so miner shows correct hashrates after applying values. Of course, if you run it for 2+ time, drivers keep settings and there is no that effect. Still, it is surprising when you run minr with some value and it is not reflected in hashrates.
1) -cclock: you wrote "you can overclock only", but it seems not to be true for, at least, Windows and Polaris. My 470x can be underclocked (GPU set to 1150 for all states).
2) Any chance to support -cclock and -mclock on Linux for amdgpu-pro drivers (for Polaris)? It is not said "unsupported on Linux", but does not work for me (mem can't be set to 1950 using this).
3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers?
4) Are older cards like 7950/7970 supported using amdgpu-pro drivers on Linux?
5) There is an issue on Windows when used -*clock commands: they are applied at some init stage, but for my 470x it instantly changes hashrates only for the card with monitor connected. I can stop and resume other cards for changes to take effect (and show correct/new hashrate), but probably makes sense to fix it somehow, so miner shows correct hashrates after applying values. Of course, if you run it for 2+ time, drivers keep settings and there is no that effect. Still, it is surprising when you run minr with some value and it is not reflected in hashrates.
1. AMD disabled underclocking in theri drivers in past. May be it enabled it again in recent drivers, I did not check it.
2. Linux requires root access for it, I remember someone said that even sudo is not working.
3. Did not check if it is possible.
4. I did not check it.
5. So if I take two 4xx cards, start miner with -*clock option and it will change clocks only for one card?
5. No. In short: changing memory clock using any tool does not change displayed hashrate until miner restarted or card stopped/resumed. Except a card with monitor connected: for it new hashrate is shown instantly.
When I change memory freq using any tool (WattTool) for a single card while miner is running, it instantly changes displayed hashrate only if the card has connected monitor (tested on Rx470). For headless cards the hashrate shown is not changed until miner restarted or card stopped/resumed. That seems to be a feature (@All: please confirm, but I saw someone complained for the same issue).
When you change freq using miner cmdline, and previous freq was not the same, miner sets freq but shows hashrate for old freq until restarted.
5. Some cards I have, wattman doesn't allow changing clocks/voltages unless I pause miner. I didn't think of if monitor was connected. I have some display emulators I got for $15 that helps with VNC, but not sure it would be worth it for more than that...
It is very strange for me because sometimes displayed hashrate changing when I change ram frequency,
sometimes it doesn't react sometimes it react for gpu frequency though
So, I have been using CDM 7.2 for about 5 days now on my W7 system. I was finally able to reduce my wattage pull through Wattman setting (and disabling dual mining), but am still stuck on a paltry 20.75 Mh/s on ETH per each of my MSI RX 470's. I have tried everything on the CDM side, such as setting ETH intensity to the max of 16 in my command line, adding in all 5 of the recommended setx lines, set my virtual memory to 24GB, etc. None of this moved the needle at all.
So, I am now trying the overclocking route before getting into modding the bios on these. A few things are perplexing though. In my Wattman, each of the 4 GPU's can only be increased from 1650 default to 1700. These seems like a very low limit to me and setting all 4 to 1700 had zero impact.
So, using Afterburner, it actually gave me the option to raise Memory Clock all the way to 2100. I only tried 1850 and applied to all 4 GPUs but yet again, absolutely NO impact... all 4 still mining at exactly 20.75. So, my question is, am I doing something wrong? Shouldn't raising the the clock speed on these yield at least a 5-10% bump in mining hash-rate? Or am I completely off base here?
I know of many people using these cards that have achieved 23+ right out of the box, so still trying to figure out why I cannot get close to that mark.
Please update your driver version..So, I am now trying the overclocking route before getting into modding the bios on these. A few things are perplexing though. In my Wattman, each of the 4 GPU's can only be increased from 1650 default to 1700. These seems like a very low limit to me and setting all 4 to 1700 had zero impact.
So, using Afterburner, it actually gave me the option to raise Memory Clock all the way to 2100. I only tried 1850 and applied to all 4 GPUs but yet again, absolutely NO impact... all 4 still mining at exactly 20.75. So, my question is, am I doing something wrong? Shouldn't raising the the clock speed on these yield at least a 5-10% bump in mining hash-rate? Or am I completely off base here?
I know of many people using these cards that have achieved 23+ right out of the box, so still trying to figure out why I cannot get close to that mark.
I have same issue with my rx 480 before update drivers I was able only to increase RAM frequency from 2000 to 2100Mhz, after update I can set 2250Mhz in Wattman
