Bitcoin Forum
April 20, 2024, 12:50:28 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 ... 499 »
  Print  
Author Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 784618 times)
papampi
Full Member
***
Offline Offline

Activity: 686
Merit: 140


Linux FOREVER! Resistance is futile!!!


View Profile WWW
February 27, 2019, 07:56:30 AM
 #2981


I cant find how to use default system GPU indexing so it start from GPU0 and not GPU1

We need this option for our latest nvOC to enable/disable GPUs and multi instance mining.

I know Claymore has the "-altnum" argument, does Phoenix use the same?

1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
Whoever mines the block which ends up containing your transaction will get its fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
1713574229
Hero Member
*
Offline Offline

Posts: 1713574229

View Profile Personal Message (Offline)

Ignore
1713574229
Reply with quote  #2

1713574229
Report to moderator
raisedbyaliens
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 27, 2019, 08:35:43 AM
 #2982

Thanks for your help with the post. I hope i did not sound arrogant lol i have only been looking into this stuff for the past week and this is as far as i have gotten. i assumed what you ment from your last message was to add something inregards to using the nvidia gpu in the command line of the batch file.. i did this and am still getting this error.

...
2019.02.20:20:46:20.091: GPU1 GPU1: DAG  84%
2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)
2019.02.20:20:46:23.651: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.20:20:46:23.652: GPU1 GPU1 search error: the launch timed out and was terminated
2019.02.20:20:46:23.963: wdog Thread(s) not responding. Restarting.
2019.02.20:20:46:24.058: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:26.438: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:26.438: eths Eth: New job #3877e351 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:20:46:26.443: GPU1 GPU1: Starting up... (0)
2019.02.20:20:46:26.444: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.20:20:46:26.444: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2019.02.20:20:46:29.082: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:29.597: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:20:46:29.597: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x5c07dbb3a088fe2d1576b7d3e1224d3b891e957ee633860b92246d1553a4386f"]}

2019.02.20:20:46:29.750: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:29.750: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}




Experiment with the values of the parameter -ethi
Start from the lowest negative value -ethi -8192  and add it by some positive step repeatedly (e.g., +512: -8192 + 512 = -7680; -7680 + 512 = -7168; and so on) until your problem is solved.

You don't have DAG generation problem because the log clearly says:
'2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)'

The hash searching kernel hits timeout with the default settings because your GPU (980ti) is very slow.

Im still getting errors having tried both things

2019.02.27:00:33:31.230: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x8d6e471fdc9247b282c1a03359c3e11822dc90727f5c7887637b50eb9d08ec7a","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce6"]}
2019.02.27:00:33:31.230: eths Eth: New job #8d6e471f from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:31.230: GPU1 GPU1: Starting up... (0)
2019.02.27:00:33:31.231: GPU1 GPU1: Generating ethash light cache for epoch #242
2019.02.27:00:33:33.521: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xe9db1b591366ad0acc9b507d8d9ec73720160598d6bf03eaa81045c209dc5c79","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce6"]}
2019.02.27:00:33:33.521: eths Eth: New job #e9db1b59 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:33.927: GPU1 Light cache generated in 2.7 s (17.2 MB/s)
2019.02.27:00:33:34.181: GPU1 GPU1: Allocating DAG (2.91) GB; good for epoch up to #244
2019.02.27:00:33:34.414: GPU1 GPU1: Allocating light cache buffer (46.5) MB; good for epoch up to #244
2019.02.27:00:33:34.429: GPU1 GPU1: Generating DAG for epoch #242
2019.02.27:00:33:35.959: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.27:00:33:36.127: GPU1 GPU1: DAG  19%
2019.02.27:00:33:37.480: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x75271779bb5876e73379db9913752435f2e6f4794d577b141bd3a9a9f30deb09","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce6"]}
2019.02.27:00:33:37.480: eths Eth: New job #75271779 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:37.823: GPU1 GPU1: DAG  41%
2019.02.27:00:33:39.521: GPU1 GPU1: DAG  63%
2019.02.27:00:33:40.797: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.27:00:33:40.944: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x75271779bb5876e73379db9913752435f2e6f4794d577b141bd3a9a9f30deb09","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce6"]}
2019.02.27:00:33:41.158: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.27:00:33:41.220: GPU1 GPU1: DAG  84%
2019.02.27:00:33:42.195: GPU1 GPU1: DAG generated in 7.8 s (381.1 MB/s)
2019.02.27:00:33:45.445: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x088daa6feef69fb37650e0bc4c08a8702b30d9abf866bf6c91a57f24d321a922","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce7"]}
2019.02.27:00:33:45.445: eths Eth: New job #088daa6f from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:46.358: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.27:00:33:48.410: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.27:00:33:48.410: GPU1 GPU1 search error: the launch timed out and was terminated
2019.02.27:00:33:48.767: wdog Thread(s) not responding. Restarting.
2019.02.27:00:33:49.328: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x145d316cf4fd44334068b66e2e11d34a52d48d919efd79040d36eb94327dcbad","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce7"]}
2019.02.27:00:33:49.328: eths Eth: New job #145d316c from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:49.332: GPU1 GPU1: Starting up... (0)
2019.02.27:00:33:49.333: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.27:00:33:49.333: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2019.02.27:00:33:50.798: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.27:00:33:50.798: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0xca71179b40260fd81878ea028613152eb33f20ebe40146e2faf22ca8e9b2e69b"]}

2019.02.27:00:33:50.946: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x145d316cf4fd44334068b66e2e11d34a52d48d919efd79040d36eb94327dcbad","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce7"]}
2019.02.27:00:33:50.946: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2019.02.27:00:33:51.529: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.27:00:33:53.252: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x54b35c4eb7d356a4087a1650131958897e90d7fcbca4e7134db96193a064818f","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce7"]}
2019.02.27:00:33:53.252: eths Eth: New job #54b35c4e from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:53.261: GPU1 GPU1: Starting up... (0)
2019.02.27:00:33:53.261: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.27:00:33:53.261: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
bategojko74
Member
**
Offline Offline

Activity: 220
Merit: 12


View Profile
February 27, 2019, 10:09:51 AM
Last edit: February 27, 2019, 10:34:24 AM by bategojko74
 #2983

Thanks for your help with the post. I hope i did not sound arrogant lol i have only been looking into this stuff for the past week and this is as far as i have gotten. i assumed what you ment from your last message was to add something inregards to using the nvidia gpu in the command line of the batch file.. i did this and am still getting this error.

...
2019.02.20:20:46:20.091: GPU1 GPU1: DAG  84%
2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)
2019.02.20:20:46:23.651: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.20:20:46:23.652: GPU1 GPU1 search error: the launch timed out and was terminated
2019.02.20:20:46:23.963: wdog Thread(s) not responding. Restarting.
2019.02.20:20:46:24.058: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:26.438: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:26.438: eths Eth: New job #3877e351 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:20:46:26.443: GPU1 GPU1: Starting up... (0)
2019.02.20:20:46:26.444: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.20:20:46:26.444: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2019.02.20:20:46:29.082: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:29.597: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:20:46:29.597: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x5c07dbb3a088fe2d1576b7d3e1224d3b891e957ee633860b92246d1553a4386f"]}

2019.02.20:20:46:29.750: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:29.750: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}




Experiment with the values of the parameter -ethi
Start from the lowest negative value -ethi -8192  and add it by some positive step repeatedly (e.g., +512: -8192 + 512 = -7680; -7680 + 512 = -7168; and so on) until your problem is solved.

You don't have DAG generation problem because the log clearly says:
'2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)'

The hash searching kernel hits timeout with the default settings because your GPU (980ti) is very slow.

Im still getting errors having tried both things

...
2019.02.27:00:33:42.195: GPU1 GPU1: DAG generated in 7.8 s (381.1 MB/s)
2019.02.27:00:33:45.445: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x088daa6feef69fb37650e0bc4c08a8702b30d9abf866bf6c91a57f24d321a922","0xd5c0f3c36d0a543d1ec6363fda4c51ba4ab00e7a5fbfa7d81ebb3ba46fd25dcb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6efce7"]}
2019.02.27:00:33:45.445: eths Eth: New job #088daa6f from eu1.ethermine.org:4444; diff: 4000MH
2019.02.27:00:33:46.358: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.27:00:33:48.410: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.27:00:33:48.410: GPU1 GPU1 search error: the launch timed out and was terminated
...
You said you have tried both things. Have you tried all the values for -ethi parameter (not only -8192 and -7680)? Have you tried -ethi -1 ? This definitely should solve your problem. Beware all the values after -ethi must be negative.
pbfarmer
Member
**
Offline Offline

Activity: 340
Merit: 29


View Profile
February 27, 2019, 10:49:59 AM
 #2984

Hello,
I can't get my Vega (56&64 reference card) stable. My rig is always crashing.
Could you share your card clock and memory and the best parameters of the minerfor these cards.
Thanks
Vega64 - Strix
OverdriveNtool
Core - P7 852/825mv
Memory - P3 1083/825mv

Thanks ! 852 core frequency ? What is your hashrate with these settings ?

ETH is memory bound, core clock effect is minimal on Vegas.  Instead of setting P7, simply disable all GPU power states above P0 in OverdriveNTool.  Also, your memory clock can go up to 1107  for a 64 and you should be able to use a voltage setting between 806-831mv.  Above 1107, your voltage requirement jumps significantly to around 900mv (due to SOC clock scaling to 1200MHz.)

For a 56, your voltages and core clock would be the same, but your memory clock will have a fuzzier limit than the 64 - somewhere between 900-950MHz most likely.
Hi, i remember u in ryo chat Grin

Hi - yep...  Keeping tabs on a lot of different forums/channels... Wink  Looks like you've got your Vegas all figured out Smiley
Marginmasters
Newbie
*
Offline Offline

Activity: 68
Merit: 0


View Profile
March 01, 2019, 04:39:01 PM
 #2985

http://c.radikal.ru/c04/1903/76/c9209898ff0b.jpg


PhoenixMiner_4.1c

guys what's the problem? he doesn't connect to solo mining through my geth
------------------------------------------------------------------------
 and this version works fine  - PhoenixMiner_4.0b_Windows
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 01, 2019, 04:41:07 PM
 #2986




PhoenixMiner_4.1c

guys what's the problem? he doesn't connect to solo mining through my geth
------------------------------------------------------------------------
 and this version works fine  - PhoenixMiner_4.0b_Windows


Have you enabled stratum connections in GETH locally?

if not then you should be connecting via getwork then.

GLTU
Marginmasters
Newbie
*
Offline Offline

Activity: 68
Merit: 0


View Profile
March 01, 2019, 05:20:19 PM
 #2987

lesjokolat

yes geth local connection PhoenixMiner.exe -pool http://192.168.1.12:8545
Other miners are working fine, what could be wrong?
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 01, 2019, 06:47:29 PM
 #2988

lesjokolat

yes geth local connection PhoenixMiner.exe -pool http://192.168.1.12:8545
Other miners are working fine, what could be wrong?

Take a look at post 1. Your startup isnt defining coin corrrectly.

See examples match them as they will still need local user  and password as well.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 03, 2019, 01:28:22 PM
 #2989

I'm having the same issue.  I'm mining Callisto (CLO).  I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work.  This is where the issue comes in.

I am setting the coin on the commandline.

I tried setting a "password' in commandline as suggested above, but that doesn't make a difference.  Over the past few days, I've also tried as many other options as I can.  It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.

See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.

Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
 
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 03, 2019, 01:38:58 PM
 #2990

Now if there is a hidden trick for enabling Stratum in geth, I'd love to hear it.  Of if there's a quick & easy way to have a proxy that talks rpc to geth and then talks stratum to miner - without having to setup a whole pool software for myself.  That would be fine, but there still appears to be a bug in PhoenixMiner's support for local rpc.
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 03, 2019, 02:48:15 PM
 #2991

I'm having the same issue.  I'm mining Callisto (CLO).  I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work.  This is where the issue comes in.

I am setting the coin on the commandline.

I tried setting a "password' in commandline as suggested above, but that doesn't make a difference.  Over the past few days, I've also tried as many other options as I can.  It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.

See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.

Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
 
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.

what is your command line startup?
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 03, 2019, 02:53:20 PM
 #2992

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 03, 2019, 03:03:14 PM
 #2993

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

is geth running on same machine?

can you add -v 3 to the command line its for more verbose output.
keksik
Jr. Member
*
Offline Offline

Activity: 169
Merit: 1


View Profile
March 03, 2019, 08:06:52 PM
 #2994

hello,

i would like to ask some questions:
- when i start to mine, how long it takes to start dev mining?
- when i start stop miner, does it reset counter for dev mining? for example im mining with another miner, then it starts with claymore, after couple hours, it switch back and then after couple hours again with claymore, so does it reset dev mining counter? or another example, im fine tunning and i left miner run for half hour or less, does the counter reset all the time?

thank you
Bigdrago
Newbie
*
Offline Offline

Activity: 312
Merit: 0


View Profile
March 03, 2019, 09:20:41 PM
 #2995

My gpu is 48C and fan is 0%  according to phoenix miner program. (I have set target temp 50C).
 
But I also have set minimum rpm. Is the fan completely shut off when my  mining program shows that the fan is 0%? Or is it 0% compared to what  minimum fan speed is. That it is actually 500rpm (0%) and max is 2400rpm  (100%) ?
I cant look at the gpus because they are boxed in and safe outside.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 04, 2019, 12:44:13 PM
 #2996

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

is geth running on same machine?

can you add -v 3 to the command line its for more verbose output.


geth is on a different machine.

-v only prints version and exits - doesn't enable verbose.  -log 2 is supposed to enable debug messages, but doesn't really appear any different.  Here's a full log with -log 2

So same thing here - why is it monitoring a stratum thread and rebooting because of it if we are not using stratum.  Seems like a pretty clear bug to me.

Code:
2019.03.04:07:37:05.759: main Phoenix Miner 4.1c Linux/gcc - Release build
2019.03.04:07:37:05.759: main Cmd line: -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 6 -gpureset 1 -rmode 2 -log 0 -wal address_redacted -worker m01n6 -log 2
2019.03.04:07:37:05.887: main CUDA version: 10.0, CUDA runtime: 8.0
2019.03.04:07:37:05.902: main Available GPUs for mining:
2019.03.04:07:37:05.902: main GPU1: GeForce GTX 1060 6GB (pcie 16), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2019.03.04:07:37:05.905: main NVML library initialized
2019.03.04:07:37:05.952: main Nvidia driver version: 415.27
2019.03.04:07:37:05.953: main Eth: the pool list contains 1 pool (1 from command-line)
2019.03.04:07:37:05.953: main Eth: primary pool: http://10.69.1.10:8547
2019.03.04:07:37:05.953: main Starting GPU mining
2019.03.04:07:37:05.953: main Eth: Connecting to http://10.69.1.10:8547 (GetWork/Solo)
2019.03.04:07:37:05.953: wdog Starting watchdog thread
2019.03.04:07:37:05.954: eths Eth: New job #ec69b6c7 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:05.954: eths Eth: Connected to ethash pool http://10.69.1.10:8547
2019.03.04:07:37:05.954: GPU1 GPU1: Starting up... (0)
2019.03.04:07:37:05.954: GPU1 GPU1: Generating ethash light cache for epoch #72
2019.03.04:07:37:06.153: main GPU1: 43C 33%
2019.03.04:07:37:07.040: GPU1 Light cache generated in 1.1 s (23.0 MB/s)
2019.03.04:07:37:07.360: eths Eth: New job #3bbc6801 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:07.557: GPU1 GPU1: Allocating DAG for epoch #72 (1.56) GB
2019.03.04:07:37:07.559: GPU1 GPU1: Allocating light cache buffer (25.0) MB; good for epoch up to #72
2019.03.04:07:37:07.682: GPU1 GPU1: Generating DAG for epoch #72
2019.03.04:07:37:09.313: GPU1 GPU1: DAG  16%
2019.03.04:07:37:10.371: eths Eth: New job #b53c3d01 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:10.930: GPU1 GPU1: DAG  34%
2019.03.04:07:37:10.958: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:12.542: GPU1 GPU1: DAG  53%
2019.03.04:07:37:13.385: eths Eth: New job #e9bee5d8 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:14.159: GPU1 GPU1: DAG  72%
2019.03.04:07:37:15.771: GPU1 GPU1: DAG  91%
2019.03.04:07:37:15.969: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:16.310: GPU1 GPU1: DAG generated in 8.6 s (185.4 MB/s)
2019.03.04:07:37:19.221: eths Eth: New job #c9a57953 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:20.980: main Eth speed: 13.738 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:22.237: eths Eth: New job #5a97fd50 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:25.991: main Eth speed: 13.455 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:30.998: main Eth speed: 13.395 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:33.290: eths Eth: New job #15d1a238 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:34.005: main GPU1: 52C 33%
2019.03.04:07:37:36.009: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:39.322: eths Eth: New job #def4241f from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:41.020: main Eth speed: 13.274 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:44.348: eths Eth: New job #91a13849 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:46.031: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:51.037: main *** 0:00 *** 3/4 07:37 **************************************
2019.03.04:07:37:51.037: main Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
2019.03.04:07:37:51.037: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.03.04:07:37:51.037: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.03.04:07:37:51.037: main Eth: Average speed (5 min): 13.326 MH/s
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:56.049: main Eth speed: 13.276 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:56.650: main Stratum thread not responsive for 51 s
2019.03.04:07:37:56.958: wdog Thread(s) not responding. Restarting.
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 04, 2019, 04:29:01 PM
 #2997

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

is geth running on same machine?

can you add -v 3 to the command line its for more verbose output.


geth is on a different machine.

-v only prints version and exits - doesn't enable verbose.  -log 2 is supposed to enable debug messages, but doesn't really appear any different.  Here's a full log with -log 2

So same thing here - why is it monitoring a stratum thread and rebooting because of it if we are not using stratum.  Seems like a pretty clear bug to me.

Code:
2019.03.04:07:37:05.759: main Phoenix Miner 4.1c Linux/gcc - Release build
2019.03.04:07:37:05.759: main Cmd line: -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 6 -gpureset 1 -rmode 2 -log 0 -wal address_redacted -worker m01n6 -log 2
2019.03.04:07:37:05.887: main CUDA version: 10.0, CUDA runtime: 8.0
2019.03.04:07:37:05.902: main Available GPUs for mining:
2019.03.04:07:37:05.902: main GPU1: GeForce GTX 1060 6GB (pcie 16), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2019.03.04:07:37:05.905: main NVML library initialized
2019.03.04:07:37:05.952: main Nvidia driver version: 415.27
2019.03.04:07:37:05.953: main Eth: the pool list contains 1 pool (1 from command-line)
2019.03.04:07:37:05.953: main Eth: primary pool: http://10.69.1.10:8547
2019.03.04:07:37:05.953: main Starting GPU mining
2019.03.04:07:37:05.953: main Eth: Connecting to http://10.69.1.10:8547 (GetWork/Solo)
2019.03.04:07:37:05.953: wdog Starting watchdog thread
2019.03.04:07:37:05.954: eths Eth: New job #ec69b6c7 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:05.954: eths Eth: Connected to ethash pool http://10.69.1.10:8547
2019.03.04:07:37:05.954: GPU1 GPU1: Starting up... (0)
2019.03.04:07:37:05.954: GPU1 GPU1: Generating ethash light cache for epoch #72
2019.03.04:07:37:06.153: main GPU1: 43C 33%
2019.03.04:07:37:07.040: GPU1 Light cache generated in 1.1 s (23.0 MB/s)
2019.03.04:07:37:07.360: eths Eth: New job #3bbc6801 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:07.557: GPU1 GPU1: Allocating DAG for epoch #72 (1.56) GB
2019.03.04:07:37:07.559: GPU1 GPU1: Allocating light cache buffer (25.0) MB; good for epoch up to #72
2019.03.04:07:37:07.682: GPU1 GPU1: Generating DAG for epoch #72
2019.03.04:07:37:09.313: GPU1 GPU1: DAG  16%
2019.03.04:07:37:10.371: eths Eth: New job #b53c3d01 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:10.930: GPU1 GPU1: DAG  34%
2019.03.04:07:37:10.958: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:12.542: GPU1 GPU1: DAG  53%
2019.03.04:07:37:13.385: eths Eth: New job #e9bee5d8 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:14.159: GPU1 GPU1: DAG  72%
2019.03.04:07:37:15.771: GPU1 GPU1: DAG  91%
2019.03.04:07:37:15.969: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:16.310: GPU1 GPU1: DAG generated in 8.6 s (185.4 MB/s)
2019.03.04:07:37:19.221: eths Eth: New job #c9a57953 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:20.980: main Eth speed: 13.738 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:22.237: eths Eth: New job #5a97fd50 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:25.991: main Eth speed: 13.455 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:30.998: main Eth speed: 13.395 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:33.290: eths Eth: New job #15d1a238 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:34.005: main GPU1: 52C 33%
2019.03.04:07:37:36.009: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:39.322: eths Eth: New job #def4241f from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:41.020: main Eth speed: 13.274 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:44.348: eths Eth: New job #91a13849 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:46.031: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:51.037: main *** 0:00 *** 3/4 07:37 **************************************
2019.03.04:07:37:51.037: main Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
2019.03.04:07:37:51.037: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.03.04:07:37:51.037: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.03.04:07:37:51.037: main Eth: Average speed (5 min): 13.326 MH/s
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:56.049: main Eth speed: 13.276 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:56.650: main Stratum thread not responsive for 51 s
2019.03.04:07:37:56.958: wdog Thread(s) not responding. Restarting.

In a command line see if geth is truly set to mine:

geth --rpc --rpcapi eth --rpcaddr IPADDR --rpcport YOURPORT --mine --miner.etherbase <the-eth-address-where-you-want-to-credit-your-rewards> console


Ok so it is supposed to be supported protocal so try one of these 3 things:

ADD -G see if it will trigger the getwork method.

Claymore command:
-mode 1

Phoenix command:
-gwtime 200 (Recheck period for Solo/GetWork mining default: 200 ms)

see if any of these help.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 04, 2019, 08:21:51 PM
Last edit: March 04, 2019, 08:43:23 PM by puithove
 #2998

In a command line see if geth is truly set to mine:

geth --rpc --rpcapi eth --rpcaddr IPADDR --rpcport YOURPORT --mine --miner.etherbase <the-eth-address-where-you-want-to-credit-your-rewards> console


Ok so it is supposed to be supported protocal so try one of these 3 things:

ADD -G see if it will trigger the getwork method.

Claymore command:
-mode 1

Phoenix command:
-gwtime 200 (Recheck period for Solo/GetWork mining default: 200 ms)

see if any of these help.

Thanks, but still no.

Geth is truly ready to mine.  I'm using ethminer against it and successfully mining blocks.  In fact, PhoenixMiner starts mining with it before it craps out due to the stratum thread error - so it's not an issue with being able to get work with eth_getwork (refer to log posted above)

Had previously tried -gwtime - no change

-G is invalid option for PhoenixMiner

-mode 1 - no change

PhoenixMiner is not an option currently.
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
March 04, 2019, 11:04:55 PM
 #2999

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
ManDoneKTM
Newbie
*
Offline Offline

Activity: 150
Merit: 0


View Profile
March 06, 2019, 03:52:04 AM
 #3000

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
why you would use pm with newest drivers ? you will have the same results in hashrate ... ffs
Pages: « 1 ... 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 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 ... 499 »
  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!