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

[UselessGuru]

Typo:

'commnad' should be 'command'

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
No avaiable GPUs for mining. Please check the -gpus commnad line option.

[UselessGuru]

turbo kernel error clCreateKernel (-46):

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG  50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)

Card is a RX 570 4 GB model. Should this not be enough memory?

[bategojko74]

turbo kernel error clCreateKernel (-46):

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG  50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)

Card is a RX 570 4 GB model. Should this not be enough memory?

Dual mining doesn't support clkernel 3

[UselessGuru]

turbo kernel error clCreateKernel (-46):

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG  50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)

Card is a RX 570 4 GB model. Should this not be enough memory?

Dual mining doesn't support clkernel 3

Thank you! Is this missing in the documentation, or did I just miss it?

[bategojko74]

turbo kernel error clCreateKernel (-46):

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG  50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)

Card is a RX 570 4 GB model. Should this not be enough memory?

Dual mining doesn't support clkernel 3

Thank you! Is this missing in the documentation, or did I just miss it?

I found it experimentally. Looks like bug.

[lesjokolat]

will you have support for ProgPoW?

  Yes, absolutely. We will be ready for the future switch to ProgPow.

Need to enable the user to increase the check interval for -wdog, for example -wdogtime 90. Now it costs 30 seconds, sometimes it’s not enough

  We will add a similar option in 4.1b, which will be released in a few days.

It should be noted that in this mode -clkernel 3, with the default setting -rvram video cards consume more power on average 2-4% and there will be more virtual memory loading, so maybe someone will need to increase it

   Yes, depending on your overclocking settings the turbo kernels may consume more power. Also, you must re-run auto-tuning because the optimal -gt values will most likely be quite different for the new kernels.

Note that you must also re-run auto-tune if you have AMD 280/285/290/380/390 GPU, because of updated kernels for these GPUs.

any plans for kernal 3 for fury x or vega 64?

also the setting of etth (claymore lower limti of 50 being lowered to 25?) i think can help squeeze out some more hashs..

thanks

[PhoenixMiner]

Could you please add the resulting autotuning parameters to the API?
Thaaaaaaaaank you!

   There will be substantial additions to the remote management API but not in this release.

Still no overclock or voltage control on nvidia cards?

Ethos has been able to do this for a long time.

    We are giving priority to any ideas to bring up the ROI of the mining but these will be implemented eventually.

Please suppress the warning messages about invalid epools.txt when valid epool parameters are passed via command line.

Eth: Invalid wallet 'YourWallet.BLACKBOX' specified for pool 1 from epools.txt. Replace with a real wallet
Eth: Invalid wallet 'YourWallet.BLACKBOX' specified for pool 2 from epools.txt. Replace with a real wallet

Code:

# The pools specified in this file will be added to the pools specified with the PhoenixMiner's
# command-line options (see -pool and -pool2 command line options).

When -epool -or -dpool is present, then no other pools should be used.

    This would change the way the miner behaved in all current releases, which will definitely cause problems for many users. You can either rename the epools.txt to something else, or comment out all lines there with the # character at the start of each line.

turbo kernel error clCreateKernel (-46):

Code:

Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG  50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)

Card is a RX 570 4 GB model. Should this not be enough memory?

    Thank you for reporting this. The -clkernel 3 option doesn't work with dual mining yet. We will try to include the turbo dual mining kernels in the final 4.1 release.

any plans for kernal 3 for fury x or vega 64?

also the setting of etth (claymore lower limti of 50 being lowered to 25?) i think can help squeeze out some more hashs..

thanks

   Unfortunately the techniques that make -clkernel 3 faster doesn't work on Fury and Vega GPUs. Can you please clarify what do you mean by etth?
   

[Bathmat]

will you have support for ProgPoW?

 Yes, absolutely. We will be ready for the future switch to ProgPow.

Any chance you have a beta version with ProgPow already implemented for coins like Bitcoin Interest (BCI)?

https://github.com/BitcoinInterestOfficial/ProgPOW

[ManDoneKTM]

are you getting better results with the blockchain drivers or with the lastest AMD drivers? RX4xx & RX5xx cards

ONLY IN GAMING YOU WILL NOTICE DIFFERENCE ! In mining drivers are the SAME ! i had tested 12 kinds of version of amd drivers , all the same results !

[JFoxOne]

User reported that 4.1a doesn't work with pool on etcget.net, but 4.0b was working fine. Could be same with other similar pools. Worth to inspect.

[ManDoneKTM]

User reported that 4.1a doesn't work with pool on etcget.net, but 4.0b was working fine. Could be same with other similar pools. Worth to inspect.

Same problem here , i have 2 rigs on a pool , but reported hashrate is only from the 1 rig ... i will go back to the previous version of PM

[Soliqesh]

whalesburg miners reported some troubles with new version, sometimes miner restart or stuck

[Guigs321]

With Ethermine, my reported hasrate is a little bit better but the current hasrate is lower and so the average hashrate. I don't have anormal rejected/invalide/stale share.

Going back to the previous version and the current hashrate and average hasrate goes up.

[cbaa]

Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2766.4)
Available GPUs for mining:
GPU1: AMD Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 1.2, 3.2 GB VRAM, 36 CUs
GPU2: AMD Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 1.2, 7.9 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie , OpenCL 1.2, 8 GB VRAM, 36 CUs

im on ubuntu. i wonder witch is the know opencl driver ?

[stortz]

what config do you guys use when you're trying to avoid screen lag?
I noticed that -mi set to lower than the default does not seem to affect screen lag and hashrate

so I'm still wondering which config should I change in case i want to use the computer while the miner is still running
I have set -mi to 12 when I'm not doing anything other than mining

[PhoenixMiner]

The third beta of the new release is out (note that 4.1b wasn't released as we found some small bugs before it was out). You can download PhoenixMiner 4.1c from here:

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

   File: PhoenixMiner_4.1c_Windows.zip
    ===================================
   SHA-1: 695f269c335f7d525ecf96450702d643f15af98a
 SHA-256: 93c3678a324fe677076cd746222dfec8e26be0fc758f0df080e14d6a5c8c4b91
 SHA-512: 7c8544a3bfd367872b624b9e1bda12d1b5484a08d6e4d0a25abec2654242ceaf1df3a29fcd86e0a5bfd71927d1bda1ad716fc6d52a9cbddb714a8c521bb8db7b

    File: PhoenixMiner_4.1c_Linux.tar.gz
    ====================================
   SHA-1: 981dc17b1f51d56a1d025940c936a779f3be9198
 SHA-256: 26d07ecb98c4d49205894224503a9faa4a1b5c5750875899cded22e5f2506815
 SHA-512: c02c6baef626039de1070ca5e049c5a65986fa0e86ad64fdc019fe30599fd664238c20f1ab1cd7e3a68c82c9f54d16032a323e481018a0044881767104f44120

Here are the changes since 4.1a (the first beta of 4.1):

• Added support for turbo kernels (-clkernel 3) and dual mining
• Added command-line option -vs to just print the version (e.g. 4.1c) and exit
• Added command-line option -wdtimeout to set the timeout of the watchdog timer. The valid values are from 30 to 300 seconds, the default is 45 seconds.
• Added support for Windows AMD drivers 19.1.1
• Small bugfixes

Here are the changes since 4.0b (the previous stable release):

• Added faster "turbo" kernels (-clkernel 3) for AMD 470/480/570/580 GPUs. These are usually faster than normal kernels (-clkernel 1 or -clkernel 2) but require double the amount of VRAM. This means that you can only use them on 8 GB cards if mining ETH or ETC. You can use them on cards with 4 GB or less VRAM only if you are mining low DAG epoch coins.
• Added Blake2s dual mining kernels, and green kernels for AMD Fury GPUs
• Added Blake2s dual mining kernels for AMD 280/285/290/380/390 GPUs
• New faster kernels for AMD 280/290/390 GPUs
• Added alternative kernels (-clkernel 2) for AMD 280 GPUs
• Added options -pauseat and -resumeat for scheduled pausing and resuming of the miner. Example: -resumeat 22:00 -pauseat 6:00 - the miner will mine only between 22:00 and 6:00. Example 2: -resumeat 22:00,12:00 -pauseat 6:00,16:00 - you can specify multiple pause and resume times.
• (Windows only) The miner now prevents the computer from sleeping if the mining is not paused, and wakes the computer when it must resume mining at the time specified with -resumeat command-line option. In combination with -pauseat and -resumeat options this allows you to mine only when the electricity rates are lower and to keep your rig(s) asleep the rest of the time.
• When the miner is paused for more than a few minutes, the pool is disconnected. The pool connection is restored when the mining is resumed.
• Added a watchdog protection against freezing of the network connection thread
• Automatic selection of compatible devfee coin if there isn't enough VRAM to mine ETH and the main coin can't be recognized or isn't supported for devfee
• Automatic switch to the next pool if the cards VRAM is not enough for the requited DAG epoch. This is especially useful if the pool is auto-switching the coins but your cards only support lower DAG epoch coins.
• Added a -rvram option to set the minimal reserved VRAM that can't be used for mining. The default values are 384 MB on Windows, and 128 MB on Linux. You can also set -rvram -1 if you want to turn off the protection against using too much VRAM.
• Added support for Windows AMD drivers 18.12.x
• Other small improvements and fixes

Finally, please note that the versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. Currently ETC is above this, and ETH is going to be on epoch 236 very soon. If you want to continue to mine ETH and ETCH, you must upgrade to PhoenixMiner 4.x.

[PhoenixMiner]

Any chance you have a beta version with ProgPow already implemented for coins like Bitcoin Interest (BCI)?

https://github.com/BitcoinInterestOfficial/ProgPOW

   We have but it is not yet ready for the public releases.

User reported that 4.1a doesn't work with pool on etcget.net, but 4.0b was working fine. Could be same with other similar pools. Worth to inspect.

   We have performed a quick test and there were no issues. Here is the command line we used:

Code:

-pool stratum+tcp://eu.etcget.net:8018 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E -worker Rig1 -pass x

Same problem here , i have 2 rigs on a pool , but reported hashrate is only from the 1 rig ... i will go back to the previous version of PM

whalesburg miners reported some troubles with new version, sometimes miner restart or stuck

   If the problems persists, please send us a (partial) log file to see what is going wrong.

Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2766.4)
Available GPUs for mining:
GPU1: AMD Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 1.2, 3.2 GB VRAM, 36 CUs
GPU2: AMD Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 1.2, 7.9 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie , OpenCL 1.2, 8 GB VRAM, 36 CUs

im on ubuntu. i wonder witch is the know opencl driver ?

   Supported AMD Linux drivers are 16.40, 16.60, 17.10, 17.20, 17.30, 17.40, 17.50, 18.10, 18.20, 18.30, 18.40. The latest 18.50 drivers are not supported yet.

what config do you guys use when you're trying to avoid screen lag?
I noticed that -mi set to lower than the default does not seem to affect screen lag and hashrate

so I'm still wondering which config should I change in case i want to use the computer while the miner is still running
I have set -mi to 12 when I'm not doing anything other than mining

   Set -mi 0. If this is not enough, try -mi 8 -gpow 80 or -mi 8 -li 1 Increase/decrease the -gpow or -li values until you have smooth desktop experience without losing too much hashrate.

[pp55]

I can`t see if I can use -Kernel option per GPU. Is it impossible at all or it is miner limitation?
I have a rig with one RX580 8Gb and four RX570 4Gb and wanna try turbo kernels. Any suggestions?

[thameur]

Hi

have there real problems, when mines with R9 390 u. R9 390X GPU's .....
For some months, the hashrate is decreasing continuously from formerly about 33 Mhs / s to about 25.9 Mhs / s even though the R9 390 (X) of the DAG Epoch problem should not be affected at all ...
have any idea to get back 33 Mh/s
Resiste the DAG Epoch

[wetec]

With AMD driver version 18.12.2 and latest 4.1c version, it seems that the fan control did not work here (@RX470/480/570 cards).
Any problems known about this?