Skip to content

Releases: MinerSource/lolMiner

lolMiner 1.92

29 Nov 12:44
251f729
Compare
Choose a tag to compare

Installation

Click the download button for your operating system:

lolMiner 1.91

01 Oct 08:21
0216e4f
Compare
Choose a tag to compare

Changes

  • Added support to mine Autolykos V2 (Ergo, BlocX) and KLS V2 on RX 400, RX 500, AMD Vega, VII and AMD MI 200 and MI 300 series. (1) (2)
  • Added Autolykos V2, Karlsenhash V2 and Fishhash dual mine capabilities with Gram / Ton for all above mentioned cards. AMD VII, MI 200 and 300 series additionally got PYRINV2 dual mine capacities. A manual dualfactor setting might be needed in case the automatic tuning drops the factor to 0 or a too low value.
  • Improved performance of Fishhash on RX 400 and 500 series by about 3%.

Notes

(1) All Vega branded cards will require rather new (Linux) drivers (from the past 2 years).
(2) The Vega codes, especially for VII for Autolykos V2 have some performance issues and are therefore flagged experimental.

Update Guides

Raveos

Open console and write in it:

stop && wget https://github.com/Lolliedieb/lolMiner-releases/releases/download/1.91/lolMiner_v1.91_Lin64.tar.gz && tar -xvf lolMiner_v1.91_Lin64.tar.gz && cp -adpR 1.91/lolMiner /app-data/miners/lolminer-1.90 && start

HiveOS

Open console and write in it:

wget https://github.com/Lolliedieb/lolMiner-releases/releases/download/1.91/lolMiner_v1.91_Lin64.tar.gz && tar -xvf lolMiner_v1.91_Lin64.tar.gz && pidof -x SCREEN && miner stop || echo lolminer && cp -adpR 1.91/lolMiner $(ls -d1 /hive/miners/lolminer/*/ | tail -1) && miner start

mmpOS

Already up to date

lolMiner 1.90

21 Sep 02:10
d06f754
Compare
Choose a tag to compare

(1) For AMD cards, we suggest manually setting the dualfactor for Autolykos V2 and Pyrin V2 mining to prevent frequent re-adjustments of the dualfactor settings.
(2) On RDNA3 cards, we observed some rejected Pyrin V2 shares when mining Ergo / BlocX with Pyrin on certain pools (though this issue didn't occur when using a stratum bridge). We're currently investigating the cause of this, but since the released code is significantly faster than the slower version that doesn’t produce these rejects, we opted to move forward with it regardless.