Bitcoin Forum
August 21, 2018, 02:52:10 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 ... 121 »
  Print  
Author Topic: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)  (Read 82297 times)
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 12, 2018, 01:16:54 PM
 #81

I have been running for 8hrs without any problem. Hash rate are approx. the same as using claymore. I can now see  3mins average hashrate and stale share. I will change to phoenixminer if it is stable for 1-2 days. Good work!  Smiley
1534863130
Hero Member
*
Offline Offline

Posts: 1534863130

View Profile Personal Message (Offline)

Ignore
1534863130
Reply with quote  #2

1534863130
Report to moderator
1534863130
Hero Member
*
Offline Offline

Posts: 1534863130

View Profile Personal Message (Offline)

Ignore
1534863130
Reply with quote  #2

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

Posts: 1534863130

View Profile Personal Message (Offline)

Ignore
1534863130
Reply with quote  #2

1534863130
Report to moderator
1534863130
Hero Member
*
Offline Offline

Posts: 1534863130

View Profile Personal Message (Offline)

Ignore
1534863130
Reply with quote  #2

1534863130
Report to moderator
1534863130
Hero Member
*
Offline Offline

Posts: 1534863130

View Profile Personal Message (Offline)

Ignore
1534863130
Reply with quote  #2

1534863130
Report to moderator
Golempl
Jr. Member
*
Offline Offline

Activity: 41
Merit: 0


View Profile
January 12, 2018, 01:34:03 PM
 #82

I did some tests with RX 570 4GB (bios mod + core 1190/mem2000)

Claymore  10.0           29.17MH/s   (1% devfee    - 0,29MH/s)  28,88MH/s effective
PhoenixMiner 2.2b        29.52MH/s   (0.65% devfee - 0,19MH/s)  29,33MH/s effective
Goobur ethminer 0.12.0   29.14MH/s   (0% devdee if u suck)

#########
Mix of cards seems better too:
RX580 8gb + GTX 1060 6gb

2 GPU CLAYMORE 10.0
ETH: GPU0 30.394 Mh/s, GPU1 23.240 Mh/s
2GPU PHOENIX 2.2b
GPUs: 1: 30.703 MH/s  2: 23.385 MH/s
#########

Seems like it's worth to use PhoenixMiner, these are local tests and need to be confirmed online.
I like these pool hashrate reports, same as claymore command line is big +


odus709
Newbie
*
Online Online

Activity: 22
Merit: 0


View Profile
January 12, 2018, 07:21:54 PM
 #83

Admin,

Nodez coin is setting up their test net and the Dev there said he would be interested in adding their coin to your mining devfee algo. He stated he would be happy to setup if you might like to reach out to him. I sent a link to the Discord from this bitcointalk thread to help you gain some support. They are looking to launch mining in the next couple days!

https://discordapp.com/channels/359804055490658315/359804055490658317

Nodez Dev Info:
WallerMaDev
Mat@nodezcrypto.io
www.twitter.com/wallermadev

-Tom
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 13, 2018, 01:40:29 AM
 #84

Hi,

   When I press "r" to reload the epool.txt, it seems that the miner cannot connect any pool. I press Ctrl + C to quit then it crashed. It was mining happily before I press the "r".  Huh

Code:

17544:09:22:08.498: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:13.094: main Eth speed: 183.750 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:13.094: main GPUs: 1: 30.667 MH/s (3) 2: 30.663 MH/s (4) 3: 30.672 MH/s (1) 4: 30.644 MH/s (3) 5: 30.663 MH/s (2) 6: 30.442 MH/s (1)
17544:09:22:18.271: main  
17544:09:22:18.271: main Eth: Mining ETH on asia1.ethermine.org:4444
17544:09:22:18.271: main Eth speed: 183.762 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:18.271: main GPUs: 1: 30.666 MH/s (3) 2: 30.626 MH/s (4) 3: 30.644 MH/s (1) 4: 30.555 MH/s (3) 5: 30.639 MH/s (2) 6: 30.632 MH/s (1)
17544:09:22:18.271: main Eth: Accepted shares 14 (0 stales), rejected shares 0 (0 stales)
17544:09:22:18.271: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
17544:09:22:18.271: main Eth: Maximum difficulty of found share: 74.0 GH (!)
17544:09:22:18.271: main Eth: Average speed (3 min): 183.797 MH/s
17544:09:22:18.271: main Eth: Effective speed: 175.00 MH/s; at pool: 175.00 MH/s
17544:09:22:18.271: main  
17544:09:22:18.459: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17544:09:22:18.459: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaf48488","0xdb505ca89c5f206be24ec09ae9dcc2683618205675a281584b4b64daa9e1e323"]}

17544:09:22:18.500: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:18.540: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:18.541: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17544:09:22:23.274: main Eth speed: 184.010 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:23.274: main GPUs: 1: 30.647 MH/s (3) 2: 30.669 MH/s (4) 3: 30.672 MH/s (1) 4: 30.670 MH/s (3) 5: 30.673 MH/s (2) 6: 30.678 MH/s (1)
17544:09:22:28.452: main Eth speed: 183.957 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:28.452: main GPUs: 1: 30.659 MH/s (3) 2: 30.652 MH/s (4) 3: 30.660 MH/s (1) 4: 30.652 MH/s (3) 5: 30.663 MH/s (2) 6: 30.672 MH/s (1)
17544:09:22:28.460: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17544:09:22:28.501: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:33.457: main Eth speed: 183.915 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:33.457: main GPUs: 1: 30.584 MH/s (3) 2: 30.665 MH/s (4) 3: 30.671 MH/s (1) 4: 30.655 MH/s (3) 5: 30.674 MH/s (2) 6: 30.665 MH/s (1)
17544:09:22:35.654: main GPU1: 60C 26%, GPU2: 55C 24%, GPU3: 47C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:22:38.473: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17544:09:22:38.473: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaf4859f","0xdb505ca89c5f206be24ec09ae9dcc2683618205675a281584b4b64daa9e1e323"]}

17544:09:22:38.476: main Eth speed: 182.615 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:38.476: main GPUs: 1: 30.357 MH/s (3) 2: 30.387 MH/s (4) 3: 30.382 MH/s (1) 4: 30.385 MH/s (3) 5: 30.420 MH/s (2) 6: 30.683 MH/s (1)
17544:09:22:38.516: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:38.555: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:38.555: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17544:09:22:43.486: main Eth speed: 183.578 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:43.486: main GPUs: 1: 30.655 MH/s (3) 2: 30.672 MH/s (4) 3: 30.659 MH/s (1) 4: 30.601 MH/s (3) 5: 30.675 MH/s (2) 6: 30.316 MH/s (1)
17544:09:22:44.584: GPU6 Eth: GPU6: ETH share found!
17544:09:22:44.584: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x11f09358634b76f5","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0x7bd061e905404708bd08967de5dbed299ed4b498414875ac7b05741a091165f5"]}

17544:09:22:44.584: eths Eth: Share actual difficulty: 26.8 GH (!)
17544:09:22:44.629: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:44.629: eths Eth: Share accepted in 45 ms
17544:09:22:48.479: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17544:09:22:48.520: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:48.558: main Eth speed: 184.649 MH/s, shares: 15/0/0, time: 0:05
17544:09:22:48.558: main GPUs: 1: 30.658 MH/s (3) 2: 30.669 MH/s (4) 3: 30.672 MH/s (1) 4: 30.674 MH/s (3) 5: 30.674 MH/s (2) 6: 31.303 MH/s (2)
17544:09:22:51.601: GPU5 Eth: GPU5: ETH share found!
17544:09:22:51.601: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x7c67ac6cba2de823","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xa8295ad3c70722c8c717b27f9f972cc67dd5f5b08129ebd57ab641e5c7a4b16f"]}

17544:09:22:51.601: eths Eth: Share actual difficulty: 10.2 GH (!)
17544:09:22:51.645: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:51.645: eths Eth: Share accepted in 44 ms
17544:09:22:53.574: main Eth speed: 184.775 MH/s, shares: 16/0/0, time: 0:05
17544:09:22:53.574: main GPUs: 1: 30.662 MH/s (3) 2: 30.631 MH/s (4) 3: 30.676 MH/s (1) 4: 30.643 MH/s (3) 5: 31.537 MH/s (3) 6: 30.627 MH/s (2)
17544:09:22:56.617: GPU6 Eth: GPU6: ETH share found!
17544:09:22:56.617: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x11f093587925191e","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xa89d6809e3f6c80b0e30a3dba70431855719e4355fa35263274a2808fb2bece7"]}

17544:09:22:56.617: eths Eth: Share actual difficulty: 15.8 GH (!)
17544:09:22:56.661: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:56.661: eths Eth: Share accepted in 44 ms
17544:09:22:56.840: main Reloading epools.txt
17544:09:22:56.840: main Eth: the pool list contains 4 pools
17544:09:22:56.840: main Eth: primary pool: asia1.ethermine.org:4444
17544:09:22:56.840: eths Eth: Reconnecting in 10 seconds...
17544:09:23:03.663: main GPU1: 61C 26%, GPU2: 55C 24%, GPU3: 46C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:23:06.851: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:10.139: unkn Eth: Connection attempt aborted
17544:09:23:10.139: unkn Eth: Reconnecting in 15 seconds...
17544:09:23:24.893: GPU6 Unable to submit share - pool disconnected
17544:09:23:25.145: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:26.938: GPU2 Unable to submit share - pool disconnected
17544:09:23:28.441: unkn Eth: Connection attempt aborted
17544:09:23:28.441: unkn Eth: Reconnecting in 20 seconds...
17544:09:23:31.863: main GPU1: 60C 26%, GPU2: 55C 24%, GPU3: 46C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:23:37.086: main Reloading epools.txt
17544:09:23:37.086: main Eth: the pool list contains 4 pools
17544:09:23:37.086: main Eth: primary pool: asia1.ethermine.org:4444
17544:09:23:37.086: unkn Eth: Reconnecting in 10 seconds...
17544:09:23:47.092: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:50.381: unkn Eth: Connection attempt aborted
17544:09:23:50.381: unkn Eth: Reconnecting in 15 seconds...
17544:09:23:52.542: GPU5 Unable to submit share - pool disconnected
17544:09:24:00.020: main GPU1: 60C 26%, GPU2: 54C 24%, GPU3: 51C 0%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:24:05.396: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:24:08.679: unkn Eth: Connection attempt aborted
17544:09:24:08.679: unkn Eth: Reconnecting in 20 seconds...
17544:09:24:16.881: main
17544:09:24:16.881: main Select pool (press key from 0 to 3)
17544:09:24:16.881: main * 0. asia1.ethermine.org:4444
17544:09:24:16.881: main   1. asia1.ethermine.org:14444
17544:09:24:16.881: main   2. us1.ethermine.org:4444
17544:09:24:16.881: main   3. asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:16.881: main
17544:09:24:21.754: main Mining on GPU3 is disabled
17544:09:24:23.530: main Mining on GPU3 is enabled
17544:09:24:28.123: main GPU1: 61C 25%, GPU2: 54C 24%, GPU3: 50C 26%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:24:28.683: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:24:31.992: unkn Eth: Connection attempt aborted
17544:09:24:31.992: unkn Eth: Giving up after 3 retries, switching to next pool
17544:09:24:31.992: unkn Eth: Reconnecting in 7 seconds...
17544:09:24:34.457: main
17544:09:24:34.457: main Select pool (press key from 0 to 3)
17544:09:24:34.457: main   0. asia1.ethermine.org:4444
17544:09:24:34.457: main * 1. asia1.ethermine.org:14444
17544:09:24:34.457: main   2. us1.ethermine.org:4444
17544:09:24:34.457: main   3. asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:34.457: main
17544:09:24:36.857: main Eth: Switching to pool: asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:36.857: unkn Eth: Reconnecting in 10 seconds...
17544:09:24:43.835: GPU5 Unable to submit share - pool disconnected
17544:09:24:46.865: unkn Eth: Connecting to ethash pool asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:50.182: unkn Eth: Connection attempt aborted
17544:09:24:50.182: unkn Eth: Reconnecting in 15 seconds...
17544:09:24:56.255: main GPU1: 61C 25%, GPU2: 54C 24%, GPU3: 48C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 58C 24%
17544:09:25:05.048: unkn Quitting...
17544:09:25:05.186: unkn Eth: Connecting to ethash pool asia.ethash-hub.miningpoolhub.com:20535
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 13, 2018, 06:09:02 AM
 #85

Nodez coin is setting up their test net and the Dev there said he would be interested in adding their coin to your mining devfee algo. He stated he would be happy to setup if you might like to reach out to him. I sent a link to the Discord from this bitcointalk thread to help you gain some support. They are looking to launch mining in the next couple days!
Thank you for the info. It can be done (to avoid devfee DAG switching for Nodez) but we need a working wallet and working pool for this coin (with at least a dozen GH/s or so). Devfee of 0.65% means that it is only about 1 in 153 found shares on average that goes to the devfee account and if the hasrate for this coin is below certain threshold, the devfee is essentially zero.

   When I press "r" to reload the epool.txt, it seems that the miner cannot connect any pool. I press Ctrl + C to quit then it crashed. It was mining happily before I press the "r".  Huh
Sorry for this problem. We managed to reproduce it here thanks to the log you have send. It doesn't happen often but when it does it can be fairly annoying. Eventually the miner manages to connect but it may take a ten or more attempts. We are going to find the root cause and will introduce a fix (but probably not in version 2.3 as it is already being tested internally). In the meantime if the miner can't connect with "Connection attempt aborted" error after a few attempts, the best workaround it to close it (ignore the error on exit if you get one) and start it again.

yes i can help you test kernel, im on windows 10 with the amd blockchain driver
We will send you the link to the new version via PM. It includes slightly modified kernels for Ellesmere GPUs (RX470/480/570/580), which can be used if the option -clKernel 2 (or -asm 2 if you prefer Claymore's command-line syntax). Please note that during our testing on similar hardware to yours, the alternative kernel runs a little bit faster but only with very specific combination of core/mem clocks so in most cases we recommend using the default Ellesmere kernels.
hafizhasan
Jr. Member
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 13, 2018, 06:27:02 AM
 #86

Can I control core clock and memory clocks from the bat files...? I m using rx580 armor oc edition..
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 13, 2018, 06:28:13 AM
 #87

Ok, it seems that we can't send PM for some reason, so here it is the download link for the beta version of PhoenixMiner 2.3:
  https://mega.nz/#F!bI1zFRxB!sK_JV0S9Vm5PxIBQo_hg9A

  Here are the checksums of the PhenixMiner.exe file:
Code:
   File: PhoenixMiner.exe
   SHA-1: 90e455d81ce2f396e3d8121a5db3f4a356910dff
 SHA-256: f119ae5b1085019522ab2a3752d20579647ed9fd9ff55cc739002de269adbc55
 SHA-512: 3b876dc5491dae6da8849af941f4d0395b051e64a7fdcd42f126819d4788ef860c7d5f6e59763a5ed2d3368e93ec9b7e6bb6bca0476509e2a95d0856fe26fd68

   Note that this is not fully tested yet and not an official release. The major changes are:
  • Added alternative kernels for RX470/480/570/580, which can be used by specifying -clKernel 2 (or -asm 2) on the command-line. In some cases these can be faster than the default kernels but more often than not you are better off with the default kernels. Additionally, the hashrate can be more unstable with the alternative kernels.
  • Fixed a problem with not reporting temperatures/fan speed with the latest AMD drivers
  • Fixed a problem with Intel iGPUs, which PhoenixMiner sometimes tries to use for mining, fails and then restarts and tries again, and so on.

Can I control core clock and memory clocks from the bat files...? I m using rx580 armor oc edition..
No, not yet. We are working on this feature but it is going to take some time as the different versions of the AMD drivers behave quite differently when trying to use Overdrive APIs. For now you should use MSI Afterburner, Wattman, or something similar to control the clocks and fans.
hafizhasan
Jr. Member
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 13, 2018, 06:34:56 AM
 #88

Do the test kernels help in limiting temp and memory clocks?
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 13, 2018, 06:49:45 AM
 #89

Do the test kernels help in limiting temp and memory clocks?

Just use overdriventool. You can set core, memory clock and control voltage. It is very stable.
cdrx
Full Member
***
Online Online

Activity: 378
Merit: 109


View Profile
January 13, 2018, 07:16:40 AM
 #90

Can you add please dev fee pool for pegascoin (PGC) ? https://bitcointalk.org/index.php?topic=2132259.0

Thanks.

choose from https://minerpool.net/pools/pegascoin/

JSEcoin is a browser mined blockchain, powered by webmasters and built for mainstream adoption
Live platform since August 2017 - ICO ends 11th Oct 2018
https://jsecoin.com
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 13, 2018, 06:29:46 PM
 #91

Hi,

   I found that sometimes the miner fall into a reconnection loop just like I pressed "r". It said "Unable to read pool response. Timeout" then keep reconnecting fail and reconnecting fail. My internet connection should be okay. Cry  Is that the timeout setting too low while my ping to the pool is too high at that moment?

Code:

17545:01:36:23.386: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x42cb6ae3d567443c5989f3bf19f5f8d3b057a9bdee303d0f6bc10f1922733829","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4acf0e"]}
17545:01:36:26.140: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x25f44f8679e82263e3259fbf46bf4c5ba027cbf5cc9ee3b6a5f07e9c59d84f32","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4acf0f"]}
17545:01:36:26.140: eths Eth: New job #25f44f86 from asia1.ethermine.org:4444; diff: 4000MH
17545:01:36:26.711: main GPU1: 61C 24%, GPU2: 53C 24%, GPU3: 46C 24%, GPU4: 61C 27%, GPU5: 56C 24%, GPU6: 56C 24%
17545:01:36:27.148: main Eth speed: 182.119 MH/s, shares: 131/0/0, time: 0:45
17545:01:36:27.148: main GPUs: 1: 30.400 MH/s (28) 2: 30.406 MH/s (22) 3: 30.411 MH/s (20) 4: 30.118 MH/s (18) 5: 30.398 MH/s (17) 6: 30.386 MH/s (26)
17545:01:36:32.159: main Eth speed: 181.602 MH/s, shares: 131/0/0, time: 0:46
17545:01:36:32.159: main GPUs: 1: 30.403 MH/s (28) 2: 30.389 MH/s (22) 3: 30.397 MH/s (20) 4: 30.205 MH/s (18) 5: 29.821 MH/s (17) 6: 30.387 MH/s (26)
17545:01:36:33.357: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xad6dc69","0x62c79658ff887ec6f458c47585562f19eb549c2d162ee3ff1c4ba52e7db8d2ae"]}

17545:01:36:37.246: main Eth speed: 181.846 MH/s, shares: 131/0/0, time: 0:46
17545:01:36:37.246: main GPUs: 1: 30.410 MH/s (28) 2: 30.398 MH/s (22) 3: 30.414 MH/s (20) 4: 29.813 MH/s (18) 5: 30.405 MH/s (17) 6: 30.407 MH/s (26)
17545:01:36:41.187: GPU6 Eth: GPU6: ETH share found!
17545:01:36:41.187: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x018e451d22f9a6cf","0x25f44f8679e82263e3259fbf46bf4c5ba027cbf5cc9ee3b6a5f07e9c59d84f32","0x110b4d7d8ce0727513e9cb8dbe2f2193b5c111fe5a9f11cdb3e86adf1c990448"]}

17545:01:36:41.187: eths Eth: Share actual difficulty: 5013 MH
17545:01:36:42.417: main Eth speed: 182.194 MH/s, shares: 131/0/0, time: 0:46
17545:01:36:42.417: main GPUs: 1: 30.405 MH/s (28) 2: 30.410 MH/s (22) 3: 30.414 MH/s (20) 4: 30.404 MH/s (18) 5: 30.412 MH/s (17) 6: 30.149 MH/s (26)
17545:01:36:43.361: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17545:01:36:47.422: main  
17545:01:36:47.422: main Eth: Mining ETH on asia1.ethermine.org:4444
17545:01:36:47.422: main Eth speed: 181.655 MH/s, shares: 131/0/0, time: 0:46
17545:01:36:47.422: main GPUs: 1: 30.118 MH/s (28) 2: 30.112 MH/s (22) 3: 30.411 MH/s (20) 4: 30.209 MH/s (18) 5: 30.403 MH/s (17) 6: 30.402 MH/s (26)
17545:01:36:47.422: main Eth: Accepted shares 131 (1 stales), rejected shares 0 (0 stales)
17545:01:36:47.422: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.76%
17545:01:36:47.422: main Eth: Maximum difficulty of found share: 2539.5 GH (!)
17545:01:36:47.422: main Eth: Average speed (3 min): 181.828 MH/s
17545:01:36:47.422: main Eth: Effective speed: 188.76 MH/s; at pool: 188.76 MH/s
17545:01:36:47.422: main  
17545:01:36:52.594: eths Eth: Unable to read pool response: 信號等待逾時。
17545:01:36:52.594: eths Eth: Reconnecting in 10 seconds...
17545:01:36:54.808: main GPU1: 61C 24%, GPU2: 54C 24%, GPU3: 46C 24%, GPU4: 61C 27%, GPU5: 56C 24%, GPU6: 56C 24%
17545:01:37:02.601: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17545:01:37:05.896: unkn Eth: Connection attempt aborted
17545:01:37:05.896: unkn Eth: Reconnecting in 15 seconds...
17545:01:37:20.913: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17545:01:37:22.887: main GPU1: 61C 24%, GPU2: 53C 24%, GPU3: 50C 0%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 57C 24%
17545:01:37:24.194: unkn Eth: Connection attempt aborted
17545:01:37:24.194: unkn Eth: Reconnecting in 20 seconds...
17545:01:37:32.502: GPU5 Unable to submit share - pool disconnected
17545:01:37:44.196: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17545:01:37:44.894: GPU6 Unable to submit share - pool disconnected
17545:01:37:47.484: unkn Eth: Connection attempt aborted
17545:01:37:47.484: unkn Eth: Giving up after 3 retries, switching to next pool
17545:01:37:47.484: unkn Eth: Reconnecting in 7 seconds...
17545:01:37:51.087: main GPU1: 61C 24%, GPU2: 53C 24%, GPU3: 51C 27%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 57C 24%
17545:01:37:54.499: unkn Eth: Connecting to ethash pool asia1.ethermine.org:14444
17545:01:37:57.778: unkn Eth: Connection attempt aborted
17545:01:37:57.778: unkn Eth: Reconnecting in 10 seconds...
17545:01:38:07.790: unkn Eth: Connecting to ethash pool asia1.ethermine.org:14444
17545:01:38:09.407: GPU3 Unable to submit share - pool disconnected
17545:01:38:09.506: GPU6 Unable to submit share - pool disconnected
17545:01:38:11.076: unkn Eth: Connection attempt aborted
17545:01:38:11.076: unkn Eth: Reconnecting in 15 seconds...
17545:01:38:15.766: GPU6 Unable to submit share - pool disconnected
17545:01:38:19.134: main GPU1: 61C 24%, GPU2: 53C 24%, GPU3: 49C 24%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 57C 24%
17545:01:38:26.083: unkn Eth: Connecting to ethash pool asia1.ethermine.org:14444
17545:01:38:29.377: unkn Eth: Connection attempt aborted
17545:01:38:29.377: unkn Eth: Reconnecting in 20 seconds...
17545:01:38:38.189: GPU1 Unable to submit share - pool disconnected
17545:01:38:45.724: GPU2 Unable to submit share - pool disconnected
17545:01:38:47.185: main GPU1: 61C 24%, GPU2: 53C 24%, GPU3: 47C 24%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 56C 24%
17545:01:38:48.777: GPU4 Unable to submit share - pool disconnected
17545:01:38:49.384: unkn Eth: Connecting to ethash pool asia1.ethermine.org:14444
17545:01:38:49.804: GPU6 Unable to submit share - pool disconnected
17545:01:38:52.665: unkn Eth: Connection attempt aborted
17545:01:38:52.665: unkn Eth: Giving up after 3 retries, switching to next pool
17545:01:38:52.665: unkn Eth: Reconnecting in 7 seconds...
17545:01:38:59.677: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444
17545:01:39:02.945: unkn Eth: Connection attempt aborted
17545:01:39:02.945: unkn Eth: Reconnecting in 10 seconds...
17545:01:39:12.948: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444
17545:01:39:13.319: GPU2 Unable to submit share - pool disconnected
17545:01:39:15.222: main GPU1: 61C 24%, GPU2: 54C 24%, GPU3: 47C 24%, GPU4: 62C 27%, GPU5: 57C 24%, GPU6: 56C 24%
17545:01:39:16.233: unkn Eth: Connection attempt aborted
17545:01:39:16.233: unkn Eth: Reconnecting in 15 seconds...
17545:01:39:31.241: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444
17545:01:39:34.535: unkn Eth: Connection attempt aborted
17545:01:39:34.535: unkn Eth: Reconnecting in 20 seconds...
17545:01:39:43.396: main GPU1: 61C 24%, GPU2: 54C 24%, GPU3: 46C 24%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 56C 24%
17545:01:39:54.538: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444
17545:01:39:57.826: unkn Eth: Connection attempt aborted
17545:01:39:57.826: unkn Eth: Giving up after 3 retries, switching to next pool
17545:01:39:57.826: unkn Eth: Reconnecting in 7 seconds...
17545:01:40:04.830: unkn Eth: Connecting to ethash pool asia.ethash-hub.miningpoolhub.com:20535
17545:01:40:08.086: unkn Eth: Connection attempt aborted
17545:01:40:08.086: unkn Eth: Reconnecting in 10 seconds...
17545:01:40:11.417: main GPU1: 61C 24%, GPU2: 54C 24%, GPU3: 48C 0%, GPU4: 61C 27%, GPU5: 57C 24%, GPU6: 56C 24%
17545:01:40:15.389: unkn Quitting...
17545:01:40:17.370: unkn Quitting...
17545:01:40:17.821: wdog Stopping watchdog thread
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 14, 2018, 05:58:24 AM
 #92

  I found that sometimes the miner fall into a reconnection loop just like I pressed "r". It said "Unable to read pool response. Timeout" then keep reconnecting fail and reconnecting fail. My internet connection should be okay. Cry  Is that the timeout setting too low while my ping to the pool is too high at that moment?
  We have already answered and we are working on a fix for the next release (perhaps 2.4):
Sorry for this problem. We managed to reproduce it here thanks to the log you have send. It doesn't happen often but when it does it can be fairly annoying. Eventually the miner manages to connect but it may take a ten or more attempts. We are going to find the root cause and will introduce a fix (but probably not in version 2.3 as it is already being tested internally). In the meantime if the miner can't connect with "Connection attempt aborted" error after a few attempts, the best workaround it to close it (ignore the error on exit if you get one) and start it again.

Can you add please dev fee pool for pegascoin (PGC) ? https://bitcointalk.org/index.php?topic=2132259.0
Yes, it seems that there is working pool and a wallet, so we will try to add support for PGC in version 2.4.
hafizhasan
Jr. Member
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 14, 2018, 11:27:42 AM
 #93

hello
i started using ur miner its stable wit good shares..got arount 30mhs each with my 2 rx580 armor.but i got into 1 problem..i tried to increase the gpu tuning by pressing + , the hash rates dropped to 20mhs each.i tried to start miner and the rig..no solution..wht should do mow..can any1 help...
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 14, 2018, 12:25:17 PM
 #94

hello
i started using ur miner its stable wit good shares..got arount 30mhs each with my 2 rx580 armor.but i got into 1 problem..i tried to increase the gpu tuning by pressing + , the hash rates dropped to 20mhs each.i tried to start miner and the rig..no solution..wht should do mow..can any1 help...

    Sounds like the DAG size issue (and probably nothing to do with you trying to tune the GPU, or PhoenixMiner).

    If you are using the latest AMD drivers, do the following things:
    1. Open AMD Radeon Settings
    2. Click the first button in the top left corner ("Gaming"), then click "Global Settings", which will appear at the same corner
    3. In the "Global settings", find the setting "GPU Workload" and switch it to "Compute"
    4. Radeon Settings will restart and then the problem should go away

    Keep in mind that sometimes this setting changes by itself (for example if you remove or add a GPU), so if the hashrate consistently (i.e. not only for a moment) drops to 18-20 MH for 570/580, this is the most likely reason.
hafizhasan
Jr. Member
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 14, 2018, 12:39:50 PM
 #95

hello
i started using ur miner its stable wit good shares..got arount 30mhs each with my 2 rx580 armor.but i got into 1 problem..i tried to increase the gpu tuning by pressing + , the hash rates dropped to 20mhs each.i tried to start miner and the rig..no solution..wht should do mow..can any1 help...

    Sounds like the DAG size issue (and probably nothing to do with you trying to tune the GPU, or PhoenixMiner).

    If you are using the latest AMD drivers, do the following things:
    1. Open AMD Radeon Settings
    2. Click the first button in the top left corner ("Gaming"), then click "Global Settings", which will appear at the same corner
    3. In the "Global settings", find the setting "GPU Workload" and switch it to "Compute"
    4. Radeon Settings will restart and then the problem should go away

    Keep in mind that sometimes this setting changes by itself (for example if you remove or add a GPU), so if the hashrate consistently (i.e. not only for a moment) drops to 18-20 MH for 570/580, this is the most likely reason.

thnk u..i had to disable both gpu's thn reinstall the drivers....and now it s fine...
regarding compute , its default enabled in the latest amd blockchain 23aug drivers..
restless
Legendary
*
Offline Offline

Activity: 1094
Merit: 1000


View Profile
January 14, 2018, 01:11:25 PM
 #96

Making a test - so far it does seem a little bit faster than Claymore
hafizhasan
Jr. Member
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 14, 2018, 02:25:58 PM
 #97

can any1 explain gpu tuning parameter and wht s better ti get good hashrate..
darkmusika
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
January 14, 2018, 02:54:32 PM
 #98

Code:
17545:22:00:54.422: main GPUs: 1: 32.105 MH/s (48) 2: 32.089 MH/s (33/10) 3: 31.884 MH/s (42) 4: 32.098 MH/s (45/6) 5: 32.072 MH/s (50) 6: 31.901 MH/s (33/5) 7: 32.280 MH/s (43) 8: 32.258 MH/s (61) 9: 32.289 MH/s (36) 10: 32.083 MH/s (45) 11: 32.097 MH/s (49) 12: 32.090 MH/s (35)
17545:22:00:59.587: main Eth speed: 369.621 MH/s, shares: 520/0/21, time: 0:49
17545:22:00:59.587: main GPUs: 1: 31.443 MH/s (48) 2: 17.736 MH/s (33/10) 3: 31.884 MH/s (42) 4: 32.119 MH/s (45/6) 5: 32.114 MH/s (50) 6: 31.917 MH/s (33/5) 7: 31.496 MH/s (43) 8: 32.282 MH/s (61) 9: 32.316 MH/s (36) 10: 32.115 MH/s (45) 11: 32.087 MH/s (49) 12: 32.111 MH/s (35)
17545:22:01:00.134: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","worker":"RIG-01","params":["0x16dfe898","0xa09c37897fd827e44441da759feef53d7ddbb91585c57694e731e5cfece31579"]}
17545:22:01:00.229: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17545:22:01:04.732: main Eth speed: 368.898 MH/s, shares: 520/0/21, time: 0:49
17545:22:01:04.732: main GPUs: 1: 32.112 MH/s (48) 2: 16.817 MH/s (33/10) 3: 31.916 MH/s (42) 4: 32.097 MH/s (45/6) 5: 32.116 MH/s (50) 6: 31.920 MH/s (33/5) 7: 31.248 MH/s (43) 8: 32.287 MH/s (61) 9: 32.314 MH/s (36) 10: 31.859 MH/s (45) 11: 32.102 MH/s (49) 12: 32.109 MH/s (35)
17545:22:01:06.085: GPU9 Eth: GPU9: ETH share found

First of all thank you for sharing your work
For my concern, if you noticed my GPU2 is usually running at 31-32MH/s, it seems that in the middle of the mining it crashed and was able to mine at 16-17 MH/s and watchdog wasn't able to detect it
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 14, 2018, 04:13:17 PM
 #99

First of all thank you for sharing your work
For my concern, if you noticed my GPU2 is usually running at 31-32MH/s, it seems that in the middle of the mining it crashed and was able to mine at 16-17 MH/s and watchdog wasn't able to detect it

Thank you for the log. This is really unusual as in virtually all cases we have seen the GPU thread either crashes or freezes entirely. The watchdog checks for this but if there is any regular progress in the GPU thread, it "thinks" that the GPU is OK and doesn't restart the miner. In any case, there is something wrong with GPU2 (maybe the clocks are too high?) as it had 10 incorrect shares and 33 correct ones: almost one quarter of its shares are incorrect. Even if it is showing 31-32 MH/s hashrate, its effective hashrate is at most 80% of this - 25-26 MH/s. Generally, anything above 1-2% incorrect shares is a sign to dial back the overclock a little on that specific GPU to avoid losing too much of the effective hashrate.

We could add a command line option that specifies the minimal "normal" speed but it would be of limited usefulness if the rig has vastly different GPUs, or if the ambient temperature slowly rises and the GPUs start to throttle to avoid overheating.

can any1 explain gpu tuning parameter and wht s better ti get good hashrate..

Basically, it "rearranges" the memory accesses of the OpenCL ethash search kernel a little in attempt to hide part of the memory access latency. If the GPU memory had zero latency, an RX580 would be making about 33 MH/s with standard 2000 MHz memory clocks. The default value (15) is usually the best but in some cases (extreme overclocks, aggressive BIOS mods to lower the memory latency, etc.), you can achieve slightly better hashrate with different GT parameter. Please note that after changing the parameter you have to wait a minute or so for the hashrate to settle and see if it is better or worse than before.
Branko
Full Member
***
Offline Offline

Activity: 434
Merit: 177


Join FlipNpik Telegram : t.me/flipnpikico


View Profile
January 14, 2018, 06:47:16 PM
 #100

thnk u..i had to disable both gpu's thn reinstall the drivers....and now it s fine...
regarding compute , its default enabled in the latest amd blockchain 23aug drivers..


Why not give new drivers a try instead using that ancient one?

Pages: « 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 ... 121 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!