Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1194. (Read 6590565 times)

member
Activity: 89
Merit: 10
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 Wink
staff
Activity: 3472
Merit: 4111
Crypto Swap Exchange
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



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.
donator
Activity: 1610
Merit: 1325
Miners developer
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).
member
Activity: 80
Merit: 10
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!
donator
Activity: 1610
Merit: 1325
Miners developer
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.
member
Activity: 80
Merit: 10
It's interesting. According to current whattomine results, mining SIA gives me +45% of the profit for R9 390 card. Wow!
member
Activity: 80
Merit: 10
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
newbie
Activity: 7
Merit: 0
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.
donator
Activity: 1610
Merit: 1325
Miners developer
Claymore 5.2 crashes for me anytime I send epool.txt or config.txt from ethman v1.5 Windows 10

With debug enabled last line is:

Code:
Remote management: file config.txt was downloaded

File gets downloaded just fine

Confirmed, I will upload an update within a few hours.
donator
Activity: 1610
Merit: 1325
Miners developer
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.
member
Activity: 80
Merit: 10
Well, It's mostly clear now. The last (I hope) question. If I've changed the order of GPU with -di option, how other options  work? If I set "-mode 1-01", then these "01" are numbers before applying -di option or after that?

All other options work with miner's GPU list, i.e. after applying "-di" option.

Well, I'm trying to implement all of this, but... If I don't set -di option at all, then the order of GPUs in the miner doesn't match the order of GPUs in Afterburner. I see that in terms of temperatures:

Miner  : GPU0: 85, GPU1: 80, GPU2: 87
MSI AB: GPU1: 87, GPU2: 85, GPU3: 80

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

UPD: Before doing this, I detected that -di 201 is the correct order of GPUs in terms of working. I started -di 0, -di 1, -di 2 and saw which GPU in Afterburner is working. It's very strange, but if we apply -di 201 to the temperature list from the miner (not to the OpenCL list!), then we get exactly MSI AB temperature order. Hm...
donator
Activity: 1610
Merit: 1325
Miners developer
Well, It's mostly clear now. The last (I hope) question. If I've changed the order of GPU with -di option, how other options  work? If I set "-mode 1-01", then these "01" are numbers before applying -di option or after that?

All other options work with miner's GPU list, i.e. after applying "-di" option.
member
Activity: 80
Merit: 10

Even if you set "-di 1" miner will show "GPU0" anyway. But this GPU0 will be GPU1 (i.e. second GPU) in OpenCL list. With "-di" you don't change order of temps list, you change order in miner GPUs list that is taken from OpenCL list of GPUs. The list of temperatures is always the same.
Afterburner does not have to use OpenCL to mine, so it can match temps and GPUs. Miner has to use two lists: for temperatures control and for OpenCL work.
Again: "-di" change the list of GPUs in miner. For example:
1. You don't specify "-di". Miner directly takes entire list of GPUs from OpenCL list:
OpenCL          Miner
GPU0         GPU0
GPU1         GPU1
GPU2         GPU2
GPU3         GPU3

2. You specified "-di 1":
OpenCL          Miner
GPU1         GPU0

So miner displays "GPU0" because it is the first GPU in its list. But this is GPU1 in OpenCL list.

3. You specified "-di 3210":
OpenCL          Miner
GPU3         GPU0
GPU2         GPU1
GPU1         GPU2
GPU0         GPU3

So miner takes GPU3 from OpenCL list and adds it to its list of GPUs, so it will be GPU0 for miner. Then it takes GPU2 from OpenCL and saves it as "GPU1", and so on.
"-di ABCD" (A, B, C, D are some numbers) will cause GPU_A from OpenCL list becomes GPU0 in miner, GPU_B from OpenCL list becomes GPU1 in the miner, etc.
So you can renumber cards as you want to match temps list. The only possible problem if you don't want to assign all cards to miner, in this case sometimes you won't be able to renumber GPUs in a proper way. I think about adding another option "-map" for that, but it seems it will make things even more complex to understand.


Well, It's mostly clear now. The last (I hope) question. If I've changed the order of GPU with -di option, how other options  work? If I set "-mode 1-01", then these "01" are numbers before applying -di option or after that?
sr. member
Activity: 298
Merit: 250
Hello all!
I think it is great miner, have been mining on it since the ver. 1.2beta Smiley
I was mining ETH as the first coin and when it forked in two blockchains, it appears to be more profitable to mine ETC at the moment.
miningpoolhub.com has this option and can autoswitch between two chains on the fly!
Is there any way to make it working with Claymore? Sia is working good as the second coin.
Please help!
Thank you
newbie
Activity: 41
Merit: 0
Does it work with the RX 480?

Version 5.1 Beta 2 already work on RX480, but you won't be able to see the temperature from claymore, which I think the watchdog will be useless.
For Linux user is the same and worse, since there is no alternative software to see the temperature ( adl3 - atitweak no longer works )

The good part is windows and linux now has the same hash speed in mining, since the driver will be at the same level between both OS.
Overclock only works using windows and with the stock amd software. I'm not sure is vbe7.0.7 and atiflash can oc this one since they are incapable to oc since R9 380.
full member
Activity: 199
Merit: 100
Does it work with the RX 480?
legendary
Activity: 4354
Merit: 3614
what is this "brake pedal" you speak of?
what is the benefit if you use SIA Stratum protocol?

less stales/rejects

also less bandwidth
newbie
Activity: 8
Merit: 0
Claymore 5.2 crashes for me anytime I send epool.txt or config.txt from ethman v1.5 Windows 10

With debug enabled last line is:

Code:
Remote management: file config.txt was downloaded

File gets downloaded just fine
donator
Activity: 1610
Merit: 1325
Miners developer
I'm not sure which stratum variant claymore is using for Sia .. doesn't seem to work with mine though :-(

Currently I use an easy Stratum version, it's similar to HTTP protocol so it's easy to implement (must be easy to implement on pool side too). My miner does not use sgminer code so it takes me long to implement your Stratum version.

https://bitcointalksearch.org/topic/m.15727385

I would love to use this miner @ suprnova's pool.
It would be nice if you could make that happen ocminer, your pool would benefit highly with all the extra hashpower from the eth(etc)/sia miners using the perfect Claymore's miner, no doubt!
For now I have to use another pool, but I would like to go back to yours!

I'm looking at it, unfortunately there is no source, no documentation so I have to do some rev engineering again...

A pity that there is no consensus with those protocols.. maybe we should start a "pool consortium" and find a common way of writing/integrating stratums...

Protocol is similar to eth miner-proxy's Stratum. Differences are:
mining.notify params: jobid, header (80 bytes, 0x.....), target (32 bytes, 0x.....)
mining.submit params: login, jobid, header (80 bytes, 0x....). Header contains nonce that was found.
Actually it's a lot easier than your Stratum.

And I agree that it's annoying to have several Stratum versions for same coin. Even if I implement them all, there will be a mess with correct Stratum version selection.
legendary
Activity: 2688
Merit: 1240
I'm not sure which stratum variant claymore is using for Sia .. doesn't seem to work with mine though :-(

Currently I use an easy Stratum version, it's similar to HTTP protocol so it's easy to implement (must be easy to implement on pool side too). My miner does not use sgminer code so it takes me long to implement your Stratum version.

https://bitcointalksearch.org/topic/m.15727385

I would love to use this miner @ suprnova's pool.
It would be nice if you could make that happen ocminer, your pool would benefit highly with all the extra hashpower from the eth(etc)/sia miners using the perfect Claymore's miner, no doubt!
For now I have to use another pool, but I would like to go back to yours!

I'm looking at it, unfortunately there is no source, no documentation so I have to do some rev engineering again...

A pity that there is no consensus with those protocols.. maybe we should start a "pool consortium" and find a common way of writing/integrating stratums...
Jump to: