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

[relax69]

Back to being stable

Still no idea why PM 5.9 starts and immediately exits tho'

Just copy/paste the command line or config from V5.8 to V5.9, and it should work.

[alucard20724]

The new beta version is ready. It is mostly a bugfix release, the more significant upgrades are coming next month. You can download PhoenixMiner 6.0a from here:

The new features in this release are:

• Full LHR disable mode -lhrdis <n>  1 - yes (default), 0 - no
• Show the GPU vendor name in the list of GPUs to make it easier to identify the GPUs
• Added support for the latest AMD Linux drivers 21.40.1. There are some bugs in these drivers, particularly the clocks and voltages can't be set properly with older
  cards (RX4x0/RX5x0/Vega/RadeonVII)
• Validated support for the latest AMD Windows drivers up to 21.11.2
• Fixed issues with AMD RX6700XT cards with the latest AMD and Linux drivers
• Fixed issues with AMD Vega and Radeon VII cards on latest Windows and Linux drivers
• Fixed crash with very old Nvidia drivers (3xx.x)
• Other fixes and small improvements

The updated list of known issues (driver incompatibilities, etc.) and workarounds:
AMD Linux driver 21.40.1 has a bug preventing proper setting of clocks and voltages on older cards (RX4x0/RX5x0/Vega/RadeonVII). Given that these drivers are also
usually slower than the older drivers for these cards, we recommend using Linux drivers 20.30 for anything older than RX6000 series.
If you are using Linux drivers 21.40.1 with Radeon VII cards, you need to add the option -fpwm 1 in order to have proper fan control.
AMD Linux drivers 21.40.1 has finally removed the requirement of PCIe atomics but there are problems when you try to mix Polaris (RX4x0/5x0) cards and Vega or newer
cards on the same rig.
Some Nvidia cards will report a lot of stale shares under Windows 11. Using the same driver version under Windows 10 resolves the issue.

SCAM.. ITS NOT FROM OFFICIAL PHOENIXMINER SITE

[pit63]

Latest version, on hiveos and windows, my GTX 1070 make only 27mhs. Before it was always above 30mhs.

How can i get with Phoenix 30mhs?

[BogBeast]

Back to being stable

Still no idea why PM 5.9 starts and immediately exits tho'

Just copy/paste the command line or config from V5.8 to V5.9, and it should work.

What usually works with upgrades before, but now, no...

Won't even work with the supplied batch file.

[TBOEMC]

Latest version, on hiveos and windows, my GTX 1070 make only 27mhs. Before it was always above 30mhs.
How can i get with Phoenix 30mhs?

Its longer time before GTX 1070 do about 27MHs, cause the TLB malfunction...
The DAG is a killer to these cards (1070Ti are not affected).
You can increase core clock +100 or +150 to keep speed around 27MHs, but it will be lower and lower with the DAG size.
Increasing memory clocks above 600 or 700 does nothing now...

[Deafran]

Latest version, on hiveos and windows, my GTX 1070 make only 27mhs. Before it was always above 30mhs.

How can i get with Phoenix 30mhs?

can u share ur setting pls   ....

[relax69]

Back to being stable

Still no idea why PM 5.9 starts and immediately exits tho'

Just copy/paste the command line or config from V5.8 to V5.9, and it should work.

What usually works with upgrades before, but now, no...

Won't even work with the supplied batch file.

Then I would try with older drivers. Dev's did not state anything about Nvidia drivers, but the one you using ( 511.23 ) is brand new released a couple of weeks ago.

[deedeeranged]

I have a rig with 6 x 6700s and 6 Nvidia cards. Windows 10 with latest updates

Has been working ok on 5.8 but has started causing me issues, generating errors on PM start:

Code:

Failed to compile program: clBuildProgram (-11)
Unable to prepare kernels: clCreateKernel (-46)
Fatal error detected. Restarting.

No idea why, has been working and stable(ish) for months. Maybe windows update.

So, I thought it might be time to update, so updated gfx drivers and trying to update to 5.9d, but just starts and immediately exits  

Code:

D:\Test>PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001
Phoenix Miner 5.9d Windows/msvc - Release build
-----------------------------------------------

CUDA version: 11.0, CUDA runtime: 8.0

D:\Test>

Does the same on two of my other rigs, using both my config.txt and the default startminer.cmd


Am I missing something stupid?

So I managed to sort out my issues with 5.8. Windows was insisting on updating the drivers, I had been relying on the DDU option to prevent driver update but this did not seem to work. So I had to edit the local policy GPEDIT to prevent the AMD cards from getting updated

https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/

Back to being stable

Still no idea why PM 5.9 starts and immediately exits tho'

What does nvidia-smi say abt cuda version?

Code:

C:\Windows\system32>nvidia-smi
Tue Jan 25 17:14:28 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 511.23       Driver Version: 511.23       CUDA Version: 11.6     |
|-------------------------------+----------------------+----------------------+

Try uninstalling/clear the driver with DDU and re-install the driver and if that does not work try an older driver. Don't let windows try to install the drivers.

Also install/re-install previous driver from AMD as the one installed might be to new (clBuildProgram error)

Use -acm to activate compute mode for AMD.

[mrbugera2]

it has started last week, and it happens only with phoenix miner.. i cant change miner because i know dual mining only with this miner, which works with zill, so i dont want o change miner, please help 






added exclusion to windows security and lets see maybe it will work 

[moderator's note: consecutive posts merged]

[batsonxl]

Hi all,

I posted this question couple of days before, but was deleted. I wonder why, since it's fully on-topic, and perhaps a simptom of a problem woth PhoenixMiner (or it's just me, but the question is honest).
Well, the cas is  I got an out of memory problem mining ETC (eth classic) with my 3GB nVidia GTX1060, since a couple of days ago.
Coincidentally with change to epoch #238 (5.9d say's to be good up to epoch #240 and 3gb cards should be able to mine etc until june/22 or so).
Any one with the same issue?

This is the command line:
./PhoenixMiner -pool us1-etc.ethermine.org:4444 -wal 0xblablabla -worker myworker -pass x -coin etc

This is the output:
Phoenix Miner 5.9d Linux/gcc - Release build
--------------------------------------------

CUDA version: 11.0, CUDA runtime: 8.0
NVML library initialized
Nvidia driver version: 470.86
OpenCL driver version: 20.40-1147287
Available GPUs for mining:
GPU1: ASUS NVIDIA GeForce GTX 1060 3GB (pcie 1), CUDA cap. 6.1, 3 GB VRAM, 9 CUs

GPU2: ASUS NVIDIA GeForce GTX 1060 3GB (pcie 2), CUDA cap. 6.1, 3 GB VRAM, 9 CUs

Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: us1-etc.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool us1-etc.ethermine.org:4444 (proto: EthProxy)
GPU1: 35C 26% 7W, GPU2: 36C 27% 40W
GPUs power: 47.1 W
Eth: Connected to ethash pool us1-etc.ethermine.org:4444 (172.65.245.119)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #e801904e from us1-etc.ethermine.org:4444; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating etchash light cache for epoch #238
GPU2: Starting up... (0)
Eth: New job #764e3116 from us1-etc.ethermine.org:4444; diff: 4000MH
Light cache generated in 2.0 s (22.7 MB/s)
GPU2: Allocating DAG (2.87) GB; good for epoch up to #240
GPU2: Generating DAG for epoch #238
GPU1: Allocating DAG (2.87) GB; good for epoch up to #240
CUDA error in CudaProgram.cu:393 : out of memory (2)
GPU1: CUDA memory: 2.95 GB total, 2.87 GB free
GPU1 initMiner error: out of memory
Fatal error detected. Restarting.
GPU2 initMiner error: Unable to initialize CUDA miner
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)

Hope somebody could help, and thanks in advance for any hint,

Try add this -eres 0 maybe helps for 2 more epoch. but anyway they will stop later

[kokodesu]

Thank you for your development.
Is it possible to do dual mining of TON with AMD VEGA?

[Digital_Seytan]

Thank you for your development.
Is it possible to do dual mining of TONCOIN or ALEPHiUM with PHOENiXMINER

WHY NO UPDATE PM   DEV  !!!!!!!!

 

[deedeeranged]

Thank you for your development.
Is it possible to do dual mining of TONCOIN or ALEPHiUM with PHOENiXMINER

WHY NO UPDATE PM   DEV  !!!!!!!!

 

A bit impatient?

If you cannot wait use a different miner.

[Helmer Hombron]

PhoenixMiner detects the first GPU twice. As a result, neither the real GPU nor its phantom counterpart works. 

[deedeeranged]

PhoenixMiner detects the first GPU twice. As a result, neither the real GPU nor its phantom counterpart works. 

Windows/Linux which videocard?

I have been using PhoenixMiner for abt. a year in a mixed rig and haven't encountered anything like that.

[majika]

Hey everyone! Hoping to troubleshoot a MATIC mining issue on my end. My graphic card( AMD Radeon RX 6600 XT ) is on the latest driver(22.1.1 released 1/7/2021 …10 days before this post). I seem to be running into an error and cannot move past 0Mh hashrate, along with the error no CUDA driver found, when using version “PhoenixMiner_5.9d_Windows”. I went downgrading version by version and had some success with version “PhoenixMiner_5.5c_Windows” with a 28.6Mh(people seem to be getting higher on newer versions) but thought I would at least illuminate the issue in hope to use a newer version 5.9. Not sure if this is impacting anyone else with an AMD Radeon RX 6600 XT for a graphics card, or because of the newer driver, but any help is appreciated!
-------------->MINER LOG START<--------------

Phoenix Miner 5.9d Windows/msvc - Release build
-----------------------------------------------

No CUDA driver found
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (3354.13)
Available GPUs for mining:
GPU1: MSI AMD Radeon RX 6600 XT (pcie 9), OpenCL 2.0, 8 GB VRAM, 32 CUs
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: etchash.unmineable.com:3333
Starting GPU mining
GPU1: AMD driver 22.1.1
Eth: Connecting to ethash pool etchash.unmineable.com:3333 (proto: EthProxy)
GPU1: 48C 0% 3W
GPUs power: 3.0 W
Eth: Connected to ethash pool etchash.unmineable.com:3333 (165.227.119.242)
Listening for CDM remote manager at port 60080 in read-only mode
Eth: New job #622207c1 from etchash.unmineable.com:3333; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating etchash light cache for epoch #239
Light cache generated in 1.4 s (34.0 MB/s)
GPU1: Free VRAM: 7.922 GB; used: 0.063 GB
GPU1: Allocating DAG (2.88 GB); good for epoch up to #241
GPU1: Generating DAG for epoch #239
GPU1: DAG  24%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  48%
GPU1: DAG  72%
GPU1: DAG  96%
GPU1: DAG generated in 6.4 s (457.8 MB/s)
GPU1: Using Ethash OCL kernels (gfx1032; -clkernel 1 -clnew 0)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
GPU1: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00






Phoenix Miner 5.9d Windows/msvc - Release build
-----------------------------------------------

Waiting 15 s for previous instance to close



-------------->MINER LOG END<--------------

PhoenixMiner doesn't support anything newer than 21.11.3.   I don't know if the drivers are so significantly different to cause this problem every three months, or if PM is just coded to look for specific driver versions and won't even TRY to use the AMD path with newer drivers than what it specifically looks for.   It's annoying, that's for sure.

An easy way to TEST would be to:
1) Create a Symbolic link/Junction link to the latest (Stable AMD supported PM drivers) but RENAME the folder to previous drive yet in the system ENV_VARS  %path%  ../../../%Path_to_Symlink% <== OR PATH_POINT_TO >= build 21.12.x (ABOVE) stable 21.11.3 drivers.
2) I suspect WMI maybe queried by PM and this is how driver version is derived.
3) Ask the dev @PhoenixMiner what the checks are AND if its hardcoded in the code to search for driver version or is it because PM fails because of an incorrect dependency contained in drivers grt > v21.11.3 which PM relies on.. OR missing *.dll it could be a million possible things.
4) It could be that AMD drivers compiled past version 21.11.3have been totally refactored and rebased and what PM relies upon is no longer a resource that is in the codebase any longer, thus fail.
5) It could also be a part of PM's dev workflow to test against a set of Drivers to keep development under control by stipulating a range of supported drivers.
..Buts thats what I would do to try and isolate reasons for fail on latest driver above PM recommended.

[ivvi30]

Hi. Such a mistake began to appear constantly:
Fatal error detected.
What's wrong with how to solve?http://a.radikal.ru/a42/2202/f6/8a8b3be0b36at.jpg

[Dung-beetle_Lives_Matter]

When ETH+TON ?
Please hurry up! Your miner is the best for ETH!

[deedeeranged]

Hi. Such a mistake began to appear constantly:
Fatal error detected.
What's wrong with how to solve?

Not enough info.
Videocard??

[waywoos2]

When ETH+TON ?
Please hurry up! Your miner is the best for ETH!

i cant wait for it either. i am using trm but want to use phoenix asap.