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

[Dr_Victor]

Which cuda version is good for nvdia gpu on x16r algorithm ?

It's obvious, Latest driver with cuda 10

It's definitely cuda 9.2 with 399.24 drivers (cuda 10 is experimental and slower).

[john1010]

@trexminer It would be great if you create a version for AMD cards.. Majority of the miners are using AMD because of the efficiency of the card for mining alts.. Looking forward for this thread for the development.  Thanks

[Divinity666]

It's definitely cuda 9.2 with 399.24 drivers (cuda 10 is experimental and slower).

yeah, I've also tried cuda 10 with 400 drivers and h\r was a blit slower with gtx1070\1080(ti), so I rolled back to 399.24

[mk111]

my t-rex miner freeze when dev fee pops up and its only happening to one of my rigs.
Any ideas?

I had the same issue today

[ProkVS]

Anyone can explain this?
Bsod pool x16r algo ravencoin

4rigs x 5x1080TI + conservative miner ) maybe..

[Nalut]

It's definitely cuda 9.2 with 399.24 drivers (cuda 10 is experimental and slower).

yeah, I've also tried cuda 10 with 400 drivers and h\r was a blit slower with gtx1070\1080(ti), so I rolled back to 399.24

Never thought i could reach 40mh/s but thanks to this miner it's possible.
Latest cuda/Driver
Edit stable for almost two days

[insider_83]

It's definitely cuda 9.2 with 399.24 drivers (cuda 10 is experimental and slower).

yeah, I've also tried cuda 10 with 400 drivers and h\r was a blit slower with gtx1070\1080(ti), so I rolled back to 399.24

https://i.imgur.com/eGcptDS.jpg
Never thought i could reach 40mh/s but thanks to this miner it's possible.
Latest cuda/Driver
Edit stable for almost two days

Lol. Do u really think that 1080ti shows 40Mh/s on X16R. It seems that u don't know aboy this algoritm, hashes jumps from 22 to 40 on 1080ti, and on other cards too. On your screen threre are 208Mh/s, but on the bottom of screen there are only 120.
P.S. 1080ti gives about 25-27Mh/s. but not 40 as u are sure.

[Nalut]

It's definitely cuda 9.2 with 399.24 drivers (cuda 10 is experimental and slower).

yeah, I've also tried cuda 10 with 400 drivers and h\r was a blit slower with gtx1070\1080(ti), so I rolled back to 399.24

Never thought i could reach 40mh/s but thanks to this miner it's possible.
Latest cuda/Driver
Edit stable for almost two days

Lol. Do u really think that 1080ti shows 40Mh/s on X16R. It seems that u don't know aboy this algoritm, hashes jumps from 22 to 40 on 1080ti, and on other cards too. On your screen threre are 208Mh/s, but on the bottom of screen there are only 120.
P.S. 1080ti gives about 25-27Mh/s. but not 40 as u are sure.

I know how the x16r algo works, i've tried old cuda with old drivers with trex 0.6.x max speed was 38mh/s min speed was 18mh/s
On the other hand when i tried the latest cuda with latest driver with trex 0.7.2 it's jumping from 22mhs to 40mhs
Just my two cents

[zot57]

How to set different intensity for different gpu's on same rig?
I have 1070 and 1060 3GB, btw which intensity would you recommend?

[jazz1984]

How to set different intensity for different gpu's on same rig?
I have 1070 and 1060 3GB, btw which intensity would you recommend?

In .bat file just set intencity for each card  -i 20,21,20,21. Try to start with default and then try to increase/decrease and watch to hashrates and stability. Ordinary it is between 19 and 22.

[Divinity666]

Never thought i could reach 40mh/s but thanks to this miner it's possible.

Depending on sequence I get 50mhs+ on 1080Ti's and 40mhs+ on 1080. On avg.(using -N 999999999) I get 26mhs and 20mhs respectively.

On the other hand when i tried the latest cuda with latest driver with trex 0.7.2 it's jumping from 22mhs to 40mhs

0.7.x will improve your h\r over 0.6.x. Cuda10 drivers over cuda9.2 on the other hand won't... at least for now.

[cyberd3vil]

my t-rex miner freeze when dev fee pops up and its only happening to one of my rigs.
Any ideas?

Same problem. Only 1 rig and always the same card when dev fee time (x22i). All other rigs with 1080Ti with exactly the same configuration and drivers, never.

[Mapuo]

my t-rex miner freeze when dev fee pops up and its only happening to one of my rigs.
Any ideas?

He mining other algo(at dev fee time), not your preferred. With more power consumption.
And will burn someone's psu.

[SEA1138]

I get an error after configuring the config_example:

Code:

* Line 8, Column 5
  Missing '}' or object member name

I don't see why. Line 8, column 5 is exactly the same as the original config_example

The full error is as follows:

Code:

20181103 03:57:07 ERROR: Can't start miner, can't parse json: {
  // List of main and failover pools
  "pools": [
    {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://eu.bsod.pw:2176",
        "pass": "d=3.8,c=RVN",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://yiimp.eu:3666",
        "pass": "d=3.8,c=RVN",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://rvn.virtopia.ca:3333",
        "pass": "x",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://minepool.com:3636",
        "pass": "d=3.8",
    }
  ],

  // Telnet API bind address.
  "api-bind-telnet": "0.0.0.0:4068", // Set to "0" to disable Telnet API

  // HTTP API bind address.
  "api-bind-http": "0.0.0.0:4067", // Set to "0" to disable HTTP API

  // If set to true enables json response for Telnet API.
  "json-response": false,

  // Connection retries count. After this number of attempts failover pool will be switched.
  "retries": 5,

  // Pause in seconds between retries.
  "retry-pause": 10,

  // Maximum time in seconds your pool connection may have no ping. After that reconnect will happen.
  "timeout": 180,

  // Name of mining algorithm. You can see available names at the top of the help file.
  "algo": "x16r",

  // This is GPU index in the system. You can select multiple GPUs sequentially: "devices": "0,2,3"
  "devices": 0, // Use only the first GPU in your rig. Remove this parameter to use all GPUs

  // Intensity used with your GPUs. It can be different for each GPU, e.g. "intensity": "20,21.4,23"
  "intensity": 19,

  // Sliding window length in sec used to compute average hashrate.
  "hashrate-avr": 30, // Set to 3600 to get average over an hour

  // Path to the log file. If only file name set log will be saved into directory with the miner.
  "log-path": "t-rex.log",
  // "log-path": "/home/x/t-rex.log", // Absolute path

  // Set process priority (default: 2) 1 below normal, 2 normal to 5 highest.
  "cpu-priority": 2,

  // Shutdown miner immediately if has any CUDA error.
  "exit-on-cuda-error": true,

  // Shutdown miner immediately if pool connection lost.
  "exit-on-connection-lost": false,

  // Forces miner to immediately reconnect to pool on N successively failed shares (default: 10).
  "reconnect-on-fail-shares": 10,

  // User protocol logging.
  "protocol-dump": false, // Set to true to turn it on.

  // Configurable GPUs report frequency. By default every 5 shares.
  "gpu-report-interval": 5,

  // Disable color output for console
  "no-color": false,

  // Quiet mode. No GPU stats at all.
  "quiet": false,

  // Shutdown miner after timeout in sec. By default disabled. (set to 0)
  "time-limit": 0,

  // Disables device till miner shutdown in case of overheat. Limit in Celsius. (set to 0)
  "temperature-limit": 0,

  // GPU temperature to enable card after it's been disabled. (default: 0 - disabled)
  "temperature-start": 0
}

* Line 8, Column 5
  Missing '}' or object member name


20181103 03:57:07 T-Rex finished

[LeGaL^CriMeR]

all night have digged def def

https://www.photobox.co.uk/my/photo/full?photo_id=501222334393

[minertalk]

Asus ROG Strix GeForce® GTX 1070 Ti Advanced edition 8GB GDDR5

Suqa (russian phonetic pronunciation : suka blea coin)
algo:x21i
t-rex-0.7.2-win-cuda10.0
win 7 sp1 64bit

After Burner settings:
power: 65%
core +240 (+250 is too much the app will return an error)
memory : +600

20181103 08:18:58 Uptime: 21 mins 35 secs
20181103 08:18:58 [ OK ] 175/176 - 7804.35 kH/s, 1027ms
20181103 08:19:03 [ OK ] 176/177 - 7813.92 kH/s, 449ms
20181103 08:19:05 [ OK ] 177/178 - 7816.01 kH/s, 449ms
20181103 08:19:24 [ OK ] 178/179 - 7813.87 kH/s, 1361ms
20181103 08:19:36 [ OK ] 179/180 - 7806.76 kH/s, 2252ms
20181103 08:19:36 GPU #0: ASUS GTX 1070 Ti - 7806.76 kH/s, [T:50C, P:105W, F:50%
, E:67kH/W]
20181103 08:19:36 Uptime: 22 mins 13 secs
20181103 08:19:53 [ OK ] 180/181 - 7806.33 kH/s, 2476ms
20181103 08:20:10 [ OK ] 181/182 - 7822.40 kH/s, 411ms
20181103 08:20:33 [ OK ] 182/183 - 7815.67 kH/s, 2242ms
20181103 08:20:48 x22i block 26197, diff 7437.214
20181103 08:20:58 [ OK ] 183/184 - 7808.31 kH/s, 2785ms
20181103 08:20:59 [ OK ] 184/185 - 7807.79 kH/s, 1854ms
20181103 08:20:59 GPU #0: ASUS GTX 1070 Ti - 7807.79 kH/s, [T:50C, P:112W, F:50%
, E:74kH/W]
20181103 08:20:59 Uptime: 23 mins 35 secs
20181103 08:21:06 [ OK ] 185/186 - 7809.43 kH/s, 3933ms
20181103 08:21:11 x22i block 26198, diff 9938.635
20181103 08:21:14 [ OK ] 186/187 - 7807.68 kH/s, 5051ms
20181103 08:21:15 [ OK ] 187/188 - 7807.95 kH/s, 3461ms
20181103 08:21:15 [ OK ] 188/189 - 7807.95 kH/s, 1386ms
20181103 08:21:39 [ OK ] 189/190 - 7806.09 kH/s, 1731ms
20181103 08:21:39 GPU #0: ASUS GTX 1070 Ti - 7806.09 kH/s, [T:50C, P:100W, F:50%
, E:72kH/W]
20181103 08:21:39 Uptime: 24 mins 16 secs
20181103 08:21:51 [ OK ] 190/191 - 7802.84 kH/s, 427ms
20181103 08:22:09 [ OK ] 191/192 - 7792.18 kH/s, 450ms
20181103 08:22:17 [ OK ] 192/193 - 7781.51 kH/s, 1303ms
20181103 08:22:21 [ OK ] 193/194 - 7783.30 kH/s, 2158ms
20181103 08:22:26 [ OK ] 194/195 - 7785.61 kH/s, 449ms
20181103 08:22:26 GPU #0: ASUS GTX 1070 Ti - 7785.61 kH/s, [T:50C, P:105W, F:50%
, E:75kH/W]
20181103 08:22:26 Uptime: 25 mins 3 secs
20181103 08:22:28 [ OK ] 195/196 - 7787.55 kH/s, 449ms
20181103 08:22:34 x22i block 26199, diff 10054.550
20181103 08:22:42 [ OK ] 196/197 - 7783.92 kH/s, 420ms
20181103 08:22:51 [ OK ] 197/198 - 7782.88 kH/s, 1733ms
20181103 08:23:07 [ OK ] 198/199 - 7788.67 kH/s, 3478ms

[minertalk]

@Depozitosuz

7870 kH/s but will eat more power  minim 120W max 140W
with 65% power is the best H/watt rate (104W-120W) and i get 7780 kH/s

[Ragnarok01]

I've tried but I miss one feature: failover pools in config.json.

[Dr_Victor]

Can someone compare t-rex 072 and z-enemy 123 for x16r?

[trexminer]

I get an error after configuring the config_example:

Code:

* Line 8, Column 5
  Missing '}' or object member name

I don't see why. Line 8, column 5 is exactly the same as the original config_example

The full error is as follows:

Code:

20181103 03:57:07 ERROR: Can't start miner, can't parse json: {
  // List of main and failover pools
  "pools": [
    {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://eu.bsod.pw:2176",
        "pass": "d=3.8,c=RVN",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://yiimp.eu:3666",
        "pass": "d=3.8,c=RVN",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://rvn.virtopia.ca:3333",
        "pass": "x",
    },
        {
        "user": "RUf8ZiAuPAmiA9jxfUZjP64fqPAtXSQTVH",
        "url": "stratum+tcp://minepool.com:3636",
        "pass": "d=3.8",
    }
  ],

  // Telnet API bind address.
  "api-bind-telnet": "0.0.0.0:4068", // Set to "0" to disable Telnet API

  // HTTP API bind address.
  "api-bind-http": "0.0.0.0:4067", // Set to "0" to disable HTTP API

  // If set to true enables json response for Telnet API.
  "json-response": false,

  // Connection retries count. After this number of attempts failover pool will be switched.
  "retries": 5,

  // Pause in seconds between retries.
  "retry-pause": 10,

  // Maximum time in seconds your pool connection may have no ping. After that reconnect will happen.
  "timeout": 180,

  // Name of mining algorithm. You can see available names at the top of the help file.
  "algo": "x16r",

  // This is GPU index in the system. You can select multiple GPUs sequentially: "devices": "0,2,3"
  "devices": 0, // Use only the first GPU in your rig. Remove this parameter to use all GPUs

  // Intensity used with your GPUs. It can be different for each GPU, e.g. "intensity": "20,21.4,23"
  "intensity": 19,

  // Sliding window length in sec used to compute average hashrate.
  "hashrate-avr": 30, // Set to 3600 to get average over an hour

  // Path to the log file. If only file name set log will be saved into directory with the miner.
  "log-path": "t-rex.log",
  // "log-path": "/home/x/t-rex.log", // Absolute path

  // Set process priority (default: 2) 1 below normal, 2 normal to 5 highest.
  "cpu-priority": 2,

  // Shutdown miner immediately if has any CUDA error.
  "exit-on-cuda-error": true,

  // Shutdown miner immediately if pool connection lost.
  "exit-on-connection-lost": false,

  // Forces miner to immediately reconnect to pool on N successively failed shares (default: 10).
  "reconnect-on-fail-shares": 10,

  // User protocol logging.
  "protocol-dump": false, // Set to true to turn it on.

  // Configurable GPUs report frequency. By default every 5 shares.
  "gpu-report-interval": 5,

  // Disable color output for console
  "no-color": false,

  // Quiet mode. No GPU stats at all.
  "quiet": false,

  // Shutdown miner after timeout in sec. By default disabled. (set to 0)
  "time-limit": 0,

  // Disables device till miner shutdown in case of overheat. Limit in Celsius. (set to 0)
  "temperature-limit": 0,

  // GPU temperature to enable card after it's been disabled. (default: 0 - disabled)
  "temperature-start": 0
}

* Line 8, Column 5
  Missing '}' or object member name


20181103 03:57:07 T-Rex finished

I believe the issue is the extra trailing comma after "pass": "d=3.8,c=RVN", and other pass fields