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

[7anonminer7]

Can confirm that 5.2c is working great with my RX 570  4Gb cards

Windows 10
Adrenalin 2019-Edition-18.12.3-Dec19 driver

2 x Sapphire Pulse Rx 570 4Gb cards mining ETH at 1100/2000 core/mem

hashrate now 29.9MH/s
hashrate before the DAG limitation: 30.3MH/s

Happy for you. Could you please post your config settings? As you can see from my post I get 0 MH/s for my 4 x RX570 4G and I had to switch to lolminer which is unstable:

Hello.

I'm using PhoenixMiner 5.2c on Windows 10 with Adrenaline 19.7.5 drivers,  4 x 570RX 4GB cards in "compute mode" (VGA output connected to intergrated Intel GPU) with following settings:

Code:

-acm
-eres 1
-lidag 2
-tt -60,-45,-60,-60
-cclock 1050,1050,1050,1050
-cvddc 900,950,900,900
-mclock 1970,1970,1970,1970
-mvddc 850,850,850,850
-daglim 3990

Yet after DAG generation I get 0 Mh/s on every card, please advise what could be wrong, thank you.

PS. https://pastebin.com/Mb1asrvP <- the the log - I couldn't pinpoint anything strange or any errors that are in there though.

So anyone able to Run PhoenixMiner on Windows 10 and RX570/470 with 4GB?

[pitersan]

HELP
ecть ктo pycкoязычный?

[rintic13]

where is this miner for linux

[bit-sokol]

Where is the miner for linux

coming soon)

[HardSign]

a few days passed yesterday:)))

WE NEED THE LINUX VERSION

[bit-sokol]

a few days passed yesterday:)))

WE NEED THE LINUX VERSION

no!! only windows, only hardcore! 

[miner29]

Ive got both 5.0e and 5.1c mining away on linux rigs with no issue.

Running AMD 4gb cards churning away on ETH still.  (average 29~31mhs .... just like life not all cards are equal)


So what is the big problem here?  There are linux versions and for me they work great . Yet i see people begging for a linux version..and yet...i run 2 different ones.... hmmmm

[jgonzi]

a few days passed yesterday:)))

WE NEED THE LINUX VERSION

If you need Linux, you should look for another miners, that developer's are still making both versions... there are some also big active in this forum...

[LeonManveli]

HELP
ecть ктo pycкoязычный?

http://ipic.su/?page=img&pic=Problem0000.1605635137.png
http://ipic.su/img/img7/fs/Problem0000.1605635212.png

You need ask to here https://bitcointalk.org/index.php?topic=4432704.0

[bategojko74]

Can confirm that 5.2c is working great with my RX 570  4Gb cards

Windows 10
Adrenalin 2019-Edition-18.12.3-Dec19 driver

2 x Sapphire Pulse Rx 570 4Gb cards mining ETH at 1100/2000 core/mem

hashrate now 29.9MH/s
hashrate before the DAG limitation: 30.3MH/s

Happy for you. Could you please post your config settings? As you can see from my post I get 0 MH/s for my 4 x RX570 4G and I had to switch to lolminer which is unstable:

Hello.

I'm using PhoenixMiner 5.2c on Windows 10 with Adrenaline 19.7.5 drivers,  4 x 570RX 4GB cards in "compute mode" (VGA output connected to intergrated Intel GPU) with following settings:

Code:

-acm
-eres 1
-lidag 2
-tt -60,-45,-60,-60
-cclock 1050,1050,1050,1050
-cvddc 900,950,900,900
-mclock 1970,1970,1970,1970
-mvddc 850,850,850,850
-daglim 3990

Yet after DAG generation I get 0 Mh/s on every card, please advise what could be wrong, thank you.

PS. https://pastebin.com/Mb1asrvP <- the the log - I couldn't pinpoint anything strange or any errors that are in there though.

So anyone able to Run PhoenixMiner on Windows 10 and RX570/470 with 4GB?

UPGRADE your drivers to the newest supported by PM

[anon2]

Hy people!

I have a problem running more than 9 RX580 at my ashrock H110. It run with 12 cards till december 19, than I stopped mining. Now I startet again, but get always error in claymore and with phoenix is the same. The mainboard found more than 9 cards, but get errors when I try to run more than 9 cards. I have old blockchain drivers for the amd rx580 cards. So, do you think after upgrading will it be posible to run more than 9 cards, or will it be the same?
I did not upgrade now, because I don´t know if the system runs stable after upgrading? Last update was maybe 2018, after installing the system.
I have two riggs with the same components - both are running only 9 cards, more than 9 - error.



thank you for your replay
Anon

[arierep60]

When the new version for linux?
With the latest stable hiveos image I get less mhs because the and drivers are the new ones and it's giving me less 10mhs per rig

[HardSign]

please fix mistake in subject "PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)". You have to delete word "Linux" at the end.

[UnclWish]

please fix mistake in subject "PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)". You have to delete word "Linux" at the end.

5.1c version for linux exists by the link on the 1st page.

[yalviert]

sorry

[vydelek]

PLEASE HELP verze 5.2c KO and verze 4.9c OK GOOD mining there it goes well but why did it stop with the version 5.2c???

6x GPU - Sapphire RX 570 8GB

Please to which DAG is SW 4.9c made? in ETH mining?

Verze 5.2c - KO STOP mining???

2020.11.18:06:18:50.791: main Eth speed: 187.647 MH/s, shares: 10339/0/0, time: 62:56
2020.11.18:06:18:50.791: main GPUs: 1: 31.249 MH/s (1674) 2: 31.278 MH/s (1730) 3: 31.281 MH/s (1699) 4: 31.283 MH/s (1723) 5: 31.283 MH/s (1771) 6: 31.272 MH/s (1742)
2020.11.18:06:18:51.327: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xf987776a40532f9510968dc7a9ceb39ce5b27b125a0d1bdf8d41c4d04e88cbc3","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac1e80"]}
2020.11.18:06:18:51.327: eths Eth: New job #f987776a from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.11.18:06:18:51.453: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xf90dd21833435c5ad440f039a992748da491d5e72d0cd254d009eba874e59d8f","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac1e80"]}
2020.11.18:06:18:51.453: eths Eth: New job #f90dd218 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.11.18:06:18:51.642: GPU6 GPU6: Starting up... (0)
2020.11.18:06:18:51.642: GPU6 GPU6: Generating ethash light cache for epoch #376
2020.11.18:06:18:51.688: GPU4 GPU4: Starting up... (0)
2020.11.18:06:18:51.727: GPU3 GPU3: Starting up... (0)
2020.11.18:06:18:51.803: GPU2 GPU2: Starting up... (0)
2020.11.18:06:18:51.844: GPU5 GPU5: Starting up... (0)
2020.11.18:06:18:51.844: GPU1 GPU1: Starting up... (0)
2020.11.18:06:18:55.359: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x5474a8821ab8b442400b20705e29d3009a5e4caa5ab944bfedb44454f0aacf94","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac1e80"]}
2020.11.18:06:18:55.359: eths Eth: New job #5474a882 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.11.18:06:18:55.763: GPU6 Light cache generated in 4.1 s (15.3 MB/s)
2020.11.18:06:18:55.809: main Eth speed: 0.000 MH/s, shares: 10339/0/0, time: 62:56
2020.11.18:06:18:55.809: main GPUs: 1: 0.000 MH/s (1674) 2: 0.000 MH/s (1730) 3: 0.000 MH/s (1699) 4: 0.000 MH/s (1723) 5: 0.000 MH/s (1771) 6: 0.000 MH/s (1742)
2020.11.18:06:18:55.996: GPU4 GPU4: Allocating DAG (3.95) GB; good for epoch up to #378
2020.11.18:06:18:56.056: GPU4 GPU4: Generating DAG for epoch #376
2020.11.18:06:18:56.230: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2020.11.18:06:18:56.243: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2020.11.18:06:18:56.244: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x5474a8821ab8b442400b20705e29d3009a5e4caa5ab944bfedb44454f0aacf94","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac1e80"]}
2020.11.18:06:18:56.315: GPU3 GPU3: Allocating DAG (3.95) GB; good for epoch up to #378
2020.11.18:06:18:56.363: GPU3 GPU3: Generating DAG for epoch #376
2020.11.18:06:18:56.597: GPU2 GPU2: Allocating DAG (3.95) GB; good for epoch up to #378
2020.11.18:06:18:56.645: GPU2 GPU2: Generating DAG for epoch #376

[1conito]

just checked my hashrate, with epoch #376 i lost arround 6% of my hashrate

[vydelek]

just checked my hashrate, with epoch #376 i lost arround 6% of my hashrate

4.9c OK

[abrgeza]

Hy people!

I have a problem running more than 9 RX580 at my ashrock H110. It run with 12 cards till december 19, than I stopped mining. Now I startet again, but get always error in claymore and with phoenix is the same. The mainboard found more than 9 cards, but get errors when I try to run more than 9 cards. I have old blockchain drivers for the amd rx580 cards. So, do you think after upgrading will it be posible to run more than 9 cards, or will it be the same?
I did not upgrade now, because I don´t know if the system runs stable after upgrading? Last update was maybe 2018, after installing the system.
I have two riggs with the same components - both are running only 9 cards, more than 9 - error.



thank you for your replay
Anon

use 20.4.2 drivers, it works fine with 10 gpu rigs

[PhoenixMiner]

PhoenixMiner 5.2d is ready with another speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2d from here (both Windows and Linux versions):

(MEGA links are no longer active)

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.2d_Windows.zip
    ===================================
   SHA-1: c0046d07d915c030c5486536a29c49e044943b4f
 SHA-256: 8093946d46acf3609d61a8ba8e2c7b71b0920e3cf8cef2732db320d8eeed30b8
 SHA-512: 70fa65657aac7b0a34f7e847dec60c859536af840be919316a619501d22cec83315bda0df2736d6e37c8af8bff00af99d92a0d23f655b17edd7c308439bc7c2c

    File: PhoenixMiner_5.2d_Linux.tar.gz
    ====================================
   SHA-1: 9ba41efc5c54ff4682e216976c6f44d3dc6dc6e8
 SHA-256: 714af07c14e960c1fb8782e91c4add3aa292a26ef820cf797f452fdf411677d7
 SHA-512: 7c13305660736d62d3de2b82875afaa18d2cbbd518a4a9b368763827a89834a38034d91fcfd5bb29ca0c21120738a03aff36d982f685336212ece868f4ceaf4c

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

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

• Added support for -daglim for AMD Fiji, Tonga, and Baffin cards with 4GB VRAM, so you will be able to use them some time beyond epoch 373 (Windows), or 381 (Linux)
• New kernels for 4GB AMD cards with higher hashrate when -daglim is in effect
• Added -daglim and -rxboost support in Linux. The default -daglim value in Linux is 4064 for older drivers (before 19.50), and 4076 for the newer drivers
• 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)

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

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This allows higher hashrate when the DAG is bigger than the available VRAM.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• 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 cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added 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
• 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.2d 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.2d 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.
• 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.2d.