The new PhoenixMiner stable version is ready.
You can download PhoenixMiner 6.0c from here:
Inside the archive you will find a file README.txt with installation instructions.
Make sure to replace the pool and wallet address by what you’re using in all files.
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
-lhrcommand line parameter. For example
-lhr 580will 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
-lhrvalue 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.2aren’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.
Here are the signatures for the files in this release: