|
The official release version was updated to 6.2c. You can download PhoenixMiner 6.2c from the first post of this thread.
Note that this is the same as release candidate that was posted here a few days ago.
NOTE: You must upgrade to PhoenixMiner 6.1b or later if you get "certificate verify failed" errors on SSL connections (especially to eu1.ethermine.org).
|
|
|
|
The next version is ready as a release candidate: PhoenixMiner 6.2c. You can download PhoenixMiner 6.2c from here: PhoenixMiner_6.2c_Windows.zipPhoenixMiner_6.2c_Linux.tar.gzTo 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): File: PhoenixMiner_6.2c_Windows.zip
===================================
SHA-1: 33b4c5f25115e147fdc959182328e5760e5dffa9
SHA-256: 5e74527181574edd659a6682bb26cbeefed9de385be1656fdb99fdab55ae42a7
SHA-512: 38b47978f7f8e7f339b2aa4adbfc7cafbc2c8eab3b9de8349072f982b8f3e408beef8ba50d75c52464e19660e823e4958c48287c17117b4997ab17ba5c825999
File: PhoenixMiner_6.2c_Linux.tar.gz
====================================
SHA-1: 79b2ce53bc51cfdc88e363baeb3a8136888920a1
SHA-256: dad2f42237269b8f98932e9dcf45d12e30d3f694e52ada01e2c891a348636319
SHA-512: c11c64b51c674bc98155c520a1c63c91ace0db92da202b8fe1fc333a376a8e153309905349f348ce9e0b1af56b04b0da4d1a3b37a5a15e46946c01a7da559e1d
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Using the newer AMD RX470/480/570/580 kernels even on older drivers (Windows driver 19.2.1, or newer; and Linux driver 19.10, or newer). If you want to revert to the older kernels on these drivers, use the new command line parameter -clabi 1
- Added a workaround for the SSL pools with self-signed or expired SSL certificate: you can use the new command-line parameter -weakssl (for the pool specified by -pool), or -weakssl2 (for the pool specified by -pool2), or the new WEAKSSL: 1 option for the pools in epools.txt.
Note that this option must be specified independently for each pool: if you use -weakssl on the command line (or in config.txt), it won't affect the pools specified in epools.txt. Instead you need to add WEAKSSL: 1 for each desired pool in epools.txt - Fixed a crash with Nvidia cards on some older drivers (e.g. 460.79, and 460.89). If PhoenixMiner crashes or exits while showing Initializing NVML... try the new command line parameter -nvmalt
- Validated support for AMD Windows drivers 22.4.2
- Other small fixes
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: 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 PhoenixMiner
v6.1b still shows "ssl certificate verify failed" in some pool
can we just have an easy option to totally ignore the certificate problem? something like "no strict ssl"?
We will add this in the next version but please do not use it lightly - with this option the whole point of using SSL is moot as it allows MITM attacks with self-signed certificates. |
|
|
|
|
The official release version was updated to 6.1b. You can download PhoenixMiner 6.1b from the first post of this thread.
You must upgrade to PhoenixMiner 6.1b if you get "certificate verify failed" errors on SSL connections (especially to eu1.ethermine.org).
|
|
|
|
The issue with SSL connections to ethermine is indeed caused by an expired root certificate (DST Root CA X3). In theory this is fixed by using a "cross-signing" with other root certificates but in many cases this doesn't work as intended. We have make the necessary fixes and we are releasing PhoenixMiner 6.1b, which should fix all SSL connection issues. You can download PhoenixMiner 6.1b from here: PhoenixMiner_6.1b_Windows.zipPhoenixMiner_6.1b_Linux.tar.gzTo 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): File: PhoenixMiner_6.1b_Windows.zip
===================================
SHA-1: 193c795a6b99dcc9a6cb7abd9594c551d8ad771b
SHA-256: 2d262b61e1dcf8d00f66390def6b835265bc44f71d26ac5dfa21cd140fa0ddd4
SHA-512: bde4938fc24ebd1e3c8a30597394d6b266e5d6c99f25631589916d746d83e6d6ffe87478e8b920098efcb1d0d463d0b61d9132a7098730fa587a33e556d0bd9c
File: PhoenixMiner_6.1b_Linux.tar.gz
====================================
SHA-1: 79c80b170a7879673e001f7e3d3126cd409eb873
SHA-256: 6f196b5b303729eaf53cc0dc77dc1408e75b6307c4802f9b8175dffbd4968d7c
SHA-512: a0641f9858a5074924c483842e2c578932a99c8a7702512292e0bb7bd4774cc602b8a6b4a705ce44afa27b6f63aa22a8d0a3a003952112176f2fe61b40e6845c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Fixed an issue with expired SSL certificate that led to "certificate verify failed" errors when connecting to some pools (notably Ethermine) when using SSL connections
- Now the miner will send SSL SNI host name which may be needed by some pools for SSL certificate validation. To go back to the old behavior (no SNI host name), use the new command-line parameter -nosni
- Added support for latest AMD Windows drivers up to version 22.4.1
- Other small fixes
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: 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/ |
|
|
|
Drivers are ok, as I said I am using Phoenix Miner after Claymore ended and still using him on severals rigs with v5.8x without anny issue and for updates I just copied old bat file into directory of new version but since v5.9 it is not working like that. In this moment I am ok with v5.8x since I am using old card GTX 1070TI and few RTX 2070 but I wanted to try new version to be prepared for future needs in case I add some newer cards RTX3 or AMD RX66xx...
It is possible that there is a bug in the new version(s) but we really need the Windows version, and the Nvidia driver version in order to be able to reproduce the problem, and then fix it. You could also try to run the miner while only listing the available GPUs, then post the results here along with Windows and driver versions: |
|
|
|
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.zipPhoenixMiner_6.0c_Linux.tar.gzTo 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): 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: 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/
|
|
|
|
The new beta version is ready. You can download PhoenixMiner 6.0b from here: PhoenixMiner_6.0b_Windows.zipPhoenixMiner_6.0b_Linux.tar.gzTo 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): 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: 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/ |
|
|
|
The official release version was updated to 5.9d because we fixed some regression bugs that were introduced in 5.9b, and 5.9c. You can download PhoenixMiner 5.9d from the first post of this thread. The changes in this release (since 5.9c) are: - Fixed issues with AMD RX6700XT with older drivers
- Other small fixes
|
|
|
|
|
PhoenixMiner 5.9c is officially released. You can find the download link and the checksums in the first post of this thread.
It is the same release as the one that was posted here as release candidate, so if you are already running it, there is no need to upgrade.
|
|
|
|
The release candidate 5.9c is ready for download. You can download PhoenixMiner 5.9c from here: PhoenixMiner_5.9c_Windows.zipPhoenixMiner_5.9c_Linux.tar.gzTo 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): File: PhoenixMiner_5.9c_Windows.zip
===================================
SHA-1: 38b2f8629cc563c82cd44418e71d3e630cc6f975
SHA-256: 78d9d0ab530a5b104c1e8a2f1fe03547a6840e67d6bd7087a017b74b34d7e164
SHA-512: 97753ec7c59f625052c5fdbe1e1f9e178969e6367475cd211593fe3560cc6ff3af86a46542496ae230c106fb4204cb84dfb5a6354620dce2b5ff93ef74bca60c
File: PhoenixMiner_5.9c_Linux.tar.gz
====================================
SHA-1: b5e113ee024e394e6d877ae5b3d7e4b1b423ec6a
SHA-256: c35047370755e0203f9e5d2bece08ddc19c8e3ebb84e9aa3d5e67ba349701258
SHA-512: 55cf344dc94c4456a9806f611d839b2f8883c0bf9f71d559ba38bc95ba5b4f0e43918a4057b8ff16dcb9876da8a7479b18044e6fb16d26067f4d91acbe3e43d5
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release (since 5.9b) are: - Validated support for the latest AMD Windows drivers 21.11.3
- Fixed some pool connection issues
The changes of the previous beta (5.9b) since the last version (5.8c) are: - 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.
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: 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/ |
|
|
|
The new beta version is ready. It is mostly a bugfix release, the more significant upgrades are coming next month. You can download PhoenixMiner 5.9b from here: PhoenixMiner_5.9b_Windows.zipPhoenixMiner_5.9b_Linux.tar.gzTo 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): File: PhoenixMiner_5.9b_Windows.zip
===================================
SHA-1: 79b66d92ab3e2928637732ebaf9253919b16f5cf
SHA-256: 77a63af619b93873460ac83f26027fc52b77526d01eaafc331a709516ca3dbea
SHA-512: ea308b92f106cdfa64e1b1beed1b0604edd242665ffedcc2be2c49ecf08f4cc29f3fff5fd0217f201c6df782b45baf99233870a5f99a4b7b5e8ebec084c632c6
File: PhoenixMiner_5.9b_Linux.tar.gz
====================================
SHA-1: 03c881e4debe7dd0f7743384a28e06c5fd1c904a
SHA-256: 0a1581fb5c2a3c0f586a303d15e8289da0c8a2dbc3d437c59294c26f70155878
SHA-512: 75b4079ea714873a54735e9cd0657ab7081ec978aec14e4b4ad8a3d25abd88cb3d5e1ca783d47fd56cfbab26dc6a09ec70582648a54c0e0ea5ec2566c94db0e3
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - 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.
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: 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/ |
|
|
|
The official release version 5.8c is ready. You can download PhoenixMiner 5.8c from here (or from the first post of this thread): PhoenixMiner_5.8c_Windows.zip PhoenixMiner_5.8c_Linux.tar.gzTo 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): File: PhoenixMiner_5.8c_Windows.zip
===================================
SHA-1: f009c2ca0633d3645f148f362cfd61bdc8993838
SHA-256: c139cfb5f4a721993dcf8b7d279c7d2d9e27a406323d73a727ad5d5ba7637bb0
SHA-512: 6440f3c040f2ac241b4ce334c67a007fc119b50d7b2b7909c3e6e6fb8a8ea8604dd7e2b1af042c0371ae267d2977d2ba7155595ee3edc27fdbed0261fe6ba80b
File: PhoenixMiner_5.8c_Linux.tar.gz
====================================
SHA-1: fdb43a9853e7182a35622a8f92b399576ae84490
SHA-256: 5b3a0e363f1a437fa3463fabc36ae551d36c722e5e2673a3021c66a9469a7a7e
SHA-512: 0fd75257dc7ceef3e174f070e5801290cebea8fbade5ae6cfd84d4d6033e16474442446fab2815c88d100f910fc68f871c3c69215f6f4019dcf8bc3eeea44c20
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release (since 5.8b) are: - Fixed a crash on Linux when mining on RDNA2 AMD cards (RX6x00) with older drivers
- Removed error messages when mining on fanless Nvidia cards
The changes of the previous beta (5.8b) since the last version (5.7b) are: - Implemented optimized kernels for AMD RX6600XT cards
- Added support for the latest AMD Windows drivers (21.10.2, 21.10.1, 21.9.2, and 21.9.1). Note that any AMD cards older than Polaris (RX470/480/570/580/590) won't work with the latest AMD drivers.
- Added support for the latest AMD Linux drivers 21.30
- The latest AMD drivers (21.9.1 and later for Windows, and 21.30 and later for Linux) dropped support for the older kernels, so we changed the kernels for AMD Polaris cards to support these new drivers. There is a very small speed improvement (less than 0.1% on average) with the new kernels and the new drivers on Polaris cards
- Other fixes and small improvements
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: Known issues (driver incompatibilities, etc.) and workarounds: - AMD Radeon VII cards will not work with Windows drivers 21.6.1 or higher, or Linux drivers 21.20 or higher - you need to use older drivers for proper operation of these cards
- AMD Vega cards will not work with Linux drivers 21.20 or higher
- Some Nvidia cards will report a lot of stale shares under Windows 11. Using the same driver version under Windows 10 resolves the issue.
|
|
|
|
Is anyone running 5700XT with AMD 21.10.2 driver? The reason I ask is because I have one rig with 5700XT only and uses 21.3.2 for now. It is stable. I got one 6600 which requires 21.10.2. If I add 6600 onto the rig with 5700XT, I will have to use 21.10.2 driver. Please let me know if there is any issue to use 21.10.2 with 5700XT or not.
It shouldn't be a problem to run 5700XT and 6600 on the same rig with 21.10.2. The latest drivers will have problems only with very old cards like Baffin or Gfx804 (RX 460/550/560), or anything older than Polaris. Polaris cards (RX 470/480/570/580/590), Vega, RX5x00, and RX6x00 cards will work fine with the latest drivers. We haven't tested with 6600 yet but the we managed to order a few of them so we will be able to confirm that they work in a week or so. Anybody got PM 5.8b working in linux with multiple RX6800XT on driver 21.30 or any driver above 20.40? I was delighted to see the update for the beta version 5.8b above however with a fresh install of ubuntu 20.04.3 kernel 5.11 and driver 21.30 promised working in PM post above but clinfo doesnt even see a single card just the IGFX which obv isnt used for mining. Using chipset B550 and the only way i have ever been able to get pm working under ubuntu on driver later than 20.40 is single GPU only long ago. Maybe its a bios thing im not used to such modern mobo, currently got pci set to gen 1 - Any ideas? And in my defence i wil state that without touching a bios setting i can boot into Manjaro and mine with 6 x RX6800XT although stale shares are running around 20% using driver 20.40 and opencl as per this info: https://community.amd.com/t5/drivers-software/6900xt-and-opencl-on-linux/td-p/439474/page/2Read about an issue with multiple GPUs caused by ROCR PCIE 3.0 atomics as per link below...have tried it without success...... Currently stuck on Manjero with driver 20.40 and clkernel0 which gives an undesirable stale share volume though it is stable and have full control... https://www.reddit.com/r/gpumining/comments/ptmyjd/ubuntu_20043_amdgpu_2130_opencl_rocr_rocm/ Unfortunately this is a limitation of the new ROCr driver itself - it usually means that the RX6x00 cards will work only on the PCIe slots that are connected directly to the CPU PCIe lanes. On the most consumer-level motherboards this means only 1 or 2 slots (usually the first PCIe 16x slot closer to the CPU socket). However, if you are able to see RX6800 in other slots using the older drivers (like 20.40), the upcoming PhoenixMiner 5.8c for Linux should solve the stale shares problem. |
|
|
|
Hello,
I have a Nvidia CMP 170HX card which is fanless. I want to use it with phoenixminer and HiveOS but Phoenixminer gives an error that it cannot get fan speed infomation back. Any advice how to solve this problem?
We will check what can be done, perhaps to report this once and then just report 0% as fan speed without further errors. As we are making some fixes in Linux version of 5.8b for some unrelated problems, we will include this in 5.8c, which will be ready in a day or two. Note that 5.8b for Windows has no important issues so far, and will probably be the release version soon. When should we expect new release? Can you please give us ETA so we don't panic next time when you disappear from the forum for some time?
Before the end of the year. We are monitoring the forum all the time but will only react if something extraordinary happens. It's just not possible to answer every post with questions. I guess I'm one of the happy miners today. I did the upgrade to 5.8b yesterday. My speed increased from 166.25 to 166.683 MH/s Not a big gain but it is an improvement and I like it. No issues at all so far. Been running 24 hrs. Thanks Phoenix *** 24:00 *** 10/18 19:57 **************************************
Eth: Mining ETC on ssl://us1-etc.ethermine.org:5555 for 24:00
GPUs: 1: 33.505 MH/s (699) 2: 33.273 MH/s (708) 3: 33.602 MH/s (645) 4: 33.144 MH/s (686/4) 5: 33.235 MH/s (736/1)
GPU1: 64C 69% 107W, GPU2: 65C 47% 97W, GPU3: 65C 26% 105W, GPU4: 65C 40% 98W, GPU5: 64C 47% 98W
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie 7), OpenCL 2.0, 4 GB VRAM, 36 CUs
GPUs power: 504.2 W; cost: 0.61 USD/day; 331 kH/J
Current -gt 13,13,13,14,13
Eth: Accepted shares 3474 (2 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 5 (0.14%), est. stales percentage 0.06%
Eth: Maximum difficulty of found share: 134.7 TH (!!!)
Eth: Average speed (5 min): 166.683 MH/s
Eth: Effective speed: 160.77 MH/s; at pool: 160.77 MH/s
Eth: Estimated income: 6.94 USD/day
Well, that's better than in our internal testing. Probably because of the more extreme timings on your cards - we keep our cards on fairly conservative timings to be sure that when something goes wrong, it's not an overclocking instability. |
|
|
|
Is PM fully compatible with WIN11 ? Any trouble with win11 ? I'm a small miner using my main computer which is win11 compliant but i'm concerned about any issue if i patch it to 11.
Yes, we have tested on Windows 11 with both AMD and Nvidia cards, everything should work as in Win10 with the same drivers. Why you don't keep downloads only in your 1st post in this topic?
And post notification eventually for a new version as a replies,
but keep all downloads in your 1st post only and not from a replies.
Because then everyone will download and install the beta version from the first post, ignoring that it is in "beta" status, and if there are some problems with it we will never hear the end of it. Plus, it is not likely that this will stop the "fake" updates from appearing in our thread. how to use optimized kernels for AMD RX6600XT cards ?
They will be used automatically instead of the generic kernels, leading to slightly higher hashrate and much less stale shares. I agree with Rickirs,unless you specifically implement the LHR mode like many of the other miners are doing you are going to lose clients from the Nvidia side,personally I am happy from quite a lot of time with your miner as I mainly have AMD cards but it is a shame that you have not implemented some kind of LHR tune yet,hopefully this will be fixed in the upcoming releases.
Hopefully there will be kernels for Nvidia LHR cards in the next release. It is a shame but we don't strive to be the best in everything - all power to our competitors that implemented it before us. After all, the crypto is doomed if is not sufficiently decentralized, including in the area of mining software. Also, I have on the way RX 6600 non-XT. Is that card will be supported in the beta release the same way as the XT models?
Should be supported, but we were unable to test because we don't have 6600 non-XT yet in our hands. Let us know if you have any problems with it. |
|
|
|
The new beta version is ready. You can download PhoenixMiner 5.8b from here: PhoenixMiner_5.8b_Windows.zipPhoenixMiner_5.8b_Linux.tar.gzTo 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): File: PhoenixMiner_5.8b_Windows.zip
===================================
SHA-1: 82e6695d39d1f823676b80bbe2419f55beb4a387
SHA-256: 61452bab132f8feef823c5cbb987d9fd0bae1644fa068a31bf66be9a043bef79
SHA-512: ba3869628f49108212536e4cae479bd479fc1a34fdcf2a6f7dd8651fdae6c6c8e1a1f51e64d470c5e323136ca1a454c581c53bf38811e469be40d994705f96bf
File: PhoenixMiner_5.8b_Linux.tar.gz
====================================
SHA-1: 19ea3af08dfcdf6228c3bee708213fe4fba0124e
SHA-256: f8586949d212896f798962440243aa75e5367d27b035407b5871c264d2802af8
SHA-512: 878d221f3c124f5b34755d1adfbd9e0368e826d4bd3a5df12785d9e878c8b0f222503b8f2ed571b13ba021b095348b6f4eea5847a3b51fb26f13ea9819157303
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Implemented optimized kernels for AMD RX6600XT cards
- Added support for the latest AMD Windows drivers (21.10.2, 21.10.1, 21.9.2, and 21.9.1). Note that any AMD cards older than Polaris (RX470/480/570/580/590) won't work with the latest AMD drivers.
- Added support for the latest AMD Linux drivers 21.30
- The latest AMD drivers (21.9.1 and later for Windows, and 21.30 and later for Linux) dropped support for the older kernels, so we changed the kernels for AMD Polaris cards to support these new drivers. There is a very small speed improvement (less than 0.1% on average) with the new kernels and the new drivers on Polaris cards
- Note that Radeon VII cards will not work with Windows drivers 21.6.1 or higher, or Linux drivers 21.20 or higher - you need to use older drivers for proper operation of these cards
- Note that AMD Vega cards will not work with Linux drivers 21.20 or higher)
- Other fixes and small improvements
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: 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/ |
|
|
|
|
PhoenixMiner 5.7b is officially released. You can find the download link and the checksums in the first post of this thread.
It is the same release as the one that was posted here as beta version, so if you are already running it, there is no need to upgrade.
Note that 5.7b supports the latest AMD Windows drivers 21.8.1 but it doesn't support the latest AMD Linux drivers 21.30. If you have AMD 6x00 card and you want to use Linux, you should use AMD drivers 21.20 but for any older AMD cards, you should stick with AMD drivers 20.30 (the latest stable PAL drivers without bugs).
|
|
|
|
The new beta version is ready. You can download PhoenixMiner 5.7b from here: PhoenixMiner_5.7b_Windows.zipPhoenixMiner_5.7b_Linux.tar.gzTo 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): File: PhoenixMiner_5.7b_Windows.zip
===================================
SHA-1: 6d55e616ea06896b6d6afde60c6cdfbac67260f0
SHA-256: febcc9abbbf5426c6caf7004167fb86a1d384dfd14966ca67b4eb55bdcfeb97e
SHA-512: 5d7a1899efae0e79963cdc6cbf2117283704a0e85539fc353b7ea291a028ba70b6df60422bcb3b97f1b7636133dc16c30cb075a2cfa95f3f4e06e8d35309db28
File: PhoenixMiner_5.7b_Linux.tar.gz
====================================
SHA-1: 6fb818bd8d96321cd5881557994755c3a9021426
SHA-256: b56da6d413b6c91716c8d97ddf75dab1b1bbd2ca3183486286097e8349019917
SHA-512: ea477315f74424489cf1048c4e1927ff8e50c177d9f14258f62ef0db5a893d96392bbfdd5d8326ed7d952593fafa8be390329f21672d76ae679762ac26b15989
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused
- Increased the maximum supported DAG epoch to 600 (i.e. until about Sep 2023)
- Implemented full hardware control for AMD RX6900/6800/6700 cards under Linux. Note that with these cards under Linux you need to specify relative core voltage: e.g. -cclock -50 will set the core voltage to be 50 mV under the default value
- Added ROCr kernels for Vega, Radeon VII and Navi cards. With these kernels you will be able to run these cards with Linux drivers 20.45 and later but the performance will be lower than with the older PAL drivers and kernels. We recommend using AMD Linux driver 20.30 for all cards except RX6900/6800/6700
- Fixed an issue causing crashing with some RX6900/6800/6700 cards under Linux (there is no need to run these cards with -clkernel 0 anymore)
- Added support for AMD Windows drivers up to 21.7.2. Note that Radeon VII cards will not work with drivers 21.6.1 or higher - you need to use older drivers for proper operation of these cards
- Added support for AMD Linux drivers up to 21.20 (use older drivers for Vega or Radeon VII cards as they will not work with 21.20)
- Numerous other fixes and small improvements
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: Please let us know if you have any problems or questions related to PhoenixMiner 5.7b. |
|
|
|
I see now you have added full support for the Rx 6800 XT cards.I was having some issues with one such card Rx 6800 Xt in the 5.6b miner,as after a few hours this card hashrate was going to 0.Now I have just started 5.6d and will report back if any problems are still there.What driver do you suggest for this new miner 5.6 d?
The latest Windows drivers should be fine. Use -hstats 2 to see the actual clocks/voltages on the card when mining. Also, either use PhoenixMiner exclusively for hardware control, or other OC program. If you use both, the problems are all but guaranteed. @PhoenixMiner
Are you adding ZIL dag pre-allocation anytime soon?
somewhat strange behavior: I have updated some of my ETH+ZIL Polaris rigs to 20.9.1 + PM 5.6D (the performance is about 0.3-0.5% higher, with 1-3% lower power consumption) however now each time the switch is happening ALL the updated rigs go down, some random GPUs are failing to init the DAG (12GPU rigs), while 19.12.2 +PM 5.5C is working fine.
Yes, it will be included in the next release. Which switch is causing the problems? From ETH to ZIL or the reverse? In any case, it is unlikely that this has anything to do with the PhoenixMiner version, it is more likely that the newer drivers are the culprit. We would suggest trying 20.4.x as the latest drivers that limit the DAG size to 4 GB if you have stability issues with 20.5.1 and later versions. I have had this several times with my GitHub repositories with miners forks. So, GitHub blocks accounts for five reasons: 1. Someone has complained 2. Automatically by mistake 3. Someone forked the repository from a "dirty" account (When a fraudulent account is created and it starts to fork normal accounts, good chain accounts are sometimes also blocked. 4. The presence of two accounts. 5. Someone spammed the issues branch (sometimes GitHub blocks the account itself) What I used to do and always got amnesty: 1. Write to support ( https://support.github.com/contact/account) and ask the reason for blocking. In a response letter (2-3 days), they always write the reason for blocking the account. They will also ask you to describe your files and what they do. After they receive this information, then in 99% of cases the unlocking takes place, if you do not drag out for a long time. I always wrote that this is a cryptocurrency miner such as NiceHash and asked why then NiceHash is not blocked? After all, this is essentially the same miner. After that I was always unblocked  Then the account never gets the Suspended status again. Try to write support, I think it will help. We appreciate the suggestions but for the time being we are done with github. If they at least had warned us, we would have taken measures to avoid this disruption (however short) but to terminate our account without even an e-mail message is just unacceptable. About what you can expect from Microsoft owned company. When a GPU crashes, is there any indication in the log of which card crashed? I normally look to see which one is stuck at 0 MH/s but sometimes the card crashes and then resumes mining normally. Is there an event logged anywhere?
If the GPU doesn't bring down the whole rig, you should see something like "GPUx is not responding" towards the end of the log. That was fast.  It certainly looks like you guys were anticipating something like this was going to happen. Kudos for getting your own repo ready quickly. We learned some lessons from the MEGA fiasco a couple of months ago. Hopefully this would be the last time something like this happens. is @Phonexminer hacked
I dont remmeber they ever gave a d version out, it was either beta like 5.5b
or the release 5.5c
5.5d has been usually malware
checked the HASH of 5.5C on the new website and old file and they match but hte 5.5D is a new file so if phonexminers account on here is hacked and their github is hacked... ummm
5.6d is a legitimate version (if you download it from the link in the first post, and compare the checksums for a good measure). It replaced the 5.6c, which contains a regression bug (not showing the Nvidia GPU temperatures unless -hstats 2 is used). The problem was annoying enough and easy to fix, so we decided to just release 5.6d instead of waiting about a month or more before releasing the fix with the next PhoenixMiner version. The above post (from the forum user stef_stef) probably contains malware! Do not download anything from the links in his post! Our GitHub account was terminated (not a big surprise after they deleted some other mining software repos but we kind of liked the functionality there). Again, no explanation was given - they just don't want to host popular mining software it seems. Our new host is up and running. You can find the latest version of PhoenixMiner (as well as older releases and beta versions) here: https://phoenixminer.info/downloads/As always, make sure to compare the checksums of the downloaded files with these from the first post of this thread. This is a good idea for any download and takes mere seconds to do. It very much did contain malware as I woke up and found I had been TeamViewer?(not sure) hacked and they transferred out 2.34 BTC (but left 0.27, wonder why?) among other coins. Don't be dumb like me, just thought I'd share, sad day for me. There isn't anything that can be done about it I'm guessing? All in all I am grateful they didn't take everything but it does hurt quite a bit... the shock is wearing off and now feeling a bit sickly. That is really bad! The best thing you can do is try to check the destination address and if it is in some of the big exchanges, you try writing them to at least block the account of the scammers. The malicious post was deleted by the admins without 30 minutes or so, and we reported it as soon as we noticed it. The github account that it linked was created just yesterday. Please, please, do not download anything PhoenixMIner-releated from posts that are not from our account! And always compare the checksums - it is quite easy to do and can spare you a lot of trouble. Additional good security practice is to always keep your private keys encrypted, and not on the same machine from which you are making the transactions. Hi. Can someone give a good guide to what I should compare the checksums(the first post no longer has checksums for 5.6c) I have been running PhoenixMiner_5.6c. But I no checksums I can find match my zip or my exe.
I got it from github several days ago. which seems down now. Yhis whole situation with nicehash and multiple compromised versions seems odd.
Here is our post with the checksums of 5.6c: https://bitcointalk.org/index.php?topic=2647654.msg56968316#msg56968316An incident with our share validation engine caused shares to be rejected for ~30 minutes. As compensation, the mining and MEV fees on Ethermine will be lowered to 0% for 48 hours starting from the 12th of May 2021 15:30 UTC. Please accept our appologies for this incident & thank you for mining with us.
what is this?
There was a problem with ethermine pool, causing a lot valid shares to be rejected as invalid. They will compensate the miners as explained in their tweet. Has anyone figured out the low hashrate problem on Windows 7 when using NVIDIA GTX10xx series cards, RTX cards work fine on Win7 and hash at full speed, I tried diff versions of PM and still only get about half the speed, I got 14 total rigs, 6 rigs on Win7 that work great with no problems but had to switch to GMINER for the time being, and 8 rigs on Win10 using PM with no problems.
Any ideas, I think the last version that worked ok with Win7 if I remember was 5.2 or earlier.
We will try to reproduce the problem on Windows 7 rig. Is this also happening with older drivers? @Phonexminer
Noticed some nasty bugs:
* Win10, 1060 6GB cards, when GPUs clocks are applied via miner with command line parameters, clocks/voltages/memory,
miner start reporting wrong power consumption.. [unreal low one],
you can check that by comparing the power consumption reported by miner with other tools like GPU-Z and similar.
When all those options are removed, (and miner no longer control the GPU parameters like clocks/voltages)
the miner start reporting the correct power consumption.
* Win10, for 3080 GPU when using command line option "-tmaxmem xx",
it cause brutal share staling for all GPUs (with regardless of GPU's models used in the same rig)
lag of 2888ms, 3000ms, 300ms in that range randomly vary between 300ms - 3000ms.
When this option is removed, all found shares return to normal latency of 38ms for all GPUs[/color]
We will need logs to reproduce these problems, as we haven't seen anything similar on our test rigs. |
|
|
|
|
Show Posts
