lolMiner 1.19 a multi algorithm Ethash / Equihash / Beam & Grin miner with focus on AMD GPUs (OpenCL based). Note it will run on most Nvidia GPUs, too but the speed and stability may vary.

Downloads:

Driver Requirement:

Nvidia:

  • Cuda 10 or 11

AMD:

  • Big Navi: amdgpu-pro 20.40 (Linux) / Adrenaline 20.11.2 (Windows) and newer.
  • Navi: amdgpu-pro 19.30 (Linux) / Adrenaline 19.10.02 (Windows) and newer.
  • Vega: amdgpu-pro 18.50 (Linux) / Adrenaline 18.10 (Windows) and newer.
  • older cards: Blockchain drivers and newer.

Usage:

There is a new online manual with basic examples hosted here.

Supported Algorithms:

Algorithm       Solvers for Memory Size
Ethash          4G+
Beam Hash I     3G / 4G
Beam Hash II    3G / 4G
Beam Hash III   3G / 4G
Cuckatoo-31     4G / 8G / 16G
Cuckatoo-32     4G / 8G / 16G
Cuckaroo-30CTX  8G
Cuckaroo-29     6G
Cuckoo-29       6G
CuckarooD-29    4G / 6G
CuckarooM-29    6G / 8G
ZelHash         3G / 4G
Equihash 144/5  2G
Equihash 192/7  3G / 4G
Equihash 210/9  2G
* and many others

Changelog:

Version 1.19

Feature Updates:

 - Added automatic tuning mode for --zombie-tune. This is default on, so just run the miner with --4g-alloc-size set only to run the zombie mode automatic tuning. At the end it will report the configuration in case you want to use the configuration again. You can also exclude cards from tuning or set their value manually, e.g. --zombie-tune 2,auto,0,auto will run the automatic tuning on the 2nd and 4th GPU while using fixed number 2 for first card and 0 for the 3rd one. The tuning will need about 30 seconds per card in the rig to show first results. The next two phases take about 1 minute per card and followed by a approximately 1.5 minutes fine tune phase.
 - Ethash stratum connection will now reconnect after three pool rejected shares in a row that did pass own CPU verify before. This solves issues with unstable proxy forwarding e.g. in some ZIL pools. Also helps to get quicker to a failover pool if configured.  

Fixes:

 - Miner did not start up when "DEVICES" was configured in as a vector in json file, e.g. in some ETHOS configurations.