@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?
1. Maybe makes sense to update readme (saying about "in the past")?
2. I am ready to test it, just give us an option and write in readme that it "requires root permissions". Better than not have it at all.
3. Same here, please check since I can't use Linux with RX470. Nitro+ 4GB reflashed, GPU opts are loaded, but Mem Voltage set to 1000mV regardless of my settings. So all runs at 1000mV instead of 900-875. On windows I can undervolt and it preserved by drivers, on Linux still no-go.
4. I may check that later, I have some mixed system.
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.
2. I would be fore trying to set voltages in Linux. I use Win7 just because I can undervolt, some mobos are under-used though
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...
.
