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

melpheos

jr. member

Activity: 557

Merit: 5

Good job on x22i

Code:

20181125 22:52:00 GPU #0: GTX 1070 Ti - 8158.73 kH/s, [T:58C, P:70W, F:35%, E:115kH/W]
20181125 22:52:00 GPU #1: GTX 1070 Ti - 7872.22 kH/s, [T:56C, P:69W, F:31%, E:119kH/W]
20181125 22:52:00 GPU #2: GTX 1070 Ti - 7950.52 kH/s, [T:57C, P:69W, F:34%, E:122kH/W]
20181125 22:52:00 GPU #3: GTX 1070 Ti - 7317.69 kH/s, [T:55C, P:63W, F:29%, E:113kH/W]
20181125 22:52:00 GPU #4: GTX 1070 Ti - 7879.56 kH/s, [T:58C, P:67W, F:37%, E:116kH/W]
20181125 22:52:00 GPU #5: GTX 1070 Ti - 8245.67 kH/s, [T:59C, P:70W, F:38%, E:116kH/W]

Juniormkl

newbie

Activity: 155

Merit: 0

T-Rex 0.8.1 (Windows/Linux) added to https://www.minermonitoring.com/

Join our discord https://discord.gg/aGGaeqq

also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

trexminer

member

Activity: 283

Merit: 63

Version 0.8.1 released.
Performance improvements: x22i +10-20%

Bug fixes:
Miner hangs on start up when it doesn't receive authorize message response

NOTE: skunk may be slower by 1% than the previous version, will be fixed soon

jasta more

member

Activity: 224

Merit: 18

Quote from: dragonmike on November 24, 2018, 09:55:00 AM

Can anybody confirm whether T-Rex 0.8.0 is faster than CryptoDredge 0.10.0 on x22i please?
Specifically for Pascal cards (1080's) if anyone's got data...

EDIT: at first sight, it doesn't look like it.

It is,i am getting 16mhs with 1080ti and 11mhs with 1080 with -i 20.Havent tried pushing intensity any more because i have weak psus since it seems to draw more power than CD miner

cel1697i845

newbie

Activity: 24

Merit: 0

Test miners 24 hour 3x1080 GTX palit CryptoDredge, T Rex, ZealotEnemy:
Algo: X16s
Coin: PGN

https://youtu.be/ah0-IpSFTSM

dragonmike

hero member

Activity: 1274

Merit: 556

Can anybody confirm whether T-Rex 0.8.0 is faster than CryptoDredge 0.10.0 on x22i please?
Specifically for Pascal cards (1080's) if anyone's got data...

EDIT: at first sight, it doesn't look like it.

Many_rigs

newbie

Activity: 3

Merit: 0

the implementation of the failover function is very strange.
see claymore's

Dr_Victor

sr. member

Activity: 954

Merit: 250

I have tested T-rex 080, CryptoDredge 0.11.0 and Z-Enemy 1.24v3 CUDA 9.2 with mixed rig (gtx 1060, 1070 and 1080ti) for BCD, Bitcore and Skunk algo. PL62%.
180/176/163
257/248/244
391/394/383

trexsupport

newbie

Activity: 18

Merit: 0

Quote from: vitalyoff on November 23, 2018, 02:06:44 PM

Same problem with watchdog.exe
Infinite error WARN: WATCHDOG: inuse sign disappeared, restart T-Rex
If start direct t-rex.exe all work fine.

This and other bugs will be fixed in the next release, thank you for reporting!

vitalyoff

newbie

Activity: 10

Merit: 0

Same problem with watchdog.exe
Infinite error WARN: WATCHDOG: inuse sign disappeared, restart T-Rex
If start direct t-rex.exe all work fine.

Dr_Victor

sr. member

Activity: 954

Merit: 250

Quote from: jazz1984 on November 23, 2018, 02:34:46 AM

Using t-rex 0.8.0 cuda 9.2, 1060 cards, x16r, windows 7 x64, driver 416.94. My average hashrate on pool is 10.5 H/s per card. It seems 0.5 H/s more than prev version, good job. Does it make sense to try cuda 10 or it is more suitable for the 20xx series?

Try it, compare and inform us, please.

jazz1984

jr. member

Activity: 392

Merit: 5

Using t-rex 0.8.0 cuda 9.2, 1060 cards, x16r, windows 7 x64, driver 416.94. My average hashrate on pool is 10.5 H/s per card. It seems 0.5 H/s more than prev version, good job. Does it make sense to try cuda 10 or it is more suitable for the 20xx series?

minertalk

jr. member

Activity: 38

Merit: 6

X22i - Suqa Coin
T-Rex NVIDIA GPU miner v0.8.0 - [CUDA v10.0]
NVIDIA Driver v416.94

asus gtx 1070ti
power 65% clock +240 memory +600
8000kH/s w/ the cpu in idle if the cpu start to do some stuff (play a game / open the suqa wallet and do a cpu mining) then I get 8100kh/s

Code:

20181122 17:20:45 Shares/min: 14.1631
20181122 17:20:45 Uptime: 35 mins 39 secs
20181122 17:21:13 [ OK ] 506/506 - 8144.60 kH/s, 91ms
20181122 17:21:28 [ OK ] 507/507 - 8148.59 kH/s, 93ms
20181122 17:21:41 [ OK ] 508/508 - 8142.55 kH/s, 91ms
20181122 17:21:41 [ OK ] 509/509 - 8141.94 kH/s, 91ms
20181122 17:21:55 [ OK ] 510/510 - 8126.86 kH/s, 91ms
20181122 17:21:55 GPU #0: ASUS GTX 1070 Ti - 8126.86 kH/s, [T:51C, P:111W, F:50%
, E:73kH/W]
20181122 17:21:55 Shares/min: 13.8469
20181122 17:21:55 Uptime: 36 mins 49 secs
20181122 17:21:59 [ OK ] 511/511 - 8125.38 kH/s, 91ms
20181122 17:22:01 [ OK ] 512/512 - 8124.35 kH/s, 94ms
20181122 17:22:03 [ OK ] 513/513 - 8124.33 kH/s, 92ms
20181122 17:22:10 x22i block 39430, diff 9652.462
20181122 17:22:24 x22i block 39431, diff 9516.544
20181122 17:22:27 [ OK ] 514/514 - 8099.83 kH/s, 91ms
20181122 17:22:36 [ OK ] 515/515 - 8099.61 kH/s, 91ms
20181122 17:22:36 GPU #0: ASUS GTX 1070 Ti - 8099.61 kH/s, [T:51C, P:107W, F:50%
, E:76kH/W]
20181122 17:22:36 Shares/min: 13.7311
20181122 17:22:36 Uptime: 37 mins 30 secs
20181122 17:22:57 [ OK ] 516/516 - 8093.70 kH/s, 97ms
20181122 17:23:00 [ OK ] 517/517 - 8093.45 kH/s, 91ms
20181122 17:23:06 x22i block 39432, diff 9442.354
20181122 17:23:09 [ OK ] 518/518 - 8093.17 kH/s, 91ms
20181122 17:23:20 [ OK ] 519/519 - 8095.70 kH/s, 92ms
20181122 17:23:22 [ OK ] 520/520 - 8096.00 kH/s, 90ms
20181122 17:23:22 GPU #0: ASUS GTX 1070 Ti - 8096.00 kH/s, [T:51C, P:102W, F:50%
, E:74kH/W]
20181122 17:23:22 Shares/min: 13.5814
20181122 17:23:22 Uptime: 38 mins 17 secs
20181122 17:23:23 [ OK ] 521/521 - 8096.26 kH/s, 94ms
20181122 17:23:28 [ OK ] 522/522 - 8093.74 kH/s, 92ms
20181122 17:23:38 [ OK ] 523/523 - 8092.99 kH/s, 92ms
20181122 17:23:44 [ OK ] 524/524 - 8092.42 kH/s, 92ms
20181122 17:23:48 [ OK ] 525/525 - 8091.49 kH/s, 92ms
20181122 17:23:48 GPU #0: ASUS GTX 1070 Ti - 8091.49 kH/s, [T:51C, P:104W, F:50%
, E:75kH/W]
20181122 17:23:48 Shares/min: 13.5639
20181122 17:23:48 Uptime: 38 mins 42 secs
20181122 17:23:48 [ OK ] 526/526 - 8091.54 kH/s, 93ms
20181122 17:23:52 [ OK ] 527/527 - 8091.10 kH/s, 91ms
20181122 17:23:53 [ OK ] 528/528 - 8090.83 kH/s, 91ms
20181122 17:24:11 [ OK ] 529/529 - 8095.85 kH/s, 91ms
20181122 17:24:16 [ OK ] 530/530 - 8096.88 kH/s, 91ms
20181122 17:24:16 GPU #0: ASUS GTX 1070 Ti - 8096.88 kH/s, [T:51C, P:122W, F:50%
, E:76kH/W]
20181122 17:24:16 Shares/min: 13.5276
20181122 17:24:16 Uptime: 39 mins 10 secs

batbobi

newbie

Activity: 2

Merit: 0

someone pls help
ERROR : Cant start miner , Failed to get handler of GPU

7*1080 ti
416 driver
t-rex 0.8.0 cuda 10

ctp9

jr. member

Activity: 52

Merit: 5

New user here. I'm experienced with mining software in general, but with T-Rex and the "watchdog" function, I am receiving the following error loop when launching the watchdog executable (NOTE: Windows User-specific %PATH% omitted from this post):

Code:

20181122 04:57:38 WARN: WATCHDOG: inuse sign disappeared, restart T-Rex
20181122 04:57:38 WATCHDOG: terminating process 2728
20181122 04:57:38 WARN: WATCHDOG: T-Rex was killed
20181122 04:57:38 WATCHDOG: observer started
20181122 04:57:40 WATCHDOG: launching T-Rex
20181122 04:57:40 WATCHDOG: T-Rex process started
  - C:\path...to\t-rex-0.8.0-win-cuda10.0\t-rex.exe
  - 1724
  - ECEB64A661B2EE60.keepalive
20181122 04:57:40
20181122 04:57:40
20181122 04:57:41 WARN: WATCHDOG: inuse sign disappeared, restart T-Rex
20181122 04:57:41 WATCHDOG: terminating process 1724
20181122 04:57:41 WARN: WATCHDOG: T-Rex was killed
20181122 04:57:41 WATCHDOG: watchdog finished
20181122 04:57:42 T-Rex miner WATCHDOG v0.3
20181122 04:57:42
20181122 04:57:42 WATCHDOG: started with pid=7564
  - C:\path...to\t-rex-0.8.0-win-cuda10.0\watchdog.exe
20181122 04:57:42 WATCHDOG: observer started
20181122 04:57:43 WATCHDOG: launching T-Rex
20181122 04:57:43 WATCHDOG: T-Rex process started
  - C:\path...to\t-rex-0.8.0-win-cuda10.0\t-rex.exe
  - 7232
  - D388036A3516AE70.keepalive
20181122 04:57:43
20181122 04:57:43
20181122 04:57:45 WARN: WATCHDOG: inuse sign disappeared, restart T-Rex
20181122 04:57:45 WATCHDOG: terminating process 7232
20181122 04:57:45 WARN: WATCHDOG: T-Rex was killed
20181122 04:57:45 WATCHDOG: observer started
20181122 04:57:46 WATCHDOG: launching T-Rex
20181122 04:57:46 WATCHDOG: T-Rex process started
  - C:\path...to\t-rex-0.8.0-win-cuda10.0\t-rex.exe
  - 3280
  - D388036A3516AE70.keepalive

Infinite loop...

What's going on?

Nalut

member

Activity: 96

Merit: 10

Quote from: Dr_Victor on November 21, 2018, 01:50:38 PM

Quote from: Nalut on November 21, 2018, 12:04:52 PM

Quote from: trexminer on November 20, 2018, 11:57:07 PM

0.8.0 released

Tried it it's stuck at selected cuda devices in yellow and does nothing.
Went back to v7.4 for now

Maybe your drivers version doesn't match t-rex cuda version?

After a second try it worked, running driver 416 cuda 10
It's working now and stable

Dr_Victor

sr. member

Activity: 954

Merit: 250

Quote from: Nalut on November 21, 2018, 12:04:52 PM

Quote from: trexminer on November 20, 2018, 11:57:07 PM

0.8.0 released

Tried it it's stuck at selected cuda devices in yellow and does nothing.
Went back to v7.4 for now

Maybe your drivers version doesn't match t-rex cuda version?

Nalut

member

Activity: 96

Merit: 10

Quote from: trexminer on November 20, 2018, 11:57:07 PM

0.8.0 released

Tried it it's stuck at selected cuda devices in yellow and does nothing.
Went back to v7.4 for now

netto7

jr. member

Activity: 252

Merit: 4

Quote from: jazz1984 on November 21, 2018, 07:16:48 AM

Hi guys! Is there are any recommendations for driver version? Using t-rex 0.8.0 cuda 9.2, 1060 cards, x16r, windows 7 x64. Thank you.

im use last driver version with cuda 10 it work fine

jazz1984

jr. member

Activity: 392

Merit: 5

Hi guys! Is there are any recommendations for driver version? Using t-rex 0.8.0 cuda 9.2, 1060 cards, x16r, windows 7 x64. Thank you.

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