PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[preda]

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

need more feedback brothers for trust to this miner

[1714140943]

1714140943

[1714140943]

1714140943

[1714140943]

1714140943

[1714140943]

1714140943

[1714140943]

1714140943

[Njeroe]

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]

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

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]

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

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]

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]

Pls add support for mining VIC without DAG switch on devfee. Thank you.

[yyyam2]

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]

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

[PhoenixMiner]

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.

  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.

[dhmctrader]

So far so good.

A little higher hash rate AND average effective hash rate reported by the pool higher than I ever saw with Claymore.

Using all default params.

Cards running slightly cooler.

Power at the wall about the same but more stable than I had with Claymore. Phoenix stable at the low end of Claymore range.

Good job. I'll be switching for good if no issues show up. Competition is a good thing.

[Yellow_donkey]

Love Phoenix Miner, really is fast.  I just got version 2.4 as well.  But I having one issue, hoping someone can help me out.  I can mine to any pool I wnat to all day long but when I try to mine to my geth node on my mineer I get the following:

phoenixminer.exe -pool 10.205.1.85:8545 -worker Rig1 -mi 12

https://ibb.co/daOVZG 

Before, using PM I solo mined using Claymore with no problems using:

EthDcrMiner64.exe -epool http://10.205.1.85:8545 -eworker Rig1 -allpools 1

It connections to geth and then creates the DAG and goes about its merry business of making me money.

What am I doing wrong with Phoenix Miner, I know if has to be something simple I am missing here?  Thank you.

[Branko]

Told you, SIA GPU mining is dead already

[PhoenixMiner]

Love Phoenix Miner, really is fast.  I just got version 2.4 as well.  But I having one issue, hoping someone can help me out.  I can mine to any pool I wnat to all day long but when I try to mine to my geth node on my mineer I get the following:
...
What am I doing wrong with Phoenix Miner, I know if has to be something simple I am missing here?  Thank you.

 You are not doing anything wrong, it's just that we don't support solo mining yet. There is noting really hard to prevent us from implementing it but in 99% of the cases it's not very practical with the difficulty of most coins. However if there is enough interest (or at least after we implement more urgent features like control over clocks and voltages, and dual mining), we are going to implement it.

  

Told you, SIA GPU mining is dead already

  Yes, you were spot on.   It was mainly wishful thinking on our part to assume that it would take more time before ASICs made siacoin GPU mining obsolete. Still we are too far into implementing dual mining with decred, so we are going to release it anyway whenever it is ready. Even if it is completely useless by then, at least we will have some experience with implementing it that would hopefully translate to some other coin that can be dual-mined with ethash profitably.

[nitrobg]

Minor issue - when I'm scrolling up the window by holding the scrollbar button, the miner freezes and doesn't resume automatically when I lift the button.

[Coinerrr]

Hi

Really liking 2.4, about 5 MHs faster then the competition for me


do you have plans to make a CryptoNight (ETN/XMR) Miner too? that would be great!

[ph0enix49]

Would be nice to have a version for linux too, I bet a lot of people run their farms on linux

[nhabaotre]

Do i need to run MSI After burner to OC ?

[token_coin_guy]

Told you, SIA GPU mining is dead already

PASC is still useful (I think), it does seem to have slowed down a lot lately though.

[d2bg]

Are there any plans to implement temperature/fan control, similar to Claymore?  I like the logging and get slightly better hashrates, the ability to specify a max gpu temp is really all that's keeping me from switching over.

[polymer_city2]

Very pleased so far. Around 3mhs faster on each rig.