Claymore, I am still curious why the 290X and Fury X hashrates are identical, after all, fury X has many more CUs and higher memory bandwidth.
More CUs and bandwidth are not important for ETH, memory latency is the key. |
|
|
|
Claymore,
You can update the miner to cryptonote GPU (AMD) & CPU?
p.s. now last version GPU 9.3 and CPU 3.4
Why do you need an update? |
|
|
|
|
The problem with mininghub is that they support several stratum versions but don't say which stratum is supported and at which port. I still cannot make 12020 work (even with genoil), but port 17020 works for me:
EthDcrMiner64.exe -epool europe.ethash-hub.miningpoolhub.com:17020 -ewal Redhex.rig1 -epsw x -allcoins 1 -esm 2
|
|
|
|
I cannot make this port work, it does not send any data at all. It's a good idea to ask if this port works on miningpoolhub thread on forum. Or send me working config for any other miner so I can check how this port works. ethminer.exe -G -S europe.ethash-hub.miningpoolhub.com:12020 -O gxxxo.ether This works Hmm, it does not work for me: e:\Ethereum\genoil>ethminer-0.9.41-genoil-1.0.7-optiminer-2.exe -G -S europe
.ethash-hub.miningpoolhub.com:12020 -O gxxxo.ether
Genoil's ethminer 0.9.41-genoil-1.0.7
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from RoBiK, tpruvot and sp_
Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
Found suitable OpenCL device [Fiji] with 4294967296 bytes of GPU memory
i 00:12:24|main Connecting to stratum server europe.ethash-hub.miningpoolhub
.com:12020
i 00:12:24|<unknown> Connected to stratum server europe.ethash-hub.miningpoo
lhub.com : 12020
i 00:12:24|<unknown> Starting farm
i 00:12:24|<unknown> Subscribed to stratum server
i 00:12:25|<unknown> Disconnecting
i 00:12:25|<unknown> Stopping farm
e:\Ethereum\genoil> |
|
|
|
I cannot make this port work, it does not send any data at all. It's a good idea to ask if this port works on miningpoolhub thread on forum. Or send me working config for any other miner so I can check how this port works. |
|
|
|
Hi mates, can I mine ETH and ETC at the same time with this miner? Thanks
Nope. There is pool called miningpoolhub ( https://miningpoolhub.com) And there is an option to mine ETH or ETC depending of whats profitable at the moment! THE POOL AUTOSWITCHES ETH AND ETC-- Nice to know, but ETH and ETC (and any other Dagger-Hashimoto coins) cannot be dual mined. The DAG files differ in size and character. The dual miner mines a memory intensive algo, and a compute intensive algo, and splits the load on the GPU so that it can be efficiently done. Merge-mining and autoswitching are done poolside. Merge-mining is not possible for Dagger-Hashimoto coins, because the DAG files differ, as stated above. I just answered the same question in this thread two days ago. --scryptr Pitty is that I have to check for profitability my self and shotdown ETH +SIA Claymore and start ETC+SIA Claymore miner manually I wanted to point this out! If the pool does it and give you 12020 port for this kind of mining.. so that miner does not have to switch anything.. but it just does not work with Claymore Why do you think that it does not work? Specify "-allcoins 1" option (or "-allcoins -1") and mine any Dagger-Hashimoto coin, even if pool changes coins all the time. Hi! Claymore.. Can you please confirm the full string that works for miningpoolhub.com and the Ethash autoswitch 12020 port + SIA (siamining stratum)? I tryed many different ways and allpools and allcoins, but may be I am little lost there. Thank you alot I did not try yet, but it must work. Devfee is not a problem. What's the problem exactly? I cannot find any info about 12020 port on pool help page however. |
|
|
|
Hi mates, can I mine ETH and ETC at the same time with this miner? Thanks
Nope. There is pool called miningpoolhub ( https://miningpoolhub.com) And there is an option to mine ETH or ETC depending of whats profitable at the moment! THE POOL AUTOSWITCHES ETH AND ETC-- Nice to know, but ETH and ETC (and any other Dagger-Hashimoto coins) cannot be dual mined. The DAG files differ in size and character. The dual miner mines a memory intensive algo, and a compute intensive algo, and splits the load on the GPU so that it can be efficiently done. Merge-mining and autoswitching are done poolside. Merge-mining is not possible for Dagger-Hashimoto coins, because the DAG files differ, as stated above. I just answered the same question in this thread two days ago. --scryptr Pitty is that I have to check for profitability my self and shotdown ETH +SIA Claymore and start ETC+SIA Claymore miner manually I wanted to point this out! If the pool does it and give you 12020 port for this kind of mining.. so that miner does not have to switch anything.. but it just does not work with Claymore Why do you think that it does not work? Specify "-allcoins 1" option (or "-allcoins -1") and mine any Dagger-Hashimoto coin, even if pool changes coins all the time. |
|
|
|
I just started using v5.2 this past Thursday, and have converted all my AMD rigs from Genoil's EthMiner since. I am about to upgrade to v5.3 this weekend. SiaCoin (SC) makes up about 20-25% of my mining revenue now, I didn't stay on Decred long enough to make a good estimate. Good Stuff!!!
I do have two questions:
1) How is the progress on the nVidia dual-miner coming? I have a lot of CUDA cards.
2) Do you think you might add Library Credits (lbry algo, LBC) as a third choice for a partner coin?
Thanks for your work. The miner has some really useful features. --scryptr
1. I'm working on, but almost every day I have to do something else: "-di detect" option, Stratum for Siacoin, etc. However, I hope to release first version for Nvidia in 1-2 weeks. 2. As soon as I have time for new coin I will add it. But right now I don't have time at all so I don't even check what coins are good. I want to use DualMiner for siacoin,but it was failed ....
Display:
SC: Stratum - connecting to 'siamining.com' <45.79.159.167> port 3333
Is it no support siamining pool?
No Stratum for Siacoin on suprnova and siamining pools for now, though you can use HTTP there, check "SAMPLE USAGE" section of readme. |
|
|
|
A serious Bug detected in -di detect option, that can lead to GPU damage (
While testing, the miner fixes the fan speed to 0 (for the faster heating). But it doesn't revert it back. So, I have to go to MSI AB to set the fans to Auto again.
Miner sets fan to 25% during tests, not to 0. And it will revert it back if you restart miner. Also it will work properly if you set "-tt" so miner manages temps, not drivers, so after tests miner will start fan management. However, if you don't use "-tt" and don't restart miner to apply "-di", miner will not return fan management to drivers, I will improve it to return fan management back to drivers after tests. Right now, if you specified "-di detect" and did not specify "-tt" - close miner after tests. |
|
|
|
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. |
|
|
|
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). |
|
|
|
|
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).
|
|
|
|
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. |
|
|
|
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: Remote management: file config.txt was downloaded File gets downloaded just fine Confirmed, I will upload an update within a few hours. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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://bitcointalk.org/index.php?topic=1433925.msg15727385#msg15727385I 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. |
|
|
|
What do you mean? If I run -di 1 it means that I run the miner for GPU1 (from my example), but actually, I will see GPU0 in the miner in both MH and T log strings. Like
MH:: GPU0: 28Mh
T:: GPU0: t=72C fan=69%
Right? So, what's the reason? They don't match yet. And I see no way how to match here.
...
if MSI Afterburner can match performance data and temp data somehow, then I can match temps, shown in MSI Afterburner and temps in CDM and get a correct "translation table"
This is the only way I see. Can you suggest any others? Without such matching all temperature features are just useless for multi GPU rigs. And the question how making a "translation table" is not covered anywhere at all.
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. |
|
|
|
Dear @Claymore, I try to repeat my question ) Dear @Claymore! Let me understand -DI option, please, to match the temperature order and the GPU order.
Let's say, I see
MH:: GPU0: 20Mh, GPU1 28Mh, GPU2: 27Mh, GPU3: 30Mh
and
T:: GPU0: t=70C fan=69%, GPU1: t=71C fan=69%, GPU2: t=72C fan=69%, GPU3: t=73C fan=69%
I do some testing and understand, that MH=T matching is:
0=1
1=2
2=0
3=3
So, I want to see
T:: GPU0: t=71C fan=69%, GPU1: t=72C fan=69%, GPU2: t=70C fan=69%, GPU3: t=73C fan=69%
Then I want to set -di parameters to match the orders. What should I write?
-di 1203 ?
-di 2013 ?
Anything else?
-di 1203 if you correctly described. If it does not work, try "-di 1", "-di 2" etc to see how it works for one card. Then if you see match, set "-di 12" to add one more card and see if it matches, etc. |
|
|
|
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://bitcointalk.org/index.php?topic=1433925.msg15727385#msg15727385 |
|
|
|
|
Show Posts
