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

[-Rodger]

Did an update to latest nVidia drivers and now t-Rex is not working.  Here's the error message it gives - "Can't start miner, unable to get number of CUDA devices, is nvidia driver installed?"

My install went fine and it was work fine before the install.  I suspect this latest version (419.67) for Windows 10 is not compatible with this latest version on t_Rex.

I have 3 Windows 10 rigs, and I have only updated this one.  The other 2 are working (well creeping along really slow due to such high difficulty levels).

I can install the earlier version of nVidia drivers, but thought you might want to take a look at whats causing this.

-Rodger

[juhakall]

I'm developing a custom stratum server that seems to be working fine now (miners submit valid work), but t-rex is outputting these messages constantly:

WARN: New iteration find shares for device [ID=0, GPU #0]: job_id=2e61

What could be the cause? I don't get that connecting to normal stratum servers.

EDIT: Sorry, I realized there were extra warnings too with protocol debugging enabled. That's happening on other servers, too. Seems like it warns about receiving the same notify twice, is that somehow bad?

[trexminer]

Did an update to latest nVidia drivers and now t-Rex is not working.  Here's the error message it gives - "Can't start miner, unable to get number of CUDA devices, is nvidia driver installed?"

My install went fine and it was work fine before the install.  I suspect this latest version (419.67) for Windows 10 is not compatible with this latest version on t_Rex.

I have 3 Windows 10 rigs, and I have only updated this one.  The other 2 are working (well creeping along really slow due to such high difficulty levels).

I can install the earlier version of nVidia drivers, but thought you might want to take a look at whats causing this.

-Rodger

419.67 should be working fine. Someone from Discord had the same issue and then said it was fixed by "properly" installing the new drivers. Not sure what that means but I suspect the driver update screwed something up in the system so they had to clean everything up and reinstall the drivers.

[trexminer]

I'm developing a custom stratum server that seems to be working fine now (miners submit valid work), but t-rex is outputting these messages constantly:

WARN: New iteration find shares for device [ID=0, GPU #0]: job_id=2e61

What could be the cause? I don't get that connecting to normal stratum servers.

If you only see these messages when you run the miner with "--protocol-dump" (or "P") flag on, then it's normal.
UPD. Yeah, it's our debugging messages, we use it to troubleshoot things. Just ignore them.

[-Rodger]

Did an update to latest nVidia drivers and now t-Rex is not working.  Here's the error message it gives - "Can't start miner, unable to get number of CUDA devices, is nvidia driver installed?"

My install went fine and it was work fine before the install.  I suspect this latest version (419.67) for Windows 10 is not compatible with this latest version on t_Rex.

I have 3 Windows 10 rigs, and I have only updated this one.  The other 2 are working (well creeping along really slow due to such high difficulty levels).

I can install the earlier version of nVidia drivers, but thought you might want to take a look at whats causing this.

-Rodger

419.67 should be working fine. Someone from Discord had the same issue and then said it was fixed by "properly" installing the new drivers. Not sure what that means but I suspect the driver update screwed something up in the system so they had to clean everything up and reinstall the drivers.

Yes, first thing I did was a full uninstall, reg clean, reboot and reinstall again.  Didn't help.  This rig is my primary computer and I only run 2 GPU miners on it, so it's not a big deal.  But, since it was working and now it's not, I have to wonder why.  Had other things to tend to until just now, but I will look at this again tomorrow. I'm a 30 year computer tech BTW, so I will get it ironed out tomorrow.

[bracinac]

@trexminer, any help with this?

How to solve this?
OS: SMOS
algo: X16R

20360207 10:04:51 x16r block 628215, diff 133433.339
20360207 10:05:06 x16r block 628216, diff 133658.400
20360207 10:08:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20360207 10:08:06 WARN: Connection with pool timed out. Trying to reconnect...
20360207 10:08:06 Authorizing...
20360207 10:08:07 Authorized successfully.
20360207 10:08:29 x16r block 628217, diff 133093.467
20360207 10:09:02 x16r block 628218, diff 133366.705
20360207 10:09:51 x16r block 628219, diff 132969.159
20360207 10:11:53 x16r block 628220, diff 131603.105


Happens often on random rigs, rig stuck at this and not hashing until I reload miner.

Thanks!

[trexminer]

@trexminer, any help with this?

How to solve this?
OS: SMOS
algo: X16R

20360207 10:04:51 x16r block 628215, diff 133433.339
20360207 10:05:06 x16r block 628216, diff 133658.400
20360207 10:08:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20360207 10:08:06 WARN: Connection with pool timed out. Trying to reconnect...
20360207 10:08:06 Authorizing...
20360207 10:08:07 Authorized successfully.
20360207 10:08:29 x16r block 628217, diff 133093.467
20360207 10:09:02 x16r block 628218, diff 133366.705
20360207 10:09:51 x16r block 628219, diff 132969.159
20360207 10:11:53 x16r block 628220, diff 131603.105


Happens often on random rigs, rig stuck at this and not hashing until I reload miner.

Thanks!

Hi, could you please run the miner with "--protocol-dump -l trex.log" flags and then send me the log file when it happens again? I'll have a look. Thanks

[tomaroc]

@trexminer

T-rex will support SIN (SUQA) after the fork? This will be the new x25x algorithm..

greetings!

[bracinac]

@trexminer, any help with this?

How to solve this?
OS: SMOS
algo: X16R

20360207 10:04:51 x16r block 628215, diff 133433.339
20360207 10:05:06 x16r block 628216, diff 133658.400
20360207 10:08:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20360207 10:08:06 WARN: Connection with pool timed out. Trying to reconnect...
20360207 10:08:06 Authorizing...
20360207 10:08:07 Authorized successfully.
20360207 10:08:29 x16r block 628217, diff 133093.467
20360207 10:09:02 x16r block 628218, diff 133366.705
20360207 10:09:51 x16r block 628219, diff 132969.159
20360207 10:11:53 x16r block 628220, diff 131603.105


Happens often on random rigs, rig stuck at this and not hashing until I reload miner.

Thanks!

Hi, could you please run the miner with "--protocol-dump -l trex.log" flags and then send me the log file when it happens again? I'll have a look. Thanks

@trexminer Can you give me some support e-mail where I can send this log file to you? Thanks!

[trexminer]

@trexminer Can you give me some support e-mail where I can send this log file to you? Thanks!

Sorry, we don't have support email. You can either join our Discord server https://discord.gg/gj7jcYf and send a direct message to me there (my nickname is "trex") or upload your log file somewhere and send me the link. Thanks.

[crairezx20]

@trexminer Can you give me some support e-mail where I can send this log file to you? Thanks!

Sorry, we don't have support email. You can either join our Discord server https://discord.gg/gj7jcYf and send a direct message to me there (my nickname is "trex") or upload your log file somewhere and send me the link. Thanks.

Let me ask if the T-rex miner support solo mining? I was planning to mine new coins in some supported algo.

I tried to follow the solo mining from ccminer and set up as the same setup from ccminer but I'm always getting an error.
Can guide me the right direction?

[x001tk]

@trexminer, any help with this?

How to solve this?
OS: SMOS
algo: X16R

20360207 10:04:51 x16r block 628215, diff 133433.339
20360207 10:05:06 x16r block 628216, diff 133658.400
20360207 10:08:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20360207 10:08:06 WARN: Connection with pool timed out. Trying to reconnect...
20360207 10:08:06 Authorizing...
20360207 10:08:07 Authorized successfully.
20360207 10:08:29 x16r block 628217, diff 133093.467
20360207 10:09:02 x16r block 628218, diff 133366.705
20360207 10:09:51 x16r block 628219, diff 132969.159
20360207 10:11:53 x16r block 628220, diff 131603.105


Happens often on random rigs, rig stuck at this and not hashing until I reload miner.

Thanks!

Hi, could you please run the miner with "--protocol-dump -l trex.log" flags and then send me the log file when it happens again? I'll have a look. Thanks

@trexminer Can you give me some support e-mail where I can send this log file to you? Thanks!

Hi, I have the same issue.

Have you found any solution on that?

[trexminer]

Let me ask if the T-rex miner support solo mining? I was planning to mine new coins in some supported algo.

I tried to follow the solo mining from ccminer and set up as the same setup from ccminer but I'm always getting an error.
Can guide me the right direction?

The miner itself doesn't support solo mining, however you can still solo mine on some pools, e.g. https://bsod.pw/

[crairezx20]

Let me ask if the T-rex miner support solo mining? I was planning to mine new coins in some supported algo.

I tried to follow the solo mining from ccminer and set up as the same setup from ccminer but I'm always getting an error.
Can guide me the right direction?

The miner itself doesn't support solo mining, however you can still solo mine on some pools, e.g. https://bsod.pw/

Ok, thanks for the suggestion it's not actually a solo mining because they are still taking a pool fee and I thought that I can mine solo with T-rex I just planning to mine in my own full node and learn something that I can use for setting up a pool someday.

Anyway, can I ask if the T-rex has more command line that not listed in "help"? Something that can optimize and overclock the settings to speed up the mining speed?

[bracinac]

@trexminer, any help with this?

How to solve this?
OS: SMOS
algo: X16R

20360207 10:04:51 x16r block 628215, diff 133433.339
20360207 10:05:06 x16r block 628216, diff 133658.400
20360207 10:08:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20360207 10:08:06 WARN: Connection with pool timed out. Trying to reconnect...
20360207 10:08:06 Authorizing...
20360207 10:08:07 Authorized successfully.
20360207 10:08:29 x16r block 628217, diff 133093.467
20360207 10:09:02 x16r block 628218, diff 133366.705
20360207 10:09:51 x16r block 628219, diff 132969.159
20360207 10:11:53 x16r block 628220, diff 131603.105


Happens often on random rigs, rig stuck at this and not hashing until I reload miner.

Thanks!

Hi, could you please run the miner with "--protocol-dump -l trex.log" flags and then send me the log file when it happens again? I'll have a look. Thanks

@trexminer Can you give me some support e-mail where I can send this log file to you? Thanks!

Hi, I have the same issue.

Have you found any solution on that?

Waiting for @trexminer to give me some e-mail so I can send log file to him

[trexminer]

Ok, thanks for the suggestion it's not actually a solo mining because they are still taking a pool fee and I thought that I can mine solo with T-rex I just planning to mine in my own full node and learn something that I can use for setting up a pool someday.

Anyway, can I ask if the T-rex has more command line that not listed in "help"? Something that can optimize and overclock the settings to speed up the mining speed?

I see. No, unfortunately we don't have solo mining functionality in our miner.

Not entirely sure what you mean. All command line arguments supported by T-Rex are listed in the help file or accessible via "t-rex --help". Or are you requesting to add new functionality to the miner to overclock GPUs? If so, it's on our to-do list but not the first priority.

[trexminer]

Waiting for @trexminer to give me some e-mail so I can send log file to him

You must've missed my reply
"Sorry, we don't have support email. You can either join our Discord server https://discord.gg/gj7jcYf and send a direct message to me there (my nickname is "trex") or upload your log file somewhere and send me the link. Thanks."

[bracinac]

Waiting for @trexminer to give me some e-mail so I can send log file to him

You must've missed my reply
"Sorry, we don't have support email. You can either join our Discord server [ur]https://discord.gg/gj7jcYf[/url] and send a direct message to me there (my nickname is "trex") or upload your log file somewhere and send me the link. Thanks."

Oh sorry, I really missed
I've sent files.

Many thanks!

[TheHas]

Have done some testing between the various x16r miners out there and can advise that trex appears to be 8-10 percent faster than the next closest miner.

It is definitely faster than the suggested miner on sprnova (at least for me). Definitely worth trying.

[fishball1310]

  :)So if I would like to have business cooperation with trex, which email should I be involved into???