Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 59. (Read 174982 times)
Hi, looks like --hide-date enabled by default. How to disable it? Tried 0, disable, 1:)
I see something strange with the newest 0.11.0:
Win 10, all Patches, newest drivers. MTP @ Nicehash with -i 21 (maybe this matters).
This only happens to 1080 Ti, but on all of my rigs. They are slightly overclocked, but 100% stable since over 1 year. Every 5-15 hours (completely random) 1-2 cards are fully crashing and then they look like deactivated. The watchdog want to restart the miner in a loop, but cant because of the "deactivated" cards. I have to reboot the system and everything is fine again. (If they would crash for real, these cards would have the stock clocks after reboot, but they still have all the settings. So its definitely not a real crash of that cards for sure.)
I dunno when and why, its completely random. But this does not happen with 0.10.2. Switched few rigs over and they run fine since 2 days without any failure.
Any guess what this could be? Already testing the intensity, already switched off the watchdog, but right now waiting for the next crash. But maybe you already have an idea.
Win 10, all Patches, newest drivers. MTP @ Nicehash with -i 21 (maybe this matters).
This only happens to 1080 Ti, but on all of my rigs. They are slightly overclocked, but 100% stable since over 1 year. Every 5-15 hours (completely random) 1-2 cards are fully crashing and then they look like deactivated. The watchdog want to restart the miner in a loop, but cant because of the "deactivated" cards. I have to reboot the system and everything is fine again. (If they would crash for real, these cards would have the stock clocks after reboot, but they still have all the settings. So its definitely not a real crash of that cards for sure.)
I dunno when and why, its completely random. But this does not happen with 0.10.2. Switched few rigs over and they run fine since 2 days without any failure.
Any guess what this could be? Already testing the intensity, already switched off the watchdog, but right now waiting for the next crash. But maybe you already have an idea.
Hi,
Why i do get the warn message "WARN: GPU #X result for XXXXXX does not validate on CPU! "
I'm using GTX 1660TI at HiveOS and T-Rex v0.11.0
Why i do get the warn message "WARN: GPU #X result for XXXXXX does not validate on CPU! "
I'm using GTX 1660TI at HiveOS and T-Rex v0.11.0
What are the best settings for mining Ravencoin x16r with a 1080ti with latest 0.11 ?
I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
You can set lowest memory clock and core will get some extra mhz I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
Best intensity in my tests is around 22-23
Thank you !
So, lowering the mem freq can get an increase of the core OC potential ?
I didn't know that
all off a sudden i get a lot off these when upgrading to the latest trex version on X16R ravencoin ( Simplemining platform ):
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
Could you check if there is any software binded to 4068 port?
Is it windows or linux? Do you get this messages right from the miner start? Will problem be fixed if you reboot your PC?
I've same issue on SMOS (linux) and solved like this :
use $rigName as worker . and seperate worker names as rig1 rig2 rig3
example : -a x16r -o stratum+tcp://rvn.suprnova.cc:6667 -u SuprnovaUserName.$rigName -p x
all off a sudden i get a lot off these when upgrading to the latest trex version on X16R ravencoin ( Simplemining platform ):
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
Could you check if there is any software binded to 4068 port?
Is it windows or linux? Do you get this messages right from the miner start? Will problem be fixed if you reboot your PC?
What are the best settings for mining Ravencoin x16r with a 1080ti with latest 0.11 ?
I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
You can set lowest memory clock and core will get some extra mhz I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
Best intensity in my tests is around 22-23
What are the best settings for mining Ravencoin x16r with a 1080ti with latest 0.11 ?
I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
I put a PL 85%, mem at stock ( doesn't increase hashrate with +300 mhz ), and I get approx 33 mh/s
Is it good ? Wich intensity is the better ?
all off a sudden i get a lot off these when upgrading to the latest trex version on X16R ravencoin ( Simplemining platform ):
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
20190521 12:40:12 WARN: ApiServer: failed to bind socket 0.0.0.0:4068 (Address already in use), next attempt in 5 seconds.
New version 0.11.0 released
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
How does the watchdog work? What do I need to set up?
(I am using the command in the .bat file)
Any tutorial...?
Watchdog activates automatically at the start. You don't need to do anything. Watchdog controls miner and GPU health, do restarts if problems occur. Also it preserves stats between restarts.
New version 0.11.0 released
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
How does the watchdog work? What do I need to set up?
(I am using the command in the .bat file)
Any tutorial...?
This happens since 0.10.2 and 0.11.0 with MTP @ Nicehash. Nothing dramatically, but its always a loss of 10 seconds when you start the miner.
i see the same with Nicehash on other miners
This happens since 0.10.2 and 0.11.0 with MTP @ Nicehash. Nothing dramatically, but its always a loss of 10 seconds when you start the miner.
What can we expect from gtx 1080ti on MTP?
3700-4200 depends from oc pl and intensity ( works up to 22 )
What can we expect from gtx 1080ti on MTP?
New version 0.11.0 released
Release notes
0.11.0
Add x25x algo (will be used by SUQA/SIN after the fork)
Bug fixes (built-in watchdog):
Miner fails to start when using Windows task scheduler or Awesome Miner
Miner restarts on Linux/Hive OS
Preserve a single log file across miner restarts
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
0.10.2
Add MTP algo (Zcoin)
Add Tesla P100 support
Add built-in watchdog (can be disabled using --no-watchdog parameter)
Default network timeout increased from 3 to 5 minutes
New parameter --hide-date to hide date part of the timestamp in the console
Prevent Windows from going to sleep mode while T-Rex is running
Release notes
0.11.0
Add x25x algo (will be used by SUQA/SIN after the fork)
Bug fixes (built-in watchdog):
Miner fails to start when using Windows task scheduler or Awesome Miner
Miner restarts on Linux/Hive OS
Preserve a single log file across miner restarts
NOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know
0.10.2
Add MTP algo (Zcoin)
Add Tesla P100 support
Add built-in watchdog (can be disabled using --no-watchdog parameter)
Default network timeout increased from 3 to 5 minutes
New parameter --hide-date to hide date part of the timestamp in the console
Prevent Windows from going to sleep mode while T-Rex is running
snip
5x EVGA GTX 1080 SC.
It's weird isn't it. Just like something's messing up the driver.
I'll try lowering the core substantially for starters, we'll see if it has any impact on this and the other crashes I'm having.
snip
5x EVGA GTX 1080 SC.
It's weird isn't it. Just like something's messing up the driver.
I'll try lowering the core substantially for starters, we'll see if it has any impact on this and the other crashes I'm having.
snip
Arguably, you have faced the conflict in sharing of interrupt signals. I would look for devices that share IRQ with your EVGA cards and turned them off one-by one until stability is achieved. Sure those devices ( if any) should have marginal significance (like sound for example) in mining.
T-Rex 0.10.2 (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
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
Thank you! Downloaded the update and am testing it now...
Failed!! I don't think it made it 10 minutes this time... :-(
T-Rex 0.10.2 (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
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
Thank you! Downloaded the update and am testing it now...
T-Rex 0.10.2 (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
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
Jump to: