Author

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

hero member
Activity: 700
Merit: 500
@Claymore
so far so good im quite happy 15h straight without major problems, keep up the good work
only problem so far was crashing while i tried changing cclock and mclock(no matter if over or underclock), and not showing reported hashrate on ethermine.org only effective current hashrate is visible even after adding worker name and changing esm to 1
-tt works ok, after some time it stabilizes fans speed

"-esm 1" works, miner must write "qtminer mode" during start. Just wait some time (an hour) and pool will show info about shares. Check this topic a few pages ago there was same problem and it was solved.

I think people are talking about the eth_submitHashrate stratum method that eth-proxy supports.  Ethermine/ethpool and mph (maybe others) will show your "reported hashrate," as in, reported by the mining software.
legendary
Activity: 1596
Merit: 1011
Why not release a solo ver if 2.0 working well ? Problems with devfee ? Problems with accepted blocks ? I don't get it. Solo is a real decentralization! Don't feed a Troll Pool, feed the dev  Cheesy

I don't want to work with proxies, so the miner will work with ETH client directly, it will take some time to implement it. I will do it soon, but not today Smiley

I don't think any serious solo miner is going to mine without a proxy. I've got 2GH spread across 14 rigs, I need the detailed statistics, simplification,  and features that EtherProxy by Sammy007 provides. Why wouldn't you want to support that? Would it prevent your miner from mining for the dev fee? Without the proxy support, I'm pretty sure I won't be alone in not using your miner to solo, unfortunately.

If he implement json api for remote monitoring like in cgminer the proxy would be not necessary.
legendary
Activity: 1596
Merit: 1000
Why not release a solo ver if 2.0 working well ? Problems with devfee ? Problems with accepted blocks ? I don't get it. Solo is a real decentralization! Don't feed a Troll Pool, feed the dev  Cheesy

I don't want to work with proxies, so the miner will work with ETH client directly, it will take some time to implement it. I will do it soon, but not today Smiley

I don't think any serious solo miner is going to mine without a proxy. I've got 2GH spread across 14 rigs, I need the detailed statistics, simplification,  and features that EtherProxy by Sammy007 provides. Why wouldn't you want to support that? Would it prevent your miner from mining for the dev fee? Without the proxy support, I'm pretty sure I won't be alone in not using your miner to solo, unfortunately.
donator
Activity: 1610
Merit: 1325
Miners developer
@Claymore
so far so good im quite happy 15h straight without major problems, keep up the good work
only problem so far was crashing while i tried changing cclock and mclock(no matter if over or underclock), and not showing reported hashrate on ethermine.org only effective current hashrate is visible even after adding worker name and changing esm to 1
-tt works ok, after some time it stabilizes fans speed

"-esm 1" works, miner must write "qtminer mode" during start. Just wait some time (an hour) and pool will show info about shares. Check this topic a few pages ago there was same problem and it was solved.
full member
Activity: 195
Merit: 104
@Claymore
so far so good im quite happy 15h straight without major problems, keep up the good work
only problem so far was crashing while i tried changing cclock and mclock(no matter if over or underclock), and not showing reported hashrate on ethermine.org only effective current hashrate is visible even after adding worker name and changing esm to 1
-tt works ok, after some time it stabilizes fans speed
full member
Activity: 348
Merit: 102
Smiley

All works, and you do not have ... The problem miners, or in you ?
full member
Activity: 215
Merit: 100
donator
Activity: 1610
Merit: 1325
Miners developer
problem in your miner. usual. everything is normal

You can check the log, pool sends the same header (job) for a long time:

23:01:14:327   16cc   got 243 bytes
23:01:14:338   16cc   buf: {"id":0,"jsonrpc":"2.0","result":["0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0x013d5197a3a035144a79e3e09dfec2505039ed176d81a0957e229886ddbee49b","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

......

23:43:57:438   16cc   got 243 bytes
23:43:57:451   16cc   buf: {"id":0,"jsonrpc":"2.0","result":["0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0x013d5197a3a035144a79e3e09dfec2505039ed176d81a0957e229886ddbee49b","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
 
42 minutes it sends the same job. Moreover, it accepts shares for this job all the time:

23:09:02:904   16cc   got 36 bytes
23:09:02:912   16cc   buf: {"id":4,"jsonrpc":"","result":true}
23:09:02:922   16cc   parse packet: 36
23:09:02:940   16cc   ETH: Share accepted!

.....

23:40:44:596   16cc   send: {"id":4,"method":"eth_submitWork","params":["0x75e8cb19ab613cb4","0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0xfc152e9f3155f53c75a270b7db26d6b63fec19c54318a49ec1513246cf14479e"]}
23:40:44:725   16cc   got 36 bytes
23:40:44:728   16cc   buf: {"id":4,"jsonrpc":"","result":true}
23:40:44:728   16cc   parse packet: 36
23:40:44:737   16cc   ETH: Share accepted!

The problem is not in my miner. The only problem with my miner is that it should understand that entire pool (or at least its thread that serves you) hangs and disconnect, I will add it.
full member
Activity: 215
Merit: 100
problem in your miner. usual. everything is normal
full member
Activity: 215
Merit: 100
after restart miner everything is normal
donator
Activity: 1610
Merit: 1325
Miners developer
I get disconnects from nanopool right now so they are doing something with the pool. It seems I really need to add failover asap, probably I will add it in next update.
donator
Activity: 1610
Merit: 1325
Miners developer

this is normal?



ETH: 04/18/16-23:26:54 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
DevFee: ETH: Stratum - connecting to 'eu1.nanopool.org' <198.211.124.56> port 9999
DevFee: ETH: Stratum - Connected
Authorized
DevFee: start mining
DevFee: ETH: 04/18/16-23:28:53 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
DevFee: ETH: 04/18/16-23:29:06 - New job (target 0x00000000dbe6fece) from eu1.nanopool.org:9999
DevFee: ETH: 04/18/16-23:29:23 - New job (target 0x00000000dbe6fece) from eu1.nanopool.org:9999
DevFee: stop mining and disconnect
ETH: 04/18/16-23:29:38 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:29:41 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:29:45 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:32:44 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:35:43 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
ETH: 04/18/16-23:35:59 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
ETH: 04/18/16-23:36:21 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:37:06 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:39:27 - SHARE FOUND - (GPU 0)
ETH: Share accepted!



Looks like a pool hangs on some block. If the problem is in miner, pool must reject old shares, but it responds "accepted", so the problem is on pool's side. Anyway, PM me the log file, I will check it. I will also add check so if miner gets same job for a long time it disconnects from the pool because it hangs.
full member
Activity: 215
Merit: 100

this is normal?



ETH: 04/18/16-23:26:54 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
DevFee: ETH: Stratum - connecting to 'eu1.nanopool.org' <198.211.124.56> port 9999
DevFee: ETH: Stratum - Connected
Authorized
DevFee: start mining
DevFee: ETH: 04/18/16-23:28:53 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
DevFee: ETH: 04/18/16-23:29:06 - New job (target 0x00000000dbe6fece) from eu1.nanopool.org:9999
DevFee: ETH: 04/18/16-23:29:23 - New job (target 0x00000000dbe6fece) from eu1.nanopool.org:9999
DevFee: stop mining and disconnect
ETH: 04/18/16-23:29:38 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:29:41 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:29:45 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:32:44 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:35:43 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
ETH: 04/18/16-23:35:59 - SHARE FOUND - (GPU 2)
ETH: Share accepted!
ETH: 04/18/16-23:36:21 - SHARE FOUND - (GPU 1)
ETH: Share accepted!
ETH: 04/18/16-23:37:06 - SHARE FOUND - (GPU 0)
ETH: Share accepted!
ETH: 04/18/16-23:39:27 - SHARE FOUND - (GPU 0)
ETH: Share accepted!

legendary
Activity: 1001
Merit: 1005
Mr. Claymore
Miner suddenly stops after 2-3 hours. I send log to PM. Please check it.

I can'n make it stable.

Win 10,
cat 15.12
4*390 + 2*280x
8Gb RAM
8Gb VirtMem
DualMiner v2.0
full member
Activity: 176
Merit: 100
Why not release a solo ver if 2.0 working well ? Problems with devfee ? Problems with accepted blocks ? I don't get it. Solo is a real decentralization! Don't feed a Troll Pool, feed the dev  Cheesy

I don't want to work with proxies, so the miner will work with ETH client directly, it will take some time to implement it. I will do it soon, but not today Smiley

If I'm reading this right, we will have to run an eth client on each miner if we want to mine solo?  I was looking forward to your single instance proxy (not to mine solo) but I guess that's off the table now...
full member
Activity: 176
Merit: 100
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

These don't need to be in your bat file every time you start the miner.  They only need to be run once.  Whenever I have to reinstall windows I just run them in a separate .bat by themselsves.

You can check if they stick by right clicking on the start icon-->System-->Advanced system settings-->Environment Variables

Also, I've always used GPU_FORCE_64BIT_PTR 1, so probably doesn't matter for this miner.
legendary
Activity: 1019
Merit: 1001
Spectreproject Community Manager
The bat file must include:

Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

Good luck

Thank you for this. I'm working so it took a little longer.
Made the changes and the first time same result, the set X commands worked. But dag file (even though I had cleared both) still had buffer size problems.
 I cleared again and shut down and rebooted system (I had read somewhere that changes to the bat file a restart was needed)

It not only started with miners connecting and now showing work (connected before but didn't start hashing).......
but the dag files both built 100%

Everything is stock on gPU and out of the box basic on the miner software.
eth speed 11.23 mh
dcr 168.2 mh

Running over an hour and 0 rejects.

At this point I wasn't so concerned with speed but getting everthing working
After I get the two R9 270X 4 GB in ...we'll start some tweaks.
Again,....Thank you so much for your help!  Cool
legendary
Activity: 1596
Merit: 1011
Why not release a solo ver if 2.0 working well ? Problems with devfee ? Problems with accepted blocks ? I don't get it. Solo is a real decentralization! Don't feed a Troll Pool, feed the dev  Cheesy

I don't want to work with proxies, so the miner will work with ETH client directly, it will take some time to implement it. I will do it soon, but not today Smiley

I see it now. Thank you.
donator
Activity: 1610
Merit: 1325
Miners developer
Why not release a solo ver if 2.0 working well ? Problems with devfee ? Problems with accepted blocks ? I don't get it. Solo is a real decentralization! Don't feed a Troll Pool, feed the dev  Cheesy

I don't want to work with proxies, so the miner will work with ETH client directly, it will take some time to implement it. I will do it soon, but not today Smiley
jr. member
Activity: 36
Merit: 2
Claymore can you please add setting for static fan speed if its not too much trouble Smiley

Ok.

I'll never complain about adding new features but is there a reason for wanting to control GPU speeds and fans through the mining program compared to just using MSI Afterburner?
Jump to: