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

Blockchain syncing from scratch is the worst thing in solo. 18 gigs ((.

If you want more hashrate using DCR-combined advantages - simply add DCR-mining "channel" with provided miner readme (RTFM guys, it's profit Maybe there are some security issues (open additional ports etc).

Geth have a few unwanted holes. One reports 100 DAO costs him all his eth with Mist and Geth (1 ETH for tokens, rest of 7,2k was stolen). Botnets work 24/7. Don't forget it.

Other then checking Geth main account balance, or monitoring your wallet address. Any other way to see you found a block? will anything show on the console or a Geth command that may show blocks solves or possible solves?

If u find a block, it doesnt mean that for some time your odds are lower. U dont gather up the work to get sometimes paid or have to be 100% online to hit the right moment, the probability of findinga a block is still the same whether u did find one minute ago or not. So devfee does nothing but lowers ur effective hashrate. But of course its hard to believe if u see the hit in "wrong" time with your own eyes.

Same rig running CMD below. Maybe Claymore will offer a paid version of the miner? Geared toward solo miners that don't want to take the DevFee time away.


GPU 1 DAG creation time 5162 ms
Setting DAG epoch #51 for GPU #1 done
GPU 0 DAG creation time 5187 ms
Setting DAG epoch #51 for GPU #0 done
GPU 3 DAG creation time 5280 ms
Setting DAG epoch #51 for GPU #3 done
GPU 2 DAG creation time 5288 ms
Setting DAG epoch #51 for GPU #2 done
ETH: 05/19/16-22:13:45 - New job (target 0x0000000000070250) from 10.110.150.88:8545
ETH - Total Speed: 121.992 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 30.493 Mh/s, GPU1 30.524 Mh/s, GPU2 30.478 Mh/s, GPU3 30.496 Mh/s
ETH: 05/19/16-22:13:59 - New job (target 0x0000000000070170) from 10.110.150.88:8545
ETH - Total Speed: 121.920 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 30.506 Mh/s, GPU1 30.471 Mh/s, GPU2 30.469 Mh/s, GPU3 30.473 Mh/s
GPU0 t=57C fan=0%
ETH: 05/19/16-22:14:11 - New job (target 0x0000000000070170) from 10.110.150.88:8545
ETH - Total Speed: 122.086 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 30.544 Mh/s, GPU1 30.529 Mh/s, GPU2 30.515 Mh/s, GPU3 30.498 Mh/s
GPU0 t=61C fan=0%
ETH: 05/19/16-22:14:45 - New job (target 0x0000000000070330) from 10.110.150.88:8545
ETH - Total Speed: 121.990 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:01
ETH: GPU0 30.514 Mh/s, GPU1 30.510 Mh/s, GPU2 30.472 Mh/s, GPU3 30.495 Mh/s

I would go with CMD.  Looking at the numbers I would have to believe that the significantly higher hash rate and processing more work would outweigh the off chance that you would have found a block in the time CMD is mining the dev fee. In the long run you might miss a block or two but should come out ahead due to the 60%+ increase in hashing power.

So I just tested using just Ethminer pointed to my Geth box in solo, looks like avg is 75Mh. This rig has 4 GPU's that usually run 102mh on a pool using ethminer and 120mh on a pool using CDM.

I get the luck factor in solo mining, but loosing that much hash compared to CDM has got to make a difference. Based on calculators I should be getting a block per day with my 550mh using CDM. But with this Ethminer avg below, total hash is only 342Mh.

Thoughts?


miner  21:38:33|main  Mining on PoWhash #8f049772ΓǪ : 74162546 H/s = 37748736 hashes / 0.509 s
miner  21:38:34|main  Mining on PoWhash #8f049772ΓǪ : 73647528 H/s = 37486592 hashes / 0.509 s
miner  21:38:34|main  Mining on PoWhash #8f049772ΓǪ : 76073160 H/s = 38797312 hashes / 0.51 s
miner  21:38:35|main  Mining on PoWhash #8f049772ΓǪ : 72617493 H/s = 36962304 hashes / 0.509 s
miner  21:38:35|main  Mining on PoWhash #8f049772ΓǪ : 74824566 H/s = 38010880 hashes / 0.508 s
miner  21:38:36|main  Mining on PoWhash #8f049772ΓǪ : 74677563 H/s = 38010880 hashes / 0.509 s
DAG  21:38:36|  Generating DAG file. Progress: 16 %
miner  21:38:36|main  Mining on PoWhash #8f049772ΓǪ : 75045145 H/s = 38273024 hashes / 0.51 s
miner  21:38:37|main  Mining on PoWhash #8f049772ΓǪ : 72475105 H/s = 36962304 hashes / 0.51 s
miner  21:38:37|main  Mining on PoWhash #8f049772ΓǪ : 77252652 H/s = 39321600 hashes / 0.509 s
miner  21:38:38|main  Mining on PoWhash #8f049772ΓǪ : 70557422 H/s = 35913728 hashes / 0.509 s
miner  21:38:38|main  Mining on PoWhash #8f049772ΓǪ : 75045145 H/s = 38273024 hashes / 0.51 s
miner  21:38:39|main  Mining on PoWhash #8f049772ΓǪ : 75707599 H/s = 38535168 hashes / 0.509 s
miner  21:38:39|main  Mining on PoWhash #8f049772ΓǪ : 74017129 H/s = 37748736 hashes / 0.51 s
miner  21:38:40|main  Mining on PoWhash #8f049772ΓǪ : 74385283 H/s = 38010880 hashes / 0.511 s
miner  21:38:41|main  Mining on PoWhash #8f049772ΓǪ : 75776000 H/s = 38797312 hashes / 0.512 s
miner  21:38:41|main  Mining on PoWhash #8f049772ΓǪ : 70933082 H/s = 36175872 hashes / 0.51 s
miner  21:38:42|main  Mining on PoWhash #8f049772ΓǪ : 75707599 H/s = 38535168 hashes / 0.509 s
miner  21:38:42|main  Mining on PoWhash #8f049772ΓǪ : 74677563 H/s = 38010880 hashes / 0.509 s
miner  21:38:43|main  Mining on PoWhash #8f049772ΓǪ : 75192581 H/s = 38273024 hashes / 0.509 s
miner  21:38:43|main  Mining on PoWhash #8f049772ΓǪ : 72989113 H/s = 37224448 hashes / 0.51 s
DAG  21:38:43|  Generating DAG file. Progress: 17 %
miner  21:38:44|main  Mining on PoWhash #8f049772ΓǪ : 76073160 H/s = 38797312 hashes / 0.51 s
miner  21:38:44|main  Mining on PoWhash #8f049772ΓǪ : 70557422 H/s = 35913728 hashes / 0.509 s
miner  21:38:45|main  Mining on PoWhash #8f049772ΓǪ : 75559152 H/s = 38535168 hashes / 0.51 s
miner  21:38:45|main  Mining on PoWhash #8f049772ΓǪ : 74531137 H/s = 38010880 hashes / 0.51 s
miner  21:38:46|main  Mining on PoWhash #8f049772ΓǪ : 75045145 H/s = 38273024 hashes / 0.51 s
miner  21:38:46|main  Mining on PoWhash #8f049772ΓǪ : 73647528 H/s = 37486592 hashes / 0.509 s

After -dwal replace "Redhex.my" with your suprnova User.worker name and replace the "x" after -dpsw with your password.

I am not getting the below error when CDM starts,


ETH: Connected (10.110.150.88:8545)
ETH: Received error: {"jsonrpc":"2.0","id":0,"error":{"code":-32000,"message":"mining not ready"}}
No pool specified for Decred! Ethereum-only mining mode is enabled
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: HTTP SOLO mode
Ethereum HTTP requests time (-etht) is set to 200 ms
Watchdog enabled

ETH: 05/19/16-21:14:20 - New job (target 0x00000000000706a0) from 10.110.150.88:8545
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s

Like all mining I think it is going to be luck that rules on this one. You could possibly have found an eth block in that 14.4 minutes a day that CMD is mining the dev fee. Mining Shift with only 50-60mh I have found that the 36 seconds doesn't really affect me. I get more from CMD on average than I do etherminer.  If I had the hash-rate to mine Ethereum solo I might feel differently.

Thanks for the info, very helpful. So in your opinion, I should use ethminer doing solo on my Geth? Even though CMD give me a higher hash rate? With either I get 103mh on 1 rig, with CMD I get 120mh. With all my hw, using Ethminer its 460mh, with CMD its 550Mh. Considerable difference.

Thanks,

"dwarfpool (and Stratum for Decred):
EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorkerName -epsw x -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal Redhex.my -dpsw x"

I dont want to sound like an idiot but in the part where it says "-dwal"? Do i need to add my decred payment address too or leave it blank? I see that the miner is accepting shares from decred but im not sure if i have to put my address or not (Is blank in the original post)

Sorry if is a dumb question first time trying this. Thanks for the help.

Hi i have problem. I have GPU R9 280X and R9 290X in one motherboard with Windows 8, CPU 4core, 8gb ram. Here i have driver 15.12. One GPU R9 280X hashrate is ok. Is 20-21 MH/s. And problem i have with two GPU card R9 290X. Before i have in this card 46-47 MH/s. But now is very critical low....20-21 MH/s. I send photo screenshot and settings my miner. I test previous version and too problem....I test another software and too...Before this time all ok....

EthDcrMiner64.exe -mode 1 -esm 1 -epool eu1.ethpool.org:3333 -ewal 0x7efa35203ded3af8394854022541a2cbfa73cc05.marian2 -epsw x -estale 0

http://s32.postimg.org/6q7dtz879/r290x.jpg

Please help me friend....where is the problem?

Hi it seems that eth_submitHashrate in eth-proxy mode is lacking the worker parameter:

While a request from eth proxy for eth_submitHahrate looks like this (when worker ids are enabled):

Maybe you could add the worker param to the request if it is set.

You should read the theory of pool operation to understand the whole thing.

A miner calculates a "checksum" of data in the block using some hashing algorithm. The result is a very long number. To solve a block this number must be lesser than some value called target. Target depends on the speed of finding blocks by the whole network and adapts so the average rate of new blocks is constant regardless of number of miners in the network. That is, more miners - more hashpower - lesser target - harder to find a block solution.

When you mine with a pool, pool sets target for miners much higher than actual target for the block solution. So miners with low hash rates can find at least something in reasonable time frame. Those solutions are called "shares" because they do NOT solve a block. But pool can estimate miner hashrate by the rate of submitted shares. Finally some share from some miner will be smaller than a block solution. This share will solve the block, but usually miner does not know that it was its share (some pools like suprnova and pool.mn report block founders, though, for stats).

Now compare the typical target from a pool: 0x0000000112e0be82 (4611686018) with your target 0x000000000006f3f2 (455666).  4611686018/455666 ~= 10120. This means that in solo mode only 1 of 10120 such pool shares will solve a block. If your miner finds 100 shares per hour, you need 101 hour to find a solution in solo mode. Until that you will not see any shares in solo mode. You see only block solution.

The not connecting is most likely because you set rpc to 127.0.0.1 and then geth only accepts connections from the same machine. Use the local ip instead.

And by the way, I wouldn't use CDM to solo mine. When you solo mine, you don't want 36 or 72 seconds per hour not mining for yourself because in this time it can be when you're gonna hit a block. If you are pool mining then it is ok because shares you will be hitting a lot anyway. I'll give you an example: a few months ago when I was still solo mining, I was gonna stop one of my rigs and in the time between hitting CTRL and C this rig found one block.

So does the miner stop mining when a new block is found or only when its submitting a share?

I actually have 600mh of miners that I want to solo mine, but so far only the local box running Geth is connecting my GPU's and that's the 120mh you see here. Tried pointing my other rigs to this Geth box and getting failure to connect messages. I would think I should still see accepted shares as rarely are they blocks on a pool. I avg 450 accepted shares per hour on a pool like Nano, so I was expecting to see similar results solo mining.

Shares are your contributions in pool mining, so no shares in solo mining, you mine the whole thing alone. Try launching geth with --rpc --rpcaddr 192.168.x.x --farm 192.168.x.x where 192.168.x.x is the lan address of the machine running geth. For me it does work like that. With 127.0.0.1 machines in the lan can't connect.

I didn't try solo mining. But I guess that with solo mode your "share" means to be a block solution. With such difficulty difference (compare yours and pool ones) and your hashrate you should mine few days, maybe a week on average, to find a block. I think so, but might be wrong.

Claymore - Your miner works great on pools, a week with no issues or crashes. I am trying to setup solo mining. Have Geth running on a local LAN machine and tried to point miner from same machine as well as another LAN machine.

Used
EthDcrMiner64.exe -epool http://localhost:8545

Connects, looks like it starts mining and Geth console shows the connection. But not seeing any shares? only temps and new jobs. On pool, i'm seeing accepted shares almost instantly. Doing something wrong here?

Also, when I point another rig to my local Geth using LAN IP and same port, can't connect. Port is open, no FW running and its local LAN.


ETH: 05/19/16-17:43:38 - New job (target 0x000000000006f68d) from localhost:8545
ETH - Total Speed: 122.037 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.444 Mh/s, GPU1 30.541 Mh/s, GPU2 30.526 Mh/s, GPU3 30.527 Mh/s
ETH: 05/19/16-17:43:43 - New job (target 0x000000000006f5af) from localhost:8545
ETH - Total Speed: 122.052 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.473 Mh/s, GPU1 30.543 Mh/s, GPU2 30.528 Mh/s, GPU3 30.508 Mh/s
GPU0 t=63C fan=0%, GPU1 t=62C fan=0%, GPU2 t=62C fan=0%
ETH: 05/19/16-17:44:09 - New job (target 0x000000000006f68d) from localhost:8545
ETH - Total Speed: 122.006 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.431 Mh/s, GPU1 30.532 Mh/s, GPU2 30.521 Mh/s, GPU3 30.523 Mh/s
ETH: 05/19/16-17:44:10 - New job (target 0x000000000006f5af) from localhost:8545
ETH - Total Speed: 121.798 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.477 Mh/s, GPU1 30.533 Mh/s, GPU2 30.280 Mh/s, GPU3 30.508 Mh/s
ETH: 05/19/16-17:44:12 - New job (target 0x000000000006f4d0) from localhost:8545
ETH - Total Speed: 122.068 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.477 Mh/s, GPU1 30.537 Mh/s, GPU2 30.539 Mh/s, GPU3 30.515 Mh/s
ETH: 05/19/16-17:44:16 - New job (target 0x000000000006f3f2) from localhost:8545
ETH - Total Speed: 122.117 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.530 Mh/s, GPU1 30.527 Mh/s, GPU2 30.539 Mh/s, GPU3 30.521 Mh/s
GPU0 t=64C fan=0%, GPU1 t=62C fan=0%, GPU2 t=63C fan=0%
ETH: 05/19/16-17:44:43 - New job (target 0x000000000006f4d0) from localhost:8545
ETH - Total Speed: 122.040 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:07
ETH: GPU0 30.482 Mh/s, GPU1 30.519 Mh/s, GPU2 30.523 Mh/s, GPU3 30.517 Mh/s