Bitcoin Forum
April 24, 2024, 06:50:24 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 [90] 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 ... 1412 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)  (Read 6589756 times)
spiete
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
May 12, 2016, 10:52:59 AM
Last edit: June 02, 2016, 05:49:00 PM by spiete
 #1781

Is Claymore working with dwarf through stratum?

What settings should it be?



Also Dwarf Admin said that Claymore are working bad with failover servers.



He suggest usung local proxy with 1+3 failover servers.

How to set up this?
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713941424
Hero Member
*
Offline Offline

Posts: 1713941424

View Profile Personal Message (Offline)

Ignore
1713941424
Reply with quote  #2

1713941424
Report to moderator
Yanakitu Tenatako
Sr. Member
****
Offline Offline

Activity: 328
Merit: 250


View Profile
May 12, 2016, 10:57:53 AM
 #1782

After restart I am getting EthDcrminer64.exe Initialization error 5 on 2 rigs. Genoil works. These rigs worked for months before restart. What is wrong? Is there some time limit or so?

BitFinex, best trading platform ever.
Register here: https://www.bitfinex.com/?refcode=53wNhi4gTx
Claymore (OP)
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 12, 2016, 11:26:21 AM
 #1783

Is Claymore working with dwarf through stratum?
What settings should it be?

It's a good idea to read first post of this thread, it has a lot of samples for many pools.

Also Dwarf Admin said that Claymore are working bad with failover servers.

Can you please send a link to this Atrides's message? I'd like to know a bit more details.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
spiete
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
May 12, 2016, 11:55:15 AM
 #1784

Is Claymore working with dwarf through stratum?
What settings should it be?

It's a good idea to read first post of this thread, it has a lot of samples for many pools.

Also Dwarf Admin said that Claymore are working bad with failover servers.

Can you please send a link to this Atrides's message? I'd like to know a bit more details.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1


d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
May 12, 2016, 12:06:50 PM
Last edit: May 12, 2016, 03:23:33 PM by d57heinz
 #1785

Is Claymore working with dwarf through stratum?
What settings should it be?

It's a good idea to read first post of this thread, it has a lot of samples for many pools.

Also Dwarf Admin said that Claymore are working bad with failover servers.

Can you please send a link to this Atrides's message? I'd like to know a bit more details.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1




you mind telling me what servers you were on.. the us server sucks .. i was getting 10 second lags on the share submitting.. I finally went to eu server.. but even it was doing funny things last couple days,, Id say its not claymores miner.. it was def dwarf.. i have yet to be satisfied of what it reports i get in hash and what i got paid from there.. always about 10 % less than i calculated..

Best Regards
d57heinz

edit ill dig thru my logs just to confirm.. One thing i really like about his miner.. It keeps a txt log off all output. Smiley

this is when it started acting up.. I was getting shares found but dwarf wasnt reporting back to me that it was accepted.. Thats when i checked the site and noticed too that my numbers dropped way down on accepted shares.. Ill post in a few i have found many entries that show that it took well over 3 seconds for some shares to be accepted.. With a fast block coin thats unacceptable.


Code:
buf: 

15:07:47:921 1858 ETH: put share nonce 283f0388114bb420
15:07:47:921 1858 ETH round found 1 shares
15:07:47:937 1860 ETH: 05/08/16-15:07:47 - SHARE FOUND - (GPU 3)
15:07:47:937 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x283f0388114bb420","0x3c4ca5983611feca62ee3a996a02026e765b5e6c25b50926ff704da67386eff6","0x02e67da788ad0bb1ef6c83f7a5f515df0cc7d68396b0111f99ae51dd660b1c95"]}


15:07:49:781 1420 em hbt: 0, fm hbt: 47,
15:07:49:781 1420 watchdog - thread 0, hb time 250
15:07:49:781 1420 watchdog - thread 1, hb time 47
15:07:49:781 1420 watchdog - thread 2, hb time 469
15:07:49:781 1420 watchdog - thread 3, hb time 219
15:07:49:781 1420 watchdog - thread 4, hb time 312
15:07:49:796 1420 watchdog - thread 5, hb time 109
15:07:49:796 1420 watchdog - thread 6, hb time 281
15:07:49:796 1420 watchdog - thread 7, hb time 94
15:07:50:374 1860 got 244 bytes
15:07:50:374 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:07:50:374 1860 parse packet: 243
15:07:50:374 1860 eth: job changed
15:07:50:374 1860 remove first packet 1
15:07:50:374 1860 new buf size: 1
15:07:50:390 1860 buf:

15:07:50:390 1860 ETH: 05/08/16-15:07:50 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:07:50:390 1860 ETH - Total Speed: 103.722 Mh/s, Total Shares: 3444, Rejected: 1, Time: 19:16
15:07:50:390 1860 ETH: GPU0 26.681 Mh/s, GPU1 17.502 Mh/s, GPU2 29.870 Mh/s, GPU3 29.668 Mh/s
15:07:50:453 1854 Job changed, drop current round
15:07:50:453 1850 Job changed, drop current round
15:07:50:484 185c Job changed, drop current round
15:07:50:484 1858 Job changed, drop current round
15:07:50:531 184c Job changed, drop current round
15:07:50:531 1844 Job changed, drop current round
15:07:50:531 1848 Job changed, drop current round
15:07:50:531 1840 Job changed, drop current round
15:07:57:000 1860 ETH: checking pool connection...
15:07:57:000 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:07:57:000 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x635ed8f", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:07:57:062 1860 got 244 bytes
15:07:57:062 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:07:57:062 1860 parse packet: 243
15:07:57:062 1860 eth: job is the same
15:07:57:062 1860 remove first packet 1
15:07:57:062 1860 new buf size: 1
15:07:57:078 1860 buf:

15:08:03:594 1850 ETH: put share nonce 21f4d9ec0b5985f0
15:08:03:594 1850 ETH round found 1 shares
15:08:03:609 1860 ETH: 05/08/16-15:08:03 - SHARE FOUND - (GPU 2)
15:08:03:609 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x21f4d9ec0b5985f0","0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0xfa43e0345bd961b323da81c592a087a669da347c992dbf0ca82e181f43c0e669"]}


15:08:04:641 1850 ETH: put share nonce 21f4d9ec0c768129
15:08:04:641 1850 ETH round found 1 shares
15:08:04:656 1860 ETH: 05/08/16-15:08:04 - SHARE FOUND - (GPU 2)
15:08:04:656 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x21f4d9ec0c768129","0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x4591c5dc863620673c369ad892924348e91a93ae2505a7e19eafd3de87ebb65b"]}


15:08:07:016 1860 ETH: checking pool connection...
15:08:07:016 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:07:016 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x636dca3", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:07:094 1860 got 244 bytes
15:08:07:094 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:07:094 1860 parse packet: 243
15:08:07:094 1860 eth: job is the same
15:08:07:094 1860 remove first packet 1
15:08:07:094 1860 new buf size: 1
15:08:07:094 1860 buf:

15:08:17:032 1860 ETH: checking pool connection...
15:08:17:032 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:17:032 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6376720", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:17:094 1860 got 244 bytes
15:08:17:094 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:17:094 1860 parse packet: 243
15:08:17:094 1860 eth: job is the same
15:08:17:094 1860 remove first packet 1
15:08:17:094 1860 new buf size: 1
15:08:17:094 1860 buf:

15:08:19:829 1420 em hbt: 16, fm hbt: 16,
15:08:19:829 1420 watchdog - thread 0, hb time 266
15:08:19:829 1420 watchdog - thread 1, hb time 63
15:08:19:829 1420 watchdog - thread 2, hb time 313
15:08:19:829 1420 watchdog - thread 3, hb time 78
15:08:19:829 1420 watchdog - thread 4, hb time 328
15:08:19:829 1420 watchdog - thread 5, hb time 125
15:08:19:844 1420 watchdog - thread 6, hb time 156
15:08:19:844 1420 watchdog - thread 7, hb time 359
15:08:27:048 1860 ETH: checking pool connection...
15:08:27:048 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:27:048 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6370d00", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:27:142 1860 got 244 bytes
15:08:27:142 1860 buf: {"result":["0xd544c1b3a04913e8ff549d3afeccdd4a57f4d20b63d58ba457db7db461ef192f","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:27:142 1860 parse packet: 243
15:08:27:142 1860 eth: job is the same
15:08:27:142 1860 remove first packet 1
15:08:27:142 1860 new buf size: 1
15:08:27:142 1860 buf:

15:08:27:204 1860 got 244 bytes
15:08:27:204 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:08:27:204 1860 parse packet: 243
15:08:27:204 1860 eth: job changed
15:08:27:204 1860 remove first packet 1
15:08:27:204 1860 new buf size: 1
15:08:27:204 1860 buf:

15:08:27:220 1860 ETH: 05/08/16-15:08:27 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:08:27:220 1860 ETH - Total Speed: 104.267 Mh/s, Total Shares: 3446, Rejected: 1, Time: 19:17
15:08:27:220 1860 ETH: GPU0 26.785 Mh/s, GPU1 17.638 Mh/s, GPU2 29.920 Mh/s, GPU3 29.924 Mh/s
15:08:27:235 1848 Job changed, drop current round
15:08:27:235 184c Job changed, drop current round
15:08:27:313 1844 Job changed, drop current round
15:08:27:329 1840 Job changed, drop current round
15:08:27:329 185c Job changed, drop current round
15:08:27:345 1858 Job changed, drop current round
15:08:27:360 1850 Job changed, drop current round
15:08:27:376 1854 Job changed, drop current round
15:08:27:688 1844 ETH: put share nonce d5acf358003d2e24
15:08:27:704 1844 ETH round found 1 shares
15:08:27:720 1860 ETH: 05/08/16-15:08:27 - SHARE FOUND - (GPU 0)
15:08:27:720 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xd5acf358003d2e24","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x369365e98f91879277d6cdda47a0b576bb6970fd9d377a288a8010f5e553adff"]}


15:08:28:454 185c ETH: put share nonce b15b444000e31c90
15:08:28:454 185c ETH round found 1 shares
15:08:28:470 1860 ETH: 05/08/16-15:08:28 - SHARE FOUND - (GPU 3)
15:08:28:470 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xb15b444000e31c90","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x12586d487964b0225f4c97577098b1d6360f7f0392a79e9dd34a0ea82aacd85c"]}


15:08:33:157 184c ETH: put share nonce 9554f330031ed640
15:08:33:157 184c ETH round found 1 shares
15:08:33:173 1860 ETH: 05/08/16-15:08:33 - SHARE FOUND - (GPU 1)
15:08:33:173 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x9554f330031ed640","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x8194182ca30ee4b65903999a4ed783c2a9c101f6bc4e207e8e50ab8f0e1bd3ed"]}


15:08:37:064 1860 ETH: checking pool connection...
15:08:37:064 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:37:064 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x636f4fe", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:37:126 1860 got 244 bytes
15:08:37:126 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:37:126 1860 parse packet: 243
15:08:37:126 1860 eth: job is the same
15:08:37:126 1860 remove first packet 1
15:08:37:126 1860 new buf size: 1
15:08:37:126 1860 buf:

15:08:38:408 184c ETH: put share nonce 9554f33005ee3875
15:08:38:408 184c ETH round found 1 shares
15:08:38:423 1860 ETH: 05/08/16-15:08:38 - SHARE FOUND - (GPU 1)
15:08:38:423 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x9554f33005ee3875","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0xfd3f8ad8ca0e4af02fb29882f0d85477a16702054e056f31df2a105d3e637534"]}


15:08:38:689 1858 ETH: put share nonce 3b2edb040a15daa0
15:08:38:705 1858 ETH round found 1 shares
15:08:38:720 1860 ETH: 05/08/16-15:08:38 - SHARE FOUND - (GPU 3)
15:08:38:720 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x3b2edb040a15daa0","0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x6644de2cbf115a09cdb310e20479ca258cc026bf5a25dfb1de96b5b2d89cb762"]}


15:08:47:080 1860 ETH: checking pool connection...
15:08:47:080 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:47:080 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x637c9db", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:47:142 1860 got 244 bytes
15:08:47:142 1860 buf: {"result":["0xe210ddf15a53ecefb85f94bfea8c0a112e54ccf690d9aecc028c8b749d7e5c6a","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:47:142 1860 parse packet: 243
15:08:47:142 1860 eth: job is the same
15:08:47:142 1860 remove first packet 1
15:08:47:142 1860 new buf size: 1
15:08:47:142 1860 buf:

15:08:49:877 1420 em hbt: 16, fm hbt: 94,
15:08:49:877 1420 watchdog - thread 0, hb time 78
15:08:49:877 1420 watchdog - thread 1, hb time 281
15:08:49:877 1420 watchdog - thread 2, hb time 141
15:08:49:877 1420 watchdog - thread 3, hb time 375
15:08:49:877 1420 watchdog - thread 4, hb time 188
15:08:49:877 1420 watchdog - thread 5, hb time 375
15:08:49:893 1420 watchdog - thread 6, hb time 235
15:08:49:893 1420 watchdog - thread 7, hb time 31
15:08:53:736 1860 got 244 bytes
15:08:53:736 1860 buf: {"result":["0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:08:53:736 1860 parse packet: 243
15:08:53:736 1860 eth: job changed
15:08:53:736 1860 remove first packet 1
15:08:53:736 1860 new buf size: 1
15:08:53:736 1860 buf:

15:08:53:752 1860 ETH: 05/08/16-15:08:53 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:08:53:752 1860 ETH - Total Speed: 104.231 Mh/s, Total Shares: 3451, Rejected: 1, Time: 19:17
15:08:53:752 1860 ETH: GPU0 26.788 Mh/s, GPU1 17.631 Mh/s, GPU2 29.909 Mh/s, GPU3 29.903 Mh/s
15:08:53:752 185c Job changed, drop current round
15:08:53:768 1858 Job changed, drop current round
15:08:53:768 1840 Job changed, drop current round
15:08:53:768 1844 Job changed, drop current round
15:08:53:799 1854 Job changed, drop current round
15:08:53:815 1850 Job changed, drop current round
15:08:53:846 184c Job changed, drop current round
15:08:53:846 1848 Job changed, drop current round
15:08:57:096 1860 ETH: checking pool connection...
15:08:57:096 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:08:57:096 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6369085", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:08:57:158 1860 got 244 bytes
15:08:57:158 1860 buf: {"result":["0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:08:57:158 1860 parse packet: 243
15:08:57:158 1860 eth: job is the same
15:08:57:158 1860 remove first packet 1
15:08:57:158 1860 new buf size: 1
15:08:57:158 1860 buf:

15:08:57:283 1840 ETH: put share nonce b9aa581802ac1490
15:08:57:283 1840 ETH round found 1 shares
15:08:57:299 1860 ETH: 05/08/16-15:08:57 - SHARE FOUND - (GPU 0)
15:08:57:299 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xb9aa581802ac1490","0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x088b6f71a6dc557b6a61074b655e8ec0c50c66a6891a8339661e449c8b81a014"]}


15:08:58:502 1858 ETH: put share nonce 13c274b404274b5d
15:08:58:502 1858 ETH round found 1 shares
15:08:58:518 1860 ETH: 05/08/16-15:08:58 - SHARE FOUND - (GPU 3)
15:08:58:518 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x13c274b404274b5d","0x9c4ed9dc6aa49a31cda584b980c65071489cb69dc68650395604148f33c638bc","0x4a0357031ddc6e9f5e0d2aaf965548a0c99a7d224873f36039e33259dd9fc6ee"]}


15:09:06:003 1860 got 244 bytes
15:09:06:003 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:09:06:003 1860 parse packet: 243
15:09:06:003 1860 eth: job changed
15:09:06:003 1860 remove first packet 1
15:09:06:003 1860 new buf size: 1
15:09:06:003 1860 buf:

15:09:06:003 1860 ETH: 05/08/16-15:09:06 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:09:06:018 1860 ETH - Total Speed: 104.314 Mh/s, Total Shares: 3453, Rejected: 1, Time: 19:17
15:09:06:018 1860 ETH: GPU0 26.795 Mh/s, GPU1 17.637 Mh/s, GPU2 29.953 Mh/s, GPU3 29.930 Mh/s
15:09:06:018 1840 Job changed, drop current round
15:09:06:018 1844 Job changed, drop current round
15:09:06:128 185c Job changed, drop current round
15:09:06:128 1858 Job changed, drop current round
15:09:06:174 1848 Job changed, drop current round
15:09:06:174 184c Job changed, drop current round
15:09:06:190 1850 Job changed, drop current round
15:09:06:190 1854 Job changed, drop current round
15:09:07:112 1860 ETH: checking pool connection...
15:09:07:112 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:09:07:112 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6364821", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:09:07:175 1860 got 244 bytes
15:09:07:175 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:09:07:175 1860 parse packet: 243
15:09:07:175 1860 eth: job is the same
15:09:07:175 1860 remove first packet 1
15:09:07:175 1860 new buf size: 1
15:09:07:190 1860 buf:

15:09:17:128 1860 ETH: checking pool connection...
15:09:17:128 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:09:17:128 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6377ed2", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:09:17:191 1860 got 244 bytes
15:09:17:191 1860 buf: {"result":["0x904031cd0a1f2b954f2baac9bb4357fc05aac509c7f496f34bd2ed7fb5a7648c","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:09:17:191 1860 parse packet: 243
15:09:17:191 1860 eth: job is the same
15:09:17:191 1860 remove first packet 1
15:09:17:191 1860 new buf size: 1
15:09:17:191 1860 buf:

15:09:19:909 1420 em hbt: 0, fm hbt: 47,

heres just one example.. i have hundreds more it appears ;/  didnt realize it was that bad for so long.. ehh thats what happens when you (set and forget).

Code:
ETH: 05/08/16-15:22:09 - SHARE FOUND - (GPU 1)
15:22:09:317 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0xc7b17160003e7631","0x37c0f742aa0dc33aec20a568f45a032b6adc7164292d403e9606f36699247873","0x5869dbb8c7964481ee65b5239cd36e0fa715480b945afcef5d6f4e2e9bebb736"]}


15:22:11:255 1860 ETH: checking pool connection...
15:22:11:255 1860 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}


15:22:11:255 1860 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6361ca7", "0x0000000000000000000000000000000000000000000000000000000097545cfb", "Asrock1"]}


15:22:11:333 1860 got 244 bytes
15:22:11:333 1860 buf: {"result":["0x37c0f742aa0dc33aec20a568f45a032b6adc7164292d403e9606f36699247873","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


15:22:11:333 1860 parse packet: 243
15:22:11:333 1860 eth: job is the same
15:22:11:333 1860 remove first packet 1
15:22:11:333 1860 new buf size: 1
15:22:11:333 1860 buf:

15:22:17:036 1860 got 40 bytes
15:22:17:036 1860 buf: {"id":4,"jsonrpc":"2.0","result":true}


15:22:17:036 1860 parse packet: 39
15:22:17:036 1860 ETH: Share accepted (7719 ms)!

15:22:17:036 1860 remove first packet 1
15:22:17:036 1860 new buf size: 1
15:22:17:036 1860 buf:

15:22:17:833 1860 got 40 bytes
15:22:17:833 1860 buf: {"id":6,"jsonrpc":"2.0","result":true}


15:22:17:833 1860 parse packet: 39
15:22:17:833 1860 remove first packet 1
15:22:17:833 1860 new buf size: 1
15:22:17:833 1860 buf:

15:22:20:083 1860 got 244 bytes
15:22:20:083 1860 buf: {"result":["0xa3c450677cda25ec700bb01897b40deaa973d96cdf179debbd1ab9fb0814d533","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


15:22:20:083 1860 parse packet: 243
15:22:20:083 1860 eth: job changed
15:22:20:083 1860 remove first packet 1
15:22:20:083 1860 new buf size: 1
15:22:20:083 1860 buf:

15:22:20:099 1860 ETH: 05/08/16-15:22:20 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
15:22:20:099 1860 ETH - Total Speed: 104.312 Mh/s, Total Shares: 3496, Rejected: 4, Time: 19:31
15:22:20:099 1860 ETH: GPU0 26.797 Mh/s, GPU1 17.634 Mh/s, GPU2 29.930 Mh/s, GPU3 29.951 Mh/s

This is the typical return time i get.. Around 80 ms for us server. and when i swapped to eu it was 120 ms round trip..

Code:
ETH: 05/07/16-19:51:30 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
19:51:30:235 1860 ETH - Total Speed: 104.103 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:51:30:237 1860 ETH: GPU0 26.653 Mh/s, GPU1 17.627 Mh/s, GPU2 29.919 Mh/s, GPU3 29.904 Mh/s
19:51:30:259 184c Job changed, drop current round
19:51:30:260 1850 Job changed, drop current round
19:51:30:262 1848 Job changed, drop current round
19:51:30:266 1854 Job changed, drop current round
19:51:30:298 1858 Job changed, drop current round
19:51:30:299 185c Job changed, drop current round
19:51:30:407 1844 Job changed, drop current round
19:51:30:410 1840 Job changed, drop current round
19:51:30:995 1840 ETH: put share nonce a89791000974346
19:51:30:997 1840 ETH round found 1 shares
19:51:30:999 1860 ETH: 05/07/16-19:51:30 - SHARE FOUND - (GPU 0)
19:51:30:999 1860 send: {"worker":"Asrock1","id":4,"method":"eth_submitWork","params":["0x0a89791000974346","0x6d17ae3e751193b988570fc5181d3fcb5c88904686429c5ceb694db81b19e53b","0xfc9a9de4a9ddc7e2ae58dc092873c96f4322bd017b8150a8efde3b76767b39cf"]}


19:51:31:078 1860 got 40 bytes
19:51:31:080 1860 buf: {"id":4,"jsonrpc":"2.0","result":true}


19:51:31:080 1860 parse packet: 39
19:51:31:086 1860 ETH: Share accepted (79 ms)!

19:51:31:090 1860 remove first packet 1
19:51:31:091 1860 new buf size: 1
19:51:31:091 1860 buf:

19:51:33:249 1860 got 244 bytes
19:51:33:252 1860 buf: {"result":["0x21b5a4d06f2fa097655d5c008e2421e580b2fb9c1989910940901de1e3272061","0x95d53b63d0b531598853dfe1f1271a355a583c442d509d228ff92a2b0a0d801a","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


19:51:33:254 1860 parse packet: 243
19:51:33:254 1860 eth: job changed
19:51:33:259 1860 remove first packet 1
19:51:33:262 1860 new buf size: 1
19:51:33:264 1860 buf:

19:51:33:264 1860 ETH: 05/07/16-19:51:33 - New job (target 0x0000000225c17d04) from eth-us.dwarfpool.com:8008
19:51:33:270 1860 ETH - Total Speed: 104.224 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
19:51:33:274 1860 ETH: GPU0 26.781 Mh/s, GPU1 17.6

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
spiete
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
May 12, 2016, 12:32:46 PM
 #1786

Is Claymore working with dwarf through stratum?
What settings should it be?

It's a good idea to read first post of this thread, it has a lot of samples for many pools.

Also Dwarf Admin said that Claymore are working bad with failover servers.

Can you please send a link to this Atrides's message? I'd like to know a bit more details.

I was asking Artides that my shares reducing second day in a row because of switching from servers.

He answered this.

https://i.snag.gy/bmDdnu.jpg

Translation of bottom message.

Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers


And i have a question.


Does this settings means that i mining on dwarfpool with stratum proxy?

EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1




you mind telling me what servers you were on.. the us server sucks .. i was getting 10 second lags on the share submitting.. I finally went to eu server.. but even it was doing funny things last couple days,, Id say its not claymores miner.. it was def dwarf.. i have yet to be satisfied of what it reports i get in hash and what i got paid from their.. always about 10 % less than i calced..

Best Regards
d57heinz

edit ill dig thru my logs just to confirm.. One thing i really like about his miner.. It keeps a txt log off all output. Smiley

after when  ru server was offline it reconnected to eu server

POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us2.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-asia.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0



d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
May 12, 2016, 12:49:29 PM
 #1787




after when  ru server was offline it reconnected to eu server

POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-us2.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0
POOL: eth-asia.dwarfpool.com:8008, WALLET: 0xA0F5578094e713c58B901eC43FB58bbbD7A63372, WORKER:dw1 , ESM: 0

could very well be that they get ddos a lot .   Due to the size.. i only used them just to test this miner.. Since it was new to me.. Im back solo now tho.. Waiting to pop the first block with this miner.. With 500 mhs i shoudl hit one in next couple days. with decent luck..

Best Regards
d57heinz

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
Claymore (OP)
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 12, 2016, 12:59:59 PM
 #1788

He answered this.
https://i.snag.gy/bmDdnu.jpg
Translation of bottom message.
Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers

In fact, I saw that dwarfpool had problems for a couple of days. You can see all miner actions in log files. If it cannot connect, cannot get job, or share accepting time >1sec - it is not a miner problem if everything is working on other pools.
Some people just put different dwarfpool severs in the failover list and when entire dwarfpool is down they ask why miner does not work. Excellent logic Smiley
If dwarfpool admin think that the problem is in miner we can talk about it in details, I'd like to see some proofs. May be he really knows something that I missed, I'm ready to fix it. But right now I have only proofs about recent problems of dwarfpool.
You can check how failover/reconnection works easily - disable network connection in Windows or plug off the network cable.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
spiete
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
May 12, 2016, 01:12:06 PM
 #1789

He answered this.
https://i.snag.gy/bmDdnu.jpg
Translation of bottom message.
Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers

In fact, I saw that dwarfpool had problems for a couple of days. You can see all miner actions in log files. If it cannot connect, cannot get job, or share accepting time >1sec - it is not a miner problem if everything is working on other pools.
Some people just put different dwarfpool severs in the failover list and when entire dwarfpool is down they ask why miner does not work. Excellent logic Smiley
If dwarfpool admin think that the problem is in miner we can talk about it in details, I'd like to see some proofs. May be he really knows something that I missed, I'm ready to fix it. But right now I have only proofs about recent problems of dwarfpool.
You can check how failover/reconnection works easily - disable network connection in Windows or plug off the network cable.

Does this address -epool eth-ru.dwarfpool.com:8008 means that im mining on dwarfpool with proxy?
Claymore (OP)
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 12, 2016, 01:21:57 PM
 #1790

He answered this.
https://i.snag.gy/bmDdnu.jpg
Translation of bottom message.
Claymore works badly with failovers and reconnections. Try use Claymore with local proxy with 1+3 failover servers

In fact, I saw that dwarfpool had problems for a couple of days. You can see all miner actions in log files. If it cannot connect, cannot get job, or share accepting time >1sec - it is not a miner problem if everything is working on other pools.
Some people just put different dwarfpool severs in the failover list and when entire dwarfpool is down they ask why miner does not work. Excellent logic Smiley
If dwarfpool admin think that the problem is in miner we can talk about it in details, I'd like to see some proofs. May be he really knows something that I missed, I'm ready to fix it. But right now I have only proofs about recent problems of dwarfpool.
You can check how failover/reconnection works easily - disable network connection in Windows or plug off the network cable.

Does this address -epool eth-ru.dwarfpool.com:8008 means that im mining on dwarfpool with proxy?

My miner does not require proxy, with these settings you mine on dwarfpool directly by using Stratum. Check "ADDITIONAL INFORMATION" section of first message of this thread for more details.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
Gagana
Member
**
Offline Offline

Activity: 80
Merit: 10


View Profile
May 12, 2016, 02:46:22 PM
 #1791

Guys, how do you set up Suprnova decred stratum in dpools.txt? I mean

stratum+tcp://dcr.suprnova.cc:2252
Tacalt
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
May 12, 2016, 03:14:48 PM
 #1792

Installed and running in minutes without a hitch!

...nice job on the console readouts btw

You are lucky guy. You are in the game when the current version is V 4.2. There are some problems in the early versions.
melloyellow
Full Member
***
Offline Offline

Activity: 176
Merit: 100


View Profile
May 12, 2016, 03:15:47 PM
 #1793

Claymore can you mine to miningpoolhub with only -esm 0 and the 20536 port?  That port corresponds to dwarf proxy implementation.  I tried to mine to the 20535 port using -esm 2 and it didn't work.  That's the coinotron proxy implementation.  Curious, as I've seen the miningpoolhub op say that's the best way to connect to his pool.

Also your example in the first post regarding miningpoolhub does not have the -allpools 1 parameter

This works for me:

EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal 0x...walletaddress.... -eworker YOURLOGIN.YOURWORKERNAME -epsw x -allpools 1

But you must create same worker on this pool, and perhaps specify same wallet address in account settings on pool (I don't remember).
About missed "-allpools 1": you are correct, I updated OP.

Yes that port works for me too.  I was curious why port 20535 and -esm2 doesn't work.
Claymore (OP)
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 12, 2016, 03:24:08 PM
 #1794

Claymore can you mine to miningpoolhub with only -esm 0 and the 20536 port?  That port corresponds to dwarf proxy implementation.  I tried to mine to the 20535 port using -esm 2 and it didn't work.  That's the coinotron proxy implementation.  Curious, as I've seen the miningpoolhub op say that's the best way to connect to his pool.

Also your example in the first post regarding miningpoolhub does not have the -allpools 1 parameter

This works for me:

EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal 0x...walletaddress.... -eworker YOURLOGIN.YOURWORKERNAME -epsw x -allpools 1

But you must create same worker on this pool, and perhaps specify same wallet address in account settings on pool (I don't remember).
About missed "-allpools 1": you are correct, I updated OP.

Yes that port works for me too.  I was curious why port 20535 and -esm2 doesn't work.

Because pool doesn't understand wallet as username and requires login.worker style. It works for me:

EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20535 -ewal YOURLOGIN.YOURWORKERNAME -epsw x -esm 2 -allpools 1

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
melloyellow
Full Member
***
Offline Offline

Activity: 176
Merit: 100


View Profile
May 12, 2016, 03:30:26 PM
 #1795

Claymore can you mine to miningpoolhub with only -esm 0 and the 20536 port?  That port corresponds to dwarf proxy implementation.  I tried to mine to the 20535 port using -esm 2 and it didn't work.  That's the coinotron proxy implementation.  Curious, as I've seen the miningpoolhub op say that's the best way to connect to his pool.

Also your example in the first post regarding miningpoolhub does not have the -allpools 1 parameter

This works for me:

EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20536 -ewal 0x...walletaddress.... -eworker YOURLOGIN.YOURWORKERNAME -epsw x -allpools 1

But you must create same worker on this pool, and perhaps specify same wallet address in account settings on pool (I don't remember).
About missed "-allpools 1": you are correct, I updated OP.

Yes that port works for me too.  I was curious why port 20535 and -esm2 doesn't work.

Because pool doesn't understand wallet as username and requires login.worker style. It works for me:

EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20535 -ewal YOURLOGIN.YOURWORKERNAME -epsw x -esm 2 -allpools 1

Great, thank you very much.
osnwt
Sr. Member
****
Offline Offline

Activity: 353
Merit: 251


View Profile
May 12, 2016, 04:40:28 PM
 #1796

Guys, how do you set up Suprnova decred stratum in dpools.txt? I mean

stratum+tcp://dcr.suprnova.cc:2252


POOL: stratum+tcp://dcr.suprnova.cc:2252, WALLET: user.rig, PSW: passwd
merlin3287
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
May 12, 2016, 05:35:09 PM
 #1797

I have been lurking here for awhile. Before I take the plunge and switch software, What kind of hash rate will I get? I have 3 380's, but will be getting more.
d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
May 12, 2016, 06:05:36 PM
Last edit: May 12, 2016, 06:27:59 PM by d57heinz
 #1798

Claymore

I have a odd issue but its only on my home pc.. I am running it thru sattelite internet pointing it to my farm.. its running about 90 mhs and it randomly is getting this error.. after about the 4th time it will lock up and restart using the watchdog.  Local network miners work like a charm.. Havent had to restart them since release..   Big issue with satellite internet is the latency.. Its around 750 ms round trip min.

DCR: http error # 56
ETH: failed to check work on pool. retryin in 20 sec..

Not sure what i can do to help this.. Is there a way i can change the polling time in ms to access the wallet.. What  im wondering if its loosing access similar to what hte eth proxy did. But it needs to be able to check sooner than 20 second.. Maybe after just a few second or let it be user definable.  

Best REgards
d57heinz

EDIt. ok i think this is it i must have overlooked it?  ill test it  and see if that cures it  
-etht   Time period between Ethereum HTTP requests for new job in solo mode, in milliseconds. Default value is 200ms.

ok setting that variable doesnt seem to effect the time for http requests  it stays at 200. Also noticed that when i first start the program its showing me as etha 1 for slow cards so i defined it in the command line to etha 0 and it made no diff in speed so i changed it to etha 1 and it slowed me down about 8 % or so across all the cards.. So i think there may be a glitch in hte way CDM 4.2 beta displays the  etha algo when its not defined in the command line(auto mode)..  Its selecting the correct mode just displaying it incorrectly on the output.     Any advice be appreciated.   "C:\Users\Doug\Desktop\Claymore's Dual Ethereum+Decred AMD GPU Miner v4.2 Beta\EthDcrMiner64.exe" -etht 500 -epool http://x.x.x.x:8545

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
Genoil
Sr. Member
****
Offline Offline

Activity: 438
Merit: 250


View Profile
May 12, 2016, 06:45:42 PM
 #1799

Is this the best miner for mining ether only? Im not concerned in mining DCR. I have been using this for the last few days on ethpool but i just wanted to make sure this is the best option for single miner.

CDMv42 a startum compliant ETH miner like qtminer - so it is I think the best there is out there, complete with failover, overclocking etc. Even qtminer doesn't have these features.

The other miner like ethminer is not Stratum compliant and still use a "get work from server" method, which is lame - you will be bound to lose $$$ this way.

In order to fix this, many have put a proxy solution so that many workers can hash into a single proxy server into the ETH pool, keeping hash steady...

For CDMv42, we dont need any proxy because the miner is Stratum compliant and will work well with Stratum based ETH pools.

In v42, even the solo mining feature did not need any proxy solution, as it mines directly into Geth, which is fantastic because it direct and does not create any delays.

Others feel free to comment, the above are strictly my opinion only.


My fork of ethminer 0.9.41 May not be as good but it has native stratum, failover, native CUDA support and it's free and open source.

Btw geth uses getwork protocol. Why has nobody forked it to add a stratum server to it?

ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
gami82
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
May 12, 2016, 07:30:11 PM
 #1800

After testing 48 hours CDM and Genoil Ethminer - back to Genoil. For me it works better than CDM. Tested on coinotron and ethermine. Now I'm testing the new Version 1.0.8 of Genoil.
Pages: « 1 ... 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 [90] 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 ... 1412 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!