Pages:
Author

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

member
Activity: 238
Merit: 11
trexminer:

Issue of trex crashing after mining dev fee still exists in 0.7.3:


Thanks. This issue has just been identified and fixed.
0.7.4 will contain the fix

Works as advertised now, thanks
jr. member
Activity: 392
Merit: 5
Just try new version of t-rex 0.7.4 on my 1060 3Gb with algo x16r. Core clock  2025, memory in stock 8,5-15 M/h from card.
newbie
Activity: 25
Merit: 0
Loving this miner so far, vs enemy. My highs and lows are higher with T-Rex. Mining RVN btw
sr. member
Activity: 954
Merit: 250
how many h/s do you get with this miner for 1080 and 1080ti please?
Do you want to know all of 20 algos speed?
jr. member
Activity: 128
Merit: 5
Hey @trexminer thanks for keeping on the new algorithms and improving the existing ones. You are one of the hottest miners we have in PiMP OS now and we really appreciate the stability of both the hashing and the api so we can get accurate stats reporting to miner.farm web interface. It was nice talking to you about code today.

Keep up the "ferocious pace" of hard work and talk to you in your discord!

~ melt
getpimp.org | miner.farm
full member
Activity: 392
Merit: 159
how many h/s do you get with this miner for 1080 and 1080ti please?
member
Activity: 283
Merit: 63
Many thanks to the creator of this great miner,
and it would be really nice to have failover for pools in pools.txt files!

This feature is already supported via "-c " launch argument. See config_example file in the miner archive.
newbie
Activity: 16
Merit: 0
Many thanks to the creator of this great miner,
and it would be really nice to have failover for pools in pools.txt files!
hero member
Activity: 1274
Merit: 556
Good job on the miner, dev. I have finally been able to break 100 Mh/s x16r average over 24 hours on my 5x 1080 rig! Using -i 21, the rig is rock stable. Well done! Keep it up!

Edit: what's that "-N 36000" setting? I must've missed it... Ah nevermind. Just averaging period.
jr. member
Activity: 156
Merit: 1

I get:
t-rex 0.7.3: 29 MH/s x16r average (-N 36000 -i 25) per 1080ti @85% power load, core +125, mem +100
enemy 1.23: 28.6 MH/s x16r average (-N 36000 -i 25) per 1080ti @85% power load, core +125, mem +100

win10, cuda10 versions, latest drivers

will try 0.7.4....

t-rex 0.7.4: 29.4 MH/s x16r average (-N 36000 -i 25) per 1080ti @85% power load, core +125, mem +100
newbie
Activity: 4
Merit: 0
Miner v0.7.3 does not detect pool connection dropped.
With ZPool.ca, I use the algo autoswitch. When you connect to the "wrong" algo, the pool immediately disconnects. The miner waits the network timeout (default: 180 seconds) until it detects the pool is not there anymore. Other miners, such as ccminer, immediately detects the connection is lost, and if you have retries set to 0 (-r 0) it immediately exits.
Can this be fixed please?

What OS are you using? And also could you please provide the cmd line to replicate the issue (PM is fine)? Thanks

PM'd. Thanks.
newbie
Activity: 1
Merit: 0
hello ... with t-rex miner i have been happy since 0.7.3 came i had very weird issues the miner was just changing my power and overclock settings and in result my psu was stoping . why is this happening
jr. member
Activity: 156
Merit: 1

I get:
t-rex 0.7.3: 29 MH/s x16r average (-N 36000 -i 25) per 1080ti @85% power load, core +125, mem +100
enemy 1.23: 28.6 MH/s x16r average (-N 36000 -i 25) per 1080ti @85% power load, core +125, mem +100

win10, cuda10 versions, latest drivers

will try 0.7.4....
newbie
Activity: 13
Merit: 0
HiveOS version for 0.74?
member
Activity: 283
Merit: 63
Version 0.7.4 released

Minor performance improvements for skunk and x16 family of algorithms for Pascal and Turing cards

Bug fixes:
1) Crashes 20 sec after dev fee session when using -r 0
2) Temporary backed out "clean job" feature that was causing rejects on some pools e.g. beepool and bitpoolmining
3) Fix average hashrate reporting when using large -N values (over -N 4294)
jr. member
Activity: 557
Merit: 5
Can someone compare t-rex 072 and z-enemy 123 for x16r?
Some results is here

Too short time period. Due to algo switching only a parallel test over 24 hours can give you an accurate result.
Right now on my specific configuration t-rex 0.7.4 is slightly faster than z-enemy 1.23
newbie
Activity: 19
Merit: 0
Need support connection to p2pool, z-enemy works with it.
newbie
Activity: 155
Merit: 0
full member
Activity: 251
Merit: 100
Can someone compare t-rex 072 and z-enemy 123 for x16r?
Some results is here
member
Activity: 283
Merit: 63
Miner v0.7.3 does not detect pool connection dropped.
With ZPool.ca, I use the algo autoswitch. When you connect to the "wrong" algo, the pool immediately disconnects. The miner waits the network timeout (default: 180 seconds) until it detects the pool is not there anymore. Other miners, such as ccminer, immediately detects the connection is lost, and if you have retries set to 0 (-r 0) it immediately exits.
Can this be fixed please?

What OS are you using? And also could you please provide the cmd line to replicate the issue (PM is fine)? Thanks
Pages:
Jump to: