Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[djraven911]

i have 3 videocards 2 of r9 380 and 1 rx480. None are overclocked and all work only in ETH mode. Each eats 150W measured by me at the wall. My psu is 1200w, and handles 1000w 90% certified. Total power request is in benchmark 100% load on everything 700w.
The rx 480 is 3 days new, i got it replaced for my r9 380 warranty.
Theoretically all should be fine. However something isnt, and i thought its the compatibility problem of this miner with the catalyst 16 driver, as he even says to use 15.12...

I also have installed Minergate, now i mine with this until i solve the problem. However i would like to use Claymores miner as with it i see greater speeds for my cards.

Those are the speeds reported by clamores:

gpu0 tonga 20mhz
gpu1 tonga 20mhz
gpu2 elleswere 23mhz

And those are the speeds with the same pc but with minergate miner:
gpu0 tonga 17mhz
gpu1 tonga 17mhz
gpu2 elleswere 20mhz

Why is this? Is it really like 10% difference in profit depending on the mining software?

[Claymore]

@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. 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?

[giagge]

Houston have a problem!

I start mining ETC + SIA on suprnova with 2x nvidia gtx 1070 .

Use this .bat :

ethdcrminer64.exe -epool etc-eu.suprnova.cc:3333 -ewal YourLogin.YourWorkerName -epsw mypassword -esm 3 -dpool sia.suprnova.cc:7777 -dwal YourLogin.YourWorkerName -dpsw mypassword -dcoin sia -allpools 1 -allcoins -1

The mining work ok :



BUT!

etc-eu.suprnova.cc send correctly share and i have ETC

sia.suprnova.cc not send share or dont show and dont have any siacoin .

Help .

[osnwt]

@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. 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.

[GH]

3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers?

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.

If you are not able to find one single working tool to set voltages under Linux, why not just code it into BIOS if you already reflash it?

[xeridea]

@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. 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...

[osnwt]

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.

If you are not able to find one single working tool to set voltages under Linux, why not just code it into BIOS if you already reflash it?

Because as I wrote above, GPU frequency/voltage for P1-P7 is read from modded BIOS and used. But for memory only P1 frequency was set, but voltage still is default 1000mV instead of flashed value. I don't know why.

[xeridea]

When switching pools, is it possible to stay on alternate pool until main pool is actually up?  My main sia pool is down, but it keeps stopping mining on alternate pool to check, so there is repeated downtime.  Can this be done in a future version?

[fittsy]

Houston have a problem!

I start mining ETC + SIA on suprnova with 2x nvidia gtx 1070 .

** clipped*

BUT!

etc-eu.suprnova.cc send correctly share and i have ETC

sia.suprnova.cc not send share or dont show and dont have any siacoin .

Help .

SIA is a slow coin. It takes a long time for each block to be confirmed. Your SIA coin will take awhile to show up. Confirmations can take 18-24 hours. I don't remember exactly but I know that my coin I mined today wouldn't show until tomorrow in most cases.

According to Suprnova:
Block time is 10 minutes for sia and difficulty is very high, it takes some time before you see some funds in your account.

Someone that actually mines SIA currently can probably give you more info. I haven't mined it for awhile.

[GabryRox]

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.

[rawbert]

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.

When you don't see change restart miner or reboot computer.
But if you want to see high hash rates (27-28mh) you MUST mod the bios.. there's a ton of info on it:
http://forum.ethereum.org/discussion/8845/rx-470-mining/p1

[AsaroUk]

3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers?

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.

If you are not able to find one single working tool to set voltages under Linux, why not just code it into BIOS if you already reflash it?

This is an option but its risky and I also think that it can void your warranty, I would not recommend you to do this honestly.

[xeridea]

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.

The MSIs have slower memory, I think 6.7GHz. 7GHz 4GB cards do 22MH, 8GB 8GHz cards do ~24.3MH.  The MSI 470 8GB is a terrible card for mining  Has 6.6-6.7GHz memory, yet costs the same as a Sapphire 8GB with 8GHz memory

[CoRpO]

Because as I wrote above, GPU frequency/voltage for P1-P7 is read from modded BIOS and used. But for memory only P1 frequency was set, but voltage still is default 1000mV instead of flashed value. I don't know why.

Have a look at bios mod threads, if gpu vcore is too high, then memory voltage stays at 1 V whatever value you set. I don't remember the exact rule

[tutorialevideo]

Claymore ar you will make a miner for zcash?

[jtoomim]

We're getting an issue on our linux-based NFS netbooted cluster with v7.2 in which after around 36 hours of operation, the miner starts to do a ridiculous amount of "disk" accesses. This saturates our gigabit ethernet (112 MiB/s) for about 5-10 minutes per rig.

As a workaround, we can restart the machines every 24 hours. We'd like to be able to do this with a cron job. What data should we send to the miner, and at which port, in order to make it restart?

[CoRpO]

We're getting an issue on our linux-based NFS netbooted cluster with v7.2 in which after around 36 hours of operation, the miner starts to do a ridiculous amount of "disk" accesses. This saturates our gigabit ethernet (112 MiB/s) for about 5-10 minutes per rig.

As a workaround, we can restart the machines every 24 hours. We'd like to be able to do this with a cron job. What data should we send to the miner, and at which port, in order to make it restart?

It's probably swapping ... try -r 720 to restart every 12 hours automatically

-r   Restart miner mode. "-r 0" (default) - restart miner if something wrong with GPU. "-r -1" - disable automatic restarting. -r >20 - restart miner if something
   wrong with GPU or by timer. For example, "-r 60" - restart miner every hour or when some GPU failed.

[adaseb]

I must give props to Claymore for his work on the older GPUs.

Radeon 6990
PreGCN. Since its not GCN 1.0 like Tahiti/Pitcairn it doesn't slow down due to DAG file increase.


Almost 6 years old. Still murdering it out at 26MH/s. 40nm technology. Loves running at 90C. And After 5 years the fan still is original.

This GPU probably made people the most money. Was the fastest GPU at the time for mining Bitcoins. Would of made millionaires during the BTC mining days. Made great money during LTC rush. Sucked at X11 unfortunately due to bad coding of the bins but picked it up with ETHEREUM mining again.

[giagge]

Houston have a problem!

I start mining ETC + SIA on suprnova with 2x nvidia gtx 1070 .

Use this .bat :

ethdcrminer64.exe -epool etc-eu.suprnova.cc:3333 -ewal YourLogin.YourWorkerName -epsw mypassword -esm 3 -dpool sia.suprnova.cc:7777 -dwal YourLogin.YourWorkerName -dpsw mypassword -dcoin sia -allpools 1 -allcoins -1

The mining work ok :



BUT!

etc-eu.suprnova.cc send correctly share and i have ETC

sia.suprnova.cc not send share or dont show and dont have any siacoin .

Help .

Anyone have the same issue ? .

[thevictimofuktyranny]

I must give props to Claymore for his work on the older GPUs.

Radeon 6990
PreGCN. Since its not GCN 1.0 like Tahiti/Pitcairn it doesn't slow down due to DAG file increase.


Almost 6 years old. Still murdering it out at 26MH/s. 40nm technology. Loves running at 90C. And After 5 years the fan still is original.

This GPU probably made people the most money. Was the fastest GPU at the time for mining Bitcoins. Would of made millionaires during the BTC mining days. Made great money during LTC rush. Sucked at X11 unfortunately due to bad coding of the bins but picked it up with ETHEREUM mining again.

Here's one of the original reviews for the 6990 - I like this line: "the total number of stream processors inside this 12in-long card is a staggering 3,072"  

http://www.bit-tech.net/hardware/2011/03/08/amd-radeon-hd-6990-review/3

And, I see some of them shipped with double lifetime warranties - I guess, someone's grandchildren are in for a real GPU treat