The new alpha version is ready. You can download PhoenixMiner 5.2a from here (this is only the Windows version, the Linux version will be ready in a few days)
You can download PhoenixMiner 5.2a from here:
The new features in this release are:
- AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
- Added new
-daglimparameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use
-daglim 1for automatic operation, or specify a concrete value for the maximum DAG size (example:
-daglim 4000will set max DAG size 4000 MB)
-rxboostparameter (also accessible via
-vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
- Added memory straps support for AMD Vega cards. Use the
-strapscommand-line option to activate it (example:
-straps 1will activate the lowest strap level)
- The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
- Many other small improvements and fixes
Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards
-strapson AMD cards requires running as administrator (or as root under Linux), so
you need to runPhoenixMiner as administrator for the VRAM timing options to work. Note that the
-mtoption will still work without running as administrator/root.
-rxboostoption is only supported on GDDR5 cards (RX4xx/RX5xx or older).
-daglimoption works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limit the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 373 on Windows (or after 384 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit, this is the default), 1 (automatic DAG limit size, usually around 4005 MB under Windows). Note that the hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.