Pages:
Author

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

jr. member
Activity: 224
Merit: 1
20181024 09:58:35 WARN: GPU #0: GeForce GTX 1080, intensity set to 20, 1048576 cuda threads
20181024 09:58:35 WARN: GPU #1: GeForce GTX 1080, intensity set to 20, 1048576 cuda threads
20181024 09:58:36 WARN: GPU #2: GeForce GTX 1060 3GB, intensity set to 20, 1048576 cuda threads
20181024 09:58:36 ApiServer: HTTP server started on 0.0.0.0:4067
20181024 09:58:36 ApiServer: Telnet server started on 0.0.0.0:4068
20181024 09:58:36 WARN: New difficulty: 8 (0.03125)
20181024 09:58:36 x16r block 417718, diff 78860.522
20181024 09:58:38 Hash order CEC13D87C50CC990
20181024 09:58:38 FugWrlFugBmwJh5ShbShvCubFugSkeBlkFugFugSmdSmdBlk
20181024 09:58:39 [ OK ] 1/1 - 55.25 MH/s, 109ms
20181024 09:58:39 [ OK ] 2/2 - 56.13 MH/s, 93ms
20181024 09:58:43 [ OK ] 3/3 - 56.72 MH/s, 109ms
20181024 09:58:45 [ OK ] 4/4 - 56.83 MH/s, 124ms
20181024 09:58:48 [ OK ] 5/5 - 56.82 MH/s, 109ms
20181024 09:58:48 GPU #0: GeForce GTX 1080 - 22.90 MH/s, [T:68C, P:199W, F:100%, E:173kH/W]
20181024 09:58:48 GPU #1: GeForce GTX 1080 - 23.18 MH/s, [T:62C, P:209W, F:100%, E:168kH/W]
20181024 09:58:48 GPU #2: GeForce GTX 1060 3GB - 10.74 MH/s, [T:60C, P:114W, F:70%, E:138kH/W]
20181024 09:58:48 Uptime: 12 secs
20181024 09:58:50 [ OK ] 6/6 - 56.80 MH/s, 93ms

------------------------------------------------------------------------------

20181024 11:40:34 GPU #0: GeForce GTX 1080 - 15.49 MH/s, [T:74C, P:196W, F:100%, E:79kH/W]
20181024 11:40:34 GPU #1: GeForce GTX 1080 - 15.67 MH/s, [T:69C, P:198W, F:100%, E:81kH/W]
20181024 11:40:34 GPU #2: GeForce GTX 1060 3GB - 7344.10 kH/s, [T:65C, P:121W, F:70%, E:64kH/W]
20181024 11:40:34 Uptime: 1 hour 41 mins 58 secs
20181024 11:40:36 [ OK ] 1036/1036 - 38.48 MH/s, 109ms
20181024 11:40:37 [ OK ] 1037/1037 - 38.49 MH/s, 102ms
20181024 11:40:46 [ OK ] 1038/1038 - 38.55 MH/s, 109ms
20181024 11:40:46 [ OK ] 1039/1039 - 38.57 MH/s, 109ms
20181024 11:40:49 [ OK ] 1040/1040 - 38.61 MH/s, 93ms
20181024 11:40:49 GPU #0: GeForce GTX 1080 - 15.54 MH/s, [T:74C, P:192W, F:100%, E:80kH/W]
20181024 11:40:49 GPU #1: GeForce GTX 1080 - 15.72 MH/s, [T:69C, P:186W, F:100%, E:81kH/W]
20181024 11:40:49 GPU #2: GeForce GTX 1060 3GB - 7346.28 kH/s, [T:65C, P:117W, F:70%, E:64kH/W]
20181024 11:40:49 Uptime: 1 hour 42 mins 13 secs
20181024 11:40:55 [ OK ] 1041/1041 - 38.76 MH/s, 109ms
20181024 11:41:06 [ OK ] 1042/1042 - 38.74 MH/s, 109ms
20181024 11:41:07 [ OK ] 1043/1043 - 38.76 MH/s, 109ms

-------------------------------------------------------------------------------

20181024 11:50:18 GPU #0: GeForce GTX 1080 - 19.75 MH/s, [T:74C, P:195W, F:100%, E:103kH/W]
20181024 11:50:18 GPU #1: GeForce GTX 1080 - 20.16 MH/s, [T:69C, P:204W, F:100%, E:105kH/W]
20181024 11:50:18 GPU #2: GeForce GTX 1060 3GB - 9321.47 kH/s, [T:65C, P:109W, F:70%, E:83kH/W]
20181024 11:50:18 Uptime: 1 hour 51 mins 42 secs
20181024 11:50:27 [ OK ] 1136/1136 - 53.82 MH/s, 124ms
20181024 11:50:32 [ OK ] 1137/1137 - 55.85 MH/s, 109ms
20181024 11:50:38 [ OK ] 1138/1138 - 58.84 MH/s, 125ms
20181024 11:50:46 [ OK ] 1139/1139 - 61.31 MH/s, 100ms
20181024 11:50:52 [ OK ] 1140/1140 - 61.33 MH/s, 103ms
20181024 11:50:52 GPU #0: GeForce GTX 1080 - 24.62 MH/s, [T:73C, P:192W, F:100%, E:129kH/W]
20181024 11:50:52 GPU #1: GeForce GTX 1080 - 25.12 MH/s, [T:69C, P:178W, F:100%, E:132kH/W]
20181024 11:50:52 GPU #2: GeForce GTX 1060 3GB - 11.59 MH/s, [T:65C, P:117W, F:70%, E:100kH/W]
20181024 11:50:52 Uptime: 1 hour 52 mins 17 secs
20181024 11:50:53 [ OK ] 1141/1141 - 61.33 MH/s, 125ms
20181024 11:50:54 [ OK ] 1142/1142 - 61.33 MH/s, 109ms

Why?
sr. member
Activity: 954
Merit: 250
Is ver 0.7.1 available? I hear people mentioning 0.7.1.
visit Discord
newbie
Activity: 165
Merit: 0
Hey guys, Whats the minimum CUDA version supported by this miner Please...

CUDA 9.1 - but works better on CUDA 9.2 and NVIDIA 399 drivers.
I update to version cuda 10 & NVIDIA 416 drivers and I'm disappointed.
Miner is not yet well optimized for new drivers.

Can you provide some more info? comparison?
Thanks
newbie
Activity: 73
Merit: 0
Is ver 0.7.1 available? I hear people mentioning 0.7.1.
newbie
Activity: 55
Merit: 0
Hey guys, Whats the minimum CUDA version supported by this miner Please...

CUDA 9.1 - but works better on CUDA 9.2 and NVIDIA 399 drivers.
I update to version cuda 10 & NVIDIA 416 drivers and I'm disappointed.
Miner is not yet well optimized for new drivers.
newbie
Activity: 11
Merit: 0
Hey guys, Whats the minimum CUDA version supported by this miner Please...
newbie
Activity: 7
Merit: 0
I'd recommend CUDA 9.2 with 399.24 drivers.
and drivers 416.16 Huh
newbie
Activity: 13
Merit: 0
Is there some command to restart miner in case of error?
sr. member
Activity: 954
Merit: 250
I'd recommend CUDA 9.2 with 399.24 drivers.
newbie
Activity: 7
Merit: 0
witch version i must install i have Nvidia 1070 and win 10 64bit
Windows:
CUDA 9.1: https://mega.nz/#!GQVxQA7L!SppCdxuy8ShbHclv0oiXuAxA1mHYllo2Okx2q8-aFIs
CUDA 9.2: https://mega.nz/#!OYNXEAhQ!abLofQ0_GZRl-HF8XjzoBH5kj664OI9beSl2nbdbFhA
CUDA 10.0: https://mega.nz/#!qVVFGaLR!B9lHI4M2zLiKLGVZ7pu1Bb_cwCjyJ-73ttE6BjCr2Kw
 what difrence betwen cuda 9.2 and 10
newbie
Activity: 8
Merit: 0
how many mh get 1060 on rvn?

GPU #0: Gigabyte GeForce GTX 1060 3GB - 9679.81 kH/s, [T:75C, P:88W, F:32%, E:113kH/W]
GPU #1: Gigabyte GeForce GTX 1060 3GB - 9657.39 kH/s, [T:70C, P:88W, F:30%, E:114kH/W]
GPU #2: Gigabyte GeForce GTX 1060 3GB - 9659.75 kH/s, [T:74C, P:79W, F:35%, E:114kH/W]
GPU #3: Gigabyte GeForce GTX 1060 3GB - 9661.77 kH/s, [T:70C, P:85W, F:30%, E:114kH/W]
GPU #4: Gigabyte GeForce GTX 1060 3GB - 9621.33 kH/s, [T:68C, P:78W, F:30%, E:113kH/W]
GPU #5: Gigabyte GeForce GTX 1060 3GB - 9582.04 kH/s, [T:70C, P:76W, F:30%, E:113kH/W]
full member
Activity: 658
Merit: 102
IDENA.IO - Proof-Of-Person Blockchain
how many mh get 1060 on rvn?
newbie
Activity: 55
Merit: 0
Hi,

Results before and after updating drivers and CUDA software.
https://www.imageupload.co.uk/images/2018/10/20/update.jpg

A little less stability Sad
4 x GeForce GTX 980 TI, win10


member
Activity: 283
Merit: 63
Hey dev!
Can you please fix "-r 0" flag behavior? It's impossible to setup multialgo mining. I noticed there is also --exit-on-connection-lost flag which doesn't really do anything in my case (first connection).
Example with "-r 0 --exit-on-connection-lost -T 5" flags:
20181018 22:58:41 Starting on: mine.zpool.ca:3643
20181018 22:58:41 ApiServer: HTTP server started on 0.0.0.0:4072
20181018 22:58:41 ApiServer: Telnet server started on 0.0.0.0:5072
20181018 22:58:41 WARN: GPU #1: PNY GeForce GTX 1080 Ti, intensity set to 24, 16777216 cuda threads
20181018 22:58:46 WARN: Connection with pool timed out. Trying to reconnect...
20181018 22:58:52 WARN: Connection with pool timed out. Trying to reconnect...

CCminer behavior with "-r 0" flag is simple. At launch try connect to the pool. If not possible, exit and don't waste time (~1 second). If yes - start mining.
Once the pool drops the connection for the first time, exit right away.



Other closed source competitors seem to have "correct" behavior, but i'd like to stick with t-rex mostly because of attitude.

Thanks!

Hi moroz,

Thanks for the bug report. We'll fix it in the next version. You may want to join our Discord channel where we usually publish our test/beta releases. The Discord link is on the first page.
member
Activity: 283
Merit: 63
Thanks for the reply.

Another question just came up today.  I am mining Suprnova's RVNCoin Pool, stratum+tcp://rvn.suprnova.cc:6667, and have seen a disparity between the confessed hash rate presented on t-rex and the confirmed hash rate presented on the Suprnova pool.  It has been absolutely accurate ever since I had started mining this pool 4 or 5 days back. Today it is not. Is there anyway to find out what going?  It seems about 25% lower on the Suprnova pool then being reported by t-rex.

Thanks.

-Rodger

If you're still using the same version of T-Rex, i.e. nothing's changed on the miner's side, then something must be going on at the pool. Maybe pool luck or some internal issue on their side, not sure.
newbie
Activity: 26
Merit: 0
Hey dev!
Can you please fix "-r 0" flag behavior? It's impossible to setup multialgo mining. I noticed there is also --exit-on-connection-lost flag which doesn't really do anything in my case (first connection).
Example with "-r 0 --exit-on-connection-lost -T 5" flags:
20181018 22:58:41 Starting on: mine.zpool.ca:3643
20181018 22:58:41 ApiServer: HTTP server started on 0.0.0.0:4072
20181018 22:58:41 ApiServer: Telnet server started on 0.0.0.0:5072
20181018 22:58:41 WARN: GPU #1: PNY GeForce GTX 1080 Ti, intensity set to 24, 16777216 cuda threads
20181018 22:58:46 WARN: Connection with pool timed out. Trying to reconnect...
20181018 22:58:52 WARN: Connection with pool timed out. Trying to reconnect...

CCminer behavior with "-r 0" flag is simple. At launch try connect to the pool. If not possible, exit and don't waste time (~1 second). If yes - start mining.
Once the pool drops the connection for the first time, exit right away.



Other closed source competitors seem to have "correct" behavior, but i'd like to stick with t-rex mostly because of attitude.

Thanks!
newbie
Activity: 7
Merit: 0
Hi Rodger,

Dev fee sessions kick in at random, so restarting the miner every hour won't affect dev fee payouts

Thanks for the reply.

Another question just came up today.  I am mining Suprnova's RVNCoin Pool, stratum+tcp://rvn.suprnova.cc:6667, and have seen a disparity between the confessed hash rate presented on t-rex and the confirmed hash rate presented on the Suprnova pool.  It has been absolutely accurate ever since I had started mining this pool 4 or 5 days back. Today it is not. Is there anyway to find out what going?  It seems about 25% lower on the Suprnova pool then being reported by t-rex.

Thanks.

-Rodger
member
Activity: 283
Merit: 63
Hello dev. 

I have been using this t-rex for windows for almost a week and like it very much.  I do have a question however concerning the fee.  More than happy to pay it as I do believe this miner is the faster then the others I have tried so far. 

My question is, if I start and stop my miner every hour, how will this affect my fee payouts?  I have shutdown setup in task scheduler to shutdown and restart every hour to make sure my 10 GPU's are all up and running.  Mining X16r can be a bit hard to hold a high overclock with low current, and I really do want all I can get out of my GPU's at minimal expense for electric.  This is the only reasonable answer I have right now, and it is working well.  But, I sure do not want to pay any extra fee for starting and stopping 24 times a day.

Thanks for your answer.

-Rodger

Hi Rodger,

Dev fee sessions kick in at random, so restarting the miner every hour won't affect dev fee payouts
member
Activity: 283
Merit: 63
Any plans to add x22i algo ?

Not yet, maybe in future releases
newbie
Activity: 7
Merit: 0
Hello dev. 

I have been using this t-rex for windows for almost a week and like it very much.  I do have a question however concerning the fee.  More than happy to pay it as I do believe this miner is the faster then the others I have tried so far. 

My question is, if I start and stop my miner every hour, how will this affect my fee payouts?  I have shutdown setup in task scheduler to shutdown and restart every hour to make sure my 10 GPU's are all up and running.  Mining X16r can be a bit hard to hold a high overclock with low current, and I really do want all I can get out of my GPU's at minimal expense for electric.  This is the only reasonable answer I have right now, and it is working well.  But, I sure do not want to pay any extra fee for starting and stopping 24 times a day.

Thanks for your answer.

-Rodger
Pages:
Jump to: