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

[twotwosix]

What is the best driver for ethereum? Im using 18.6.1

[VasilyS]

Latest version is working good, I finally launched it on 12 GPU rig. But unfortunately, there is no fan control on 19.1.1 AMD drivers. As I see, the same problem is with Claymore. The problem is in drivers, 19.1.1 AMD drivers are worse than 18.5.1.

[Digital_Seytan]

is there a way to disable the ssl 5555, delivers far too many problems often crashes windows 10

[khafan11]

   (also to all miners experiencing problems with PhoenixMiner 3.5 and below versions when trying to create the DAG):

   The versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. ETC passed epoch 235 a few weeks ago, and recently ETH also passed DAG epoch 235 and is now on 236. The unfortunate result is that the old version(s) of PhoenixMiner won't be able to create DAG or mine ETH or ETC any more - you must upgrade to PhoenixMiner 4.x.
   We have printed this warning here during the release of PhoenixMiner 4.0 but admittedly we could have done much better job with making it visible. We will pin this message in the first post too.

After trying I also found 4.0b version does work now although it wasn’t working well before additionally it runs my rtx2070s hash a bit slower than versions 3.5 did

   We are working on RTX20x0 optimizations but they won't be ready until the next release.

i use Adrenalin 2019 Edition 18.12.2 and rx580 8gb but in this new 4.X ver i can't use -tt and -tmax and everything about fan control  is not working
in ver  3.5 i set this and worked perfectly
-tt 47
-tmax 52
-fanmin 10
-fanmax 55

but now i use the same commend but when gpu go to 59 degree  fan start on 24% and after it's cooling they be shutdown and again this Repeat 59start ......... 

[deforester]

Noticed the same thing with the latest version and some RX580 under Linux.

Had -tt set to 68 and one GPU kept creeping up way past 80 degrees and the fan was idling at 23%.

[cadj92]

Sadly 4.1c does not support 19.1.1, as it gives the Unknown OpenCL version error and suffers a hashrate loss because of it.
-clkernel 3 mode does not even work with it. ( clSetKernelArg (-49) )

I have 19.1.1 installed and latest version of miner works normal. RX 580 8 Gb Windows 10.

That`s strange... Well, I guess I can go back to 18.12.3 until we get a fix.

2019.01.19:21:21:33.279: main Phoenix Miner 4.1c Windows/msvc - Release build
2019.01.19:21:21:33.279: main Cmd line: -pool @@@
2019.01.19:21:21:33.279: main No CUDA driver found
2019.01.19:21:21:35.924: main OpenCL driver version: 19.1.1
2019.01.19:21:21:35.924: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.19:21:21:35.924: main OpenCL platform: OpenCL 2.0 AMD-APP (2348.3)
2019.01.19:21:21:35.924: main Ignoring old OpenCL driver(s), using driver version 19.1.1
2019.01.19:21:21:35.924: main Available GPUs for mining:
2019.01.19:21:21:35.924: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2019.01.19:21:21:36.002: main ADL library initialized

[evlo]

I see totally minuscule reported hasharete improvement with "3" kernels, wonder if there would be any real hashrate improvement.

[PhoenixMiner]

What is the best driver for ethereum? Im using 18.6.1

   In terms of hashrate there is no big difference. We found that 18.5.1 are the best as far as stability goes but YMMV.

i use Adrenalin 2019 Edition 18.12.2 and rx580 8gb but in this new 4.X ver i can't use -tt and -tmax and everything about fan control  is not working
in ver  3.5 i set this and worked perfectly
-tt 47
-tmax 52
-fanmin 10
-fanmax 55

but now i use the same commend but when gpu go to 59 degree  fan start on 24% and after it's cooling they be shutdown and again this Repeat 59start ......... 

   This is most probably driver related. Downgrade to 18.5.1 or similar drivers. There are hardware control bugs in the latest AMD drivers. We will try to think of some workaround but the for now the best solution is to stay away from the latest drivers.

Noticed the same thing with the latest version and some RX580 under Linux.

Had -tt set to 68 and one GPU kept creeping up way past 80 degrees and the fan was idling at 23%.

  -tt is not sported under Linux yet.

Sadly 4.1c does not support 19.1.1, as it gives the Unknown OpenCL version error and suffers a hashrate loss because of it.
-clkernel 3 mode does not even work with it. ( clSetKernelArg (-49) )

I have 19.1.1 installed and latest version of miner works normal. RX 580 8 Gb Windows 10.

Code:

That`s strange... Well, I guess I can go back to 18.12.3 until we get a fix.

2019.01.19:21:21:33.279: main Phoenix Miner 4.1c Windows/msvc - Release build
2019.01.19:21:21:33.279: main Cmd line: -pool @@@
2019.01.19:21:21:33.279: main No CUDA driver found
2019.01.19:21:21:35.924: main OpenCL driver version: 19.1.1
2019.01.19:21:21:35.924: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.19:21:21:35.924: main OpenCL platform: OpenCL 2.0 AMD-APP (2348.3)
2019.01.19:21:21:35.924: main Ignoring old OpenCL driver(s), using driver version 19.1.1
2019.01.19:21:21:35.924: main Available GPUs for mining:
2019.01.19:21:21:35.924: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2019.01.19:21:21:36.002: main ADL library initialized

   In your log we can see that you have two versions of the drivers mixed up. The 19.1.1 are recognized properly but there are others too (probably "leftovers" from the previous driver version). You should use DDU to completely remove the drivers and then install 18.5.1 or other drivers besides 18.12.x and 19.1.x, which seems to cause problems.

I see totally minuscule reported hasharete improvement with "3" kernels, wonder if there would be any real hashrate improvement.

   The real hashrate improvement will be the same in the long run. However make sure to check your power consumption as it may increase in some cases, negating the benefit of the slightly higher hashrate.

[singlass]

finally !! thank you for the -clkernel 2 i used to be forced to use the generic  -clkernel 0 which was instable & produced a lotta stale shares

[kevyong]

Still no Yocoin for devfee to avoid switching DAGs while mining Yocoin?

Thank you!

[gploj]

hello,

how write comand line for turbo mode ?
On this rig must have only 8Gb cards ? I have 8x 8Gb and 1x 4Gb is this problem ?

Tnx

[bategojko74]

hello,

how write comand line for turbo mode ?
On this rig must have only 8Gb cards ? I have 8x 8Gb and 1x 4Gb is this problem ?

Tnx

clkernel -3 recognizes the GPU RAM size and switches automatically the cards with 4GB to clkernel -1. Sou you will not have a problem by simply passing clkernel -3. If you like your 4GB card to use clkernel -2 you have to pass clkernel 333333332 if your 4GB card is with index 9, otherwise you have to put the '2' on a position equal to the 4GB card index. You can find the index of the GPU in PM's log when it initially lists the available GPUs.

[ardeneast]

Hello
I use Phoenix since last spring. At first, I used it for Nice Hash and did not experience any problems, an excellent miner.
Since last summer I switched to ethermine pool and everything worked fine. But from the end of autumn I constantly try to return to Nice Hash, but the miner constantly stops working. it shows an error after allocating DAG buffer. (this is visible on the screenshot of the page) In the topic such a problem is indicated, but it says that the problem lies in the small swap file. The size of my page file is more than 30 GB per 6 1080ti video cards. At the same time, the phoenix works great on the ezermine pool. And only if I switch to Nice hash - then this problem occurs. What should I do so that the phoenix could work for Nice Hash.

My system is Windows 7. Video cards on this rig are 5 pieces of 1080 ti, power supply units 2 pcs corsair HX1200. RAM 4 GB, Video card driver 417.71, PhoenixMiner 4.1c

https://i.gyazo.com/760b8fcdd8b9a7cea52bf11cee0b50f4.png

[gploj]

hello,

how write comand line for turbo mode ?
On this rig must have only 8Gb cards ? I have 8x 8Gb and 1x 4Gb is this problem ?

Tnx

clkernel -3 recognizes the GPU RAM size and switches automatically the cards with 4GB to clkernel -1. Sou you will not have a problem by simply passing clkernel -3. If you like your 4GB card to use clkernel -2 you have to pass clkernel 333333332 if your 4GB card is with index 9, otherwise you have to put the '2' on a position equal to the 4GB card index. You can find the index of the GPU in PM's log when it initially lists the available GPUs.

tnx for your answer. I test it. Power consuption is the same ?

tnx

[carlosmonaco]

Hello ,
What are the best setting for VEGA 56 and 64 for ETH ?

[PhoenixMiner]

Hello
I use Phoenix since last spring. At first, I used it for Nice Hash and did not experience any problems, an excellent miner.
Since last summer I switched to ethermine pool and everything worked fine. But from the end of autumn I constantly try to return to Nice Hash, but the miner constantly stops working. it shows an error after allocating DAG buffer. (this is visible on the screenshot of the page) In the topic such a problem is indicated, but it says that the problem lies in the small swap file. The size of my page file is more than 30 GB per 6 1080ti video cards. At the same time, the phoenix works great on the ezermine pool. And only if I switch to Nice hash - then this problem occurs. What should I do so that the phoenix could work for Nice Hash.

My system is Windows 7. Video cards on this rig are 5 pieces of 1080 ti, power supply units 2 pcs corsair HX1200. RAM 4 GB, Video card driver 417.71, PhoenixMiner 4.1c

  The page file should be enough for six cards. Instability during DAG generation could indicate too much overclocking - try to lower the memory overclock a little (especially if the crashes occur on the same GPU). Although your PSUs seem more than enough for the system, you can also try the option -gser 1 (or bigger value, if 1 doesn't help). Finally, you can also try to set -gpureset 0 . If nothing helps, please cut the last few hundred rows from the log file before the crash and send it to us (via PM for example) to see what is going on.

Hello ,
What are the best setting for VEGA 56 and 64 for ETH ?

  Depends on the card but basically you have to experiment a little - overclock the memory as much as it can without losing stability and lower the core clock as much as you can without affecting the hashrate too much (the temperatures and the power consumption depend mostly on the core clock). Also, make sure that the temperature is kept no more than 60-64 C because the memory is stacked on the chip and can get quite hot even the reported temperature is relatively low.

[cadj92]

Sadly 4.1c does not support 19.1.1, as it gives the Unknown OpenCL version error and suffers a hashrate loss because of it.
-clkernel 3 mode does not even work with it. ( clSetKernelArg (-49) )

I have 19.1.1 installed and latest version of miner works normal. RX 580 8 Gb Windows 10.

Code:

That`s strange... Well, I guess I can go back to 18.12.3 until we get a fix.

2019.01.19:21:21:33.279: main Phoenix Miner 4.1c Windows/msvc - Release build
2019.01.19:21:21:33.279: main Cmd line: -pool @@@
2019.01.19:21:21:33.279: main No CUDA driver found
2019.01.19:21:21:35.924: main OpenCL driver version: 19.1.1
2019.01.19:21:21:35.924: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.19:21:21:35.924: main OpenCL platform: OpenCL 2.0 AMD-APP (2348.3)
2019.01.19:21:21:35.924: main Ignoring old OpenCL driver(s), using driver version 19.1.1
2019.01.19:21:21:35.924: main Available GPUs for mining:
2019.01.19:21:21:35.924: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2019.01.19:21:21:36.002: main ADL library initialized

   In your log we can see that you have two versions of the drivers mixed up. The 19.1.1 are recognized properly but there are others too (probably "leftovers" from the previous driver version). You should use DDU to completely remove the drivers and then install 18.5.1 or other drivers besides 18.12.x and 19.1.x, which seems to cause problems.

Thanks, I always use DDU, but it seem the update to 1809 switched back Window's auto-driver-download option. Switching it off and installing a clean 19.1.1 after a DDU solved the problem.

[VasilyS]

Today I launched Phoenix miner 4.1c in dual mode with blake2s on three R9 290. They recently gave about 23 mh/s on Ether in solo. Unlike the RX series, there is no support in AMD drivers for a large DAG size for old cards, so their speed, which was once 30-31 max, has seriously decreased. Got a fantastic speed in the miner window (45 mh/s). Blake2s showed 1300 mh/s, but there were no shares at all.
I was very pleased, but after checking on the pool (Ethermine) it turned out that these are only numbers in the miner's console. The real speed remained 22-23 mh/s as it was earlier.

[VasilyS]

It seems to me that your last version doesn't support R9 290 cards while dual mining (Ether and Blake2s algo). I tested different kernels and there are a lot of errors. I switched back to Claymore.

[Bigdrago]

I am using 4.0B without any issues.
Does this only affect if the miner crash and have to restart?