T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner

[therteen]

The miner crashes on any intensity on 11 GPU rig
Ubuntu 16.04 Cuda 9.2
In two instances work with 6 and 5 gpu.

[1714043699]

1714043699

[1714043699]

1714043699

[trexminer]

The miner crashes on any intensity on 11 GPU rig
Ubuntu 16.04 Cuda 9.2
In two instances work with 6 and 5 gpu.

Hi therteen,

Yep, it's a known problem, the miner can't handle more than 8 gpus per instance. The temporary workaround is to run two or more instances depending on the number of cards in the rig - just the way you did it. Going to fix it in future versions.

[ingservi]

Increase of 20-30% of speeds

Amazing miner thanks so much dev for the hard work!!

But best be Increase of 100-150% of speeds 
And do not work rig 12 gpus

[MATPOC]

hi!

First of all I want to say dev - THANK YOU!!!

I gave questions.

1. I have got 3.95Mh on different 1080ti (core:-100, mem: -500. PL: default). What settings have you used to get 4.2Mh?
2. What about API? It seems doesn't work (hive don't line it:)

THANK YOU!!!:)

Please, continue your impossible work!:)

[trexminer]

hi!

First of all I want to say dev - THANK YOU!!!

I gave questions.

1. I have got 3.95Mh on different 1080ti (core:-100, mem: -500. PL: default). What settings have you used to get 4.2Mh?
2. What about API? It seems doesn't work (hive don't line it:)

THANK YOU!!!:)

Please, continue your impossible work!:)

You are very welcome. Regarding your questions:
1. It seems you've "underclocked" your card rather than overclock it. Try increasing your core from -100 to +100, I believe that would significantly increase your hashrate.
2. API and a windows version are on our priority list, we'll try to release it as soon as we can.

Cheers.

[MATPOC]

1. I have got 3.95Mh on different 1080ti (core:-100, mem: -500. PL: default). What settings have you used to get 4.2Mh?
2. What about API? It seems doesn't work (hive don't line it:)

You are very welcome. Regarding your questions:
1. It seems you've "underclocked" your card rather than overclock it. Try increasing your core from -100 to +100, I believe that would significantly increase your hashrate.

I have played with core freq and -i. I found stable work -i 17 and -100.... it's reason cause I asked you:)

I can send you any detailed bug report if you want.

2. API and a windows version are on our priority list, we'll try to release it as soon as we can.

Well!:)

[SimpleM]

3750MH/s on 1080Ti
1200MH/s on 1060/3

Hive doesn't have the libcudart.so.9.1, so perhaps you should include the library in the binary.

The miner crashes on the default intensity of 17 with this error:

Code:

*** Error in `./t-rex': free(): invalid size: 0x00007fc12c68e1d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fc1834647e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7fc18346d37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7fc18347153c]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1ebd3c)[0x7fc17df70d3c]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0xf886b)[0x7fc17de7d86b]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x248808)[0x7fc17dfcd808]
/usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1e4e80)[0x7fc17df69e80]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc1849186ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc1834f441d]
======= Memory map: ========
00400000-00595000 r-xp 00000000 00:00 0
00595000-00794000 ---p 00000000 00:00 0
00794000-00795000 r-xp 00000000 00:00 0
00795000-007bf000 rwxp 00000000 00:00 0
00800000-00801000 rwxp 00000000 00:00 0
00fd0000-01064000 rwxp 00000000 00:00 0                                  [heap]
200000000-200200000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
200200000-200400000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
200400000-200600000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
200600000-200800000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
200800000-200a00000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
200a00000-200c00000 rwxs 00000000 00:06 15577                            /dev/nvidiactl
...........

Lowering it down to intensity 16 seems to have solved it.
Can you enable the default API?

just type the following before running t-rex and it'd work. I used the 9.1 version.

Code:

export LD_LIBRARY_PATH=/hive/ccminer/cuda

[SimpleM]

Thanks for your efforts.

I tried with 1070Ti, works very good and im getting about 2.9Mh/s. However on 1070 (MSI) ive tried various OC settings and lower intensity, but gets my screen flooded with the following error.

Code:

[2018-06-14 22:52:27] GPU monitoring enabled.
[2018-06-14 22:52:27] 6 miner threads started, using 'lyra2z' algorithm.
[2018-06-14 22:52:28] New difficulty: 1 (0.00391)
[2018-06-14 22:52:28] lyra2z block 71279, diff 5522.959
[2018-06-14 22:52:28] GPU#0: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#1: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#3: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#5: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#2: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#4: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:35] [ OK ] [A/R]: 1/1, diff: 0.010, 1560.61 kH/s
[2018-06-14 22:52:37] [ OK ] [A/R]: 2/2, diff: 0.006, 7806.30 kH/s
[2018-06-14 22:52:38] [ OK ] [A/R]: 3/3, diff: 0.006, 8007.13 kH/s
[2018-06-14 22:52:40] [ OK ] [A/R]: 4/4, diff: 0.014, 8413.97 kH/s
[2018-06-14 22:52:40] [ OK ] [A/R]: 5/5, diff: 0.020, 8821.47 kH/s
[2018-06-14 22:52:41] [ OK ] [A/R]: 6/6, diff: 0.006, 9023.73 kH/s
[2018-06-14 22:52:41] [ OK ] [A/R]: 7/7, diff: 0.004, 9145.72 kH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 8/8, diff: 0.019, 9227.28 kH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 9/9, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 10/10, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 11/11, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:43] [ OK ] [A/R]: 12/12, diff: 0.038, 10.36 MH/s
[2018-06-14 22:52:43] [ OK ] [A/R]: 13/13, diff: 0.025, 10.48 MH/s
[2018-06-14 22:52:44] [ OK ] [A/R]: 14/14, diff: 0.014, 10.69 MH/s
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#0: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#2: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#0: the launch timed out and was terminated

[trexminer]

Thanks for your efforts.

I tried with 1070Ti, works very good and im getting about 2.9Mh/s. However on 1070 (MSI) ive tried various OC settings and lower intensity, but gets my screen flooded with the following error.

Code:

[2018-06-14 22:52:27] GPU monitoring enabled.
[2018-06-14 22:52:27] 6 miner threads started, using 'lyra2z' algorithm.
[2018-06-14 22:52:28] New difficulty: 1 (0.00391)
[2018-06-14 22:52:28] lyra2z block 71279, diff 5522.959
[2018-06-14 22:52:28] GPU#0: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#1: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#3: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#5: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#2: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:28] GPU#4: Intensity set to 17, 131072 cuda threads
[2018-06-14 22:52:35] [ OK ] [A/R]: 1/1, diff: 0.010, 1560.61 kH/s
[2018-06-14 22:52:37] [ OK ] [A/R]: 2/2, diff: 0.006, 7806.30 kH/s
[2018-06-14 22:52:38] [ OK ] [A/R]: 3/3, diff: 0.006, 8007.13 kH/s
[2018-06-14 22:52:40] [ OK ] [A/R]: 4/4, diff: 0.014, 8413.97 kH/s
[2018-06-14 22:52:40] [ OK ] [A/R]: 5/5, diff: 0.020, 8821.47 kH/s
[2018-06-14 22:52:41] [ OK ] [A/R]: 6/6, diff: 0.006, 9023.73 kH/s
[2018-06-14 22:52:41] [ OK ] [A/R]: 7/7, diff: 0.004, 9145.72 kH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 8/8, diff: 0.019, 9227.28 kH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 9/9, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 10/10, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:42] [ OK ] [A/R]: 11/11, diff: 0.004, 10.16 MH/s
[2018-06-14 22:52:43] [ OK ] [A/R]: 12/12, diff: 0.038, 10.36 MH/s
[2018-06-14 22:52:43] [ OK ] [A/R]: 13/13, diff: 0.025, 10.48 MH/s
[2018-06-14 22:52:44] [ OK ] [A/R]: 14/14, diff: 0.014, 10.69 MH/s
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#0: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#2: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#4: the launch timed out and was terminated
[2018-06-14 22:52:44] GPU#0: the launch timed out and was terminated

Hi SimpleM,

Error "the launch timed out and was terminated" usually indicates a problem with OC. Try using default intensity and no overclock at all to see if it's stable. And then slowly increase your OC. Just for reference, my 1070 are running stable at core +150, mem -500, power limit 110W. Yours may be different.

[Anthony42]

what maximum intensity can be put on 1070ti ?

[trexminer]

what maximum intensity can be put on 1070ti ?

Which algo? If Lyra2z, then default 17 should be okay to use. You can find out what the max intensity the card can handle by increasing it gradually and noting when it starts failing.

[skablast]

IF you are going to rewrite the software as you said, please mantain the basic setting of CCMiner for using/not using cards and for intensity.

I am using it with multipool/multialgo switcher, and I just rename it ccminer.... if you change the basic setting, Iam going to mess it up

[pileto3]

Waiting for the Windows version...

[Mind163]

1060 6GB = 1,749. +175/-1500. (core = 2180). Not bad.

[pekacoin]

Waiting for the Windows version...

Yes, I join the question. Will there be a version for Windows?

[Zoktog]

hello. how i'm run this miner with api?

[trexminer]

Yes, the Windows version will be available, we're working on it.
There's no API yet, we'll add it in the future versions.

[HashAuger]

Yes, the Windows version will be available, we're working on it.
There's no API yet, we'll add it in the future versions.

Porting your miner to Windows must be quite the endeavor, so thank you for all your efforts to do so.  While you are coding it, would you please consider either writing the miner in such a way that the console output can be redirected (for example, piping to a file) or that you include a parameter to generate a log file?  Without an API, those would be the only methods of extracting information from the miner.  Some miners, such as Klaust's variant of CCMiner will not redirect their screen output but other versions of CCMiner, such a Tpruvot's, will. Thanks for considering my suggestion.

[kwchmining]

Looking forward to deploying to my 150+ rigs as soon as Windows version is released. Tuned in..

[proo7]

T-Rex miner for modern Nvidia GPUs - Pascal & Maxwell generations

Supported algorithms: Lyra2z, Tribus, Phi1612. Linux version only.
This is a beta version so many features are missing or may not work properly. New algorithms/improvements are on their way.
Supported GPU architecture: Pascal (10xx series) and Maxwell

Performance

Lyra2z:
1070 (Core +160, Mem -500): ~2300 Kh/s
1070 Ti (Core +210, Mem -600): ~2900-3000 Kh/s
1080 Ti: 4200 Kh/s

Tribus:
1070 (Core +190, Mem 0):
   PL 150W - 77 Mh/s
   PL 130W - 74 Mh/s
1070 Ti (Core +210, Mem -600):
   PL 180W - 101 Mh/s
   PL 150W - 95 Mh/s
1080 Ti: ?

Phi1612:
1070 (Core +170, Mem -500):
   PL 130W - 23 Mh/s
1070 Ti (Core +210, Mem -600):
   PL 180W - 31.5 Mh/s
   PL 150W - 29.8 Mh/s
1080 Ti: ?


Please, do report what hashrate you get using other cards for our stats, and also feel free to experiment with overclock/power limit/intensity settings.

Download for Linux
CUDA 9.1: https://mega.nz/#!3NViQDiL!86C4-PCW_2ibP6JPgAZwW8kbh3wnXgPZuLa5fwzXrew
CUDA 9.2: https://mega.nz/#!DIsggTIb!x_IFOkine1JlatT6sLNnG6Nhry42nWfQtsymbOZv2Og

Usage
T-Rex supports command line arguments similar to that of ccminer:
lyra2z:

Code:

./t-rex -a lyra2z -o stratum+tcp://pool.bsod.pw:2159 -u <wallet> -p d=0.01 -N 30

phi:

Code:

./t-rex -a phi -o stratum+tcp://pool.bsod.pw:6667 -u <wallet> -p d=0.01 -N 10

tribus:

Code:

./t-rex -a tribus -o stratum+tcp://pool.bsod.pw:2260 -u <wallet> -p d=0.01 -N 10

Dev fee
Dev fee is set to 1%. When the miner starts and stops mining dev fee it reports it to the console output.

Release notes
0.3a
Faster Lyra2z, Tribus and slightly faster Phi1612.
Warning: If using Lyra2z in this version you will likely need to lower your overclock settings and probably also increase the power limit.

0.2
Added Lyra2z and Tribus.

0.1
Initial release. Phi1612 added.

When will windows version be released ?