Skip to content

Releases: Lolliedieb/lolMiner-releases

lolMiner 1.51a

20 May 15:49
bf46ed7
Compare
Choose a tag to compare

Changes & Fixes

  • Improved / Fixed Nvidia memory management (allowing dual mining in Windows to run for more epochs on 6G cards)
  • Updated Web Gui - showing LHR unlock percentage and dual factor
  • "LHR_Unlock_Pct" and "Dual_Factor" now provided per GPU in the API

lolMiner 1.51

19 May 10:37
db6ee2b
Compare
Choose a tag to compare

Changes (compared with 1.50)

  • Windows: significantly improved the speed of Nvidia Ethash mining
  • Extended working range of 100% LHR unlocker to 470 and 472 drivers. Note: please do not use the new 515.x drivers - on them the unlock currently does not work.
  • New parameter for dualmining: --dualfactor (default: "auto"). (see Note below)

Fixes

  • Linux: Fixed a bug causing the Zombie mode on 5G Pascal GPUs (1060 5G, P2000) not to work.
  • Minor LHR unlocker stability improvements.

How to use new --dualfactor parameter:

This parameter can be used as more direct alternative to --maxdualimpact. It is build in a way such that the hashrate of the Ton / Aleph solver will be dualfactor * Eth hash rate. So for example if the factor is 25 and the Eth hash rate is 59.5 mh/s, then the dual hash rate will be 25 times 59.5 mh/s = 1487,5 mh/s. The maximum dual factor at the moment is 64, a value of 0 will disable dual mining on the GPU. Using the parameter will skip all tuning of the dual algorithm and set the ratio directly after DAG build. Note that if you turn the value too high, then the Ethash hash rate might fall, turning it lower usually decreases energy intake.

The parameter takes a comma separated list of values, where auto or a star can be used to skip over a GPU that should remain in auto tuning mode. If you use --devices for restricting to some GPUs, then also it is sufficient to define it for the selected GPUs only. Note, that the old --maxdualimpact parameter now also understands "auto" to keep it more consistent.

Know Bugs
Values of TON/ALPH in Windows with Turing GPU are not correct.

lolMiner 1.50

14 May 08:08
db6ee2b
Compare
Choose a tag to compare

lolMiner has only 0.7% fee on Ethash, 1.5% on Autolykos V2 and only 1%+0% fee on dual mining. You will find no lower ones in the market with this feature set.

Changes

  • 100% LHR unlock on LHR V1 and V2 GPUs. Unlock working on all supported algorithms including Ethash and dual Mining. Requires Nvidia driver versions 510.x (Linux) or 512.x (Windows) and sudo / administrator privileges!
  • Added experimental LHR v3 unlock to ~90% (3050) and ~92% (3080 12G) (default enables) Use --lhrv3boost 0 to disable the mode and fall back to ~65% unlock (see notes below).
  • If the pool connection gets lost on the dual mining algorithm, the miner will now stop the dual mining to save the energy and continues in Ethash only mode until the connection is re-established.
  • Updated web gui

Fixes

  • Fixed a bug in 1.49 causing Ergo mining not to start on Nvidia GPUs.

Notes

  • The LHR unlock will start about 30 seconds after the miner did start, giving room for running the DAG generation with delayed OC.
  • If any of the above requirements are not met, the miner will load the old 79% unlock function and print a fitting warning method with the statistics.
  • The experimental mode for LHR V3 seems to sometimes have unstable when starting up with only a reboot solving it - but after a first successful start it is stable - therefore the option to turn it off if you are struggling to start it up too many times.
  • When configuring the --lhrv3boost via json file, use "LHRV3BOOST" : 1 to set it.

lolMiner 1.50 public beta

11 May 16:56
db6ee2b
Compare
Choose a tag to compare
Pre-release

Changes

  • 100% LHR unlock for all LHR affected algorithms on LHR v1 and v2 GPUs. Required drivers: 510.60.02 or 510.68 in Linux, 512.15 in Windows. On other drivers the previous 79% unlock on Ethash will be active.

Notes:

  • The miner needs admin / root privileges to unlock the cards.
  • The miner will unlock the cards approximately 30 seconds after start. Please make sure all OC operations are completed before.
  • On dual mining the LHR cards will now behave live full hash rate cards. This means dual mining tuning will start approximately 1 Minute after the DAG build is completed.

lolMiner 1.49

07 May 12:42
22c769f
Compare
Choose a tag to compare

Changes

  • Improved performance of Nvidia LHR V2 cards in Ethash to 79 - 79.5% (86.5 - 87 % on RTX 3060 V1 and 460.39 driver). Note that dual mode codes remain unchanged.
  • Added an experimental zombie mode for Nvidia Pascal generation 5GB cards, allowing them to continue mining Ethash after epoch 492 (in Linux)
  • Reduced fee for LHR unlocker back to 0.7%. Now all Ethash solo codes have only 0.7% fee (again).
  • LHR cards that have memory junction temperature sensors will automatically throttle LHR unlock by ~0.4 - 0.5% when hitting 106Β° C memory clock to prevent unneeded locks
  • LHR calibration on startup now taking approx 2 minutes instead of 4.
  • Extended crc table for Ethash up until epoch 550
  • Changed default behavior for "." signs in wallet address when Ton or Aleph dual mining. These will now automatically separate the string at the given position, so the thing after a . is treated as worker name.

Fixes

  • Fixed a bug that may cause TLS connections not cleanly reconnecting after a connection loss

lolMiner 1.48

01 Apr 10:47
9564cac
Compare
Choose a tag to compare

lolMiner 1.48

Changes

  • Implementing the new LHR scheme in Windows. Recommended driver: 512.15
  • Slightly improved initial speed after startup on 510.x & 512.x drivers allowing to reach best performance faster
  • Made the LHR unlocker more robust against small changes in work load. We still recommend to not put other load then mining during the calibration phase - after that is finished, the miner is more robust.
  • Full hash rate cards will disable LHR detection latest one minute after --lhrwait has passed. This means that by default one minute after the DAG was created the cards now get "protected" from further detection.
  • Added Nvidia core junction temperature reading
  • Added color grades for temperatures in web api
  • Change in configuration for making it more comfy: If the number of entries for --cclk, --mclk, --lhrtune or --maxdualimpact matches exactly the number of selected GPUs, the miner will now automatically skip over the inactive devices. E.g. --devices 1,2,4 --cclk 1050,1400,1500 now makes sense, while before --cclk ,1050,1400,,1500 was needed to skip over inactive devices.
  • --lhrtune 0 is now semantically identical to --lhrtune off

Fixes

  • Changed handling of user/wallet names containing one or multiple dots. This should fix issues with mining rig rentals and ezil pool. Note: some pool might not like appending your user name with a dot. If so and you get authorization rejected make sure you use --worker instead
  • Fixed a bug causing LHR unlock not working when too many GPUs needed to perform DAG repair in Aleph dual mining (yea, that is a special case one ... )
  • Fixed a bug causing RTX 3050 & RTX 3080 12GB to have extremely low Ethash performance when dual mining
  • Fixed a bug causing dual mining hash rate on FHR cards not showing up during dual mine calibration in 1.47
  • Fixed a bug causing --lhrtune off occasionally not to work in 1.47

lolMiner 1.47

25 Mar 12:02
f50b7e7
Compare
Choose a tag to compare

lolMiner 1.47

Note: at the moment the release is Linux only, because testing the new scheme on Windows will take us some time. Be patient please :)

Changes

  • lolMiner bringing you the fastest public Ethash LHR solver! 77.2 - 78.2% on GDDR6 and 76 - 77% on GDDR6X Nvidia Ampere cards! Exceptions: 86% on RTX 3060 v1 with driver 460.39 or older, 55-58% on RTX 3050 and RTX 3080 12G. Fee on the new scheme is 1%, other solvers are unchanged. Please read the important notes section below.
  • Added support for LHR unlock in 470.103.01 and all 510.x drivers. In fact we highly recommend using these drivers, because it will give a more stable unlocker experience!
  • the parameter --lhrtune now takes absolute % values to fix a certain percentage of unlocking. If chosen too high, lolMiner will reduce the value to the maximum possible. The value will be tied to keep regardless of the number of locks this implies. The default is "auto" in which the miner tries to balance the number of locks and re-calibrations with the speed to achieve, hash rate might change from time to time based on unlock quality heuristics.
  • Cheaper locks: when unlocking the miner will continue mining at low speed to make the unlock procedure more cheap.
  • Reduced Ton & Alephium fee in Eth+Ton / Ethash+Alephium dual mining to 0%. You will be only paying the 1% fee on Ethash in this dual mining. This also means: no more unsafe connections to Ton servers to collect fee in case you are in a country with mining restrictions - if your own Ton connection is using Stratum over TLS.
  • New parameter --silence that controls the amount of information the miner will print during its work. 0 is the default behavior, 1 will turn off "new job" messages, 2 will additionally turn of the messages about found shares, 3 will leave the miner with the minute statistics only.
  • Added Nvidia memory junction temperature readings on cards that support this, e.g. GDDR6X customer GPUs, most professional and server GPUs and so on.

Fixes

  • Fixed a bug with dual mining on LHR cards where the dual algorithm was mined with reduced rate after Ethash epoch change.
  • Fixed a bug with --compactaccept not showing the * sign on short statistics.

Important notes about the new LHR unlocker scheme

  • Use 470.103.01 or 510.x drivers! They have turned out to be much more stable in unlock in testing then older drivers.
  • The miner software needs to learn certain aspects about your cards over time to optimize for the best balanced pool hash rate. The needed calibration will get better over time, but the things learned are too complex to display them or store into parameters.
  • Therefore in automatic mode the miner might start with a slightly slower hash rate at the beginning, but will get better over time. In non-automatic mode you might see more re-calibrations during the first hour of mining then normal. If the number keeps too high after that point, lower the requested % value.
  • As a consequence: the longer you can keep it running the better - avoid frequent restarts of the software.
  • Dual mining with Aleph & Ton is supported as well as doing ZIL dual mining. When doing ZIL make sure --enablezilcache is used on all the LHR cards, because the re-calibration is needed on every hard epoch change.
  • Try to keep your settings as stable es possible. Especially: Set clocks that your GPUs can keep without running into thermal throttling. Also use locked clock core with no set power limit to maintain a stable GPU core clock for ideal results. Having GPUs freely changing their clocks and sometimes running into their power limit will invalidate a lot of data collected and decrease efficiency of the unlocker a lot. Same applies to memory clock - do not change it after the calibration did start. Use --lhrwait parameter to delay the initial calibration until you are done with your settings.
  • The initial configuration takes approx 3-4 minutes from the moment the DAG was build.
  • Keep away other work load from your GPU as e.g. connected screens. Also CPU mining in parallel to the new unlocker is untested and might give unexpected results.

lolMiner 1.46a

22 Feb 16:42
0596a1f
Compare
Choose a tag to compare

lolMiner 1.46a

Changes (over 1.45)

  • Significantly improved the Ton performance in Eth+Ton dual mining for all supported GPUs. Gain is 15-20% over the old implementation at same Eth reward - combined with new tuning some cards can be much higher (e.g. RX 580) while others optimize for more Eth hash rate (e.g. RX 5700)
  • Changed the Eth+Ton and Eth+Alephium tuning functions on AMD and all Nvidia non-LHR cards. Tuning now uses a scoring function to score resulting Eth and dual coin rewards and try to optimize this. Note that with --maxdualimpact you still can just define the max % of Eth hashrate to give away. This will overwrite the scoring function.
  • Added experimental Eth+Alephium dual mining kernels for Pascal GPUs.
  • API now also gives the worker name on Ethash, Ton and Alephium mining.
  • Updated Web-gui.
  • Ton stratum: https://next.ton-pool.com now using mode 2 automatically again. New whalespool server wss://stratum.whalestonpool.com/stratum now using mode 6 automatically.

Fixes

  • 1.46a: Fixed a bug causing the miner to sometimes end up in an infinite re-connect cycle - instead of actually reconnecting
  • 1.46a: Fixed a bug causing --maxdualimpact not having effect on some Nvidia cards
  • Fixed a bug causing connection time out (for a retry) not working properly
  • Fixed a bug in Alephium stratum: miner did not check fail-over when primary worker name was not accepted by the pool
  • Fixed a crash when trying to specify more fail-over pools for dual algorithm then for the primary connection
  • Windows: fixed a bug causing dual mining (especially Eth+Alephium) freeze the card & driver on startup
  • Fixed some minor glitches

lolMiner 1.45

15 Feb 13:04
ede3f48
Compare
Choose a tag to compare

lolMiner 1.45

Changes

  • Added Ethash + Alephium dual mining mode analogous to existing Ethash + Ton mode. Use --dualmode ALEPHDUAL to use it. Supported GPUs: Nvidia Turing & Ampere generation, AMD Polaris (RX 400, 500), Navi and Big Navi generations.
    See this page how to configure it: https://github.com/Lolliedieb/lolMiner-releases/wiki/Example-to-configure-Dual-Mining-ETH-ETC-UBQHASH-ALPH
  • Stratum connections will now have an increasing timeout (steps of 5 seconds) when reconnecting plus a small random time of 1 second in order to not overload the target pool in case of recovering from a network outtake.
  • lolMiner API now has new page /gui, which allows you to watch your rig mining in a web browser. Navigate to http://<ip of your rig>:<apiport>/gui in your brower doing so.
  • Added experimental (at the moment a bit slow) Ethash kernels for new AMD BC-250 APUs
  • In dual mining the algorithm that mined a share will now be shown in command line output
  • --ton-mode 6 stratum mode will now obey the prefix send to it on the first bytes of the nonce (request from other pools that want to use this scheme)
  • Startup time of dual mining on non-LHR cards is now reduced to 30 seconds after DAG build
  • Removed --ton-mode 2 from automatic detection (you still can request it explicitly) - ton-pool.com will instead use mode 1 for existing and mode 6 for upcoming new stratum servers.

Fixes

  • Fixed multiple stratum bugs - mostly crash fixes when running web socket based connections
  • Windows: clicking into the miner Window will no longer halt the miner completely

Preview of lolMiner web monitoring:
image

lolMiner 1.44

08 Feb 11:45
ede3f48
Compare
Choose a tag to compare

Features

  • Added experimental Ethash + Ton dual mining kernels for Nvidia Pascal generation GPUs.
  • Setting the parameter --maxdualimpact to 0 will now completely disable dual mining on this card.
  • Setting the parameter --dualdevices can now be used to make GPUs mine Ton only in Eth+Ton dual mode. In combination with --maxdualimpact this means one can choose for every card which algorithm to mine. (See example below)
  • Automatic tuning for dual mining will now always make sure the parameter is adjusted so the GPUs start on both algorithms if --maxdualimpact is not set. Manually setting --maxdualimpact will disable automatic parameter stretching.
  • Windows: Adjusted LHR parameters a bit for more stable operation.
  • icemining.ca Ton stratum now can use the --pass or --dualpass parameter to apply pool settings.

Fixes

  • Windows: fixed a bug that caused abnormal high stale rates on Ethash and Ethash / Ton dual mining on Nvidia cards.
  • Windows: fixed a bug that made the miner crash when a https connection tried to re-connect (mostly Ton).
  • Linux: fixed a bug that might cause a SIGSEV or SIGPIPE crash on some Linux platforms when reconnecting.
  • Fixed a bug that caused the miner to enter re-connect routine when one endpoint of a Ton - pool did not work, although other endpoints did connect well (That in combination with the previous one was root cause for most Ton errors in Windows we recently had).
  • Fixed a bug with icemining.ca Ton stratum not sending correct job id when dual mining on AMD cards.
  • Fixed a bug with json style configuration not working with dual mining in 1.43 release version.
  • Temporarily disabled the ZIL cache function on AMD GPUs, because it sometimes did not swap clearly. We will bring this back as soon as possible.

Example for --dualdevices and --maxdualimpact

Consider a 6 card rig with --dualdevices 4,5 --maxdualimpact 0,0,*,*,*,*
This rig will mine:

  • Eth only on GPUs 0 & 1 (ton dual mining disabled by maxdualimpact)
  • Eth + Ton on GPUs 2 & 3
  • Ton only on GPUs 4 & 5 (eth mining disabled by dualdevices)