|
UPDATE: Fixed bug with Linux build when miner is closed after some time, re-download v4.1 for Linux.
|
|
|
|
Claymore,
should your miner report "Sent hashrate" to DwarfPool in ESM=0 mode? I see no reported hashrate, but eth-proxy with ethminer report this.
Yes, it sends hashrate in -esm 0. |
|
|
|
When SoloETH/PoolDCR version will be released ?
In 5-7 days, I'm working on it right now. Also monitoring and stratum proxy will be available. PM me if your patience is over  I will have unfinished working version very soon. |
|
|
|
|
v4.1 updated: Added build for Linux x64 (tested on Ubuntu 12.04 + Catalyst 15.12).
|
|
|
|
Claymore, sorry, still about missing shares @ethermine with -esm 1. Doubled hashrate seen only after miner start, then it stabilizes to the real. But still no share info. What should I find in miner logs to find out why? What's the protocol difference, can you help? Not say it is very important (no rejected shares for me), but nice to see the number of shares found.
Well, I can only repeat what I said before. Start this (only change wallet address, nothing else, don't remove/change ".sample" after wallet address): EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F.sample -epsw x -esm 1 Wait for 30 minutes. See stats for rig "sample". That is all. |
|
|
|
having a problem on one of my machines since the new Epoc 23:03:56:142 e9c
23:03:56:157 e9c ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
23:03:56:157 e9c º Claymore's Dual Ethereum + Decred AMD GPU Miner v4.0 Beta º
23:03:56:173 e9c ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
23:03:56:173 e9c
23:03:56:392 e9c ETH: 1 pool is specified
23:03:56:392 e9c DCR: 1 pool is specified
23:03:56:798 e9c
Cards available: 5
23:03:56:798 e9c GPU #0: name: Hawaii, 8192 MB available, 40 units
23:03:56:798 e9c GPU #1: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #2: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #3: name: Fiji, 4096 MB available, 64 units
23:03:56:829 e9c GPU #4: name: Hawaii, 8192 MB available, 40 units
23:03:56:829 e9c Total cards: 5
23:03:56:829 e9c Initializing...
23:03:56:829 e9c GPU #0 recognized as Radeon 390
23:03:56:829 e9c GPU #1 recognized as Radeon 390
23:03:56:829 e9c GPU #2 recognized as Radeon 390
23:03:56:845 e9c GPU #3 recognized as Fury X/Nano
23:03:56:845 e9c GPU #4 recognized as Radeon 390
23:03:56:845 e9c POOL version
23:03:56:845 e9c b121
23:03:56:860 e9c GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876 e9c GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829 33c ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939 e9c DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939 131c DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954 e9c Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970 e9c miner-proxy stratum mode
23:03:57:970 e9c "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985 e9c Watchdog enabled
23:03:57:985 e9c
23:03:57:985 33c send: {"id": 1, "method": "mining.subscribe", "params": []}
23:03:58:001 33c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}
23:03:58:001 33c ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079 131c send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}
23:03:58:079 131c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
23:03:58:095 131c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}
23:03:58:095 131c DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173 33c got 107 bytes
23:03:58:173 33c buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}
23:03:58:189 33c parse packet: 99
23:03:58:189 33c new buf size: 0
23:03:58:220 131c got 591 bytes
23:03:58:220 131c buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}
23:03:58:220 131c parse packet: 116
23:03:58:220 131c remove first packet 449
23:03:58:220 131c new buf size: 449
23:03:58:220 131c parse packet: 58
23:03:58:235 131c remove first packet 391
23:03:58:235 131c new buf size: 391
23:03:58:235 131c parse packet: 391
23:03:58:235 131c new buf size: 0
23:03:58:329 33c got 342 bytes
23:03:58:329 131c got 82 bytes
23:03:58:329 33c buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}
23:03:58:329 131c buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}
23:03:58:345 33c parse packet: 62
23:03:58:345 131c parse packet: 36
23:03:58:360 33c remove first packet 267
23:03:58:360 131c remove first packet 36
23:03:58:360 33c new buf size: 267
23:03:58:360 131c new buf size: 36
23:03:58:360 33c parse packet: 267
23:03:58:376 131c parse packet: 36
23:03:58:376 33c eth: job changed
23:03:58:376 131c DCR: Authorized
23:03:58:376 33c new buf size: 0
23:03:58:376 131c new buf size: 0
23:03:58:454 97c Setting DAG epoch #48...
23:03:58:532 33c got 101 bytes
23:03:58:532 33c buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}
23:03:58:532 33c parse packet: 36
23:03:58:532 33c ETH: Authorized
23:03:58:532 33c remove first packet 54
23:03:58:532 33c new buf size: 54
23:03:58:532 33c parse packet: 54
23:03:58:548 33c send: {"error": null, "id": 9876, "result": "eth 1.0"}
23:03:58:548 33c new buf size: 0
23:03:59:673 97c Setting DAG epoch #48 for GPU #4
23:03:59:673 12dc Setting DAG epoch #48 for GPU #3
23:03:59:673 1238 Setting DAG epoch #48 for GPU #2
23:03:59:673 c94 Setting DAG epoch #48 for GPU #0
23:03:59:673 1244 Setting DAG epoch #48 for GPU #1
23:03:59:673 97c Create GPU buffer for GPU #4
23:03:59:673 12dc Create GPU buffer for GPU #3
23:03:59:673 1238 Create GPU buffer for GPU #2
23:03:59:689 c94 Create GPU buffer for GPU #0
23:03:59:689 1244 Create GPU buffer for GPU #1
23:03:59:767 97c GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 1238 GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 c94 GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829 12dc GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845 1244 GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048 e9c OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
23:04:01:079 e9c OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst
Probably you use "Data.bin" file from v3.x version. |
|
|
|
Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??
ETH: Stratum - socket send failed 10053, disconnect
Change pool or check your ISP, I don't have other ideas why TCP connection is broken. Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good. In v4.0/4.1 I did not change anything in network code. Not a single line. |
|
|
|
Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??
ETH: Stratum - socket send failed 10053, disconnect
Change pool or check your ISP, I don't have other ideas why TCP connection is broken. |
|
|
|
|
Within 24 hours I will release Linux version of the miner, it is almost ready, Ubuntu 12.04 is used for tests.
|
|
|
|
I'm trying to mine at ethermine.org. All works except two things (tested on both 4.0 beta and 4.1): - Sometimes ethermine reports doubled "Reported hashrate" for the account, but always correct hashrate for the rig (just one rig used). - With -esm 0 or -esm 1 it still does not show stats "Shares (Invalid / Valid / %)". All are always 0. Command line: EthDcrMiner64.exe -ewal 0xWALLET -epsw x -eworker rig01 -epool eu1.ethermine.org:4444 -esm 1 What can be wrong? Have you tried this? Wait at least 30 mins to see stats. EthDcrMiner64.exe -ewal 0xWALLET.rig01 -epsw x -epool eu1.ethermine.org:4444 -esm 1 |
|
|
|
Received unknown response:
try "-esm 2" option. Or better use different pool that has some help page that mentions what proxy mode should be used so you can understand what "-esm" mode must be used. Because at the moment there are three stratum modes/proxies and it's a good idea to mention on help page what stratum proxy must be used. |
|
|
|
@claymore : Is it possible to use your miner on miningrigrentals? if so could you help with the options. I've tried multiple qtminer combinations, but so far nothing works. according to miningrigrentals, they have a qtminer example that shows : qtminer -s us-west01.miningrigrentals.com:3333 -u username.rignumber -G
Love all the work you've done on this miner. Thanks!!!
I read this: https://www.miningrigrentals.com/rigs/hashimotog.... This algo is typically used to mine Ethereum. This section is for the GETWORK miner and related pools only. Typically this is ethminer. Attempting to use rigs from this section with stratum based pools will fail. .... So it seems they don't support stratum, I cannot find page with your sample about qtminer. They haven't updated their faq about the stratum side. When you setup a Dagger-Hashimoto(S) rig, in the properties block of the rig they give an example of a qtminer command line. That is the only place I have found an example for their stratum based dagger-hashimoto rigs. dp if qtminer is supported, my miner will work too: EthDcrMiner64.exe -epool us-west01.miningrigrentals.com:3333 -ewal username.rignumber -epsw x -esm 1 -allpools 1 If it does not work, read the log for details about error. |
|
|
|
You can PM me log file and I will check how many shares miner submitted.
Hi Claymore, thnx for your miner, its worth every penny that we pay you, for using it. A few weeks ago, you said, that once the miner becomes a stable version, you will port it to linux... Is it possible, now? Because atleast 10% of all the miners, are using linux. I'm working on solo mode, monitoring/management utility and linux version. Not sure what will be released first, perhaps I will have linux version in 1-2 days (assuming v4.1 is stable). |
|
|
|
You can PM me log file and I will check how many shares miner submitted.
Thanks! Fortunately I can do this job by myself )) Here is my calc, I have 2 rigs named 7990 and 7950 )) time shares(7990) shares (7950)
02:00 2127 874
03:00 2250 946
=================================
17:00 3985 1977
18:00 4122 2040
Shares delta
1. 123 + 72 = 195
2. 137 + 63 = 200 Dwarf statistics shows only 98 shares for 02:00-03:00 period and only 102 shares for 17:00-18:00 All time is GMT + 3 If miner shows shares and they are accepted (can be checked in log file that pool sent "result: true" answer) - it is the problem of the pool. |
|
|
|
Thank you for quick response.
Usually I have 200 shares an hour, this is rather stable, +- 20.
But on 2:00 I received only 98 shares and on 17:00 only 102 shares - it is exacly the half of my usual rate. And the ru-server was down exactly during 30 minutes both times.
I already write to dwarfpool admin with my problem. Will hope he will find time to answer.
You can PM me log file and I will check how many shares miner submitted. |
|
|
|
@claymore : Is it possible to use your miner on miningrigrentals? if so could you help with the options. I've tried multiple qtminer combinations, but so far nothing works. according to miningrigrentals, they have a qtminer example that shows : qtminer -s us-west01.miningrigrentals.com:3333 -u username.rignumber -G
Love all the work you've done on this miner. Thanks!!!
I read this: https://www.miningrigrentals.com/rigs/hashimotog.... This algo is typically used to mine Ethereum. This section is for the GETWORK miner and related pools only. Typically this is ethminer. Attempting to use rigs from this section with stratum based pools will fail. .... So it seems they don't support stratum, I cannot find page with your sample about qtminer. |
|
|
|
OpenCL cannot allocate memory buffers. Unfortunately I have no idea why, but it's uncommon error, something is wrong with your system if it cannot allocate 1.5GB of video RAM. |
|
|
|
Seems like a pool bug ... but dwarf is known to be a very accurate and stable pool in accounting.
Maybe some sort of incompatibility between Dualminer and Dwarf on failover switching?
Maybe this is already corrected in stable v4.1?
I don't know if it is enough 2 hours to get correct statistics on dwarfpool and if it worked correctly if some of its servers were unavailable, but miner just changes pool and mines as usual, such switching cannot cause less shares or less mining speed. If you have enough hashrate to find shares reqularly, you can calculate number of shares for these two hours in log file and compare to the number of shares for any other 2-hours period. |
|
|
|
|
v4.1: This version is assumed to be stable, so it is not marked as "beta".
- improved working with DAG on GPUs during epoch changing, it must work fine now.
- added watchdog for threads that communicate with pools.
- minor bug fixes.
|
|
|
|
|
Guys, it's a good idea to read OP or readme.
froilan_rivero - Expanse is supported, search "Ethereum forks mining" string in readme or OP.
Doramha - Read "FAILOVER" section: "Every pool has 3 connection attempts."
|
|
|
|
|
Show Posts
