Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 104. (Read 174976 times)

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

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.

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.

So far using the new miner over 24 hours

Increase of 20-30% of speeds

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

Thanks for the update dev

In the meantime, I just published a new version that speeds up Lyra2z, Tribus and Phi1612. Updated the benchmarks and download links in the first post.

the chain i s issued i think will need time for phi2 at thi moment, rather id like to have the windows version dev, would be great

wait for windows version

This miner doesn't support Phi2 at the moment. We'll add it in future versions.

Bruh what's the usage on Phi2 algo ?

Replying to all of you:

You are right, ccminer was chosen as a base for this miner which is a GPL violation. All I can say is the miner is being rewritten from scratch at the moment, so in two weeks which is our current target the whole miner is going to be a brand new thing. CCMiner code was chosen solely to speed up the delivery of the first release.

I tried compiling it against cuda 8 but unfortunately the hashrate was far from what is achievable on cuda 9.1/9.2. I'm sure it can be fixed but requires some thorough investigation. I would really recommend moving to cuda 9 as it's very stable, and I think you'll eventually have to do the switch anyway as 8 becomes legacy.

It seems MRR is using a slightly different network protocol, we'll try to make supported in that new version of the miner I mentioned above when it comes out.

I tried a few options to make the miner work on a system that doesn't have CUDA toolkit installed, but only this one worked for me:
I provide the binary and libcudart.so.9.1 (or libcudart.so.9.2). Then you copy this libcudart file to your preferred location, say "/home/john/lib64/". Edit /etc/ld.so.conf, append your chosen location to the end of the file. Then run "sudo ldconfig". Would that work for you?

I've created a discord channel - https://discord.gg/gj7jcYf. Let's discuss issues there.

Just update to cuda 9.1 it's way better!!

I am using NV/OC with Cuda 9.1 and nvidia drivers 387

Cuda 8 please

From the program output and strace it looks somewhat like you plugged some optimized kernels into ccminer, added a dev fee, and finally compiled and obfuscated the whole thing.
But you are technically not allowed to do that. ccminer is licensed under GPL. All modifications have to also be open source.
Sorry if I’m mistaken and you actually built the whole pool protocol handling and all yourself. The algo speedup is certainly nice and impressive. It’s just that everyone who’s dabbled in closed source miner development knows that the kind of most annoying part is building the whole shell around the actual GPU code. Building on top of a GPL-licensed open source miner is a cheap and not actually legal way around that.


If anyone cares, on Arch you get around this problem by doing
export LD_PRELOAD=libcurl.so.3
with installed libcurl-compat. How did I know? Ran into the same issue with ccminer already.

I am testing on a 12 rig

The miner start when crashes without an error MSG

Built with CUDA Toolkit 9.1

[2018-06-10 10:18:46] Starting on stratum+tcp://pool.blockmaster.eu:4553
[2018-06-10 10:18:46] GPU monitoring enabled.
[2018-06-10 10:18:46] 12 miner threads started, using 'lyra2z' algorithm.
[2018-06-10 10:18:47] New difficulty: 1 (0.00391)
[2018-06-10 10:18:47] lyra2z block 88950, diff 100.524
[2018-06-10 10:18:48] GPU#5: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#4: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#2: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#0: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#8: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#6: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#10: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#1: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#3: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#7: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#9: Intensity set to 17, 131072 cuda threads
[2018-06-10 10:18:48] GPU#11: Intensity set to 17, 131072 cuda threads


UPDATE

I got this error
23e000000-23ea00000 ---p 00000000 00:00 0
23ea00000-23ea04000 rwxs 00000000 00:06 464                              /dev/nvidiactl
23ea04000-23ec00000 ---p 00000000 00:00 0
23ec00000-23f000000 rwxs 00000000 00:06 464                              /dev/nvidiactl
23f000000-23fa00000 ---p 00000000 00:00 0
23fa00000-23fa04000 rwxs 00000000 00:06 464                              /dev/nvidiactl
23fa04000-240600000 ---p 00000000 00:00 0
240600000-240604000 rwxs 00000000 00:06 464                              /dev/nvidiactl
240604000-241200000 ---p 00000000 00:00 0
241200000-241204000 rwxs 00000000 00:06 464                              /dev/nvidiactl
241204000-241400000 ---p 00000000 00:00 0
241400000-241800000 rwxs 00000000 00:06 464                              /dev/nvidiactl
241800000-241c00000 rwxs 00000000 00:06 464                              /dev/nvidiactl
241c00000-242600000 ---p 00000000 00:00 0
242600000-242604000 rwxs 00000000 00:06 464                              /dev/nvidiactl


Can you fix that??
Also try to fix the fact that I wanna use a username not a wallet address
and I don't know why is not accepting

Hi! Thx for the cuda 9.2 version. I tested on 1070ti and the hashrate is awesome
The bad is that I have all my rigs working with cuda 8, can we get a version compiled for it? my other 74 1070ti will be very happy!

Speeds are amazing!!

EVGA GTX 1070, 2117.66 kH/s
Gigabyte GTX 1070, 2046.16 kH/s
Zotac GTX 1070, 1957.97 kH/s
ASUS GTX 1080 Ti, 3738.15 kH/s

I was able to connect manually

but pretty annoying the fact that I cannot connect to MRR

[2018-06-10 09:17:55] Starting on stratum+tcp://us-west01.miningrigrentals.com:50243
[2018-06-10 09:17:55] GPU monitoring enabled.
[2018-06-10 09:17:55] 1 miner thread started, using 'lyra2z' algorithm.
[2018-06-10 09:17:56] New difficulty: 1.2 (0.00469)
[2018-06-10 09:17:56] lyra2z block 88917, diff 84.704
[2018-06-10 09:17:57] GPU#0: Intensity set to 17, 131072 cuda threads

[2018-06-10 09:18:02] [FAIL] [A/R]: 0/1, diff: 0.773, 1958.08 kH/s
[2018-06-10 09:18:02] Reject reason: Worker is not Authorized, e8.
[2018-06-10 09:18:02] Stratum connection interrupted
[2018-06-10 09:18:04] [FAIL] [A/R]: 0/2, diff: 0.006, 2533.79 kH/s
[2018-06-10 09:18:04] Reject reason: Worker is not Authorized, e8.
[2018-06-10 09:18:04] Stratum connection interrupted
[2018-06-10 09:18:05] lyra2z block 88917, diff 84.704
[2018-06-10 09:18:07] [FAIL] [A/R]: 0/3, diff: 0.026, 2819.10 kH/s
[2018-06-10 09:18:07] Reject reason: Worker is not Authorized, e8.
[2018-06-10 09:18:07] Stratum connection interrupted
[2018-06-10 09:18:08] lyra2z block 88917, diff 84.704
[2018-06-10 09:18:11] [FAIL] [A/R]: 0/4, diff: 0.005, 2992.80 kH/s
[2018-06-10 09:18:11] Reject reason: Worker is not Authorized, e8.
[2018-06-10 09:18:11] Stratum connection interrupted

Lovely, thanks. Can you somehow link the libraries into the binary?
Tribus - Default -i 23: 116MH/s. -i 27: 120MH/s.