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

[UnclWish]

Errors with the new 21.3.1 AMD drivers:

Code:

2021.03.18:19:09:34.041: GPU1 GPU1: DAG generated in 2.0 s (2166.6 MB/s)
2021.03.18:19:09:34.041: GPU1 GPU1: Using Ethash OCL kernels (gfx1030; -clkernel 1 -clnew 0)
2021.03.18:19:09:34.041: GPU1 GPU1: no -gt value specified, switching to auto-tune
2021.03.18:19:09:34.041: GPU1 GPU1: starting auto-tune process
2021.03.18:19:09:34.041: GPU1 GPU1: clSetKernelArg (-48)
2021.03.18:19:09:34.041: wdog Fatal error detected. Restarting.

Does this normally get fixed, or roll back?

-clKernel 0 fixes it, but don't know how much of a hit to expect yet.

PM just didn't support new 21.3.1 AMD drivers. It's need to wait update for PM.

[PhoenixMiner]

Hi @phoenix it is nice to read your posts,
Waiting new version with straps for polaris cards. By the way 5.4c more stable than 5.5c.

  Straps for Poloaris will be available in the version after the next one (kind of working but not very stable yet).
 
  The only reason for 5.4c working more stable with Polaris than 5.5c is that 5.5c introduced new kernels, which are slightly faster and with lower power consumption with the current DAG epochs on ETH. If you want to use the old kernels, you can still mine with 5.5c but with drivers older than 20.5.1. We may add a command-line option to force the use of the older kernels even on new drivers.

Is anyone running a 6800, 6800XT or 6900XT with SAM enabled with Phoenix miner? I am waiting for mine to come in and I am thinking 100MH/s could be possible with it but would like to see some real world numbers.

There is a few videos on youtube showing just 64MH/s on those cards. I was expecting much more due to the Infinity Cache and it having double the cores of the RX 5700XT maybe the kernels or compute drivers aren't quite there yet.

   Ethash is limited mainly by memory bandwidth and latency. The Infinity cache helps a bit, but SAM wont't improve the hashrate much. RX5700XT had 448 GB/s memory bandwidth, 6800/6900 have 512 GB/s, so not a big improvement.

Sup all..
Nice work on the project guys.. and Fk NHash too

Ok, So i'm having a little problem with loading in the epools.txt.
I have copied over my config.txt/start.bat/epools.txt

For the life of me I cant seem to figure out how to build my config.txt to force PheonixMiner (v5.5c) to use the pools from my epools.txt file.
Its needed to switch pool ports now and then and this will save me restarting miner plus its easier to manage over multiple rigs.

in the example below I have to put in the start_miner.bat the following:
-pool <pool1_nfo>
-pool2 <pool2_nfo>
-wal 0x_WALXXX
-pass x

otherwise it wont start.

I have inside start_miner.bat

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
D:\MiningTools\_PACKAGES\PhoenixMiner_5.5c\PhoenixMiner.exe -proto 2 -coin eth -stales 1 -config D:\MiningTools\_PACKAGES\PhoenixMiner_5.5c\config.txt -pool stratum+tcp://ethash.pool1.com:8888 -pool stratum+tcp://ethash.pool1.com:3333
-pool2 stratum+tcp://ethash.pool1.com:1800 -wal 0x_WALXXX -pass x
pause
exit

My config file looks like so:

Code:

-wal 0x_WALXXX
-pass x
-mode 1
-amd
-acm
-gbase 0
-gser 0
-gpus 0123456789
-altinit
-mi 14
-gt 0
-sci 0
-clKernel 1
-clgreen 1
-clNew 1
-clf 1
-minRigSpeed 250
-dagrestart 2
-lidag 0
-tt 70
-ttli 75
-tmax 85
-tstop 83
-tstart 65
-pidle 145
-prate 0.18
-fanmin -0
-fanmax 100
-fcm 0
-powlim 0
-mt 2
-leavemt
-rxboost 0
-cdm 1
-cdmport <PORT_NFO>
-cdmpass <PWD_NFO>
-cdmrs
-wdog 1
-rmode 1
-wdtimeout 30
-log 1
-logsmaxsize 100
-logfile ETH_<POOL_NAME>_Log.txt$
-logdir D:\MiningTools\_PACKAGES\PhoenixMiner_5.5c\logs
-astats 1

My ePools.txt Looks like so:

Code:

POOL: ethash.pool1.com:1800, WAL: 0x_WALXXX , PASS: x, PROTO: 2, COIN: eth, STALES: 1
POOL: ethash.pool1.com:8888, WAL: 0x_WALXXX , PASS: x, PROTO: 2, COIN: eth, STALES: 1
POOL: ethash.pool1.com:25, WAL: 0x_WALXXX , PASS: x, PROTO: 2, COIN: eth, STALES: 1
POOL: ethash.pool1.com:443, WAL: 0x_WALXXX , PASS: x, PROTO: 2, COIN: eth, STALES: 1
POOL: ethash.pool1.com:3333, WAL: 0x_WALXXX , PASS: x, PROTO: 2, COIN: eth, STALES: 1

..As per instructions.

# PhoenixMiner ethash pools list (you MUST rename this files to epools.txt in order to use it)
#
# The pools specified in this file will be added to the pools specified with the PhoenixMiner's
# command-line options (see -pool and -pool2 command line options).
#
# Alternatively, you can omit the -pool option on the command-line and use only the pools in
# epools.txt file. This will give you the ability to specify more than two pools, and to change
# the pools without restarting the miner by using the 'r' key in the PhoenixMiner console to
# reload the epools.txt file.

Now when i try to omit -pool and -pool2 from inside my start_miner.bat its no Bueno.. fail to start..

I execute start_miner.bat "As Administrator"
I have check file permissions..

I am probably missing something really simple but cant seem to spot where the issue is.
If you guys could take a look to see and point out the obvious i would much appreciate the help..

Cheer's Maj.

    The pools that are specified on the command-line with -pool and -pool2 are always used as first and second pool respectively. You just need to remove them from the command line and use only epools.txt to specify the pools. Also note the change of the current drive letter to D: and the change of the directory that are added before your bat file in order to make sure that PhoenixMiner can find the epools.txt file. Finally, you need to specify the wallets in the epools.txt only, so remove any -wal, -pool, or -pass options from your config.txt file too.

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
D:
cd \MiningTools\_PACKAGES\PhoenixMiner_5.5c\
PhoenixMiner.exe -proto 2 -coin eth -stales 1 -config config.txt
pause
exit

I have Win 10 LTSC, AMD driver 21.2.2, PheonixMiner 5.5c.

I get about 50Mhs on my RX 6700, but I am only getting about 7Mh/s on my 8GB RX 470. I think my 8GB RX 470 used to get almost 30Mh/s.

Any ideas why my RX 470 is so slow?

   Switch to Compute Mode in AMD control center (in the section Advanced settings of the GPU).

Errors with the new 21.3.1 AMD drivers:

Code:

2021.03.18:19:09:34.041: GPU1 GPU1: DAG generated in 2.0 s (2166.6 MB/s)
....

Does this normally get fixed, or roll back?

-clKernel 0 fixes it, but don't know how much of a hit to expect yet.

Same with 20.50 drivers on linux.

    AMD drivers 20.3.1 (Windows) and 20.50 (Linux) are not supported by PhoenixMiner 5.5c. Do not upgrade to them, or you will get errors, lower hashrate, high stale shares, etc. Support for these drivers will be added in the next release of PhoenixMiner.

[Verbl Kint]

I have been using PhoenixMiner 5.5c using the 21.2.2 AMD drivers.  I have 6 RX 6800s and 1 RX 5700 all in the same rig.  6800's are currently running at 63 MHs and up with the 5700 at 52.5 MHs. 

Longest uptime for this rig was 70+ hours before it crashed.  I now follow a 48 hour reboot routine (I want to use Linux but will wait for the next PM version).

Settings for the 6800s are (using Adrenalin, not MSI):

• Core Clock: 1500 MHz
• Memclock: 2100 MHz (Gigabyte), 2110 MHz (PowerColor)
• Core Voltage: 1025 MHz
• Fast timings on
• Power Limit: +5
• Fan curve: 100% at 90C, 90% at 80C, 75% at 70C, 60% at 60C, 40% at 50C

Temps are 55C to 59C for the RX 6800s.  Total wattage used for all 7 GPUs is 905w (as seen on the console), with about 432 MHs for all 7 cards.  Note that the 6800s leap to just over 70 MHs about once every couple of hours and stays there for about 2-4 minutes, depending on difficulty level.


Hope the PM devs can figure out how to keep that 70 MHs number permanent and consistent. 

[majika]

@PheonixMiner - FIXED ..Genius mate !

The pools that are specified on the command-line with -pool and -pool2 are always used as first and second pool respectively. You just need to remove them from the command line and use only epools.txt to specify the pools. Also note the change of the current drive letter to D: and the change of the directory that are added before your bat file in order to make sure that PhoenixMiner can find the epools.txt file. Finally, you need to specify the wallets in the epools.txt only, so remove any -wal, -pool, or -pass options from your config.txt file too[/b].

Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
D:  <=============================== BINGO! Perfect !!
cd \MiningTools\_PACKAGES\PhoenixMiner_5.5c\
PhoenixMiner.exe -proto 2 -coin eth -stales 1 -config config.txt
pause
exit

TYVM

[TBOEMC]

I can confirm, that RTX 3060 12GB with driver version 470.05
memory +1000
ETHash algo - 47.7MH/s
happy mining

If anyone wants to download this driver, there is a ZIP package.
https://webshare.cz/#/file/b9ddT7wy5u
Of course - beware of faked links, viruses etc - blah blah, you know.
I had to install this driver manually, not with installator.
I have few 3060 12GB cards - Palit Dual OC.
All of those cards must have dummy plugs (or monitors) and be in x16 port (or x16 riser)
After that i have the speed written above (about 47.8MH/s Phoenix 5.5c)

happy mining, bros...

[tassu]

Ok I came here and made an account only to tell everyone hello and thanks to the Phoenix Miner devs. The incident with NH made me research more as I am pretty "new to mining" (knew about it since 2018 but started only this year - yea, sucks to be me). I wanted to say that I am very very thankful for PH devs and totally agree with their anonimity. Unfortunately I am still using NH as it is a painless method of getting the cash out or setting it to USDT/C before drop. So far PH has been giving me the best results in learning to operate and tweak my gpu. Maybe one day I will become a full time miner with lots of racks. Time will tell!

[alucard20724]

    AMD drivers 20.3.1 (Windows) and 20.50 (Linux) are not supported by PhoenixMiner 5.5c. Do not upgrade to them, or you will get errors, lower hashrate, high stale shares, etc. Support for these drivers will be added in the next release of PhoenixMiner.

will the next release add support for the 6700XT also?

[majika]

Hi @PheonixMiner

Possible feature request

Built-in  - Stratum Pool Port Ping Tool

Some mining pools specify multiple ports for miners to connect to and in some cases these ports are not necessarily load balanced / geo-location specific ports
so, to ensure lowest possible stale shares, etc I run ping the ports offered by the mining pool frequently and when I notice the share times beginning to climb higher.

I used to test latency times the old fashioned way using ping.exe util but this is not very accurate way as stratum is not same as tcpip right, its like on its own layer..
Anyway, I discovered : stratum-ping [git:// >> https://github.com/2miners/stratum-ping]

USAGE

Code:

Usage of ./stratum-ping:
  -6    use ipv6
  -c int
        stop after <count> replies (default 5)
  -p string
        pass (default "x")
  -t string
        stratum type: stratum1, stratum2 (default "stratum2")
  -tls
        use TLS
  -u string
        login (default "0x63a14c53f676f34847b5e6179c4f5f5a07f0b1ed")

Now, in my head having some kind of feature which is already built-in to PheonixMiner which you could either constantly run a ping trace in the background of the miner (Resource intensive)
or have the stratum-ping util fire-off a ping every XX seconds and query against the pool ports listed in the epools.txt list 'or' -pool and -pool2

So, PheonixMiner would then track if there is a deviation from the mean latency times or the current pool over the past 15mins (for example)  Or if the ping-times drift outside of a set profile / tolerance configured by the user (Like: +125ms now time to hop to next port).
 
Kind of like, it could either be set to auto switch the miner onto the port with the lowest ping time or just echo:-  "+xx ms faster if switching to port 8888" a report back in console with the recommendation to switch to a faster port (on the same pool)

I mean this is a cool feature to have to monitor port ping times in real-time to ensure shares being sent to a pool are optimised.

but at the same time, additional cpu usage comes at a cost when making a miner when all processing power counts to getting better hashrates.

IDK.. maybe this is something that other miners want to see in a miner. its definitely something I use frequently as it seems the pool latency climbs up overnight and in the .am its high so i switch ports and latency falls again.

..or just have the pheonixMiner set to switch to the fastest port every 2.5hrs or something maybe.. idk..

Food for Thought

[doncoyote]

    AMD drivers 21.3.1 (Windows) and 20.50 (Linux) are not supported by PhoenixMiner 5.5c. Do not upgrade to them, or you will get errors, lower hashrate, high stale shares, etc. Support for these drivers will be added in the next release of PhoenixMiner.

I'm using AMD drivers 21.3.1 (Windows) in 5.5c with my RX 6800 getting 63 MH/s, no errors, 2% stales (1 in 55 valid shares), so it's very weird.
I tried AMD drivers 20.11.2 (WHQL) and were very buggy, 35 MH/s or something.

[User_86]

I used to test latency times the old fashioned way using ping.exe util but this is not very accurate way as stratum is not same as tcpip right, its like on its own layer..

Ping uses ICMP packets, not TCP/IP packets. ;-)

[Leftarmer]

Has anyone seen this?  What do we make of this?

STOP using Phoenix miner immediately!
https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

[didouday]

I used to test latency times the old fashioned way using ping.exe util but this is not very accurate way as stratum is not same as tcpip right, its like on its own layer..

Ping uses ICMP packets, not TCP/IP packets. ;-)

It does use the TCP/IP Protocol, most specifically at Layer 3 : IP.

[P00P135]

Has anyone seen this?  What do we make of this?

STOP using Phoenix miner immediately!
https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

Did you just wake up out of coma? This has already been discussed and resolved.

[Leftarmer]

I found the thread.. thanks

Has anyone seen this?  What do we make of this?

STOP using Phoenix miner immediately!
https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

Did you just wake up out of coma? This has already been discussed and resolved.

[doncoyote]

Has anyone seen this?  What do we make of this?

STOP using Phoenix miner immediately!
https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

garbage

[Hackintoshihope]

Why doesnt this work anymore?

phoniex miner cant set memory clock delta -137

I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950

[earlybird36]

Why doesnt this work anymore?

phoniex miner cant set memory clock delta -137

I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950

did you run phoenixminer as administrator?

[majika]

I used to test latency times the old fashioned way using ping.exe util but this is not very accurate way as stratum is not same as tcpip right, its like on its own layer..

Ping uses ICMP packets, not TCP/IP packets. ;-)

It does use the TCP/IP Protocol, most specifically at Layer 3 : IP.

ICMP packtz yeah.. OSI layer 3 yeh indeed..  As per the ping utility output, my bad I should have took time to look it up properly, im a bit rusty when it comes to transport protocols, its been a while

Ok so .. any ideas on how to integrate this util into PheonixMiner..  I know its ultimately down to dev for some kind of hard-integration. but maybe there is a way to tie it in with "Claymore's Remote Manager" or some other mining monitoring tool/app of same ilk.
I don't use anything apart from PuTTY/vnc/Teamviewver to track my rigs.

BUT.. Ive been thinking on it a little and what about using Claymore's Miner manager to fire off ping batch onEvent.
IDK.. if any .bat scripters wanting to take a look at ways to implement automated ping tool to compliment pheonixminer..

One potential ugly method to make this work would be to leverage Claymore's Miner Monitor tool to track the rigs hashrate and the setting where it report *if* hashrate drops do XYZ Mh/s, instead of having it "action" reboot.bat or whatever only when hashrate drops, instead set a really tight hashrate value so when the rig fluctuates/deviate's even just a couple of hashes per sec.,  claymore monitor will ping off a bat file that does the pool ping routine.. idk what the polling time is between the PheonixMiner and Claymore's Miner manager hence why this is a ugly way to potentially achieve this without use of some kind of static scheduled task. plus this woudl still involve hands-on to switch pools from epools.txt..
so yeah thinking out loud here..
I reckon it would be a really helpful feature, Especially when looking at times like this..

Code:

Eth: Share accepted in 688163 ms <=============

[jethro777]

I have RX5700 all with modified BIOSes. The version 5.5c is the most stable version I have tried. I easily get mining campaigns of a week or more now. I had continual crashes with 5.4c that were supremely annoying. I am not sure what drivers I am using.

[Hackintoshihope]

Why doesnt this work anymore?

phoniex miner cant set memory clock delta -137

I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950

did you run phoenixminer as administrator?

This was it I forgot I needed to do this...