GMiner Nvidia LHR Booster

Since the release of version 2.67 on 12th of September, GMiner now includes a mode that tries to partially lift the limitations of mining using Ethash and Etchash algorithm on Low Hash Rate (LHR) GPUs. 

Since the cards are LHR series, the hashrate is limited in some of the algorithms. The booster, also called an "unlock" of peformance is attempting to run the cards at hashrates higher than the lock allows, but below the speed at which the locking mechanism will "notice" the "violation" and attempt to lock the performance. Think of it as a gray zone between the target allowed by the drivers and the point where sensitivy starts, zone in which you're still not limited, but if you go a bit higher than that — you'll be forced down by a lot.

The booster also has a mechanism to counterplay the locking: if the miner detects hashrate going down significantly, it will pause mining on the GPU to "reset" it and attempt to run at a bit lower tune in order to not trigger the locking mechanism again. During this process the reported hashrate will fluctuate and mostly stay on the lower side because every LHR lock will cause the miner to pause for 20 seconds to unlock the GPU, so you may need to wait till it finds stable settings.

The booster is enabled by default and the miner will attempt to tune the GPUs automatically so only a simple config (steps 1-3 below) is necessary to enable the unlock (for 3060v1 cards, add --lhr 1 in advanced config to force enable the unlock).

You can change the base values by setting --lhr_tune X parameter in the advanced configuration to adjust the tune of the unlock.

You can also disable the auto-tuning by adding --lhr_autotune 0 in the advanced config.

1. Open the Worker's config by going to the workers list and clicking the wrench icon next to the worker you want to configure.
2. Scroll down to the "Default miner" entry and select GMiner.
3. In Simple configuration mode, choose the coin, pool and wallet that you want to use.
4. Press the pencil icon to edit the generated configuration in advanced mode.
5. At the end of the configuration, add the --lhr_tune X and / or  --lhr_autotune 0 as desired. X can be a value between -10 and 10, with 10 being the highest hashrate and highest chance of getting a lock and -10 — the lowest chance of getting a lock with lower hashrate.

Instead of value 1 in the given example, you can set different value for each of the GPUs. For example, --lhr-tune 3 -2 0 3 will set enable tune the booster for cards 0 and 3, to value 3 and for the card #1 to value -2, while not enabling the lhr mechanism for the non-lhr cards (value 0) if such are present in the system.

Here's a full example config with the tune configured and auto-tune disabled: 

On windows-based systems, you manually need to install drivers for cards. The cards have been tested to work with driver version 471.68 and you can find other versions on Nvidia's official driver search.

You can use the new versions of msOS to use the LHR series cards with new driver version included, available on msOS Version Archive. For most motherboards msOS version 1.4.10+ should work, but if your system requires newer kernel (mostly for newer motherboards, like H510 Pro BTC+), you can use msOS version 1.7.5+.

If you are already using an older version and would prefer to not reinstall OS completely, while adding LHR Nvidia GPUs to your system, and they turn out to be not detected on msOS, update drivers with nvidia-update command: nvidia-update --install 470.63.01

Driver updating details are also available here.

If after driver update and reboot, your GPUs are still not detected, then re-check BIOS settings:

• UEFI
• PCIe GEN2
• Above 4G Decoding

On msOS side, you can try this command: pci-realloc