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

vydelek

Newbie

Offline

Activity: 73
Merit: 0

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

November 18, 2020, 09:23:11 AM

#5821

Quote from: PhoenixMiner on November 18, 2020, 08:55:28 AM

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):

https://mega.nz/folder/OYcgVZJD#jC_7RaccVXhi0TGov5JupA (MEGA)

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.

PROBLEM! Claymore OK, lolminer OK, TeamRedMiner OK ale PM 5.2d KO...
Please do something from the SW to be able to benefit on the RX 570 8GB. How come other SWs go?

2020.11.18:10:21:03.440: main Phoenix Miner 5.2d Windows/msvc - Release build
2020.11.18:10:21:03.440: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal adresa.Miner16 -rmode 2 -tstop 85 -cdmport 2222
2020.11.18:10:21:03.440: main No CUDA driver found
2020.11.18:10:21:04.955: main OpenCL driver version: 17.8-BETA
2020.11.18:10:21:04.989: main Available GPUs for mining:
2020.11.18:10:21:04.989: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
2020.11.18:10:21:04.989: main Increase the Windows page file size to at least 29 GB to avoid out of memory errors and unexpected crashes.
2020.11.18:10:21:04.989: main ADL library initialized
2020.11.18:10:21:06.300: main Eth: the pool list contains 2 pools (2 from command-line)
2020.11.18:10:21:06.300: main Eth: primary pool: ssl://eu1.ethermine.org:5555
2020.11.18:10:21:06.300: main Starting GPU mining
2020.11.18:10:21:06.300: main Matched GPU1 to ADL adapter index 24 (method 1)
2020.11.18:10:21:06.321: main GPU1: AMD driver BETA
2020.11.18:10:21:06.321: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7 (7)
2020.11.18:10:21:06.321: main GPU1: using the blockchain beta driver
2020.11.18:10:21:06.321: main Matched GPU2 to ADL adapter index 0 (method 1)
2020.11.18:10:21:06.342: main GPU2: AMD driver BETA
2020.11.18:10:21:06.342: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2020.11.18:10:21:06.342: main GPU2: using the blockchain beta driver
2020.11.18:10:21:06.342: main Matched GPU3 to ADL adapter index 12 (method 1)
2020.11.18:10:21:06.365: main GPU3: AMD driver BETA
2020.11.18:10:21:06.365: main GPU3: Created ADL monitor for adapter 12; overdrive version: 7 (7)
2020.11.18:10:21:06.365: main GPU3: using the blockchain beta driver
2020.11.18:10:21:06.365: main Matched GPU4 to ADL adapter index 18 (method 1)
2020.11.18:10:21:06.390: main GPU4: AMD driver BETA
2020.11.18:10:21:06.390: main GPU4: Created ADL monitor for adapter 18; overdrive version: 7 (7)
2020.11.18:10:21:06.390: main GPU4: using the blockchain beta driver
2020.11.18:10:21:06.390: main Matched GPU5 to ADL adapter index 6 (method 1)
2020.11.18:10:21:06.410: main GPU5: AMD driver BETA
2020.11.18:10:21:06.410: main GPU5: Created ADL monitor for adapter 6; overdrive version: 7 (7)
2020.11.18:10:21:06.411: main GPU5: using the blockchain beta driver
2020.11.18:10:21:06.411: main Matched GPU6 to ADL adapter index 30 (method 1)
2020.11.18:10:21:06.436: main GPU6: AMD driver BETA
2020.11.18:10:21:06.436: main GPU6: Created ADL monitor for adapter 30; overdrive version: 7 (7)
2020.11.18:10:21:06.436: main GPU6: using the blockchain beta driver
2020.11.18:10:21:06.539: wdog Starting watchdog thread
2020.11.18:10:21:06.820: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2020.11.18:10:21:06.821: main GPU1: 40C 22% 36W, GPU2: 44C 25% 32W, GPU3: 43C 25% 32W, GPU4: 45C 27% 32W, GPU5: 43C 24% 34W, GPU6: 43C 25% 32W
GPUs power: 196.6 W
2020.11.18:10:21:07.023: main Listening for CDM remote manager at port 2222 in read-only mode
2020.11.18:10:21:07.061: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106)
2020.11.18:10:21:07.144: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xAc6C6D400644eF9861373514266899F891e7e130.Miner16"]}

2020.11.18:10:21:07.182: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2020.11.18:10:21:07.182: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2020.11.18:10:21:07.199: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa69bf44a20854d836f582aafd03c0f9051fa569e9e36c4b80de5a88f9be1c8c9","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]}
2020.11.18:10:21:07.199: eths Eth: New job #a69bf44a from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.11.18:10:21:07.205: GPU1 GPU1: Starting up... (0)
2020.11.18:10:21:07.205: GPU1 GPU1: Generating ethash light cache for epoch #376
2020.11.18:10:21:07.209: GPU2 GPU2: Starting up... (0)
2020.11.18:10:21:07.213: GPU3 GPU3: Starting up... (0)
2020.11.18:10:21:07.215: GPU4 GPU4: Starting up... (0)
2020.11.18:10:21:07.218: GPU5 GPU5: Starting up... (0)
2020.11.18:10:21:07.220: GPU6 GPU6: Starting up... (0)
2020.11.18:10:21:08.823: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x9b9ef2712ee05d68cb52143b9d8259bd169ccb7cf25e2f165d9a2c36a1fba7b2","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]}
2020.11.18:10:21:08.823: eths Eth: New job #9b9ef271 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.11.18:10:21:11.522: GPU1 Light cache generated in 4.3 s (14.6 MB/s)
2020.11.18:10:21:11.885: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.11.18:10:21:11.885: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)

puntodecontrol

Newbie

Offline

Activity: 18
Merit: 0

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

November 18, 2020, 09:38:33 AM

#5822

The -mvddc doesnt work

If i put 800, HWiNFO64 shows me 850, and if i put 820,830,... al time HWiNFO64 shows 850.

Any idea? Im using 5.2c with AMD driver ver 19.12.2 (rig of 5700 xt)

Christian26

Newbie

Offline

Activity: 9
Merit: 0

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

November 18, 2020, 09:41:40 AM

#5823

Quote from: vydelek on November 18, 2020, 09:23:11 AM

Quote from: PhoenixMiner on November 18, 2020, 08:55:28 AM

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.

I have the same problems with 8 GB Cards ... they do not work at all with the new version !

zeezoo

Newbie

Offline

Activity: 42
Merit: 0

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

November 18, 2020, 10:41:41 AM

#5824

Quote from: Christian26 on November 18, 2020, 09:41:40 AM

Quote from: vydelek on November 18, 2020, 09:23:11 AM

Quote from: PhoenixMiner on November 18, 2020, 08:55:28 AM

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.

I have the same problems with 8 GB Cards ... they do not work at all with the new version !

Drivers!

vydelek

Newbie

Offline

Activity: 73
Merit: 0

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

November 18, 2020, 11:04:38 AM

#5825

Quote from: zeezoo on November 18, 2020, 10:41:41 AM

Quote from: Christian26 on November 18, 2020, 09:41:40 AM

Quote from: vydelek on November 18, 2020, 09:23:11 AM

Quote from: PhoenixMiner on November 18, 2020, 08:55:28 AM

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.

I have the same problems with 8 GB Cards ... they do not work at all with the new version !

Drivers!

I won't play drivers when it works in Claymore and BETA. It is a problem only SW from PM. He has to solve this :-(

Ursul0

Sr. Member

Offline

Activity: 857
Merit: 262

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

November 18, 2020, 12:10:09 PM
Last edit: November 18, 2020, 12:25:41 PM by Ursul0

#5826

Quote from: DooGZ on November 17, 2020, 12:16:46 PM

Quote

You are wrong, every Nvidia Pascal Card, reduce the hashrate with every new DAG epoche. It's the same bug as the AMD R9 290x and R9 390 in the past.
The reduction is not much, but it will happened, You see it, when you let your miner benchmark in epoch 0 and for example in epoch 300. Test it and you will see it dude;)

My 1070's can easily reach 30-32mhs around 2018, current speed is 25-27mhs with the same OC as before, needed to increase core speed + voltage + "-straps" to reach 29-30mhs again.
Same with 1060's, from 24mhs, went down to 21-22mhs with the same 2018 OC.

RX's Polaris are not affected.

here's my 1060 Palits that hold awesome +800 to +850 memory .... for the past 3+ years:)

and here it is on ZIL(and 1080tis below):

bluspirit

Jr. Member

Offline

Activity: 70
Merit: 3

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

November 18, 2020, 12:18:59 PM

#5827

RX 580 4GB - 20.4.2 drivers - Win 10 (1709)

@epoch 375 - PM 5.2c 31.7 MH/s (stable)
@epoch 376 - PM 5.2c 28.8 MH/s (stable)
@epoch 376 - PM 5.2d 29.8 MH/s (in testing)

I'm still using PM 5.1c for 8GB cards, stable so far.

Thanks PM

SergeySS

Newbie

Offline

Activity: 15
Merit: 0

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

November 18, 2020, 12:46:02 PM

#5828

PM 5.2 stopped working, 5.1c works. I will not change the Betta driver with them, my cards consume less.

VictorGT

Hero Member

Offline

Activity: 748
Merit: 523

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

November 18, 2020, 01:06:52 PM

#5829

Quote from: bluspirit on November 18, 2020, 12:18:59 PM

I agree. Much better 5.1c for my AMD 6GB and 8GB cards.

samigen

Newbie

Offline

Activity: 4
Merit: 0

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

November 18, 2020, 02:40:48 PM

#5830

I also have a loss of 6% hash rate

cscheat

Newbie

Offline

Activity: 84
Merit: 0

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

November 18, 2020, 02:46:53 PM

#5831

same here

179MH become 167MH

Guigs321

Newbie

Offline

Activity: 41
Merit: 0

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

November 18, 2020, 04:05:24 PM

#5832

6,5 % less exactly here

cscheat

Newbie

Offline

Activity: 84
Merit: 0

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

November 18, 2020, 04:19:58 PM

#5833

Quote from: Guigs321 on November 18, 2020, 04:05:24 PM

6,5 % less exactly here

dammit... hope to mine ETC soon at full speed

bategojko74

Member

Offline

Activity: 220
Merit: 12

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

November 18, 2020, 04:37:27 PM
Last edit: November 18, 2020, 06:42:14 PM by bategojko74

#5834

Quote from: samigen on November 18, 2020, 02:40:48 PM

I also have a loss of 6% hash rate

If you have 4gb cards it is normal to lose 6% on every new epoch.
If you have 8gb cards then check if this 6% drop happens at the pool's side too. PM could have a bug in showing the stats properly.
If the drop exists at the pool's side with 8gb cards then updating your drivers to the newest supported by PM is very likely to fix your problem.

zeezoo

Newbie

Offline

Activity: 42
Merit: 0

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

November 18, 2020, 06:24:09 PM

#5835

Quote from: vydelek on November 18, 2020, 11:04:38 AM

Quote from: zeezoo on November 18, 2020, 10:41:41 AM

Quote from: Christian26 on November 18, 2020, 09:41:40 AM

Quote from: vydelek on November 18, 2020, 09:23:11 AM

Quote from: PhoenixMiner on November 18, 2020, 08:55:28 AM

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.

I have the same problems with 8 GB Cards ... they do not work at all with the new version !

Drivers!

I won't play drivers when it works in Claymore and BETA. It is a problem only SW from PM. He has to solve this :-(

Then use Claymore. It's clearly mentioned in the first post that "these are recommended drivers that work best with our software" and BETA drivers are no longer recommended. By the way - These drivers are from which year? 2018?... If it works good with the other mining software there's no need to use PhoenixMiner, right?
I'm using 20.4.2 myself on 4 different rigs and have no issues at all with 5.2d and 4GB/8 GB cards... except 1-2 MH/s loss with RX574 and RX474 ...

Peace.

andrew115200

Newbie

Offline

Activity: 20
Merit: 8

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

November 18, 2020, 07:05:57 PM

#5836

Quote from: cscheat on November 18, 2020, 02:46:53 PM

same here

179MH become 167MH

try set -daglim 4076, i have 474/574 cards, PM 5.2d, win10 1703, drivers 19.6.2, if -daglim 1 (auto, 4023) hashrate about 167MH/s, if set -daglim 4031-4076 hashrate is normal 180Mh, as before

anon2

Newbie

Offline

Activity: 13
Merit: 0

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

November 18, 2020, 07:26:08 PM

#5837

Quote from: abrgeza on November 18, 2020, 08:10:54 AM

Quote from: anon2 on November 17, 2020, 10:19:41 PM

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

Hi!
Thx for the answer! I did upgrade to this driver 20.4.2, but it is the same. The miner crashes, error something in phoenix. At Claymore error at gpu x, gpu y...
The system finds 12 gpu´s, but not posible to mine more than 9 gpu´s.

I can mix the 9 gpu´s at all 12 slots with also mixing the risers to know if the gpu´s are ok, the risers are ok and the gpu-slots at the mainboard are ok, no idea at the moment....

I tryed also with a brand new ashrock h110 btc plus, with also the driver 20.4.2, but phonix and claymore are not willing to mine...

Maybe motherboard bios update??

thank you
Anon

zeezoo

Newbie

Offline

Activity: 42
Merit: 0

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

November 18, 2020, 07:30:32 PM

#5838

Quote from: anon2 on November 18, 2020, 07:26:08 PM

Quote from: abrgeza on November 18, 2020, 08:10:54 AM

Quote from: anon2 on November 17, 2020, 10:19:41 PM

use 20.4.2 drivers, it works fine with 10 gpu rigs

https://www.youtube.com/watch?v=N_9-3zVsgDg

It is possible to mine even with 19 gpus under Windows. Just make sure you're running latest Win10 version as well as recommended drivers.

UnclWish

Sr. Member

Offline

Activity: 1484
Merit: 253

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

November 18, 2020, 08:16:24 PM

#5839

@PhoenixMiner, AMD released 20.11.2 driver. PM 5.2c didn't support it. It's need update.

vmgv

Newbie

Offline

Activity: 12
Merit: 0

⇾ Re: PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

November 18, 2020, 10:20:53 PM
Last edit: November 18, 2020, 10:46:21 PM by vmgv

#5840

Working great on

(1) rx 570 4 gb 25mhs
(3) rx 580 4 gb 28mhs per card

Drivers AMD 20.4.2
Windows 10

Wink

Thank u

Pages: « 1 ... 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 [292] 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 ... 499 »

Bitcoin Forum > Alternate cryptocurrencies > Mining (Altcoins) > PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

« previous topic next topic »