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

[AzzAz]

I know, new card and driver but I got many invalid shares in connection with Nicehash on my new RX 6800.
At the moment no OC and anyone else optimizings active. Seems to be a problem with the many new DAG generation within the mining process.

2020.11.20:14:50:21.563: main Phoenix Miner 5.2c Windows/msvc - Release build
2020.11.20:14:50:21.563: main Cmd line: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal 39d2gVnrTCRyUKxdWUiTtHjyiYjm5Z6nsA$0-Lvv+41KBzlKZvrdxo--nQA -proto 4 -amd -gpus 0 -wdog 0 -gbase 0 -mport 127.0.0.1:-4000
2020.11.20:14:50:21.995: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2020.11.20:14:50:21.995: main OpenCL platform: OpenCL 2.1 AMD-APP (3188.4)
2020.11.20:14:50:21.999: main Available GPUs for mining:
2020.11.20:14:50:21.999: main GPU0: AMD Radeon RX 6800 (pcie 43), OpenCL 2.0, 16 GB VRAM, 30 CUs
2020.11.20:14:50:22.000: main ADL library initialized
2020.11.20:14:50:22.469: main Eth: the pool list contains 1 pool (1 from command-line)
2020.11.20:14:50:22.469: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
2020.11.20:14:50:22.469: main Starting GPU mining
2020.11.20:14:50:22.469: main Matched GPU0 to ADL adapter index 0 (method 1)
2020.11.20:14:50:22.474: main GPU0: AMD driver 20.11.2
2020.11.20:14:50:22.474: main GPU0: Created ADL monitor for adapter 0; overdrive version: 8 (
2020.11.20:14:50:22.474: main GPU0: using AMD driver ver 20.11.2
2020.11.20:14:50:22.601: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)

2020.11.20:15:06:10.307: main *** 0:15 *** 11/20 15:06 **************************************
2020.11.20:15:06:10.307: main Eth: Mining ETH on daggerhashimoto.eu.nicehash.com:3353 for 0:15
2020.11.20:15:06:10.307: main Eth: Accepted shares 29 (5 stales), rejected shares 1 (1 stales)
2020.11.20:15:06:10.307: main Eth: **Incorrect shares 4** (11.76%), est. stales percentage 20.76%
2020.11.20:15:06:10.307: main Eth: Maximum difficulty of found share: 85.8 GH (!)
2020.11.20:15:06:10.307: main Eth: Average speed (5 min): 58.397 MH/s
2020.11.20:15:06:10.307: main Eth: Effective speed: 62.83 MH/s; at pool: 59.99 MH/s

"Normal" ETC and ETH mining runs properly, but with very fluctuating (56-60Mhs) hashrate!

I would first update driver to a version that supports the 6000 series. 20.11 seems to be old isnt it?

i would like share this problem. it is driver and poenix version dont match. i was using 5.1c with 20.4.2 with no problems. then 5.2d was good but after couple days i god invalid shares. i updated to 20.11.1 now it is good again.
5.1c wotks great with 20.4.2
and 5.2d works great with 20.11.1

1. Does miner now see all CUs?
2. Hashrate now is?

[soulistyce]

im geting an error with phoenix miner 5.2c and 5.2d
setkernelarg (48)
and it restarts
amd driver 20.11.2 the newest
rx 580 8gb

[ak313]

looking for Linux version before dag problem for 4GB cards

[peteycamey]

Whats the release date for 5.2e ?

[soulistyce]

im geting an error with phoenix miner 5.2c and 5.2d
setkernelarg (48)
and it restarts
amd driver 20.11.2 the newest
rx 580 8gb

any help how to bypass it

[Trietch]

https://i.imgur.com/U07clX6.png

Even if I'm running in administrator on Windows 10 I got this error.
Any ideas? Thanks

[SpeedY_Hun]

@Phoenixminer how about the etchash compatibility with the latest version?

[AzzAz]

im geting an error with phoenix miner 5.2c and 5.2d
setkernelarg (48)
and it restarts
amd driver 20.11.2 the newest
rx 580 8gb

any help how to bypass it

20.11.1?

[Binary100100]

Even if I'm running in administrator on Windows 10 I got this error.
Any ideas? Thanks

I'm getting that too except on HiveOS. Strange.

[Binary100100]

Even if I'm running in administrator on Windows 10 I got this error.
Any ideas? Thanks

I'm getting that too except on HiveOS. Strange.

he said it for the new version: rxboost and straps must be administrator.

Moreover he does not recommend the 20.11x

Thanks for your response but he stated "Even if I'm running in administrator on Windows 10..."

And I'm using Linux... so why is it prompting for Administrator on Linux? Any ideas on how to su on HiveOS?

[PhoenixMiner]

I found the solution for my 390's under smos and hiveos: -clKernel 0 -clNew 0. Now all cards are working with 30+ Mh/s!!!

   Great! Once the current "perfect storm" of 4GB DAG, ETCHash, and thew GPU releases passes, we will try to find the time to modify the older kernels to work with above 3.9x GB DAG files, and to eliminate the issues of the generic kernels with stale shares and unstable hashrate.

Even if I'm running in administrator on Windows 10 I got this error.
Any ideas? Thanks

   The miner itself needs to be started "As Administrator" - right-click the .bat file and select "Run as Administrator" from the context menu. It is not enough to run it from user account that has administrator rights.

Thanks for your response but he stated "Even if I'm running in administrator on Windows 10..."

And I'm using Linux... so why is it prompting for Administrator on Linux? Any ideas on how to su on HiveOS?

   Under Linux you need to use sudo ./PhoenixMiner .... when starting the miner. You will be prompted for your password and then the miner will run as usual.

@Phoenixminer how about the etchash compatibility with the latest version?

     The 5.2e does not support etchash but we will release a new version (5.3) in a week or so with ETCHash support. The idea is to have a version to go back to with the old ETC algo in case the hard fork fails (unlikely but still).

[PhoenixMiner]

PhoenixMiner 5.2e (release candidate) is ready with some fixes for AMD cards. You can download PhoenixMiner 5.2e from here (both Windows and Linux versions):

https://github.com/PhoenixMinerDevTeam/files  (github)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2e_Windows.zip
    ===================================
   SHA-1: bcaf624af82fab8fd52e3ccb01017293e8ef4a31
 SHA-256: cc6f26cc6791b9ca6d4bc50d1889fed6890ff8a4e29adf21947d4aeb318609d6
 SHA-512: 2891a797dba41bcc914bab51d5786b8c03dfbf2906f5871f20527b81ca77285225afbdbf822394500356fa97eecee58ffcb91901663b8128449221b1f073bd61

    File: PhoenixMiner_5.2e_Linux.tar.gz
    ====================================
   SHA-1: 7dd7b74ac90061fbdccf0b6b70ca32879f8821ea
 SHA-256: 4bc80a2b97de6703bdc011b1abbaf9973e85b7955204071c0adfc26ed764bb51
 SHA-512: 222bfcd28866475cd8090f89bff66e4774df3ea8cad33de1a40d3666eb6c80a1c66f1aadc17cc77665ee4274e50b2053367cc3f7fb832449738e045014ee7d11

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The changes in this release (since 5.2d) include the following:

• Fixed some problems with using 8GB AMD cards
• Fixed some problems with 4GB AMD cards when mining ETH or ETC
• Fixed crash when using the AMD Windows beta blockchain drivers from 2017 (still not recommended to use these drivers)
• Added support for the latest AMD Windows 10 drivers 20.11.2

The changes of the previous beta (5.2d) since the last version (5.1c) are:

• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris, Fiji, Tonga, and Baffin cards. It is automatically enabled for the 4GB cards if the DAG size approaches 4GB. You can also specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB). Under Windows the default DAG limit is 4023, and under Linux it is 4064 for older drivers (before 19.50), and 4076 for the newer drivers.
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added experimental memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Added support for the AMD Linux drivers 20.20, and 20.30
• Added support for the latest AMD Linux drivers 20.40-1147286 (however they seem to have hardware control problems with some cards, so no need to upgrade for now)
• Many other small improvements and fixes

Here are some additional notes:

• The -daglim option works on Polaris (RX470, RX480, RX570, RX580, RX590), Baffin (RX560, RX550), Tonga, and Fiji cards. It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 381 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the  hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
• (Windows) With PhoenixMiner 5.2e either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
• (Windows) If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
• (Linux) With PhoenixMiner 5.2e either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4064 on older drivers (before 19.50), or -daglim 4076 on newer drivers.
• (Linux) When the -daglim option is in effect (i.e. if you are mining ETH or ETC with 4GB cards), the miner will restart on each new DAG epoch, and will force serial (one-by-one) generation of the DAG buffers. To allow more stable operation under these conditions, it is best to use -rmode 0 and to use a script to restart the miner when it exits. Two such scripts are provided with the miner:  start_amd_4g_old_drv.sh for older drivers (before 19.50, note that when using -rmode 0, the -daglim for these older drivers can be increased to 4068), and start_amd_4g_new_drv.sh for newer drivers. Make sure to change the pools and the wallet in these scripts with your own before using them for mining.
• It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
• The new -rxboost option sets the memory refresh rate on AMD cards (only those with GDDR5 memory). The possible values are: 0 - default values, 1 - predefined value that should work on most cards, 2 to 100 - increasingly aggressive settings from lowest to highest. You should start by specifying -rxboost 1, then check the log file and find a message like this: "set VRAM refresh rate -rxboost 1 (equal to -vmr xx)". Write down the xx value and then replace -rxboost 1 with -vmr xx (for example -vmr 25). You can than try to increase the -vmr value until you start to see incorrect shares or some other instability (crashes, freezes, etc). If even the default value gives you incorrect shares or other problems, you should decrease it.
• Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator.
• The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
• The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.

Please let us know if you have any problems or questions related to PhoenixMiner 5.2e.

[waywoos]

thank you phoenixminer for always working hard on the support.

[cscheat]

Professor PhoenixMiner TQ for your hardwork!!!!

[miner95]

@PhoenixMiner Thanks for your hard work but why Turbo kernels (clkernel 3) not working anymore on my 2x RX 580 8GB ??
It says there is not enough VRAM for clkernel 3 but both my cards have 8GB memory and Windows never uses neither of them because my monitor connected to iGPU (Intel UHD).

https://i.imgur.com/bzBt23a.png

[miner95]

@PhoenixMiner Thanks for your hard work but why Turbo kernels (clkernel 3) not working anymore on my 2x RX 580 8GB ??
It says there is not enough VRAM for clkernel 3 but both my cards have 8GB memory and Windows never uses neither of them because my monitor connected to iGPU (Intel UHD).

https://i.imgur.com/bzBt23a.png

try:

-rvram -1

Thanks it worked but now I have only 11MH for my first card and 2MH for second one but I used to get 31.5MH for each card in Turbo kernels.
I still can get 30.5MH in Standard kernels and I know extra 1MH for each card doesn't worth it but I want to know why Turbo kernels suddenly broken?
I haven't changed anything on my cards (including overclocks, bios and...) for years and this suddenly happens.
And also I never use overclock softwares like MSI After Burner instead I changed core and memory clocks in my cards bios from 2 year ago.

https://i.imgur.com/nabxfsS.png

[BitKingRoss]

I am not a developer and wish I was. I have been mining since 2016. I would have had this miner well tested before deployment. I cannot comprehend to you the number of issues I have run into the latest Phoenix miner, DAG level, and Polaris cards when running large scale GPU farms. I manage and own a few, all running Windows Server with proper data center infrastructure management in place. It's as if Phoenix miner has only focused on development for Vega and Navi GPUs, but forgotten about Polaris as the DAG has limit increased. All of my Navi based rigs are fine for the most part. I manage many. Yes Claymore should be getting just as much backlash for not at all providing support but he is not available for commentary. Phoenix has been here and known about this encroaching issue. Please do something about this. We rely no stability.

[Trietch]

https://i.imgur.com/U07clX6.png

Even if I'm running in administrator on Windows 10 I got this error.
Any ideas? Thanks

   The miner itself needs to be started "As Administrator" - right-click the .bat file and select "Run as Administrator" from the context menu. It is not enough to run it from user account that has administrator rights.

I do not use the .bat file, I run directly the miner with PhoenixMiner.exe "As Administrator" with "Run as Administrator" from the context menu.

[ivomm]

I am not a developer and wish I was. I have been mining since 2016. I would have had this miner well tested before deployment. I cannot comprehend to you the number of issues I have run into the latest Phoenix miner, DAG level, and Polaris cards when running large scale GPU farms. I manage and own a few, all running Windows Server with proper data center infrastructure management in place. It's as if Phoenix miner has only focused on development for Vega and Navi GPUs, but forgotten about Polaris as the DAG has limit increased. All of my Navi based rigs are fine for the most part. I manage many. Yes Claymore should be getting just as much backlash for not at all providing support but he is not available for commentary. Phoenix has been here and known about this encroaching issue. Please do something about this. We rely no stability.

I test the new version with -vmr 85
I am at 33.900Mhs

PH: 5.2e
amd driver 20.11.2

If you put rxboost (or vmr) too high you will have memory errors and the real hash will be half of what the miner shows. You have to check always the stats of the pool. It is good to use some memory errors tool or just watch the screen. If you see artifacts (like small blinking dots), you are above the possibility of the memory. For me, I can use like -rxboost 1 with the best hash on the pool without memory errors. It gives 32.4 Mh/s with moded timings (rx 580 8Gb).

[waywoos]

I am not a developer and wish I was. I have been mining since 2016. I would have had this miner well tested before deployment. I cannot comprehend to you the number of issues I have run into the latest Phoenix miner, DAG level, and Polaris cards when running large scale GPU farms. I manage and own a few, all running Windows Server with proper data center infrastructure management in place. It's as if Phoenix miner has only focused on development for Vega and Navi GPUs, but forgotten about Polaris as the DAG has limit increased. All of my Navi based rigs are fine for the most part. I manage many. Yes Claymore should be getting just as much backlash for not at all providing support but he is not available for commentary. Phoenix has been here and known about this encroaching issue. Please do something about this. We rely no stability.

fix it yourself you ungrateful prick