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

[PhoenixMiner]

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

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.

[1714180736]

1714180736

[1714180736]

1714180736

[PhoenixMiner]

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:
  (MEGA links are no longer active)

  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.

[yyyam2]

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]

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/

[yyyam2]

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

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

[PhoenixMiner]

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.

[restless]

Making a test - so far it does seem a little bit faster than Claymore

[darkmusika]

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]

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]

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?

[darkmusika]

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.

Thank you for your fast reply,
Yes I'm having trouble with that Gpu since when I started mining, Thanks for your advice, I will try to clock it down..

It will be very helpful if to add a command like -minspeed in claymore, if it is also possible to set it per GPUs, instead of the total hashrate..
Ex:
If one of the GPUs hash rate didn't exceed 20MH/s for 5mins it will have an option to restart the miner or execute the reboot.bat

Thanks again! And more power!

[Branko]

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?

i read tht blockchain drivers gives some improved hashrate than newest adrenaline drivers..can any1 confirm

Only for noobs that don't switch workload from graphics to compute

[jendabenda]

Thanks for great miner. I got nearly 100MH more on my setup. (nearly 0,6 per RX570).

Are you close to solving pool disconnect issue? Is there any workaround? Happened on one rig after about 24h,

[4ward]

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files with the notable exception of the dual mining feature (yet).

  -proto <n> Selects the kind of stratum protocol for the ethash pool:
     1: miner-proxy stratum spec (e.g. coinotron)
     2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
     3: qtminer (e.g. ethpool)
     4: EthereumStratum/1.0.0 (e.g. nicehash)

  -gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma)

If you are aiming at simplicity with switching from Claymore, can these option values be aligned with Claymore's?

-esm   Ethereum Stratum mode. 0 - eth-proxy mode (for example, dwarpool.com), 1 - qtminer mode (for example, ethpool.org),
   2 - miner-proxy mode (for example, coinotron.com), 3 - nicehash mode. 0 is default.

-di    GPU indexes, default is all available GPUs. For example, if you have four GPUs "-di 02" will enable only first and third GPUs (#0 and #2).
   You can also turn on/off cards in runtime with "0"..."9" keys and check current statistics with "s" key.
   For systems with more than 10 GPUs: use letters to specify indexes more than 9, for example, "a" means index 10, "b" means index 11, etc; also "a", "b", and "c" keys allow you to turn on/off GPU #10, #11 and #12 in runtime.

[mshordja]

any chance to see here dual mine option? if yes any deadline?
Thanks

[PhoenixMiner]

Thanks for great miner. I got nearly 100MH more on my setup. (nearly 0,6 per RX570).

Are you close to solving pool disconnect issue? Is there any workaround? Happened on one rig after about 24h,

If you mean the "Connection attempt aborted" error messages when the miner is trying to reconnect, we are testing several workarounds but as the problem occurs randomly, it would take a few more days before we are sure that it is solved completely. The fix will be included for sure in version 2.4 which is scheduled for release in five days.

If you are aiming at simplicity with switching from Claymore, can these option values be aligned with Claymore's?

-esm   Ethereum Stratum mode. 0 - eth-proxy mode (for example, dwarpool.com), 1 - qtminer mode (for example, ethpool.org),
   2 - miner-proxy mode (for example, coinotron.com), 3 - nicehash mode. 0 is default.

-di    GPU indexes, default is all available GPUs. For example, if you have four GPUs "-di 02" will enable only first and third GPUs (#0 and #2).
   You can also turn on/off cards in runtime with "0"..."9" keys and check current statistics with "s" key.
   For systems with more than 10 GPUs: use letters to specify indexes more than 9, for example, "a" means index 10, "b" means index 11, etc; also "a", "b", and "c" keys allow you to turn on/off GPU #10, #11 and #12 in runtime.

You can use the Claymore options directly, e.g. just add

-esm 3 -di 02

   to the PhoenixMiner command line (or in the config.txt file) and they should work exactly as in Clyamore. In this example the stratum protocol would be nicehash and only the first and the third GPU will be used.

any chance to see here dual mine option? if yes any deadline?
Thanks

Yes, definitely. We have very raw early version in development for the Decred algorithm. If everything goes well, it can be released for beta testing in about four weeks. As it seems that the dual mining is still in high demand, we have shifted resources from the Linux version to dual mining support, so the Linux version will be delayed for after the dual mining is implemented.

[4ward]

You can use the Claymore options directly, e.g. just add

-esm 3 -di 02

   to the PhoenixMiner command line (or in the config.txt file) and they should work exactly as in Clyamore. In this example the stratum protocol would be nicehash and only the first and the third GPU will be used.

Perfect, thank you

[jendabenda]

Thanks for great miner. I got nearly 100MH more on my setup. (nearly 0,6 per RX570).

Are you close to solving pool disconnect issue? Is there any workaround? Happened on one rig after about 24h,

If you mean the "Connection attempt aborted" error messages when the miner is trying to reconnect, we are testing several workarounds but as the problem occurs randomly, it would take a few more days before we are sure that it is solved completely. The fix will be included for sure in version 2.4 which is scheduled for release in five days.

Thanks, great news. I realy like your miner. If you have more rigs problem is more likely to occur...

[shimpa]

a pleasant surprise I must say.

besides lower fee, AMD cards actually hash 1Mh/s more, didn't see any increase on nVidia

All things considered, 1,5%-2% better mining performance on AMD systems.

thanks a lot!