any idea when ethermine.org support will be added ?
and nanopool eth & sia ?
Nanopool not support Excavator. I wrote the pool administration, but they have long disregarded users' appeals, so the answer will be with low probability...
Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 34. (Read 179296 times)
July 01, 2017, 04:28:06 AM
and nanopool eth & sia ?
Nanopool not support Excavator. I wrote the pool administration, but they have long disregarded users' appeals, so the answer will be with low probability...
July 01, 2017, 03:19:38 AM
any idea when ethermine.org support will be added ?
and nanopool eth & sia ?
June 30, 2017, 03:32:20 PM
any idea when ethermine.org support will be added ?
June 30, 2017, 02:03:23 PM
Okay, testing it:
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
Wow! nice hash
Could you share OC setup?
Thank you
Sure.
+100, +900, 80W, 60% fan.
Cards are with Samsung memory chips.
Mine are Hynix ...will try and share how far could I go
June 30, 2017, 11:50:10 AM
I get 150mh with new ethminer optimised for 1060 with my 6x 1060 3gb
80%tdp
+100 core
+880 memory
Power consumption 525w total
This is like nicehash app but more fast? And you get paid in bitcoin?
80%tdp
+100 core
+880 memory
Power consumption 525w total
This is like nicehash app but more fast? And you get paid in bitcoin?
June 30, 2017, 11:35:48 AM
I have reported the same admin mode AMD issue on github again with new version
Please fix this devs!!
I would like to run some miners just for BTC rather than changing to BTC
I have faith, you seem to be so close.
Can you tell me what you think the issue is? hardware/software/code bugs?
Something I noticed in the last version was this;
Hashrate got to 190 (7 x rx480) - Great!
After about 12hrs hashrate continually fell to about 140 (when i stopped it)
I would like to use this miner, but until its as profitable as Claymore, I really can't
Please fix this devs!!
I would like to run some miners just for BTC rather than changing to BTC
I have faith, you seem to be so close.
Can you tell me what you think the issue is? hardware/software/code bugs?
Something I noticed in the last version was this;
Hashrate got to 190 (7 x rx480) - Great!
After about 12hrs hashrate continually fell to about 140 (when i stopped it)
I would like to use this miner, but until its as profitable as Claymore, I really can't
June 30, 2017, 11:22:21 AM
@nicehash:
After more testing I see there are many bad shares (share above target) > 20%.
After more testing I see there are many bad shares (share above target) > 20%.
Which pool do you use? Have you tried with a bit lower mem OC? It is possible that OC is too agressive causing memory errors which produce invalid shares.
Nicehash.
Same core/mem settings don't cause those errors on claymore and latest ethmier.
I think that you included in miner latest ethminer patch (--cuda-parallel-hash).
No, we did not include, GPL would not allow us that, but we used the idea + some other tunning.
June 30, 2017, 11:12:38 AM
@nicehash:
After more testing I see there are many bad shares (share above target) > 20%.
After more testing I see there are many bad shares (share above target) > 20%.
Which pool do you use? Have you tried with a bit lower mem OC? It is possible that OC is too agressive causing memory errors which produce invalid shares.
Nicehash.
Same core/mem settings don't cause those errors on claymore and latest ethmier.
I think that you included in miner latest ethminer patch (--cuda-parallel-hash).
June 30, 2017, 10:08:35 AM
For all the people that are getting net errors when using pools that aren't NiceHash. That is because Excavator is only using strict protocol specifications. Any deviations out of that will cause something to be broken. If you wish to fix this, contact pool operators to fix their protocol and make it by specifications.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
I tried several pools and same results, which is a pitty, I would have loved to test doublemining daggerhashimoto with sia and lbry, but I dont mine ETH, I only mine ETC right now, and suprnova doesnt have an ETC pool.
I am currently using claymore dual miner with on rig of 5 Asus 1070, and I get 29Mh for ETC and about 295Mh on SIA, which is pretty neat, you get SIA for free basically.
I am pretty sure contacting pool managers will not result in anything, they are probably happy with the way things are working, no need for them to change anything.
Yes, and we won't change anything either. We do not want to participate in this double work duplicate shit that started previously year already when bunch of monkeys at dwarfpool created so called "stratum for ethereum".
Does this include ethermine.org? When I try their stratum URL excavator throws: Net error: JSON member "result" not expected type: Array
To my knowledge, only suprnova implemented real stratum. All other pools use that dup(e) shit protocol where some miners can cheat with sending dup shares.
June 30, 2017, 10:05:48 AM
@nicehash:
After more testing I see there are many bad shares (share above target) > 20%.
After more testing I see there are many bad shares (share above target) > 20%.
Which pool do you use? Have you tried with a bit lower mem OC? It is possible that OC is too agressive causing memory errors which produce invalid shares.
June 30, 2017, 07:26:21 AM
For all the people that are getting net errors when using pools that aren't NiceHash. That is because Excavator is only using strict protocol specifications. Any deviations out of that will cause something to be broken. If you wish to fix this, contact pool operators to fix their protocol and make it by specifications.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
I tried several pools and same results, which is a pitty, I would have loved to test doublemining daggerhashimoto with sia and lbry, but I dont mine ETH, I only mine ETC right now, and suprnova doesnt have an ETC pool.
I am currently using claymore dual miner with on rig of 5 Asus 1070, and I get 29Mh for ETC and about 295Mh on SIA, which is pretty neat, you get SIA for free basically.
I am pretty sure contacting pool managers will not result in anything, they are probably happy with the way things are working, no need for them to change anything.
Yes, and we won't change anything either. We do not want to participate in this double work duplicate shit that started previously year already when bunch of monkeys at dwarfpool created so called "stratum for ethereum".
Does this include ethermine.org? When I try their stratum URL excavator throws: Net error: JSON member "result" not expected type: Array
June 30, 2017, 07:12:58 AM
@nicehash:
After more testing I see there are many bad shares (share above target) > 20%.
After more testing I see there are many bad shares (share above target) > 20%.
June 30, 2017, 07:04:20 AM
Dupe
June 30, 2017, 06:58:14 AM
Okay, testing it:
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
Wow! nice hash
Could you share OC setup?
Thank you
Sure.
+100, +900, 80W, 60% fan.
Cards are with Samsung memory chips.
June 30, 2017, 06:45:42 AM
Okay, testing it:
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
Wow! nice hash
Could you share OC setup?
Thank you
June 30, 2017, 06:43:20 AM
[15:42:00][0x00000e18][info] Log started
[15:42:01][0x00000e18][error] opencl | Failed to load phymem.
[15:42:01][0x00000e18][error] opencl | Please run miner as administrator if you are using AMD cards.
and work only 1 card....
Any help me?
[15:42:01][0x00000e18][error] opencl | Failed to load phymem.
[15:42:01][0x00000e18][error] opencl | Please run miner as administrator if you are using AMD cards.
and work only 1 card....
Any help me?
June 30, 2017, 06:25:21 AM
Okay, testing it:
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
~148 MH/s on 6 x 1060 3GB.
Also very fast DAG generation.
Q: What number of miner threads is optimal? 1 or 2?
Anyway, good job!
June 30, 2017, 04:48:55 AM
@baten
Coinotron pool works for ETH also, they have ETC too but did not test it....
I tested a bit dual mine but was not happy, same with claymore it VERY BAD on Nvidia..... (most ppl dual mining on claymore lose money but they are stupid to calculate and pay 2% fee for less just for claymore name on NV)
I only know claymore worked a lot on asm on AMD to make it usable and with almost no hash drop on ethereum, for some reason NV see hash drop and its not profitable
Coinotron pool works for ETH also, they have ETC too but did not test it....
I tested a bit dual mine but was not happy, same with claymore it VERY BAD on Nvidia..... (most ppl dual mining on claymore lose money but they are stupid to calculate and pay 2% fee for less just for claymore name on NV)
I only know claymore worked a lot on asm on AMD to make it usable and with almost no hash drop on ethereum, for some reason NV see hash drop and its not profitable
June 30, 2017, 04:44:54 AM
What about the gtx 1080 hash rate on Ethereum on last miner update?
June 30, 2017, 04:27:10 AM
For all the people that are getting net errors when using pools that aren't NiceHash. That is because Excavator is only using strict protocol specifications. Any deviations out of that will cause something to be broken. If you wish to fix this, contact pool operators to fix their protocol and make it by specifications.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
Now, regarding daggerhashimoto compatibility with other pools. Unfortunately, only suprnova implemented protocol EthereumStratum: https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt
There is one very good reason why we created this protocol and why we will never support other protocols - with other protocols, duplicates are allowed because miners can work on same piece of work.
I tried several pools and same results, which is a pitty, I would have loved to test doublemining daggerhashimoto with sia and lbry, but I dont mine ETH, I only mine ETC right now, and suprnova doesnt have an ETC pool.
I am currently using claymore dual miner with on rig of 5 Asus 1070, and I get 29Mh for ETC and about 295Mh on SIA, which is pretty neat, you get SIA for free basically.
I am pretty sure contacting pool managers will not result in anything, they are probably happy with the way things are working, no need for them to change anything.
Yes, and we won't change anything either. We do not want to participate in this double work duplicate shit that started previously year already when bunch of monkeys at dwarfpool created so called "stratum for ethereum".
Thanks guys for the new miner.
Are you willing to share the config file on how to get the best speeds for 1070 and 1060?
Are you willing to share the config file on how to get the best speeds for 1070 and 1060?
There is nothing special. To reach 33 MH/s on 1070, you need to up your mem to 4700 MHz. You can also push TDP down to the bottom - speed stays the same. For 1060 to reach 24.7 MH/s, you also need to push your mem to 4700 MHz and TDP to low. We managed to get these 24.7 MH/s with only 73 W of power consumption.
Jump to: