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

[Pe_Da]

For my RX 580 8Gb rigs Phoenix 5.1c didn't create DAG epoch №385. It creates DAG for 0,5 sec and all shares are incorrect. Speed shows normal.

I think PM just didn't support epochs 385+

Looks similar here, since estimated 6 hours almost all shares on ETC-Mining (Ethermine) are invalid.
ETH seems to be working properly, still ...

Doublecheck with NBMiner, no issues! Seems to be a problem with Phoenix only .... oh wait, NBMiner produce many (>20%) rejected shares at ETC-Mining currently ...  

I'm use lolMiner now. All fine.

Problem solved by using other miner. Teamredminer or lolminer works fine for me if I run the nVidia and AMD Cards in parallel instances.
It seems PhoenixMiner have a problem on Radeon since Epoch 385. NBMiner as well!

My Rig:

16GB RAM

1x Radeon VII (16GB)                    >TeamRedMiner
2x Radeon RX 5700 (8GB)              >TeamRedMiner
1x Radeon RX 5700XT (8GB)          >TeamRedMiner
1x Geforce GTX 1660 Super (6GB)  >PhoenixMiner
1x Geforce RTX 2060 Super (8GB)  >PhoenixMiner

After further testing with newer drivers and another PC, the problem still persist.
PhoenixMiner have definitely a problem from Epoch 385 on at AMD .....

[Rambo1984]

I've now found that it works still on Windows with Nividia cards but not AMD cards

So it's a software glitch with the amd.

Linux etc all uneffected.

[PhoenixMiner]

The new alpha version is ready. You can download PhoenixMiner 5.2a from here (this is only the Windows version, the Linux version will be ready in a few days):

(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.2a_Windows.zip
    ===================================
   SHA-1: 04e04056a2ec117c91f94fae63a7b6c94a64a237
 SHA-256: c15f474b34310d92642a10fc460d03b5232a7714ede2b12de9e3ba3bbd2e8edc
 SHA-512: 24bb6370b476e3f7dfc4e21dc382b9d7ff8c78a2328e21b0a52bf465c5be2b480ed84dda81719209023ec1bb024d1be8ef199e61be56a5aa7a1c1000e4d38d04

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

The new features in this release 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 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 about the VRAM timing adjustments of Nvidia 10x0 cards:

• 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/root.
• The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
• The -daglim option works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limit the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 373 on Windows (or after 384 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit, this is the default), 1 (automatic DAG limit size, usually around 4005 MB under Windows). 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 3950
• 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 note that this is an alpha release, we rushed it because the epoch 374 is just a few hours away and because of the problems with DAG epoch 385 on ETC and AMD cards. Please let us know if you have any problems or questions related to PhoenixMiner 5.2a.

[Kiawpqe]

Bienvenido 5.2a
Otra vez a x ETC!!!!!
muchas gracias lo pruebo y comento.

[MegaVlad]

Hello. I have 1660 super + Phoenix 5.1c + Windows 10.
In command file I add key -cvddc 650, but in fact core voltage is 1050 mV and does not go down.
I know about -powlim key, but I need to use direct core voltage key -cvddc.
Has anyone already encountered this?
Thanks for advance.

[Kiawpqe]

PhoenixMiner.exe -config config-ETC.txt -rmode 1 -tt 1:-37,2:-39,3:-35,4:-41 -eres 100 -proto 3 -cdm 2 -hstats 2 -amd -acm -wdog 1 -log 0 -gpow 100 -fcm 0 -coin etc -clf 1 -clNew 1 -clKernel 1 -clgreen 1 -minRigSpeed 100 -prate 0.15 -gpus 1,2,3,4 -cclock 1160,1160,1160,1160 -cvddc 855,855,855,855 -mclock 2120,2120,2120,2120 -mvddc 865,865,865,865 -pool ssl://eu1-etc.ethermine.org:5555 -wal xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phoenix Miner 5.2a Windows/msvc - Release build
-----------------------------------------------

OpenCL driver version: 20.7-10/20.11.1
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie , OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 12), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 13), OpenCL 2.0, 8 GB VRAM, 36 CUs
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: ssl://eu1-etc.ethermine.org:5555
Starting GPU mining
GPU1: AMD driver 20.9.2
GPU2: AMD driver 20.9.2
GPU3: AMD driver 20.9.2
GPU4: AMD driver 20.9.2
GPU1: switching to alt fan control mode
GPU1: set fixed fan PWM 37%
GPU1: set GPU clocks to 1160 MHz (Vddc 855 mV)
GPU1: set VMEM clocks to 2120 MHz (Vddc 865 mV)
GPU2: switching to alt fan control mode
GPU2: set fixed fan PWM 39%
GPU2: set GPU clocks to 1160 MHz (Vddc 855 mV)
GPU2: set VMEM clocks to 2120 MHz (Vddc 865 mV)
GPU3: switching to alt fan control mode
GPU3: set fixed fan PWM 35%
GPU3: set GPU clocks to 1160 MHz (Vddc 855 mV)
GPU3: set VMEM clocks to 2120 MHz (Vddc 865 mV)
GPU4: switching to alt fan control mode
GPU4: set fixed fan PWM 41%
GPU4: set GPU clocks to 1160 MHz (Vddc 855 mV)
GPU4: set VMEM clocks to 2120 MHz (Vddc 865 mV)
Eth: Connecting to ethash pool ssl://eu1-etc.ethermine.org:5555 (proto: QtMiner)

GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #385
GPU2: Starting up... (0)
GPU3: Starting up... (0)
GPU4: Starting up... (0)
Listening for CDM remote manager at port 3333 in full mode
Eth: New job #bedd1a9c from ssl://eu1-etc.ethermine.org:5555; diff: 4000MH
Light cache generated in 3.6 s (17.6 MB/s)
The option -clGreen 1 is ignored for GPU1
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Allocating DAG (4.01) GB; good for epoch up to #485
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
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)
GPU1: Generating DAG for epoch #385
The option -clGreen 1 is ignored for GPU2
GPU2: Free VRAM: 7.948 GB; used: 0.052 GB
GPU2: Allocating DAG (4.01) GB; good for epoch up to #485
Eth: New job #9cc5e19e from ssl://eu1-etc.ethermine.org:5555; diff: 4000MH
GPU2: Generating DAG for epoch #385
The option -clGreen 1 is ignored for GPU3
GPU1: DAG  23%
GPU3: Free VRAM: 7.948 GB; used: 0.052 GB
GPU3: Allocating DAG (4.01) GB; good for epoch up to #485
GPU3: Generating DAG for epoch #385
The option -clGreen 1 is ignored for GPU4
GPU2: DAG  23%
GPU1: DAG  46%
GPU4: Free VRAM: 7.948 GB; used: 0.052 GB
GPU4: Allocating DAG (4.01) GB; good for epoch up to #485
GPU4: Generating DAG for epoch #385
GPU3: DAG  23%
GPU2: DAG  46%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
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)
GPU1: DAG  68%
GPU4: DAG  23%
GPU3: DAG  46%
GPU2: DAG  68%
GPU1: DAG  86%
GPU4: DAG  46%
GPU3: DAG  68%
GPU1: DAG generated in 7.9 s (520.8 MB/s)
GPU1: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
GPU2: DAG  86%
Eth: New job #37899a81 from ssl://eu1-etc.ethermine.org:5555; diff: 4000MH
GPU4: DAG  68%
GPU3: DAG  89%
GPU2: DAG generated in 7.9 s (521.7 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU2: no -gt value specified, switching to auto-tune
GPU2: starting auto-tune process
GPU3: DAG generated in 7.3 s (561.3 MB/s)
GPU3: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU3: no -gt value specified, switching to auto-tune
GPU3: starting auto-tune process
Eth speed: 47.173 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 23.569 MH/s (0) 2: 23.605 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0)
Eth: New job #c1001438 from ssl://eu1-etc.ethermine.org:5555; diff: 4000MH
GPU4: DAG  86%
GPU4: DAG generated in 7.8 s (526.2 MB/s)
GPU4: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU4: no -gt value specified, switching to auto-tune
GPU4: starting auto-tune process


*** 0:06 *** 11/8 10:56 **************************************
Eth: Mining ETC on ssl://eu1-etc.ethermine.org:5555 for 0:06
Eth: Accepted shares 8 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 6 (42.86%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 16.8 GH (!)
Eth: Average speed (5 min): 122.991 MH/s
Eth: Effective speed: 88.40 MH/s; at pool: 88.40 MH/s

GPU1: 61C 36% 81W, GPU2: 58C 39% 82W, GPU3: 66C 34% 86W, GPU4: 61C 40% 83W
GPU1: cclock 1160 MHz, cvddc 868 mV, mclock 2120 MHz
GPU2: cclock 1160 MHz, cvddc 868 mV, mclock 2120 MHz
GPU3: cclock 1160 MHz, cvddc 868 mV, mclock 2120 MHz
GPU4: cclock 1160 MHz, cvddc 868 mV, mclock 2120 MHz
GPUs power: 333.1 W; cost: 1.20 USD/day

[Kiawpqe]

Eth speed: 119.553 MH/s, shares: 1/0/1, time: 0:01
GPUs: 1: 31.468 MH/s (0) 2: 31.458 MH/s (1) 3: 25.151 MH/s (0) 4: 31.475 MH/s (0/1)

4:RX-580 8Gb
 
3ª: 25.151 MH/s with monitor
  all OK
THX

[Kiawpqe]

Eth speed: 123.107 MH/s, shares: 10/0/0, time: 0:10
GPUs: 1: 30.795 MH/s (4) 2: 30.797 MH/s (2) 3: 30.718 MH/s (3) 4: 30.797 MH/s (1)

*** 0:10 *** 11/8 11:28 **************************************
Eth: Mining ETC on ssl://eu1-etc.ethermine.org:5555 for 0:10
Eth: Accepted shares 10 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 73.6 GH (!)
Eth: Average speed (5 min): 123.106 MH/s
Eth: Effective speed: 63.29 MH/s; at pool: 63.29 MH/s
GPU1: 60C 36% 81W, GPU2: 56C 39% 82W, GPU3: 69C 34% 87W, GPU4: 60C 40% 83W
GPU1: cclock 1160 MHz, cvddc 868 mV, mclock 2115 MHz
GPU2: cclock 1160 MHz, cvddc 868 mV, mclock 2120 MHz
GPU3: cclock 1160 MHz, cvddc 868 mV, mclock 2115 MHz
GPU4: cclock 1160 MHz, cvddc 868 mV, mclock 2115 MHz
GPUs power: 333.0 W; cost: 1.20 USD/day

config more stable,low watt ,low temp.
1shared x 1min,80/85w x gpu,60cº x gpu +69cº with monitor 3ª gpu

[PhoenixMiner]

IMPORTANT! All owners of AMD cards with 6 GB or 8 GB RAM must either use drivers 20.4.x or lower (do not upgrade to 20.5.1 or later), or upgrade to PhoenixMiner 5.2b or later version to continue mining after DAG epoch 384 (ETC has already passed DAG epoch 384, and ETH will pass it in less than two months).

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.2b or later version to continue mining after DAG epoch 373 (set -daglim 1, or see bellow how to use the -daglim option). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.2a and later:

• After the epoch 373 the hashrate will drop dramatically (to just a few MH/s) because the DAG no longer fits in the card's VRAM and part of it is stored in the system memory. Use the option -daglim 1 to use only 4006 MB for the DAG buffer. This will allow you to mine for several more weeks with gradually lower hashrate for each passing DAG epoch. If the speed is too low (less than 10 MH/s for epoch 374), you need to use -daglim 4000, or even lower value - keep trying with lower and lower -daglim values until the speed is jumps higher. Note that this value can be different for each card but as a general rule of thumb, if you are able to mine without problems and speed loss on epoch 373, -daglim 1 should work fine.
• Note that -daglim will only work on Polaris GPUs (RX470, RX480, RX570, RX580, RX590), and the PhoenixMiner 5.2b is still in alpha stage of testing

Additionally, we would like to read feedback about the new -rxboost option for AMD cards with GDDR5 memory, and the straps for AMD Vega cards.

[SpeedY_Hun]

@Phoenixminer: the 5.2a will compatible with the ETCHASH?

[haliy-2017]

Who ran 6 GB on 1060, what did they write in the batch file, what is the speed ETH? Thanks

[NCarter84]

Is it true? Let's take a look at the numbers...

https://bitcointalk.org/index.php?topic=5287578.0

[4play]

I try new version PM 5.2a on my gtx 1070 rig. So far I don't notice any changes compared to the version 5.0e

[Dowper_]

-cdmport is not working in the new version...

[UnclWish]

Is it true? Let's take a look at the numbers...

https://bitcointalk.org/index.php?topic=5287578.0

You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent!

[Lolliedieb]

You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent!

I certainly could write a kernel using way less power (actually one for 8Gs is on the way) ... but pushing that too far would need me to fake the hashrate to get users on it... ahm ... wait...

[NCarter84]

You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent!

I certainly could write a kernel using way less power (actually one for 8Gs is on the way) ... but pushing that too far would need me to fake the hashrate to get users on it... ahm ... wait...

Sorry Lolli that your miner wasn't included but it was after everything already started... Perhaps I will do another one after the 1st of the year for some others that I had missed

[NCarter84]

Is it true? Let's take a look at the numbers...

https://bitcointalk.org/index.php?topic=5287578.0

You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent!

This test was 2 part... Mainly was about how the console hash comes is pretty much always going to be 3.5% higher than at the pool.... There will be days where you actually get it (as you can see in my test, but odds are going to be very slim) Also, TRM produced a better over hashrate, over the course of the year, that .75-1% will add up quickly.

Power on both miners were so close that it was marginal.

[UnclWish]

Is it true? Let's take a look at the numbers...

https://bitcointalk.org/index.php?topic=5287578.0

You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent!

This test was 2 part... Mainly was about how the console hash comes is pretty much always going to be 3.5% higher than at the pool.... There will be days where you actually get it (as you can see in my test, but odds are going to be very slim) Also, TRM produced a better over hashrate, over the course of the year, that .75-1% will add up quickly.

Power on both miners were so close that it was marginal.

I didn't know about your system, but for me PM uses about 1-2% less power only from sensors (overall power economy from wall can be more). So 0.75-1% less efficiency but 1-2% less power.
Until lol and TR didn't lower power draw by their miners for me choise is obvious.

[patinencomun]

3 cards
5700XT, 5700, 480 4GB

PhoenixMiner 5.2a ~19 Mhs with -daglim 3967, any greater daglim produces a hashrate drop to 0-1 Mhs

If I use PhoenixMiner for the 5700 and Lolminer with 480 it makes 30,31Mhs

Driver 20.8.1, Windows.

Any suggestion?