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

[swogerino]

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

Not enough info.
Videocard??

1060 6gb

I had the  same issue with Phoenix miner if I start it with the overclock going on in my Nvidia cards,I start the miner with default settings for the Nvidia cards and then I put in place the overclock,most likely this is a memory issue as I see this when my memory clocks are high enough usually over 1000 for my 3000 series but for the 10 series should start seeing this once you pass the 750 mark.

[1715224938]

1715224938

[1715224938]

1715224938

[1715224938]

1715224938

[Real-Duke]

I still use the "old" PhoenixMiner 5.9d with my nvidia 2070 (not super) and latest nvidia driver.
No hesitate to make any changes for 0,5% more profit.

[PhoenixMiner]

The new beta version is ready. You can download PhoenixMiner 6.0b from here:

PhoenixMiner_6.0b_Windows.zip
PhoenixMiner_6.0b_Linux.tar.gz

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_6.0b_Windows.zip
    ===================================
   SHA-1: 38730224ef10963322b4d950a726438497ca66c1
 SHA-256: f2c66cc5ba9ddac440a8206d1aa9becb74bd819b8811149501be35736589596e
 SHA-512: 9b758939c87f56e83cf27d417238e4c4f4ace8049519715c6efef43892e94ffb0504e6037764986bc04fe4fa2124a39998399e480e55e3eca7c6461ea022a754

    File: PhoenixMiner_6.0b_Linux.tar.gz
    ====================================
   SHA-1: dbf2edbf964dd51fee5b2b6136213a7a81943fb9
 SHA-256: 16cc12acaad323036e9cce87a8312f5d5cbdd665420f6d0c23d92cd22f0187da
 SHA-512: d706a9f41f629418773135bfbbd58442a204841ee709a4e4b9b73c738ca0e07a4d90fbdb4b65a1a9be972c07407068f1c9bc162f4a2e9a2be87ab3120113a1a3

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

The new features in this release are:

• Implemented partial unlocking of Nvidia LHR cards. By default they are detected automatically, and unlocked with the default unlock intensity (520). If you want to try higher (or lower) LHR unlock intensity, use the new -lhr command line parameter. For example -lhr 580 will try more aggressive unlocking than the default 520 unlock intensity. This parameter may (and should) be specified for each GPU separately as some GPUs can support higher unlocked speeds.
• If an Nvidia LHR card locks up because of high -lhr (the default 520 will work with most cards), the card will be unlocked again, and the -lhr value will be lowered if necessary
• Added support for new AMD Windows drivers up to driver version 22.2.3
• Multiple other small fixes and improvements

The updated list of known issues (driver incompatibilities, etc.) and workarounds:

• The new Nvidia 3050 and 3080 12GB cards have different kind of LHR lock, which is not supported yet.
• The latest AMD Linux drivers 21.50 are not supported; the AMD Linux drivers 21.40.2 aren't verified also - this will be added in the final release of 6.0 next week.
• 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.

For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869. Here are the signatures for the files in this release:

• PhoenixMiner_6.0b_Windows.zip.asc
• PhoenixMiner_6.0b_Linux.tar.gz.asc
• PhoenixMiner_NVRTC_Windows.zip.asc

Please disregard any posts with "new" versions of PhoenixMiner in this thread unless they are from our user account, and the files are hosted on our web server: https://phoenixminer.info/

[speed07]

The new beta version is ready. You can download PhoenixMiner 6.0b from here:

PhoenixMiner_6.0b_Windows.zip
PhoenixMiner_6.0b_Linux.tar.gz

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_6.0b_Windows.zip
    ===================================
   SHA-1: 38730224ef10963322b4d950a726438497ca66c1
 SHA-256: f2c66cc5ba9ddac440a8206d1aa9becb74bd819b8811149501be35736589596e
 SHA-512: 9b758939c87f56e83cf27d417238e4c4f4ace8049519715c6efef43892e94ffb0504e6037764986bc04fe4fa2124a39998399e480e55e3eca7c6461ea022a754

    File: PhoenixMiner_6.0b_Linux.tar.gz
    ====================================
   SHA-1: dbf2edbf964dd51fee5b2b6136213a7a81943fb9
 SHA-256: 16cc12acaad323036e9cce87a8312f5d5cbdd665420f6d0c23d92cd22f0187da
 SHA-512: d706a9f41f629418773135bfbbd58442a204841ee709a4e4b9b73c738ca0e07a4d90fbdb4b65a1a9be972c07407068f1c9bc162f4a2e9a2be87ab3120113a1a3

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

The new features in this release are:

• Implemented partial unlocking of Nvidia LHR cards. By default they are detected automatically, and unlocked with the default unlock intensity (520). If you want to try higher (or lower) LHR unlock intensity, use the new -lhr command line parameter. For example -lhr 580 will try more aggressive unlocking than the default 520 unlock intensity. This parameter may (and should) be specified for each GPU separately as some GPUs can support higher unlocked speeds.
• If an Nvidia LHR card locks up because of high -lhr (the default 520 will work with most cards), the card will be unlocked again, and the -lhr value will be lowered if necessary
• Added support for new AMD Windows drivers up to driver version 22.2.3
• Multiple other small fixes and improvements

The updated list of known issues (driver incompatibilities, etc.) and workarounds:

• The new Nvidia 3050 and 3080 12GB cards have different kind of LHR lock, which is not supported yet.
• The latest AMD Linux drivers 21.50 are not supported; the AMD Linux drivers 21.40.2 aren't verified also - this will be added in the final release of 6.0 next week.
• 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.

For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869. Here are the signatures for the files in this release:

• PhoenixMiner_6.0b_Windows.zip.asc
• PhoenixMiner_6.0b_Linux.tar.gz.asc
• PhoenixMiner_NVRTC_Windows.zip.asc

Please disregard any posts with "new" versions of PhoenixMiner in this thread unless they are from our user account, and the files are hosted on our web server: https://phoenixminer.info/

hi bro, can -mt on linux?

[xuzicheng1001]

Why not support SSL

[ctp9]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

[makipsee]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

You can use the miner Zilminer and it will start and stop a second miner.

[defoto]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

PhoenixMiner.exe -pool ssl://eu.ezil.me:24443 -proto 2 -wal EthWallet.zilWalet -worker etc -vmr 70 -gt 90 -acm -mclock 2100 -gpus 3 -amd -coin etc -mi 13 -eres 0 -clKernel 2 -stales 0  -cclock 1250 -cvddc 900 -mvddc 900 -fret 8 -ptimeout 5 

[ctp9]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

PhoenixMiner.exe -pool ssl://eu.ezil.me:24443 -proto 2 -wal EthWallet.zilWalet -worker etc -vmr 70 -gt 90 -acm -mclock 2100 -gpus 3 -amd -coin etc -mi 13 -eres 0 -clKernel 2 -stales 0  -cclock 1250 -cvddc 900 -mvddc 900 -fret 8 -ptimeout 5  

Thank you but this configuration doesn't point ETH to, say... Ethermine, and Zil to another pool.

I'm looking for a configuration where I can point ETH to one pool - and Zil to ANOTHER pool...

[swogerino]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

PhoenixMiner.exe -pool ssl://eu.ezil.me:24443 -proto 2 -wal EthWallet.zilWalet -worker etc -vmr 70 -gt 90 -acm -mclock 2100 -gpus 3 -amd -coin etc -mi 13 -eres 0 -clKernel 2 -stales 0  -cclock 1250 -cvddc 900 -mvddc 900 -fret 8 -ptimeout 5  

Thank you but this configuration doesn't point ETH to, say... Ethermine, and Zil to another pool.

I'm looking for a configuration where I can point ETH to one pool - and Zil to ANOTHER pool...

I don't know any such configuration as of yet,you either do dual mining in the same pool,at least for ETH+ZIL as I have not seen different pools during the dual mining and it doesn't make sense.Another thing is that ZIL is usually only mined once in every 90 minutes and it is not worthy to mine it alone in another pool that is why the developers have chosen this way as they say to be more eco friendly,to mine it for very little time together with another algorithm.I use Ezil.eu pool for dual mining ETC+ZIL for my 4GB cards but yet I don't know if what you are asking is supported in any pool or miner.

[defoto]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

PhoenixMiner.exe -pool ssl://eu.ezil.me:24443 -proto 2 -wal EthWallet.zilWalet -worker etc -vmr 70 -gt 90 -acm -mclock 2100 -gpus 3 -amd -coin etc -mi 13 -eres 0 -clKernel 2 -stales 0  -cclock 1250 -cvddc 900 -mvddc 900 -fret 8 -ptimeout 5  

Thank you but this configuration doesn't point ETH to, say... Ethermine, and Zil to another pool.

I'm looking for a configuration where I can point ETH to one pool - and Zil to ANOTHER pool...

I don't know any such configuration as of yet,you either do dual mining in the same pool,at least for ETH+ZIL as I have not seen different pools during the dual mining and it doesn't make sense.Another thing is that ZIL is usually only mined once in every 90 minutes and it is not worthy to mine it alone in another pool that is why the developers have chosen this way as they say to be more eco friendly,to mine it for very little time together with another algorithm.I use Ezil.eu pool for dual mining ETC+ZIL for my 4GB cards but yet I don't know if what you are asking is supported in any pool or miner.

in youtube uses hiveOS, but they use trm https://www.youtube.com/watch?v=JAqcWacUBZw&t=504s

[ctp9]

So is anyone mining ETH on one pool and ZIL on another pool? What are the command line arguments to make this configuration work? I cannot find anything relevant in the documentation in regards to mining ETH+ZIL on different pools...

PhoenixMiner.exe -pool ssl://eu.ezil.me:24443 -proto 2 -wal EthWallet.zilWalet -worker etc -vmr 70 -gt 90 -acm -mclock 2100 -gpus 3 -amd -coin etc -mi 13 -eres 0 -clKernel 2 -stales 0  -cclock 1250 -cvddc 900 -mvddc 900 -fret 8 -ptimeout 5  

Thank you but this configuration doesn't point ETH to, say... Ethermine, and Zil to another pool.

I'm looking for a configuration where I can point ETH to one pool - and Zil to ANOTHER pool...

I don't know any such configuration as of yet,you either do dual mining in the same pool,at least for ETH+ZIL as I have not seen different pools during the dual mining and it doesn't make sense.Another thing is that ZIL is usually only mined once in every 90 minutes and it is not worthy to mine it alone in another pool that is why the developers have chosen this way as they say to be more eco friendly,to mine it for very little time together with another algorithm.I use Ezil.eu pool for dual mining ETC+ZIL for my 4GB cards but yet I don't know if what you are asking is supported in any pool or miner.

in youtube uses hiveOS, but they use trm https://www.youtube.com/watch?v=JAqcWacUBZw&t=504s

I actually know how to do this with T-Rex and TRM, but I am looking specifically for instructions on making this work with PhoenixMiner.

[Digital_Seytan]

PhoenixMiner link=topic=2647654.msg56755869#msg56755869 date=1618108079]
Here is how we are going to proceed to publish our singing GnuPG key, and verify that it is in fact ours:

• Our GpuPG key pair is already generated and tested
• We will make a transaction from our defvee account at 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E to an address 0xF9403D7EAE2AC5F4C361015E654C5927EE163067 that is the same as the fingerprint of
  
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  !       Devfee phoenixminer adres  :  0x007b689F699bfcCEe48049Db9d3D139872dB8692      !
  !                                                              0x00d4405692b9F4f2Eb9E99Aee053aF257c521343       !
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[batsonxl]

im still using 5.4c version for my old polaris cards.
@phoenix is there any update to add ETH+TON or ETH+ALPH or ETC+TON

[waywoos2]

im still using 5.4c version for my old polaris cards.
@phoenix is there any update to add ETH+TON or ETH+ALPH or ETC+TON

i stopped using phoenix because lack of dual
hoping i can go back to phoenix
please and thanks

[OgNasty]

im still using 5.4c version for my old polaris cards.
@phoenix is there any update to add ETH+TON or ETH+ALPH or ETC+TON

i stopped using phoenix because lack of dual
hoping i can go back to phoenix
please and thanks

Does dual mining really increase rewards that much?  I have always avoided it because the one time I did try, I found that mining a single chain actually produced better results.  Has the tech improved and everyone should be dual mining now, or are there certain cards where this makes sense while others do not?  I'm genuinely curious because all of the miners seem to have dual mining options these days, yet I can't seem to figure out how this would be beneficial when I consider my own results (admittedly a long time ago).  If anyone has any information or a resource to help me learn more about dual mining and if it is worth it, I would be appreciative.  Thanks!

[swogerino]

im still using 5.4c version for my old polaris cards.
@phoenix is there any update to add ETH+TON or ETH+ALPH or ETC+TON

i stopped using phoenix because lack of dual
hoping i can go back to phoenix
please and thanks

Does dual mining really increase rewards that much?  I have always avoided it because the one time I did try, I found that mining a single chain actually produced better results.  Has the tech improved and everyone should be dual mining now, or are there certain cards where this makes sense while others do not?  I'm genuinely curious because all of the miners seem to have dual mining options these days, yet I can't seem to figure out how this would be beneficial when I consider my own results (admittedly a long time ago).  If anyone has any information or a resource to help me learn more about dual mining and if it is worth it, I would be appreciative.  Thanks!

I can tell you my personal experience in ETC+ZIL which I dual mined with my 4GB cards and I got like 0.10 ETC plus like 3-4 ZILS,I did it so for a long time then I saw that with that amount of Mhsh I had I would get like 0.05 ETC more daily if I mined only ETC and so I got back to single mining because 0.05 ETC is surely more than 3-4 ZIL which are just 0.20 USD now.Personally I think the only advantage that dual mining has is for people who has LHR cards from Nvidia and miners offering dual mining for LHR cards somewhat gave better rewards in terms of dollar daily.

[PhoenixMiner]

PhoenixMiner 6.0c is officially released. You can find the download links and the checksums in this post, or in the first post of this thread.

You can download PhoenixMiner 6.0c from here:

PhoenixMiner_6.0c_Windows.zip
PhoenixMiner_6.0c_Linux.tar.gz

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_6.0c_Windows.zip
    ===================================
   SHA-1: ae8819916641a500b9837d2cf921d059db3aab5e
 SHA-256: d77c667ffc3275a51bcfd5a53c7799a32a17386154cec1f87c44a626586027c0
 SHA-512: 92f257489d702db8c19670659231c4e3d8b17a301259d00f07fcda7e8a0369a4633c315a226aedbab962d341a5edb83c4b4837ef239aebaa30a830a1e0f3b6f7

    File: PhoenixMiner_6.0c_Linux.tar.gz
    ====================================
   SHA-1: ff4498c8c3e42a887ea103a2e9e18ec11dc85b48
 SHA-256: 9e6bfbdb37b1c41f6d7254d3f1560a42d2dc316a68a36cfbacee0aba95835afb
 SHA-512: d330bcfc7b04550264022bd11da20a81f61b3d0c0bfd30f78bab7eabd4c6e0d6348bc33986f8c758b57bc65992fe1dc65f3f90083bea0db09a74af04ca792938

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

The new features in this release are (since the last official release 5.9d):

• Implemented partial unlocking of Nvidia LHR cards. By default they are detected automatically, and unlocked with the default unlock intensity (520). If you want to try higher (or lower) LHR unlock intensity, use the new -lhr command line parameter. For example -lhr 580 will try more aggressive unlocking than the default 520 unlock intensity. This parameter may (and should) be specified for each GPU separately as some GPUs can support higher unlocked speeds.
• If an Nvidia LHR card locks up because of high -lhr (the default 520 will work with most cards), the card will be unlocked again, and the -lhr value will be lowered if necessary
• Added support for new AMD Windows drivers up to latest driver version 22.2.3
• Added support for new AMD Linux drivers up to latest driver version 21.50
• Multiple other small fixes and improvements

The updated list of known issues (driver incompatibilities, etc.) and workarounds:

• The new Nvidia 3050 and 3080 12GB cards have different kind of LHR lock, which is not supported yet by PhoenixMiner.
• When mining with LHR cards, the hashrate will start lower and will go up to its normal value in about 2-4 minutes (similar to the auto-tune process on AMD cards).
• 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.

For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869. Here are the signatures for the files in this release:

• PhoenixMiner_6.0c_Windows.zip.asc
• PhoenixMiner_6.0c_Linux.tar.gz.asc
• PhoenixMiner_NVRTC_Windows.zip.asc

Please disregard any posts with "new" versions of PhoenixMiner in this thread unless they are from our user account, and the files are hosted on our web server: https://phoenixminer.info/

[swogerino]

Finally the LHR unlock is here after many people asked for it.I think many other people will change to Phoenixminer once again as you implement more and more LHR settings,dual mine for LHR cards as this is one of the most stable miners for me.I am running all my miners on Phoenixminer 5.9 d and I don't see any reason to upgrade because I have no LHR cards and from what I see this major release is geared to the LHR cards.

[zertor]

The new beta version is ready. PhoenixMiner 6.0b

PhoenixMiner 6.0c is officially released

The new features in this release are (since the last official release 5.9d):

Implemented partial unlocking of Nvidia LHR cards. By default they are detected automatically, and unlocked with the default unlock intensity (520). If you want to try higher (or lower) LHR unlock intensity, use the new -lhr command line parameter. For example -lhr 580 will try more aggressive unlocking than the default 520 unlock intensity. This parameter may (and should) be specified for each GPU separately as some GPUs can support higher unlocked speeds.
If an Nvidia LHR card locks up because of high -lhr (the default 520 will work with most cards), the card will be unlocked again, and the -lhr value will be lowered if necessary

Got some feedback, if you can improve them.
It doesn't work well for 3060/3070 msi gaming models,
it constantly lockups due LHR and throwing a lot of invalid shares.  

If been left for a while it auto drops lhr value to 470 (and keep dropiing), but issues remains,
both constant lockups and a lot of invalid shares at any GPU settings.

With the same GPU settings if run another miner [like t-rex]
they works very steady without lockups, at 74.2% - 74.3% lhr % unlock percent,
without any invalid shares too.

Nvidia driver version: 472.12