Search content
Sort by
Showing 8 of 8 results by VVoutje
Re: T-Rex 0.19.9 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
Any support for RTX 4ooo cards?
what rtx4000 cards are you talking about?
Nvidia quadro, used for video editing and some medical applications
In a RTX4000 you will find a TU104 processor and GDR6 memory, the same processor you will find on a RTX2080 also using GDR6 memory. So I thought T-REX should work here as well or doesn't it?
Are you using actual drivers "R460 U3 (461.40)" ?
Are you using t-rex-0.19.10(cuda10.0) or t-rex-0.19.10(cuda11.1) ?
Prefer to use t-rex-0.19.10(cuda11.1) on Turing processors, it will support the newest one.
Let us know how it's going, I'm rather curious about this.
Re: [ANN] T-Rex 0.8.3 NVIDIA GPU miner with web control monitoring page
Anyone know what this error is about? as soon as it goes to dev pool this happens
Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.
miner restarts
Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.
miner restarts
It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.
Yeah thanks ive increased the power from 65 to 70 and it seems ok for now well for the 2hrs anyway. The overclock is 100 on core and 300 on mem (1070ti)
On my GTX1070 core on +75 just stays stable on x16r algo, mem isn't used for that algo so is set to -400, in linux you set a power limit in Watt witch I did on 160W (Max=200)
Re: [ANN] T-Rex 0.8.3 NVIDIA GPU miner with web control monitoring page
Anyone know what this error is about? as soon as it goes to dev pool this happens
Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.
miner restarts
Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.
miner restarts
It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.
Re: [ANN] T-Rex 0.8.2 NVIDIA GPU miner with web control monitoring page
problem nvml?
Everything is running well, just try to find out how this intensity is influencing the gain and reports, that with a to high setting the gain was less on exactly the same system running parallel. Like to share it and hope for more shares so that we can set up things easy.
Re: [ANN] T-Rex 0.8.2 NVIDIA GPU miner with web control monitoring page
Did a test with my rig, 8 x 1070 under Linux Ubuntu LTE 18.04 Cuda 10.
Trex 0.8.2 first 4 cards intensity 21 / gpu +50 / men -400 / 170W -pl Brought me to 113 Raven/24h on a miner
Trex 0.8.2 last 4 cards intensity 22 / gpu +50 / men -400 / 170W -pl Brought me to 98 Raven/24h on a miner.
Great past 24h mining results I must say, blocks flying around
but getting a lower result on a higher intensity makes you think and get nuts. What to do with your settings on a X16r also?
GUI on rig was usable, for graph I do use the internal Intel of course. nvidia-smi shows some spare on the pl of 170W sometimes it jumps a little over it on both settings. GPU use most of the time 100% temps around 69 C and fans running 60%
What bothers me is the intensity, there is just so little usable info for it on a wild algorithm like the x16r and is difficult to prove as well. A day later it react smooth and then really aggressive again. But that?s probably also the reason it backs of the ASIC world of course.
For now I ?am happy and collecting, looking forward on shares of other experiences.
PS! switched now to t-rex 0.8.3 on Linux Ubuntu LTE 18.04 Cuda 10, till now it runs fine for 12 hours again.
Was it on the same rig on the same day or one day after the other.Trex 0.8.2 first 4 cards intensity 21 / gpu +50 / men -400 / 170W -pl Brought me to 113 Raven/24h on a miner
Trex 0.8.2 last 4 cards intensity 22 / gpu +50 / men -400 / 170W -pl Brought me to 98 Raven/24h on a miner.
Great past 24h mining results I must say, blocks flying around
but getting a lower result on a higher intensity makes you think and get nuts. What to do with your settings on a X16r also?GUI on rig was usable, for graph I do use the internal Intel of course. nvidia-smi shows some spare on the pl of 170W sometimes it jumps a little over it on both settings. GPU use most of the time 100% temps around 69 C and fans running 60%
What bothers me is the intensity, there is just so little usable info for it on a wild algorithm like the x16r and is difficult to prove as well. A day later it react smooth and then really aggressive again. But that?s probably also the reason it backs of the ASIC world of course.
For now I ?am happy and collecting, looking forward on shares of other experiences.
PS! switched now to t-rex 0.8.3 on Linux Ubuntu LTE 18.04 Cuda 10, till now it runs fine for 12 hours again.
With the difficulty changing everyday you can only compare on the same day with two rigs doing exactly the same hashrate on the same intensity. Then you can do a parallel test with different intensity.
Otherwise, you are comparing oranges to apples
Same miner with 8 cards split in 2 times 4 running parallel on same pool.
I know it's hard to get reliable results only the difficulty switching differs over the past 24h, that's my hole point of sharing it here to get useful info how to setup things well.
Re: [ANN] T-Rex 0.8.2 NVIDIA GPU miner with web control monitoring page
Did a test with my rig, 8 x 1070 under Linux Ubuntu LTE 18.04 Cuda 10.
Trex 0.8.2 first 4 cards intensity 21 / gpu +50 / men -400 / 170W -pl Brought me to 113 Raven/24h on a same miner
Trex 0.8.2 last 4 cards intensity 22 / gpu +50 / men -400 / 170W -pl Brought me to 98 Raven/24h on a same miner.
Great past 24h mining results I must say, blocks flying around but getting a lower result on a higher intensity makes you think and get nuts. What to do with your settings on a X16r also?
GUI on rig was usable, for graph I do use the internal Intel of course. nvidia-smi shows some spare on the pl of 170W sometimes it jumps a little over it on both settings. GPU use most of the time 100% temps around 69 C and fans running 60%
What bothers me is the intensity, there is just so little usable info for it on a wild algorithm like the x16r and is difficult to prove as well. A day later it react smooth and then really aggressive again. But that's probably also the reason it backs of the ASIC world of course.
For now I ?am happy and collecting, looking forward on shares of other experiences.
PS! switched now to t-rex 0.8.3 on Linux Ubuntu LTE 18.04 Cuda 10, till now it runs fine for 12 hours again.
Trex 0.8.2 first 4 cards intensity 21 / gpu +50 / men -400 / 170W -pl Brought me to 113 Raven/24h on a same miner
Trex 0.8.2 last 4 cards intensity 22 / gpu +50 / men -400 / 170W -pl Brought me to 98 Raven/24h on a same miner.
Great past 24h mining results I must say, blocks flying around
but getting a lower result on a higher intensity makes you think and get nuts. What to do with your settings on a X16r also?GUI on rig was usable, for graph I do use the internal Intel of course. nvidia-smi shows some spare on the pl of 170W sometimes it jumps a little over it on both settings. GPU use most of the time 100% temps around 69 C and fans running 60%
What bothers me is the intensity, there is just so little usable info for it on a wild algorithm like the x16r and is difficult to prove as well. A day later it react smooth and then really aggressive again. But that's probably also the reason it backs of the ASIC world of course.
For now I ?am happy and collecting, looking forward on shares of other experiences.
PS! switched now to t-rex 0.8.3 on Linux Ubuntu LTE 18.04 Cuda 10, till now it runs fine for 12 hours again.