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

[UnclWish]

Version 4.2c have full support AMD drivers up to 19.4.3.
Miner need update to support OpenCL from 19.5.1 driver.

Are there some big openCL changes in 19.5.1 that broke compatibility?

I don't see anything related in release notes:

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-5-1

Who knows what AMD changed... But it's the fact, I checked. We need miner update if we want to use AMD 19.5.1+ driver...

If I update to the newest AMD driver. Will it affect GPU order 1,2,3,4,5,6 that I have today?

I think, no. But until you didn't try we can't know it exactly...

[CryptoDan132]

I have the PhoenixMiner running for 2 days with no Problems so far. I cant confirm connection problems after long running times.

There is another Problem but it has nothing to do with the PhoenixMiner i think
-> My stats wont show up on Ethashpool, i changed the default wallet to mine, its also the same that shows up in the logs when i start the Miner.
Is this normal? I know from other pools that my stats will show up there even after only a few minutes of mining.

[rockyO]

I am having issue of frequent disconnection on ethermine pool. I have tried claymore also but same issue. but when using nanopool or any other it works fine.


2019.05.17:23:17:24.350: eths Eth: Unable to read pool response: An existing connection was forcibly closed by the remote host
2019.05.17:23:17:24.351: eths Eth: Reconnecting in 10 seconds...
2019.05.17:23:17:27.230: main 

does anyone has any clue as ethermine team says they are not seeing nay disconnect log, but I get it every 1-2 mins..

[DBIXDBIX]

Teslafunds-TSF(ETHASH) digifinex airdrop

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

be ready

[Cryptee80]

Do you guys have an idea why my GPU1 (RX580 with HDMI dummy plug) would be doing only 24Mh/s where as 4 other cards are all doing 31mh/s? In Claymore this card gets 31Mh/s with all the same settings.

Am I missing something?

[nitrobg]

Can't really search the thread, so I'll report a bug here. On NVIDIA rigs, the main display card (GPU0) crashes during DAG switch - this usually happens on 1080 and 1080 Ti. The main reason seems to be that the cards briefly go from loaded P2 to unloaded P0 during the switch, which brings them to unstable memory clocks.

[ManDoneKTM]

Can't really search the thread, so I'll report a bug here. On NVIDIA rigs, the main display card (GPU0) crashes during DAG switch - this usually happens on 1080 and 1080 Ti. The main reason seems to be that the cards briefly go from loaded P2 to unloaded P0 during the switch, which brings them to unstable memory clocks.

you have to post the log , whatever your post will be null without logs

[laik2]

Can't really search the thread, so I'll report a bug here. On NVIDIA rigs, the main display card (GPU0) crashes during DAG switch - this usually happens on 1080 and 1080 Ti. The main reason seems to be that the cards briefly go from loaded P2 to unloaded P0 during the switch, which brings them to unstable memory clocks.

This is usually caused by nvidia driver bug, try using low intensity dag loading or reduce your memclk( usually the pill crashes it, not the miner ).

[nitrobg]

This is usually caused by nvidia driver bug, try using low intensity dag loading or reduce your memclk( usually the pill crashes it, not the miner ).

Switching briefly from P2 to P0 is not a driver bug, that's how the P-states work on nvidia. There's a workaround on Windows, but Linux has no such settings. I'll try to check the GPU clocks when a dag is being switched to see whether my suspicions are correct.
All ethash miners experience the same issue, except Claymore.

Edit - looks like my suspicions are correct:

Code:

#Date       Time        gpu   pwr  temp    sm   mem   enc   dec  mclk  pclk
#YYYYMMDD   HH:MM:SS    Idx     W     C     %     %     %     %   MHz   MHz
 20190519   14:27:01      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:02      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:03      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:04      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:05      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:06      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:07      0   160    67   100   100     0     0  5613  1531
 20190519   14:27:08      0    63    66     0     0     0     0  5613  1544
 20190519   14:27:09      0    69    65     3     0     0     0  6106  1556
 20190519   14:27:10      0 < this is where it crashed

This is while the DAG switches to another one. Note the mclk column.

[jdash]

using hiveos running with the latest hive OS
anyone has encountered these error

phoenixminer exited, waiting to cooldown a bit


using p106 cards
i cant seem to run the hiveos on phoenixminer

thanks

[Madenim.Org]

Hello phoenix devs, i will use -proto 4(nicehash) mining mode but this mod not using mining.hashrate method, please add this mode to program. Thank you.

[laik2]

This is usually caused by nvidia driver bug, try using low intensity dag loading or reduce your memclk( usually the pill crashes it, not the miner ).

Switching briefly from P2 to P0 is not a driver bug, that's how the P-states work on nvidia. There's a workaround on Windows, but Linux has no such settings. I'll try to check the GPU clocks when a dag is being switched to see whether my suspicions are correct.
All ethash miners experience the same issue, except Claymore.

Edit - looks like my suspicions are correct:

Code:

#Date       Time        gpu   pwr  temp    sm   mem   enc   dec  mclk  pclk
#YYYYMMDD   HH:MM:SS    Idx     W     C     %     %     %     %   MHz   MHz
 20190519   14:27:01      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:02      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:03      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:04      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:05      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:06      0   159    67   100   100     0     0  5613  1531
 20190519   14:27:07      0   160    67   100   100     0     0  5613  1531
 20190519   14:27:08      0    63    66     0     0     0     0  5613  1544
 20190519   14:27:09      0    69    65     3     0     0     0  6106  1556
 20190519   14:27:10      0 < this is where it crashed

This is while the DAG switches to another one. Note the mclk column.

Yes there are settings to bypass that issue from P0 to P2 in linux while compute is idling. Not going to further discuss this because its not related to miner at all.

[ManDoneKTM]

Hehe ... seems to be silence here ... no response from the OP ... Really weird . 

[Altcoinlog]

Altcoinlog about Phoenix miner



The official website and instructions for setting up the Phoenix Miner. Comparison of TOP 3 programs for mining and expert conclusion. How to start mining ETH and possible installation problems.

The article is written in Russian.

https://altcoinlog.com/download-phoenix-miner/

[UselessGuru]

Version 4.2c have full support AMD drivers up to 19.4.3.
Miner need update to support OpenCL from 19.5.1 driver.

Same here...

[sirkorro]

using hiveos running with the latest hive OS
anyone has encountered these error

phoenixminer exited, waiting to cooldown a bit

Had the same issue. It's related to wrong miner config.
Here is mine:
https://i.postimg.cc/HLssN5Fy/Greenshot-2019-05-23-09-28-58.png

[big_daddy]

is anyone mining with the last AMD driver using PhoenixMiner 4.2c?
if not, what is the last supported

tnx

[UnclWish]

is anyone mining with the last AMD driver using PhoenixMiner 4.2c?
if not, what is the last supported

tnx

Read 2 post up. 4.2c full supports driver up to 19.4.3

[Digital_Seytan]

AMD Best version works with nofee is phoenixminer 3.5  with nodevfee https://mirrorace.com/m/2SD23

[big_daddy]

is anyone mining with the last AMD driver using PhoenixMiner 4.2c?
if not, what is the last supported

tnx

Read 2 post up. 4.2c full supports driver up to 19.4.3

o sorry, I was on my mobile and passed through it