Bitcoin Forum
August 18, 2018, 08:48:16 AM *
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 56 57 58 59 ... 121 »
  Print  
Author Topic: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)  (Read 81681 times)
nimy
Jr. Member
*
Offline Offline

Activity: 50
Merit: 0


View Profile
January 23, 2018, 12:42:04 PM
 #161

i try 2.4. sometime reported hashes on the pool is not registered. Need to restart miner.. Any solution for this?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534582096
Hero Member
*
Offline Offline

Posts: 1534582096

View Profile Personal Message (Offline)

Ignore
1534582096
Reply with quote  #2

1534582096
Report to moderator
1534582096
Hero Member
*
Offline Offline

Posts: 1534582096

View Profile Personal Message (Offline)

Ignore
1534582096
Reply with quote  #2

1534582096
Report to moderator
1534582096
Hero Member
*
Offline Offline

Posts: 1534582096

View Profile Personal Message (Offline)

Ignore
1534582096
Reply with quote  #2

1534582096
Report to moderator
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 23, 2018, 01:24:23 PM
 #162

i swapped about 30 machines to this for a test yesterday and while it seems to be decent there are some quirks. 2 just crash of the 30 on this program but run perfect on claymore.

Mainly and really important for anyone with more than a couple machines is the use of claymores manager.  Yes it shows up but I logged in this morning to see and they showed all up but 2 were in fact down but still showing up.  When I logged into the troubled machines they were trying to connect to pools.  As soon as I shut it off and restarted the miner program NOT the machine it sparked right up.  The problem is that it was reporting to the miner manager that all was good with even the hashrate that was non-existant!  Normally a machine up and not hashing reports 0.00  these were reporting normal hash.

I guess question for dev is, are you going to come up with your own miner manager to fix this or at least fix it to where claymores works correctly in your product?
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 23, 2018, 04:19:52 PM
 #163

Yep this is a bad problem.... it just sits there trying to connect to the 2 pools in config and the other 2 in epools and never connects.  If I shut PM down and just restart the app it connects and works fine.  FIX THIS it's a bad problem and with that said back to claymore I go until I can get a confirmation this is repaired.
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 23, 2018, 04:41:09 PM
 #164

I tested the phoenixminer 2.4 and its showing gpu2 fan error and gpu5? any fix on this?
 Are you using Adrenalin driver 17.12.x? If so, please upgrade to the newest driver, which should fix the problem.

i try 2.4. sometime reported hashes on the pool is not registered. Need to restart miner.. Any solution for this?
 Most probably the problem is with the pool - we have seen such problems some pools, which sometimes do not show the reported hasrate (but accepts shares and shows the effective hashrate normally). If the problem persists, please let us know which pool you are using to try and reproduce the problem.

Yep this is a bad problem.... it just sits there trying to connect to the 2 pools in config and the other 2 in epools and never connects.  If I shut PM down and just restart the app it connects and works fine.  FIX THIS it's a bad problem and with that said back to claymore I go until I can get a confirmation this is repaired.
 Thank you for trying our miner. The first problem (with the "connection attempt aborted" errors) is already fixed in PhoenixMiner 2.4, which is now being officially released. However we will also fix the continuing mining after the connection is being lost for any reason. In such cases the mining will stop after a few minutes and this will be properly reported to the remote manager. We are also adding some DAG switching stability improvements in version 2.5 and we will net you know when it is ready.


PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 23, 2018, 04:54:45 PM
 #165

PhoenixMiner 2.4 is officially released. There are no changes from the release candidate that was released a few days ago so if you are already using 2.4, no need to download and install again.

We now are working on 2.5, which should include a few fixes for the DAG allocation and generation instabilities, and a fix for continuing mining when the miner is unable to connect for more than a few minutes. A per-GPU minimal speed will also be implemented, allowing finer control over GPUs slowing down for some reason.
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 23, 2018, 06:54:10 PM
 #166

ok loading on 10 units to test =)
ultiman2
Jr. Member
*
Offline Offline

Activity: 98
Merit: 0


View Profile
January 24, 2018, 12:06:44 AM
 #167

trying version 2.4

so far so good

i just have a question

what those two options change?
-mi  when i use the default 10 i have a constant mhs, when i put 12 i have some up and down so what better?
-gt  seem to not change a lot
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 24, 2018, 01:38:43 AM
 #168

One of the units crashed but did not report again to claymore manager and hash and everything looked correct.  It was just scrolling dev fee disconnected and stopped or something like that.  over and over and over again

Closed it and relaunched and it started to work as normal.

clip of log

17554:19:35:24.587: main DevFee: Disconnected and stopped
17554:19:35:24.790: main DevFee: Disconnected and stopped
17554:19:35:24.937: GPU4 Eth: Incorrect ETH share from GPU4
17554:19:35:24.993: main DevFee: Disconnected and stopped
17554:19:35:25.196: main DevFee: Disconnected and stopped
17554:19:35:25.399: main DevFee: Disconnected and stopped
17554:19:35:25.602: main DevFee: Disconnected and stopped
17554:19:35:25.809: main DevFee: Disconnected and stopped
17554:19:35:26.024: main DevFee: Disconnected and stopped
17554:19:35:26.228: main DevFee: Disconnected and stopped
17554:19:35:26.432: main Eth speed: 200.521 MH/s, shares: 851/1/299, time: 6:30
17554:19:35:26.432: main GPUs: 1: 28.677 MH/s (137/40) 2: 28.679 MH/s (118/40) 3: 28.404 MH/s (121/35) 4: 28.745 MH/s (105/52) 5: 28.678 MH/s (138/39) 6: 28.664 MH/s (113/40) 7: 28.674 MH/s (120/53)
17554:19:35:26.432: main DevFee: Disconnected and stopped
17554:19:35:26.635: main DevFee: Disconnected and stopped
17554:19:35:26.839: main DevFee: Disconnected and stopped
17554:19:35:27.042: main DevFee: Disconnected and stopped
17554:19:35:27.245: main DevFee: Disconnected and stopped
17554:19:35:27.448: main DevFee: Disconnected and stopped
17554:19:35:27.651: main DevFee: Disconnected and stopped
17554:19:35:27.855: main DevFee: Disconnected and stopped
17554:19:35:28.059: main DevFee: Disconnected and stopped
17554:19:35:28.261: main DevFee: Disconnected and stopped
17554:19:35:28.465: main DevFee: Disconnected and stopped
17554:19:35:28.668: main DevFee: Disconnected and stopped
17554:19:35:28.871: main DevFee: Disconnected and stopped
nitrobg
Member
**
Offline Offline

Activity: 376
Merit: 16


View Profile
January 24, 2018, 07:42:17 AM
 #169

The miner didn't switch to the backup pool after one of ethermine's servers dropped. Needed a manual restart:

17555:00:58:07.986: main GPUs: 1: 29.930 MH/s (902/1) 2: 28.957 MH/s (845) 3: 28.905 MH/s (872) 4: 30.118 MH/s (841) 5: 28.908 MH/s (919) 6: 28.902 MH/s (925/1)
17555:00:58:09.584: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17555:00:58:09.593: eths Eth: Unable to read pool response: An existing connection was forcibly closed by the remote host
17555:00:58:09.593: eths Eth: Reconnecting in 10 seconds...
17555:00:58:15.883: main GPU1: 66C 32%, GPU2: 67C 18%, GPU3: 66C 33%, GPU4: 66C 32%, GPU5: 61C 17%, GPU6: 59C 17%
17555:00:58:17.866: GPU4 Unable to submit share - pool disconnected
17555:00:58:19.596: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444
17555:00:58:19.622: eths Eth: Connected to ethash pool eu1.ethermine.org:4444
17555:00:58:19.622: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"pmethash","params":["0x40EDA1a5924f22CB5C267cbc13525daf46635672.RX2"]}

17555:00:58:25.334: GPU6 Unable to submit share - pool disconnected
17555:00:58:44.057: main GPU1: 66C 32%, GPU2: 66C 19%, GPU3: 66C 34%, GPU4: 66C 32%, GPU5: 61C 17%, GPU6: 59C 17%
17555:00:59:12.123: main GPU1: 66C 32%, GPU2: 66C 18%, GPU3: 66C 33%, GPU4: 66C 33%, GPU5: 61C 17%, GPU6: 59C 17%
17555:00:59:40.302: main GPU1: 66C 33%, GPU2: 66C 18%, GPU3: 66C 34%, GPU4: 66C 32%, GPU5: 62C 17%, GPU6: 59C 17%
17555:00:59:45.489: GPU1 Unable to submit share - pool disconnected
17555:01:00:08.372: main GPU1: 66C 32%, GPU2: 66C 18%, GPU3: 66C 34%, GPU4: 66C 32%, GPU5: 62C 17%, GPU6: 59C 17%
17555:01:00:14.301: GPU1 Unable to submit share - pool disconnected
17555:01:00:17.404: GPU2 Unable to submit share - pool disconnected
17555:01:00:30.295: GPU5 Unable to submit share - pool disconnected
17555:01:00:35.082: GPU1 Unable to submit share - pool disconnected



About the dual mining - IMO it is no longer worth it because there are ASICs for those coins. If you manage to include another algorithm - I'm sure that you'll get even more users.
rockk
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 24, 2018, 07:47:16 AM
 #170

today i got message unable to submit share to pool, but my other rig was connected just fine phoenix 2.4 as always. using ethminer eu.1 pool port 14444 , no failovers.

mitrobg -- maybe happend the same time with u and me also? weird.

yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 24, 2018, 08:20:21 AM
 #171

Tried 2.4 for running 25 hrs straight without any interruption and restart. Good job! Now i can switch to your miner.  Cool
preda
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250



View Profile
January 24, 2018, 08:58:33 AM
 #172

Tried 2.4 for running 25 hrs straight without any interruption and restart. Good job! Now i can switch to your miner.  Cool


need more feedback brothers for trust to this miner

                 ░▒▓▓▓▓▓▓▓▓▓▒▒░
           ░▒█████████████████████▒░
         ▓███████████████████████████▓░
      ░███████████████▓░▒███████████████░
     ▓██████████▓▓▒░        ▒▒▓▓██████████
   ░███▓                               ▒███▒
  ░████               ▒▒▒               ████▒
 ░█████░           ░███████░            █████▒
 ██████░          ░██      ██▒          ██████
░██████░          ██       ██           ██████▒
▓██████           ██░ ░   ░██           ███████
▓██████         ████████████████        ███████
▓██████        █████████████████        ███████
░██████▒       ███████████████       ░██████▓
 ███████       █████████████████       ▓██████
 ░███████       ████████████████      ▓██████▒
  ▒███████▒       ░ ░     ░ ░       ░███████▒
   ░████████▒                     ▒████████▒
     ▓████████▓░               ░▓█████████
      ░██████████▓░          ▓██████████░
         ▓██████████▒     ▒██████████▓░
           ░▒██████████▒▓█████████▓░
                 ░▒▓▓▓▓▓▓▓▓▓▒▒░
Njeroe
Jr. Member
*
Offline Offline

Activity: 47
Merit: 0


View Profile
January 24, 2018, 11:16:29 AM
 #173

I've tried the 2.4 on a 11 GPU rig (9xRX580 4Gb 1xRX570 4Gb 1xRX480 8Gb), I got steady 325.xxx Mh/s, it's more consistent than Claymore, with Claymore I get 290-322...
Waiting for the dual mining version...
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 24, 2018, 11:55:50 AM
 #174

Tried 2.4 for running 25 hrs straight without any interruption and restart. Good job! Now i can switch to your miner.  Cool


need more feedback brothers for trust to this miner
u are paying around 10% for claymore, make no mistake  is not 1%.

Don't spread BS man.  Claymore makes a great product no need to lie about his stuff.  That's coming from a guy using both.
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 24, 2018, 11:57:33 AM
 #175

Tried 2.4 for running 25 hrs straight without any interruption and restart. Good job! Now i can switch to your miner.  Cool


need more feedback brothers for trust to this miner

Using it on 10 machines now.  I used 2.3 for about 3 hours and it was acting funky but 2.4 fixed some connection issues.  I did have that devfee problem on 2.4 on 1 out of 10 machines.  Hopefully that gets fixed asap.
dagarair
Sr. Member
****
Offline Offline

Activity: 629
Merit: 334


View Profile
January 24, 2018, 12:57:40 PM
 #176

ok you are right.  I also have some Ocean front property in Arizona if you want I'll make you a great deal.


At the end it don't really matter, believe what you want.  I'm glad you are happy here as I am testing it to deploy to my machines.
zeii
Jr. Member
*
Offline Offline

Activity: 41
Merit: 0


View Profile
January 24, 2018, 01:11:46 PM
 #177

Pls add support for mining VIC without DAG switch on devfee. Thank you. Grin
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 24, 2018, 02:45:03 PM
 #178

Hi,

   I notice there are some error "eth share timeout in xxxxx s". It happen once a while (about 3-4 hrs). I guess it is some kind of warning. What is it actually? Thanks!

Code:
17555:22:38:09.724: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0509a43d412cd720f9922cb4f472eae02344bebc3e5faf6e54cba5b93675703e","0x51e74ac038c9e3e66658ef25c159102238ecfd6ec09db5abc675fa9207530dad","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4bc0e1"]}
17555:22:38:09.765: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0509a43d412cd720f9922cb4f472eae02344bebc3e5faf6e54cba5b93675703e","0x51e74ac038c9e3e66658ef25c159102238ecfd6ec09db5abc675fa9207530dad","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4bc0e1"]}
17555:22:38:09.765: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17555:22:38:12.857: main Eth speed: 360.270 MH/s, shares: 10181/11/2, time: 32:04
17555:22:38:12.857: main GPUs: 1: 29.984 MH/s (857) 2: 29.979 MH/s (823) 3: 30.121 MH/s (897) 4: 30.127 MH/s (874) 5: 29.982 MH/s (860/1) 6: 29.950 MH/s (877) 7: 30.070 MH/s (820) 8: 29.989 MH/s (847) 9: 29.958 MH/s (860) 10: 29.988 MH/s (859) 11: 30.131 MH/s (792) 12: 29.992 MH/s (826/1)
17555:22:38:13.087: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2d56b2edf89996789e389997f7eb0016d174e619087c9367857544a4df52cdbf","0x51e74ac038c9e3e66658ef25c159102238ecfd6ec09db5abc675fa9207530dad","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4bc0e2"]}
17555:22:38:13.088: eths Eth: New job #2d56b2ed from asia1.ethermine.org:14444; diff: 4000MH
17555:22:38:17.945: main Eth speed: 361.114 MH/s, shares: 10181/11/2, time: 32:04
17555:22:38:17.945: main GPUs: 1: 30.106 MH/s (857) 2: 30.121 MH/s (823) 3: 30.124 MH/s (897) 4: 30.120 MH/s (874) 5: 30.107 MH/s (860/1) 6: 30.128 MH/s (877) 7: 30.137 MH/s (820) 8: 30.130 MH/s (847) 9: 30.102 MH/s (860) 10: 30.132 MH/s (859) 11: 29.797 MH/s (792) 12: 30.110 MH/s (826/1)
17555:22:38:23.030: main Eth speed: 361.334 MH/s, shares: 10181/11/2, time: 32:04
17555:22:38:23.030: main GPUs: 1: 30.129 MH/s (857) 2: 30.132 MH/s (823) 3: 30.126 MH/s (897) 4: 29.969 MH/s (874) 5: 30.113 MH/s (860/1) 6: 30.120 MH/s (877) 7: 30.130 MH/s (820) 8: 30.128 MH/s (847) 9: 30.113 MH/s (860) 10: 30.120 MH/s (859) 11: 30.134 MH/s (792) 12: 30.119 MH/s (826/1)
17555:22:38:28.116: main Eth speed: 360.618 MH/s, shares: 10181/11/2, time: 32:04
17555:22:38:28.116: main GPUs: 1: 29.982 MH/s (857) 2: 30.137 MH/s (823) 3: 29.980 MH/s (897) 4: 30.138 MH/s (874) 5: 29.978 MH/s (860/1) 6: 30.112 MH/s (877) 7: 29.986 MH/s (820) 8: 29.992 MH/s (847) 9: 30.122 MH/s (860) 10: 30.112 MH/s (859) 11: 30.112 MH/s (792) 12: 29.967 MH/s (826/1)
17555:22:38:28.389: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa973911f62c4996547da69982b76cc79279e287b2d4e15d0c4f19363fbc9101d","0x51e74ac038c9e3e66658ef25c159102238ecfd6ec09db5abc675fa9207530dad","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4bc0e3"]}
17555:22:38:28.389: eths Eth: New job #a973911f from asia1.ethermine.org:14444; diff: 4000MH
17555:22:38:29.681: eths Eth: Share timeout in 600337 s
17555:22:38:29.681: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x15845210","0x9f7a549c18560ea9ed989475c94cd598163323ac1d21047adc0844f685cc791c"]}

17555:22:38:29.724: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17555:22:38:33.195: main Eth speed: 360.488 MH/s, shares: 10181/12/2, time: 32:04
17555:22:38:33.195: main GPUs: 1: 30.102 MH/s (857) 2: 29.842 MH/s (823) 3: 30.065 MH/s (897) 4: 30.113 MH/s (874) 5: 30.069 MH/s (860/1) 6: 29.959 MH/s (878) 7: 30.103 MH/s (820) 8: 30.113 MH/s (847) 9: 29.959 MH/s (860) 10: 29.957 MH/s (859) 11: 30.108 MH/s (792) 12: 30.097 MH/s (826/1)
17555:22:38:33.838: main GPU1: 64C 26%, GPU2: 60C 24%, GPU3: 48C 24%, GPU4: 64C 25%, GPU5: 62C 24%, GPU6: 64C 28%, GPU7: 61C 24%, GPU8: 59C 24%, GPU9: 64C 26%, GPU10: 64C 26%, GPU11: 61C 24%, GPU12: 60C 24%
ultiman2
Jr. Member
*
Offline Offline

Activity: 98
Merit: 0


View Profile
January 25, 2018, 02:16:05 AM
 #179

more than 24 hours with version 2.4, everything stable and a little bit more mhs than claymore. i really like it
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
January 25, 2018, 06:38:26 AM
 #180

what those two options change?
-mi  when i use the default 10 i have a constant mhs, when i put 12 i have some up and down so what better?
-gt  seem to not change a lot
 The first option (-mi) changes the size of each "chuck" of work that is send to the GPU. The lower numbers mean generally lower and more unstable hashrate but you will be able to use your GPU for normal work without stuttering of the display, which is useful if the GPU is used for anything else than mining. Values above the default 10 aren't recommended because while they can marginally increase the hashrate, the number of stale shares will also increase and some GPUs may become unstable.
  The second one (-gt), which can also be changed with + and - keys when the miner is running, is a way to fine tune the GPU for maximum hashrate. Because the memory timings of each GPU can be a little bit different (especially after BIOS mods and overclocoking/underclocking), the default value of 15 may not be the best (although we have found that it is the best for the 90% of the GPUs).
  Please note that both -mi and -gt can be specified per-GPU, for example -mi 0,10,10,10,10,10 if you want only the first GPU of six GPU rig to mine with low intensity while using the PC and the display is connected to the first GPU.

One of the units crashed but did not report again to claymore manager and hash and everything looked correct.  It was just scrolling dev fee disconnected and stopped or something like that.  over and over and over again

Closed it and relaunched and it started to work as normal.
  We have implemented a 180 second timer in version 2.5 that will stop the mining and report 0 hashrate to the manager in cases of lost connection that can't be restored. But the devfee disconnection issue is something new and will be fixed thanks to your report. Most probably the connection was lost at some short time period while the devfee was ending and some kind of race condition caused the loop.

The miner didn't switch to the backup pool after one of ethermine's servers dropped. Needed a manual restart:
today i got message unable to submit share to pool, but my other rig was connected just fine phoenix 2.4 as always. using ethminer eu.1 pool port 14444 , no failovers.

mitrobg -- maybe happend the same time with u and me also? weird.
  We had the same problem at exactly the same time with eu1.ehtermine.org but our test servers reconnected successfully. Thank you for the log - from it seems that connection to the pool was restored but it never replied to the authorization request from PhoenixMiner and it didn't close the socket, so the miner was left waiting forever for the authorization from the pool. We will include a code to detect such weird pool connection issues in version 2.5.

Pls add support for mining VIC without DAG switch on devfee. Thank you. Grin
  We will look into it but it would probably have to wait until 2.6 as the stability improvements and fixes are with higher priority.

  I notice there are some error "eth share timeout in xxxxx s". It happen once a while (about 3-4 hrs). I guess it is some kind of warning. What is it actually? Thanks!
  After finding a share, the miner waits for a confirmation from the pool if it was accepted or rejected. Only after this confirmation, the share is included in the effective hashrate calculations and other statistics. If there is no confirmation after some (fairly long) time, the miner "writes off" the share as rejected. This message notifies you that a share that was found a few hours ago never received accept or reject response from the pool and was therefore considered rejected in the stats of the miner. There is no reason to worry about these messages if they are infrequent. If the happen too often, it means that the pool is overloaded or has same issues and doesn't respond properly to the found shares.


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 56 57 58 59 ... 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!