Bitcoin Forum
July 26, 2021, 02:25:16 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 ... 1431 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)  (Read 6583152 times)
Patrice7
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
May 20, 2016, 01:16:02 AM
 #2081


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,

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.
1627266317
Hero Member
*
Offline Offline

Posts: 1627266317

View Profile Personal Message (Offline)

Ignore
1627266317
Reply with quote  #2

1627266317
Report to moderator
1627266317
Hero Member
*
Offline Offline

Posts: 1627266317

View Profile Personal Message (Offline)

Ignore
1627266317
Reply with quote  #2

1627266317
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1627266317
Hero Member
*
Offline Offline

Posts: 1627266317

View Profile Personal Message (Offline)

Ignore
1627266317
Reply with quote  #2

1627266317
Report to moderator
1627266317
Hero Member
*
Offline Offline

Posts: 1627266317

View Profile Personal Message (Offline)

Ignore
1627266317
Reply with quote  #2

1627266317
Report to moderator
PPOC
Hero Member
*****
Offline Offline

Activity: 575
Merit: 500



View Profile
May 20, 2016, 01:17:33 AM
 #2082

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

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 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

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
Patrice7
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
May 20, 2016, 01:19:58 AM
 #2083

"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.




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

Activity: 575
Merit: 500



View Profile
May 20, 2016, 01:44:05 AM
 #2084


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,

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.

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|<unknown>  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|<unknown>  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

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
Patrice7
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
May 20, 2016, 02:10:28 AM
 #2085


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,

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.

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|<unknown>  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|<unknown>  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

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.
PPOC
Hero Member
*****
Offline Offline

Activity: 575
Merit: 500



View Profile
May 20, 2016, 02:16:32 AM
 #2086


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,

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.

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|<unknown>  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|<unknown>  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

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.

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

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
elzium
Member
**
Offline Offline

Activity: 96
Merit: 10


View Profile
May 20, 2016, 03:17:10 AM
 #2087

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.
PPOC
Hero Member
*****
Offline Offline

Activity: 575
Merit: 500



View Profile
May 20, 2016, 03:19:49 AM
 #2088

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.

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?

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
Balbec
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
May 20, 2016, 05:28:17 AM
 #2089

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 Wink 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.
citronick
Legendary
*
Offline Offline

Activity: 1834
Merit: 1080


---- winter*juvia -----


View Profile
May 20, 2016, 05:49:41 AM
 #2090

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 Wink 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.

there is a geth "--fast" switch that can do entire synch in less than 30 mins from scratch.
I had to do this on a new PC a few weeks ago, and was quite surprised on how fast it was.

If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 20, 2016, 07:10:19 AM
 #2091

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.

Your logic is incorrect. Miner will send 1% or 2% of mining time anyway - pool or solo modes. Probability to find the block in solo mining when miner is busy in devfee mining is the same 1% or 2%.
So check your math again.

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
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 20, 2016, 07:13:40 AM
 #2092

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

For solo minig mode every share in the miner means a block because share target = block target. Miner will continue mining when block is found, exactly as it works in pool mode.

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
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 20, 2016, 07:31:41 AM
 #2093

Hi it seems that eth_submitHashrate in eth-proxy mode is lacking the worker parameter:
Code:
{"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x7b64145", "0x000000000000000000000000000000000000000000000000000000009ff1e5fb"]}

While a request from eth proxy for eth_submitHahrate looks like this (when worker ids are enabled):
Code:
{"id":6,"worker": "rig1","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x7b64145", "0x000000000000000000000000000000000000000000000000000000009ff1e5fb"]}

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

Ok I will do it.

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
malandante
Full Member
***
Offline Offline

Activity: 142
Merit: 100


View Profile
May 20, 2016, 09:04:19 AM
 #2094

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.

Your logic is incorrect. Miner will send 1% or 2% of mining time anyway - pool or solo modes. Probability to find the block in solo mining when miner is busy in devfee mining is the same 1% or 2%.
So check your math again.

You're right in the probability thing. What I mean is that unless you have a huge hashrate and are solo finding blocks all the time, the situation is not like in pool mining. I miss a share in devfee time when pool mining and I don't care because it will even out in no time. I miss a block in solo mining and it will take ages to even out. And meanwhile the difficulty will be raising making the chance to even out smaller. Unless you have a huge hashrate, as I said. Please correct me if my thoughts are wrong.
malandante
Full Member
***
Offline Offline

Activity: 142
Merit: 100


View Profile
May 20, 2016, 09:07:24 AM
 #2095

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?

ETH: 05/19/16-17:44:09 - New job (target 0x000000000006f68d) from localhost:8545
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.

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.

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.

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,

In your case with this hashrate increase it pays off to use CDM. My thoughts are right or maybe wrong, I tried to clarify them in the post above.
osnwt
Sr. Member
****
Offline Offline

Activity: 353
Merit: 251


View Profile
May 20, 2016, 09:10:17 AM
 #2096

I think that the probability to get a block in 1-2% of time is compensated by increased probability to find it in the remaining 98-99% of time due to higher hash rate. So it still win. If you miss a block in this 1-2% of time, you just get a new hash to calculate, and the probability to find this one will be exactly the same. So as soon as your average hash rate (in 100% of time) is higher, you win.
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 20, 2016, 09:19:28 AM
 #2097

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.

Your logic is incorrect. Miner will send 1% or 2% of mining time anyway - pool or solo modes. Probability to find the block in solo mining when miner is busy in devfee mining is the same 1% or 2%.
So check your math again.

You're right in the probability thing. What I mean is that unless you have a huge hashrate and are solo finding blocks all the time, the situation is not like in pool mining. I miss a share in devfee time when pool mining and I don't care because it will even out in no time. I miss a block in solo mining and it will take ages to even out. And meanwhile the difficulty will be raising making the chance to even out smaller. Unless you have a huge hashrate, as I said. Please correct me if my thoughts are wrong.

I can only say the same: Probability to miss the block in solo mining when miner is busy in devfee mining is the same - 1% or 2%. Not more.
In your point of view, you afraid that you can miss the block. Yes you can miss it, but probability is 1-2%.
But for the rest of time (98%-99%) you pay nothing for devfee at all because you would check weak hashes anyway.

About slow/huge hashrate: if you mine solo with slow hashrate to find one block, probability to miss it due to devfee mining is the same - 1-2%. Of course if you are very unlucky (1-2%), you can miss it immediately. But if you are unlucky, you can also search for a block forever. It is not a devfee problem, it is a problem of bad luck. On other side, if you are lucky a bit (98-99%), you will lose absolutely nothing for devfee in solo mode.

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
DDSZ
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
May 20, 2016, 09:49:38 AM
 #2098

It would be cool to have ping in remote manager Smiley
Anyway, thank you for it.
Made a small PHP thing for myself Wink
http://jpegshare.net/images/78/98/7898354c3131913d0949dd1fc61a90bf.png
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 20, 2016, 10:13:25 AM
 #2099

It would be cool to have ping in remote manager Smiley
Anyway, thank you for it.
Made a small PHP thing for myself Wink


If miner is not available, it becomes red. Why do you need ping?

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
DDSZ
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
May 20, 2016, 10:26:18 AM
 #2100

It would be cool to have ping in remote manager Smiley
Anyway, thank you for it.
Made a small PHP thing for myself Wink
http://jpegshare.net/images/78/98/7898354c3131913d0949dd1fc61a90bf.png

If miner is not available, it becomes red. Why do you need ping?

I mean the ping that shows in miner when share was accepted.
Pages: « 1 ... 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 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 ... 1431 »
  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!