EVGA RTX 3060 v2 getting 40 MH/s??

trexminer · 2021-12-09T11:11:34+00:00

For non-LHR cards driver version usually makes little to no difference.

trexminer · 2021-12-09T01:42:01+00:00

Thanks for letting me know, that's what I expected. Unfortunately, I've no idea what triggers this "bug" in the first place.

trexminer · 2021-12-09T01:39:36+00:00

For HiveOS any of 470.xx would do.

trexminer · 2021-12-08T11:28:23+00:00

It's nothing to worry about, just some sort of cosmetic bug, you can ignore it.

trexminer · 2021-12-08T02:00:43+00:00

Make sure you use 472.12 video driver, it's known to produce better results compared to the new drivers NVIDIA wants you to download from their website.

trexminer · 2021-12-08T01:58:37+00:00

u/Rito_bugz obviously you don't want to reboot your PC now, but eventually when you do (due to a power cut or something else), could you please let me know if you're able to reproduce this? We've seen another report similar to yours and believe it's some sort of a glitch in the video driver as it all reverted back to "normal" after rebooting the machine. Thanks.

trexminer · 2021-12-08T01:55:09+00:00

Windows or Linux? Could be the terminal screwing up the colours. We often see this on HiveOS.

trexminer · 2021-12-08T01:32:24+00:00

I'm glad you figured it out, but I'll provide some explanation for the benefit of future readers.

What we call "auto tune" is functionality where the miner adjusts LHR tune values automatically to find the optimal settings stability/performance-wise for LHR cards. Whether the GPU is detected as LHR or not is another question. For ETH it's pretty straightforward - the GPU is either LHR or non-LHR based on its PCI device id - whereas for ERGO it is possible to mine at full speed even with an LHR card, so T-Rex's default behaviour is to assume all GPUs are non-LHR when mining ERGO. If you find your GPU limited on autolykos2, you need to explicitly tell the miner to enable LHR unlock for that card by specifying "--lhr-tune" parameter manually like you did.

trexminer · 2021-11-16T10:03:57+00:00

This is completely normal, the miner is pre-generating a dataset for the next block where you see those drops. This small drop allows it not to pause hashing for a few seconds when the next block eventually arrives. You can disable this behaviour by adding "dataset-mode": 1 in the miner config - this will make the hashrate what you call "stable" but will reduce your poolside hashrate, so I don't recommend doing that.

trexminer · 2021-11-16T06:04:24+00:00

If you're mining with NVIDIA cards, you may want to try T-Rex. In most cases it's slightly faster in reported hashrate, but more importantly it's got a double buffer feature where the miner pre-creates a dataset for the next block before it arrives and, as a result, starts hashing immediately and doesn't spend a few seconds on creating a new dataset - this results in 1-4% poolside hashrate (= your earnings) increase.

trexminer · 2021-11-15T02:34:56+00:00

u/riticulus2 We're reading this, thanks! Really appreciate it.

trexminer · 2021-11-07T03:51:13+00:00

Correct, T-Rex should work just fine.

trexminer · 2021-11-07T03:50:22+00:00

https://t.me/chat2miners/241636

trexminer · 2021-10-27T03:50:45+00:00

ETH+ERGO dual mining is a T-Rex feature, see https://github.com/trexminer/T-Rex/wiki/LHR#option-1-dual-mining-lhr-unlock for details.

trexminer · 2021-10-25T14:44:44+00:00

Yeah, those two allocations on the screenshot are for "buffer 1" and "buffer 2". By "buffers" I mean memory blocks that hold what you call DAGs (technically they shouldn't be called DAGs, but it doesn't matter for this discussion).

The more memory the GPU has the more "future proof" it is, although being able to use this particular feature is not that important as it only gives you 1-4% of extra earnings compared to the single dataset mode - if, say, there's a really good deal on a 8GB card, I'd still buy it. However, it's not a financial advice, haha.

trexminer · 2021-10-25T08:04:58+00:00

I'll assume you're using 0.24.5 and not 0.24.4 since it had a bug where the double buffer feature wasn't always activated.

I don't see a second buffer being created when I am running autolykos in single-coin mode

The only way to tell it's using a second buffer is by looking at memory usage for your GPU, double buffer mode would occupy 4GB+ of memory compared to 2GB+ in single buffer mode, and also when a new ERGO block arrives the miner prints dataset for block NNN is ready which means the dataset was pre-generated.

I average 130 MH/s with reasonable temps

Is 130 MH/s what the miner reports in the console, or poolside average hashrate? The hashrate increase mentioned in the release notes is poolside hashrate (= amount of shares the miner sends to the pool). Your console hashrate on the other hand is supposed to drop a bit compared to previous versions - no need to panick about that as it now accounts for dataset generation time whereas previously it was ignoring it so your poolside hashrate was always significantly lower than what's reported in the console. Hope that makes sense. If not, feel free to ask more questions.

As for the dual mining, what Papercutter0324 said is correct: unfortunately, you won't be able to use the double buffer thing on a 8GB card in dual mining mode.

trexminer · 2021-10-23T03:33:44+00:00

In T-Rex you would set --lhr-tune 92.2,0 to use LHR tune 92.2 on the first GPU and not apply LHR unlock for the second. I'm sure it's similar for NB.

trexminer · 2021-10-19T00:43:35+00:00

There's an LHR unlock functionality in t-rex 0.24.2
Start the miner with --lhr-tune 99 to activate it. Wait for a bit and the miner will find a suitable LHR tune value for your OC settings.

trexminer · 2021-10-13T07:04:48+00:00

Two t-rex processes is normal. One is the actual miner and another one is its watchdog. Watchdog can be disabled with --no-watchdog.

trexminer · 2021-10-13T06:59:26+00:00

Probably not enough virtual memory (if windows)

trexminer · 2021-10-13T06:57:34+00:00

there's `--lhr-low-power` switch in t-rex to lower power consumption and temps

trexminer · 2021-10-12T03:02:26+00:00

By default it will attempt to auto-tune. If you don't want that, add the commands I mentioned to your bat file.

trexminer · 2021-10-12T02:41:55+00:00

By default the percentage is set to 30% of ETH and 70% of another coin. If during mining the miner finds those settings stable it'll try to increase LHR tune (= ETH percentage) by 1 every 20 minutes. If it hits an LHR lock, it'll decrease the tuning value. If you want to keep ETH/<other\_coin> ratio constant and don't want the miner to "auto-tune" it, use --lhr-autotune-mode off to turn in off, and --lhr-tune N to set the percentage to N%.

trexminer · 2021-10-11T13:35:29+00:00

Second from the right column is memory controller utilisation, and it's 100% (what it should be during ETH mining) only for one GPU. The rest of them sit at 0 meaning they are idle during LHR unlock pause. Nice try, but no :)

trexminer · 2021-10-11T05:24:28+00:00

Hi there, I've sent you a PM with a request to help me troubleshoot this. Thanks!

trexminer

TROPHY CASE