TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI

[TrailingStop]

New Version: 3.0.2

FIX: Crash if password-field is too long
FIX: Minor fixes/corrections
Gen: Improved most of the supported algos
Gen: Support of CUDA 10.1 Update 2
New: Temperature control - please see ReadMe.txt
Note: Linux version requires Ubuntu 18.04 or later

Please report any issues and problems.

Thanks and: Happy Mining

[TrailingStop]

any idea why it's crashing on MTP for the last few versions? I have to use cryptodredge now for it.

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.8.3
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 431.60
nVidia OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TtMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: 
Properties: (WindowMode: ConsoleFormat, EngineType: TtMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\Miner\AppData\Roaming\AwesomeMinerService\tt-miner-3.0.1_1\TT-Miner.exe  -A MTP -P stratum+tcp://xxxx.nVidiaRig:xxx,verbose,sd=650@zcoin.mintpond.com:3000 --api-bind 127.0.0.1:4028
====================================================================================================
Mining Engine Process started, PID: 7320
> TT-Miner - Version: 3.0.1 (Aug  6 2019 08:19:01)
> 

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed

Hi,

thanks for your report. I was able to find a bug that could cause the problem you reported. It is fixed in the new release 3.0.2:

Windows: https://TradeProject.de/download/Miner/TT-Miner.zip
Linux: https://TradeProject.de/download/Miner/TT-Miner.tar.xz

Thanks for reporting!

[jasta more]

Any benchmarks with improved algo speed?

[dragonmike]

If you get cuda-error 7 please reduce the compute version of your GPU with the command line option: -compute 61
I see this a lot with 1660Ti.

Howdy!
I get that with my 2060's too.
What should I set the -compute option for the GPUs that do actually work (i.e. if I have to specify per device, like -compute xx, xx, xx, 61, 61, xx)?

[TrailingStop]

If you get cuda-error 7 please reduce the compute version of your GPU with the command line option: -compute 61
I see this a lot with 1660Ti.

Howdy!
I get that with my 2060's too.
What should I set the -compute option for the GPUs that do actually work (i.e. if I have to specify per device, like -compute xx, xx, xx, 61, 61, xx)?

Hi,

take as default the values you see when you start TT, compute is in brakets after the GPU name - here 7.5 and 6.1:

* #0 PCI 0:1 Zotac     GeForce RTX 2060 (7.5)     CoreClk 300 MHz   MemClk 405 MHz   6144 MB   SM: 30
* #1 PCI 0:2 Zotac     GeForce GTX 1070 (6.1)     CoreClk 139 MHz   MemClk 405 MHz   8192 MB   SM: 15


use: -compute 61 61 to set both to compute 6.1

On the other side you shouldn't get this. Are you on windows? Make sure to have the latest nvidia driver installed!

[TrailingStop]

Any benchmarks with improved algo speed?

I have some for my 2060 and 1070, but you will see that you will get completely different results. You will see differences for a different OS, a different OS-Version, different CPU, RAM, Vitual Memory, GPU, OC-settings, Memory on your GPU (size/clk), base/turbo clk of your gpu, fan & temp. And much more - they all have impact on your results. Also if you run ProgPoW you see the performance for a algo-snapshot - the algo will change all 50 blocks for rev 0.9.2 - and the ZANO version, and for every new epoch. So if I say you can get 14MH/s instead of 13.8 MH/s for ProgPoW092 with a 1070, then this might not be correct for you.

So- sorry, but I really think that it doesn't not make much sense because you will get other results.

[dragonmike]

If you get cuda-error 7 please reduce the compute version of your GPU with the command line option: -compute 61
I see this a lot with 1660Ti.

Howdy!
I get that with my 2060's too.
What should I set the -compute option for the GPUs that do actually work (i.e. if I have to specify per device, like -compute xx, xx, xx, 61, 61, xx)?

Hi,

take as default the values you see when you start TT, compute is in brakets after the GPU name - here 7.5 and 6.1:

* #0 PCI 0:1 Zotac     GeForce RTX 2060 (7.5)     CoreClk 300 MHz   MemClk 405 MHz   6144 MB   SM: 30
* #1 PCI 0:2 Zotac     GeForce GTX 1070 (6.1)     CoreClk 139 MHz   MemClk 405 MHz   8192 MB   SM: 15


use: -compute 61 61 to set both to compute 6.1

On the other side you shouldn't get this. Are you on windows? Make sure to have the latest nvidia driver installed!

I'm on HiveOS. The 1080's are fine as such, it's the 2060's that throw out the errors. I'll try with the other compute values!

EDIT: hmmm, still doing it: Error ******** GPU[04] CudaError: 7 at position 50

[TrailingStop]

If you get cuda-error 7 please reduce the compute version of your GPU with the command line option: -compute 61
I see this a lot with 1660Ti.

Howdy!
I get that with my 2060's too.
What should I set the -compute option for the GPUs that do actually work (i.e. if I have to specify per device, like -compute xx, xx, xx, 61, 61, xx)?

Hi,

take as default the values you see when you start TT, compute is in brakets after the GPU name - here 7.5 and 6.1:

* #0 PCI 0:1 Zotac     GeForce RTX 2060 (7.5)     CoreClk 300 MHz   MemClk 405 MHz   6144 MB   SM: 30
* #1 PCI 0:2 Zotac     GeForce GTX 1070 (6.1)     CoreClk 139 MHz   MemClk 405 MHz   8192 MB   SM: 15


use: -compute 61 61 to set both to compute 6.1

On the other side you shouldn't get this. Are you on windows? Make sure to have the latest nvidia driver installed!

I'm on HiveOS. The 1080's are fine as such, it's the 2060's that throw out the errors. I'll try with the other compute values!

Yes, setting the compute-value should fix this. It might come from a old cuda compiler that do not support your compute level, or it is just the graphics driver that doesn't support it.
you can also use -compute 61 to set all devices to 6.1

[dragonmike]

So if I set them all to 6.1 it works.
I'm using driver 430.26 in HiveOS.
Miner version is 3.0.1 I think (HiveOS hasn't updated to 3.0.2 yet).

Shouldn't the cards be able to run higher compute versions though?...

[TrailingStop]

So if I set them all to 6.1 it works.
I'm using driver 430.26 in HiveOS.
Miner version is 3.0.1 I think (HiveOS hasn't updated to 3.0.2 yet).

Shouldn't the cards be able to run higher compute versions though?...

Depends on the card you have. Rtx will be 7 and up.
I guess that the nvidia compiler that comes with hiveos.

[styleshifter]

Do you have a link with the version number in the file name for Linux, too?

[TrailingStop]

Do you have a link with the version number in the file name for Linux, too?

Yes. Same as for Windows with .tar.xz extention for zip.

[dragonmike]

For the records, I've been mining ProgPow overnight and hashrates have increased over time... That's a very nice feature (if intended!).

Before I let HiveOS upgrade itself (and TT-miner) to the latest version, I was doing 18.3+ MH/s on the 1080's and 17.7+ MH/s on the 2060's.
That's with power limit at 150W on the 1080's and 135W on the 2060's.

Impressive.
Good job, Herr TrailingStop.

[styleshifter]

Do you have a link with the version number in the file name for Linux, too?

Yes. Same as for Windows with .tar.xz extention for zip.

Okay, thanks for your reply.
I added the linux link to my page.

[TrailingStop]

UPDATE WILL BE AVAILABLE LATER TODAY!!!


TT-Miner Release 3.0.3

FIX: Possible crash under certain conditions
FIX: No notification about DevFee mining
Gen: Reduced CPU usage for MTP/ProgPoW/ETHASH
Gen: Reduced system-memory requirements for MTP/ProgPoW/ETHASH
Gen: Reduced requirements may result in better performance on your system


Please let me know if you have any issues.

[gusknure]

Hi TrailingStop, please see attached logs for new version. For me most stable version 2.2.5
https://drive.google.com/open?id=1-Cn1efFEWlCKRyZfaR4hn70kbLEiVcPJ
https://drive.google.com/open?id=1l5CReqMcO-X_pZW90IArCvk5qN40TU6Z
Thanks

[balda2017]

The requested URL /download/Miner/TT-Miner.zip was not found on this server.

[devivier]

The requested URL /download/Miner/TT-Miner.zip was not found on this server.
3.02 can not do the benchmark on asus rog strik rtx 2060 the 3.01 works

[TrailingStop]

TT-Miner Release 3.0.4

FIX: Possible crash under certain conditions
FIX: No notification about DevFee mining
FIX: TT sends invalid shares to pool under certain conditions when switch from REG to DEV mining
Gen: Reduced CPU usage for MTP/ProgPoW/ETHASH
Gen: Reduced system-memory requirements for MTP/ProgPoW/ETHASH
Gen: Reduced requirements may result in better performance on your system


Sorry for the confusion with version 3.0.3 - too many bugs ;-(

Please let me know if you have any issues with the release.

[devivier]

89/5000
impossible to benchmark with nicehash (time hout) 1.9.1.12 et 1.9.2.12 mtp et lyra2
asus card rog strik geforce rtx 2060 6go