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

[Gagana]

It's interesting. According to current whattomine results, mining SIA gives me +45% of the profit for R9 390 card. Wow!

[1714173886]

1714173886

[1714173886]

1714173886

[1714173886]

1714173886

[1714173886]

1714173886

[Claymore]

So MSI AB uses the list of GPU different from the miner's temperature list! ((( How could it be? And... What to do then?

Now you ask me why AB does not match the miner. I'm not developer of AB. I have no idea how it enumerates cards.

I'm sorry, if it looks like this. I just want to use your fantastic miner as much as possible, paying you 35Mh of my hash power. To do it effectively, I have to understand these temperature questions. I need a working method how to obtain SPEEDS/TEMPS list matching.

Well, while writing this I've found the way. It's sad, but it works.

Assume you have 4 GPUs onboard.

1. Run CDM with -mode 1 option. Let it mine for at least 5 min to reach stable temperatures
2. Write down current temperature values with -mode 1 option. Let's say 87 88 92 90
3. Stop CDM and run it with -mode 1-123 option. As you can see, you run only one GPU in the dual mode. Wait 1-2 min
4. Compare current temperatures with ones, written on the step 2. One of them should be higher since the dual mode consumes more power and produces more heat. Let's say, you see 87 93 92 90. It means that GPU0 should be GPU1. Write down this match: 1XXX
5. Stop CDM and run it with -mode 1-023 option. Here you find GPU1. Imagine, that you see something like 87 88 92 95. Well, GPU1 should be GPU3. Write down this match: 13XX
6. Repeat steps 3-4 until you detect all GPUs. Let's say, the match string is 1302.
7. At the end just put the match string to -di option. In our case it should be -di 1302.
8. Enjoy

I'm adding "-di detect" option right now to avoid such weird actions to detect correct order.

[Gagana]

Well, while writing this I've found the way. It's sad, but it works.

Assume you have 4 GPUs onboard.

1. Run CDM with -mode 1 option. Let it mine for at least 5 min to reach stable temperatures
2. Write down current temperature values with -mode 1 option. Let's say 87 88 92 90
3. Stop CDM and run it with -mode 1-123 option. As you can see, you run only one GPU in the dual mode. Wait 1-2 min
4. Compare current temperatures with ones, written on the step 2. One of them should be higher since the dual mode consumes more power and produces more heat. Let's say, you see 87 93 92 90. It means that GPU0 should be GPU1. Write down this match: 1XXX
5. Stop CDM and run it with -mode 1-023 option. Here you find GPU1. Imagine, that you see something like 87 88 92 95. Well, GPU1 should be GPU3. Write down this match: 13XX
6. Repeat steps 3-4 until you detect all GPUs. Let's say, the match string is 1302.
7. At the end just put the match string to -di option. In our case it should be -di 1302.
8. Enjoy

I'm adding "-di detect" option right now to avoid such weird actions to detect correct order.

Many thanks!

[Claymore]

v5.3:

- added experimental "-di detect" option value to detect correct GPU order for temperatures management.
- improved Nicehash pool support (mining.extranonce.subscribe).
- fixed issue with sending config.txt to EthMan.
- fixed issue in EthMan (possible garbage during remote editing config.txt).

[xandry]

Greetings,

I am trying to resolve a system-hanging-requiring-reboot issue, the ETH/SIA mining runs fine for a minute or so, then does the GPU hangs in OpenCL call thing.  These are stock video cards with no overclocking, Claymore 5.1, Beta 2. Ubuntu 15.10.  It runs fine with ethminer, and has 8Gb.  I saw a previous answer to this type of problem to be add memory, but that doesn't seem to me to be the problem.  The shown hash rate isn't the problem, I have adjusted the SIA intensity up and down.  Thanks much in advance for any insight. 

GPU #0 recognized as Radeon 280X/380X
GPU #1 recognized as Radeon 280X/380X
GPU #2 recognized as Radeon 390
GPU #3 recognized as Radeon 290X
GPU #4 recognized as Radeon 290X

<runs good for a little while>

ETH - Total Speed: 41.449 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:01
ETH: GPU0 5.401 Mh/s, GPU1 0.000 Mh/s, GPU2 13.438 Mh/s, GPU3 11.316 Mh/s, GPU4 11.294 Mh/s
SC - Total Speed: 2486.920 Mh/s, Total Shares: 4, Rejected: 0
SC: GPU0 324.062 Mh/s, GPU1 0.000 Mh/s, GPU2 806.296 Mh/s, GPU3 678.943 Mh/s, GPU4 677.619 Mh/s
WATCHDOG: GPU 1 hangs in OpenCL call, exit
WATCHDOG: GPU 1 hangs in OpenCL call, exit


����������������������������������������������������������������ͻ
� Claymore's Dual ETH + DCR/SC AMD GPU Miner v5.1 Beta �
����������������������������������������������������������������ͼ

ETH: 1 pool is specified
Main Ethereum pool is us-east1.nanopool.org:9999
SC: 1 pool is specified
Main Siacoin pool is sia-us-east1.nanopool.org:9980

I had such a problem and a replacement riser on GPU wich constantly hangs helped me.

[NewbieTreider]

I had the same problem, but with two overclocked cards in my rig, at the end I discovered that if I change those cards to another PCI slots, the problem dissapears!, I'm using a Asrock H97 Anniversary mobo... I don't know if that can be your solution, but it's easy to change cards to another slot and try

[fittsy]

Is there an easy way to test my backup pool config?

Do I just put in a wrong address for my primary pool? Is that the best way to do it?

[ps_jb]

Is there an easy way to test my backup pool config?

Do I just put in a wrong address for my primary pool? Is that the best way to do it?

Start your mining

And then put the prime pool DNS in black list

[beammeup]

Hi all I am new here trying to set up for solo mining on a ubuntu machine Eth only. I have the blockchain downloaded and geth running I have set the address in start.bash to 127.0.0.1:8545 I have tried 192.168.1.13:8545 , localhost:8545 but I keep gettimng "ETH: Failed to connect to pool (127.0.0.1:8545), retry in 20 sec...
GPU0 t=44C fan=24%, GPU1 t=45C fan=25%
What am I doing wrong I have read the read me 100 times.

Here is my ./start.bash  ./ethdcrminer64 -epool http://127.0.0.1:8545 -ewal 1c0b92f3aef254a2c122713a8e8a34eb2a760c77 -mode 1

It works ok with the default pool but I would like to solo. It reads the graphics catds OK and I have the right drivers.

[toptek]

anyone tried this

https://www.techpowerup.com/downloads/2739/techpowerup-gpu-z-v1-9-0/mirrors

I use it all the time , not sure if it works with a 480 don't have one yet gonna buy a 470 Thursday .!!!

[beammeup]

Hi all I am new here trying to set up for solo mining on a ubuntu machine Eth only. I have the blockchain downloaded and geth running I have set the address in start.bash to 127.0.0.1:8545 I have tried 192.168.1.13:8545 , localhost:8545 but I keep gettimng "ETH: Failed to connect to pool (127.0.0.1:8545), retry in 20 sec...
GPU0 t=44C fan=24%, GPU1 t=45C fan=25%
What am I doing wrong I have read the read me 100 times.

Here is my ./start.bash  ./ethdcrminer64 -epool http://127.0.0.1:8545 -ewal 1c0b92f3aef254a2c122713a8e8a34eb2a760c77 -mode 1

It works ok with the default pool but I would like to solo. It reads the graphics catds OK and I have the right drivers.

OK it is working now the problem was how I was running geth. all good now

[gold368]

help ! give me claymore EXP+ SIA , thanks

[ps_jb]

help ! give me claymore EXP+ SIA , thanks

Here we are

https://bitcointalk.org/index.php?action=search;advanced

[Gagana]

v5.3:

- added experimental "-di detect" option value to detect correct GPU order for temperatures management.
- improved Nicehash pool support (mining.extranonce.subscribe).
- fixed issue with sending config.txt to EthMan.
- fixed issue in EthMan (possible garbage during remote editing config.txt).

Great! Oh, one more thing I forgot to ask ((( May be later... We have "+" and "-" buttons to change the intensity of the second coin mining. It would be fine to have a "on/off" button also for the second coin. Well, I can decrease the "dcri" to 0 by pressing "-" 40 times, but...

[Gagana]

Testing -di detect

From the first sight it works fine. But, please, can you consider exit from the miner after detecting the GPU order? Yes, you write in the log that the order detected is not applied automatically, but it disappears so fast, scrolling up... If I run -di detect as it is, I don't want to continue mining. I want to see the result, apply it to my batch file and only after that go to mine. 

So either apply the detected order immediately, or stop the miner right after showing the result. Pleeeeease )

[turdor]

Hi, I'm converting/tuning my multirig setup to Claymore's...

Win (GPUz) detects only 5 cards of 6 (didn't tried 7 yet till 6 will work).
Any suggestions?

CHEERS!

My system (all rigs are identical except videocards):
Win 10 Pro N (updated, original)
15.12 drivers
MSI Z87-G45 Gaming mobo
30GB mSATA with about 20GB for virtual RAM/free space
6x (7x) 7950 NOW ON TEST
5x 290 ROCK SOLID
mixed 280x/7950/290 (did not tried yet)
1700W PSU  (1800w max and I'm watching it not being overloaded)
Celeron 1840
4GB RAM (various brands)

I have few rigs like this, on Linux they do fine (EthOS).
Also it was 6 cards working w. Claymore's on this machine w identical setup but another same model HDD.
Other rig with exact same specs have 5x 290 on 60GB SSD and works rock solid w Claymore's.

HDD is a primary suspect? but looks strange.

[Gagana]

Back to "tstop" and "ttdcr" options

We have very hot days recently. The typical scenario unless 5.3 was:

1) At 11:00am I look at Remote Manager. I see overheated rigs. It doesn't mean that something is wrong with the hardware. It's just hot.
2) I change the config for an overheated rig to switch off the second coin mining on overheated GPUs
3) If it's not enough, I switch off the whole mining on overheated GPUs
4) I repeat steps 1-3 at 02:00pm and 04:00pm (because it' getting warmer)
5) At 10:00pm I revert all these changes back, because it's cold now

I had to do all these weird actions every day for many rigs and I really hated this ) It should be done by the miner in my dreams. -di detect has made my life much easier, my miners more profitable and your income is bigger. Thank you, mr.Claymore. I don't have to perform step 2 anymore!

But the step 3 is still here ;-) What I would ask to implement is an option, that works exactly as -ttdcr, but for the main coin. Could you, please? It's really usefull.
 

[Claymore]

Back to "tstop" and "ttdcr" options

We have very hot days recently. The typical scenario unless 5.3 was:

1) At 11:00am I look at Remote Manager. I see overheated rigs. It doesn't mean that something is wrong with the hardware. It's just hot.
2) I change the config for an overheated rig to switch off the second coin mining on overheated GPUs
3) If it's not enough, I switch off the whole mining on overheated GPUs
4) I repeat steps 1-3 at 02:00pm and 04:00pm (because it' getting warmer)
5) At 10:00pm I revert all these changes back, because it's cold now

I had to do all these weird actions every day for many rigs and I really hated this ) It should be done by the miner in my dreams. -di detect has made my life much easier, my miners more profitable and your income is bigger. Thank you, mr.Claymore. I don't have to perform step 2 anymore!

But the step 3 is still here ;-) What I would ask to implement is an option, that works exactly as -ttdcr, but for the main coin. Could you, please? It's really usefull.
 

Yes it will be added in next update, "-ttli" option, it will reduce entire mining speed like "-li" option but based on current temperature (like -ttdcr).

[Gagana]

Continue to test -ttdcr

It looks like it worked not exactly as I thought. See the log.

I set -ttdcr 88
I see that after going to 89 on GPU3 it decreases the DCR coef to 85% (not in the log) and then to 70%. But why it is not going lower? It is still 90 on the GPU3 but the DCR coef for the GPU3 is not 55% or 40%... Why? Isn't it a bug? 

Code:

14:37:07:367	d20	args: -di 31420 -r 1 -ttdcr 88 -dcri 40 -dcoin sia 
14:37:07:367	d20	
14:37:07:367	d20	ЙHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH»
14:37:07:367	d20	є      Claymore's Dual ETH + DCR/SC AMD GPU Miner v5.3 Beta      є
14:37:07:383	d20	ИHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHj
14:37:07:383	d20	
14:37:07:602	d20	ETH: 3 pools are specified
14:37:07:602	d20	Main Ethereum pool is xxxx.dwarfpool.com:8008
14:37:07:602	d20	SC: 1 pool is specified
14:37:07:602	d20	Main Siacoin pool is sia-eu1.nanopool.org:9980
14:37:08:086	d20	OpenCL platform: AMD Accelerated Parallel Processing
14:37:08:086	d20	
Cards available: 5 
14:37:08:086	d20	GPU #3: name: Hawaii, 8192 MB available, 40 compute units 
14:37:08:086	d20	GPU #1: name: Hawaii, 8192 MB available, 40 compute units 
14:37:08:102	d20	GPU #4: name: Hawaii, 8192 MB available, 40 compute units 
14:37:08:102	d20	GPU #2: name: Hawaii, 8192 MB available, 40 compute units 
14:37:08:102	d20	GPU #0: name: Hawaii, 8192 MB available, 40 compute units 
14:37:08:102	d20	Total cards: 5 
14:37:08:102	d20	Initializing...

14:37:08:133	d20	GPU #0 recognized as Radeon 390
14:37:08:133	d20	GPU #1 recognized as Radeon 390
14:37:08:133	d20	GPU #2 recognized as Radeon 390
14:37:08:133	d20	GPU #3 recognized as Radeon 390
14:37:08:133	d20	GPU #4 recognized as Radeon 390
14:37:08:133	d20	POOL/SOLO version
14:37:08:133	d20	b176 
14:37:08:149	d20	start building OpenCL program...
14:37:09:414	d20	done
14:37:09:414	d20	GPU #0: set -etha as 0 (ETH algo for fast cards)
14:37:09:414	d20	GPU #1: set -etha as 0 (ETH algo for fast cards)
14:37:09:414	d20	GPU #2: set -etha as 0 (ETH algo for fast cards)
14:37:09:414	d20	GPU #3: set -etha as 0 (ETH algo for fast cards)
14:37:09:430	d20	GPU #4: set -etha as 0 (ETH algo for fast cards)
14:37:40:622	d20	GPU0 t=84C fan=95%, GPU1 t=81C fan=92%, GPU2 t=78C fan=59%, GPU3 t=88C fan=90%, GPU4 t=81C fan=69%
14:38:11:592	d20	GPU0 t=86C fan=97%, GPU1 t=83C fan=94%, GPU2 t=79C fan=63%, GPU3 t=89C fan=93%, GPU4 t=83C fan=75%
14:38:42:502	d20	GPU0 t=86C fan=97%, GPU1 t=83C fan=94%, GPU2 t=79C fan=63%, GPU3 t=89C fan=96%, GPU4 t=83C fan=75%
14:39:13:442	d20	GPU0 t=86C fan=98%, GPU1 t=84C fan=95%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=83C fan=75%
14:39:44:397	d20	GPU0 t=87C fan=98%, GPU1 t=84C fan=95%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=83C fan=78%
14:40:15:281	d20	GPU0 t=88C fan=99%, GPU1 t=84C fan=95%, GPU2 t=80C fan=66%, GPU3 t=89C fan=96%, GPU4 t=83C fan=78%
14:40:21:514	da4	DCR coefs (-ttdcr): GPU0 100%, GPU1 100%, GPU2 100%, GPU3 70%, GPU4 100%
14:40:21:561	da4	GPU0 t=88C fan=99%, GPU1 t=84C fan=95%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=83C fan=78%
14:40:46:247	d20	GPU0 t=88C fan=99%, GPU1 t=85C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:41:17:174	d20	GPU0 t=88C fan=99%, GPU1 t=85C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:41:46:174	da4	DCR coefs (-ttdcr): GPU0 100%, GPU1 100%, GPU2 100%, GPU3 70%, GPU4 100%
14:41:46:237	da4	GPU0 t=88C fan=99%, GPU1 t=85C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:42:18:973	d20	GPU0 t=88C fan=99%, GPU1 t=85C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:42:20:036	da4	DCR coefs (-ttdcr): GPU0 100%, GPU1 100%, GPU2 100%, GPU3 70%, GPU4 100%
14:42:20:083	da4	GPU0 t=88C fan=99%, GPU1 t=85C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:42:49:847	d20	GPU0 t=88C fan=99%, GPU1 t=84C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%
14:42:53:053	da4	DCR coefs (-ttdcr): GPU0 100%, GPU1 100%, GPU2 100%, GPU3 70%, GPU4 100%
14:42:53:131	da4	GPU0 t=88C fan=99%, GPU1 t=84C fan=96%, GPU2 t=80C fan=66%, GPU3 t=90C fan=96%, GPU4 t=84C fan=78%

[Claymore]

Continue to test -ttdcr

It looks like it worked not exactly as I thought. See the log.

I set -ttdcr 88
I see that after going to 89 on GPU3 it decreases the DCR coef to 85% (not in the log) and then to 70%. But why it is not going lower? It is still 90 on the GPU3 but the DCR coef for the GPU3 is not 55% or 40%... Why? Isn't it a bug? 

-ttdcr works not in the same way as -tt. It gets temp delta (CurrentTemp - TargetTemp) and calculates intensity. Every 1C of delta is 15% of intensity. You can see current intensity by "s" key. So it will not reduce intensity until it gets 88C, but it will reduce intensity to 25% if temp reaches 93C. Perhaps I will change it to make it work similar to "-tt", I'm going to do some tests how it will work.