Bitcoin Forum
June 17, 2021, 12:03:58 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 [62] 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 »
  Print  
Author Topic: T-Rex 0.20.4 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)  (Read 151541 times)
weifa
Sr. Member
****
Offline Offline

Activity: 768
Merit: 308


GeoCoin Developer - GIS Technologist


View Profile
December 03, 2020, 10:58:04 PM
 #1221

Great job with T-Rex Miner!  I found your miner on a list of Etchash supported miners, great job supporting the new Ethash variant.

I was wondering if you had any interest in adding support for Ubqhash?

Here's some of the technicals to help explain the algo changes more in depth:  https://blog.ubiqsmart.com/introducing-ubqhash-8fa515befd7

Ubiq has quite a large community of miners, but the current number of mining programs is somewhat limited.  I'm reaching out on behalf of the Ubiq community to see if you're interested in potentially adding Ubqhash support, thanks!
Thanks for reaching out. We might have a look into adding Ubqhash support in the future.
That would be great!  I'm happy to help test things out on some of my miners if you're able too.  Cheers!
1623888238
Hero Member
*
Offline Offline

Posts: 1623888238

View Profile Personal Message (Offline)

Ignore
1623888238
Reply with quote  #2

1623888238
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1623888238
Hero Member
*
Offline Offline

Posts: 1623888238

View Profile Personal Message (Offline)

Ignore
1623888238
Reply with quote  #2

1623888238
Report to moderator
LukaL
Jr. Member
*
Offline Offline

Activity: 87
Merit: 2


View Profile
December 07, 2020, 07:21:02 PM
 #1222

Hello guys... I need some help here.

I switched my gpus (gtx 1070 8gb) to ETH after a long time, and what I see is some strange behavior. It seems that hashrate is low, and memory overclock doesn't have any effect.
What I was able to google out is that apparently when there is more than 50% of 1070's gpu memory utilized it starts to behave strangely. When I try mining ETC everything is normal (sure ETC have DAG size much lower, after fork).
So mining ETC I am able to get 33 MHs at 90W, while
mining ETH I get 28 MHs at 115W ... you see my despair Cheesy ... also mining ETH overclockin core have positive effect on hashrate, while overclocking memory doesn't have any impact - which is not normal for ethash.

I was not able to find any solution to this.
So is there any workaround this issue?
Thanks for your help Wink Cheers

Crypto delegating manager
rotor33
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
December 10, 2020, 09:28:08 AM
 #1223

Fails on Game Ready Driver 460.79

20201209 17:22:39 T-Rex NVIDIA GPU miner v0.18.11  -  [CUDA v11.10]
20201209 17:22:39 r.2c8851280f45
20201209 17:22:39
20201209 17:22:40 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20201209 17:22:43 T-Rex NVIDIA GPU miner v0.18.11  -  [CUDA v11.10]
20201209 17:22:43 r.2c8851280f45
20201209 17:22:43
20201209 17:22:43 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20201209 17:23:45 T-Rex NVIDIA GPU miner v0.19.1  -  [CUDA v10.0]
20201209 17:23:45 r.99a7206c3590
20201209 17:23:45
20201209 17:23:46 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20201209 17:23:48 T-Rex NVIDIA GPU miner v0.19.1  -  [CUDA v10.0]
20201209 17:23:48 r.99a7206c3590
20201209 17:23:48
20201209 17:23:49 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
sxemini
Member
**
Online Online

Activity: 845
Merit: 16


View Profile
December 10, 2020, 09:37:13 AM
 #1224

Hello guys... I need some help here.

I switched my gpus (gtx 1070 8gb) to ETH after a long time, and what I see is some strange behavior. It seems that hashrate is low, and memory overclock doesn't have any effect.
What I was able to google out is that apparently when there is more than 50% of 1070's gpu memory utilized it starts to behave strangely. When I try mining ETC everything is normal (sure ETC have DAG size much lower, after fork).
So mining ETC I am able to get 33 MHs at 90W, while
mining ETH I get 28 MHs at 115W ... you see my despair Cheesy ... also mining ETH overclockin core have positive effect on hashrate, while overclocking memory doesn't have any impact - which is not normal for ethash.

I was not able to find any solution to this.
So is there any workaround this issue?
Thanks for your help Wink Cheers

Here i give you a reminder. My answer for you in the Phönixminer Thread

it is normal for the Nvidia Pascal GPU´s (all gtx 10x0) This cards slow down with every new DAG epoch, same HARDWARE bug as the AMD R9 290 and R9 390 had in the past.
So there is no solution. You can check this, if you benchmark ETH in Epoch 0 and Epoch 400 for example.

My P106 cards do 26mh at the beginning, now i am down to 24mh.

Donations ETH/ETC/TOKENS 0x3586fE59934c1Af2eE40d8376D1d1AF3BbA61708
Binance Bonus -> https://www.binance.com/de/register?ref=XTP9URDX
Phemex 200$ for free -> https://phemex.com/web/user/register?referralCode=DKJHM
turbare
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
December 10, 2020, 11:36:13 AM
 #1225

Getting error: WARN: WATCHDOG: T-Rex does not exist anymore, restarting...

T-rex 0.19.1 CUDA10

Just updated to NVIDIA drivers 460.79, Windows 10 x64; was working well with the previous driver version.



sxemini
Member
**
Online Online

Activity: 845
Merit: 16


View Profile
December 10, 2020, 12:12:00 PM
 #1226

Getting error: WARN: WATCHDOG: T-Rex does not exist anymore, restarting...

T-rex 0.19.1 CUDA10

Just updated to NVIDIA drivers 460.79, Windows 10 x64; was working well with the previous driver version.





Nvidia changed some things in new driver. Why you update? Newer driver bring not more hashrate. I can´t understand why all people update the driver if a new one is released.

Donations ETH/ETC/TOKENS 0x3586fE59934c1Af2eE40d8376D1d1AF3BbA61708
Binance Bonus -> https://www.binance.com/de/register?ref=XTP9URDX
Phemex 200$ for free -> https://phemex.com/web/user/register?referralCode=DKJHM
turbare
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
December 10, 2020, 12:13:53 PM
 #1227

If I didn't, you wouldn't have a reason to reply now right?
On a more serious note, because I mine on my gaming PC.

In any case, adding --no-nvml fixes it.
Cenorez
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
December 10, 2020, 08:10:19 PM
 #1228

If I didn't, you wouldn't have a reason to reply now right?
On a more serious note, because I mine on my gaming PC.

In any case, adding --no-nvml fixes it.



You are a genius! Thank you very much!
trexminer
Member
**
Offline Offline

Activity: 234
Merit: 52


View Profile
December 11, 2020, 08:52:35 AM
 #1229

T-Rex 0.19.3

* ("octopus") Performance improvements 1-2% on some configurations
* ("octopus", "ethash") Reduce the amount of invalid shares
* Add "--no-hashrate-report" parameter to disable hashrate reporting to the mining pool
* Add "--gpu-report-interval" parameter removed in an earlier version
* Add "--keep-gpu-busy" parameter to continue mining even in case of connection loss (useful if pausing GPUs causes instability)
* Add "--api-read-only" parameter to forbid applying config changes via API and web-monitoring page
* Add CUDA Compute Capability 8.0 video cards support (NVIDIA A100)
* (UI) Various cosmetic changes

Bug fixes:
* (Windows) Miner crashes when using v460.79 video drivers
unsivilaudio
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 11, 2020, 03:14:16 PM
 #1230

Heads up, new version breaks (on older AMD cpus?) now with 0.19.3
Quote
20201211 08:44:35 TREX: eyJhIjoiZEhab0NhQk91TDNjZ1FpRlptaG1XQjdid25DMEwwOEdDaXBXZC9SYnlYK1B4OXFFUnlURll jOHVXWENZTWdrUEZHM1ZLYVdNTlNyeGZ3WGxFZ1JuRm4xY3ZYc0VPNzloamhnUnpKaU9PTHdZTVR0Rj lILy9lWlYwNDRYUHA0QUE3WjhaUXU3QWdBd21LZzN3OXY5RTh3PT0iLCJiIjoiNndrb0h6cllXN015Q WdkTmRIaU5hdz09In0K
20201211 08:44:35 WARN: Miner is going to shutdown...
20201211 08:44:40 TREX: eyJhIjoieXZOMHNnVEhlM0VTTHVrMkFQMVpHTUZmbEEyMGF5WHpnM0lGeGlzT3YreVg4SHBoWitxY01 DWW1HWHVYQVk5b1FhWVdSaXBkaHE3VHExRDd6Tk9PcEs1Q1lMNnk3dFMrd3lGWjB4TlB3aWtZekZnU2 9tNFp4VklPSTJuakNsWDlXMnZjY0dkV3RmcnVyRDQ2R2EvVlV3PT0iLCJiIjoiTlF1aUt4WmxvaTV3Q VRuOGg3ajBFZz09In0K
20201211 08:44:40 WARN: Miner is going to shutdown...
20201211 08:44:46 TREX: eyJhIjoidjIwQUdHUzJVN2RMUnplRmcyNG5ja1pkVEY1VFpwYU1oeVVTTmx3RnRWdnd6eVdLMGk2amp odnZkRjRnczNzTWEyTFF3LzFoNGhSOU5ZbFJPWXBWcFR2N1ozVm41WHp3RlJBYmRQU3krMTVVVXZFb0 N4U2wwOVQ2OHVNY05sUjdxc283YU9TQUU5YmRIRGZGbytDWTNRPT0iLCJiIjoiVXNBbUhYcWljYkVme VRrcjVOT1N4dz09In0K
20201211 08:44:46 WARN: Miner is going to shutdown...
20201211 08:44:52 TREX: eyJhIjoiK1orbGx0WXhQMmE2b1hNTkxSRXRTQkpYUlo2MHBFa1U1MlEwVGovZERFUzFnWHE1eDlCbHN DWHdCdS9QZ0ZJWEYrdFhnUmJ3S0hJZDJpQkFrZldIdDBHL1l1b3dHdjE3Uk1TTG4xbERwYVRjZFlUYk x3K0xvN1hCU0Q4RURHY2xpdkQybmoyam8wa3A4T1hOUmFFU2hBPT0iLCJiIjoiMDErcmE4bWE4TVN6W XRUaHQvdEVDdz09In0K
20201211 08:44:52 WARN: Miner is going to shutdown...
20201211 08:49:39 TREX: eyJhIjoiUzljTkJ5dFhEanBwYUQyL2lzMzF3UFZjV01oVFhtYW9HSktIQVBXN3FGVlZnTjE5ZDhqNnl 2UTQzR0FGWGRjcjMwRWFJaG1BbjNJeG1EUDVHWmFxODFlWFZCSmVJd2s2cmg5bU00TzA5dm5MM0liSH VwWU9YZFRMRk94WlViZUU2RUFpb3ZleWk1c09qREk1QUUyc29nPT0iLCJiIjoiUENUMTdUczhBVzg3Q i9FbFV6NmlBQT09In0K
20201211 08:49:39 WARN: Miner is going to shutdown...
20201211 08:49:45 TREX: eyJhIjoib3dMdDdLL0xFNDdmVVFGcEU0dGYvbEVNNGwxb0Z0eC9nbzR3S0pDM0dINzlQcjhyUTVMdHp mY1dkYXR4Q0RsR0pUbm41YllUaytyTGt3cFozRmo0OXVyWC8ySGRzaGF5VWczWEpqNzc3QU5IaUVJNX hrMlp5enB4SWc3RUZIWTFBcVE2dU9XeCtBU010WVA0dlZJd3F3PT0iLCJiIjoieWZwbTZzWlFtc1BLc DNVNU1aMjlpUT09In0K
20201211 08:49:45 WARN: Miner is going to shutdown...

Host system is an old FX processor.  0.19.1 works fine still.
trexminer
Member
**
Offline Offline

Activity: 234
Merit: 52


View Profile
December 11, 2020, 03:20:54 PM
 #1231

Heads up, new version breaks (on older AMD cpus?) now with 0.19.3

Host system is an old FX processor.  0.19.1 works fine still.

Thanks for reporting, we'll fix it in the next version.
trexminer
Member
**
Offline Offline

Activity: 234
Merit: 52


View Profile
December 13, 2020, 07:50:46 AM
 #1232

T-Rex 0.19.4

Bug fixes:
* (Windows) Not showing temperature / power consumption details when using v460.79 video drivers
* (Linux) Miner not starting with various "TREX: xxxx" (base64 encoded) errors
* "--keep-gpu-busy" not working under some conditions
giga2020
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 17, 2020, 01:03:07 PM
Last edit: December 17, 2020, 02:20:35 PM by giga2020
 #1233

Hi,

I have used one internet connection on one system shared by Windows 10 and a switch between the other computer systems (all use Windows 10 and now Trex 0.19.4 cuda 11.10). I have no problem with the pool connection in the source system (which shared the Internet connection) and it works well and find shares. However, I get connection time out on the other ones starting from today, after the DAG sizes are set and MH/s are also visible (with all firewalls off) and working some minutes (e.g., 3 min), and hence they do not find any shares.  This process is repeated with no success such a loop.

FYI: Every thing about connection with pool was OK the previous days on Ethash algo with Claymore 15
The ping of the pool is also OK in all Windows 10 systems. I am not sure what the problem will be   Huh Huh

Thanks
giga2020
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 20, 2020, 12:11:40 PM
 #1234

Dear T-rex developer,

I hope everything goes well on your side. Recently, I have tried to migrate to one of the mining software recommended by 2miners website (i.e., gminer and t-rex). However, I have face difficulties in making them start to mine through a cable based or wireless based network. I am not sure what strategies or algorithms are behind the software for communicating with the mining pools, but the issue is still there on my side.
For your information, I have been successful in using an LTE USB dongle in using the t-rex 0.19.4 by the time being, but not tried it yet in gminer. The Claymore has also the same issue and is working using an LTE USB dongle, as a couple of days ago it faced the errors of time out or no connection through ADSL router cable or the shared Internet of working LTE USB dongle shared through a switch.
In other words, recently all of the the sofwares in my side have faced an strange issue.
Additionally, the Internet network can easily ping the eth.2miners.com without any problems on all rigs using cable, wireless or LTE USB dongle.
As I am not aware of the inside of the mining program, so I can not find out why the no connection or time out messages can be issued even if the ping replies are OK.

I would appreciated it if you may kindly comment on this issue.

Thanks for your attention in this regards.
trexminer
Member
**
Offline Offline

Activity: 234
Merit: 52


View Profile
December 20, 2020, 02:11:48 PM
 #1235

Dear T-rex developer,

I hope everything goes well on your side. Recently, I have tried to migrate to one of the mining software recommended by 2miners website (i.e., gminer and t-rex). However, I have face difficulties in making them start to mine through a cable based or wireless based network. I am not sure what strategies or algorithms are behind the software for communicating with the mining pools, but the issue is still there on my side.
For your information, I have been successful in using an LTE USB dongle in using the t-rex 0.19.4 by the time being, but not tried it yet in gminer. The Claymore has also the same issue and is working using an LTE USB dongle, as a couple of days ago it faced the errors of time out or no connection through ADSL router cable or the shared Internet of working LTE USB dongle shared through a switch.
In other words, recently all of the the sofwares in my side have faced an strange issue.
Additionally, the Internet network can easily ping the eth.2miners.com without any problems on all rigs using cable, wireless or LTE USB dongle.
As I am not aware of the inside of the mining program, so I can not find out why the no connection or time out messages can be issued even if the ping replies are OK.

I would appreciated it if you may kindly comment on this issue.

Thanks for your attention in this regards.

Hi. I'm not a network engineer, so you may want to direct your question to someone who is. What you describe sounds like a network related issue that's outside of our control. By the way, ICMP (used by ping) and TCP (used by mining software) are two different protocols, so if you don't have issues with one, that doesn't necessarily mean you won't have issues with the other.
Sorry I don't have a solution for your issue.
giga2020
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 20, 2020, 04:07:09 PM
 #1236

Dear T-rex developer,

I hope everything goes well on your side. Recently, I have tried to migrate to one of the mining software recommended by 2miners website (i.e., gminer and t-rex). However, I have face difficulties in making them start to mine through a cable based or wireless based network. I am not sure what strategies or algorithms are behind the software for communicating with the mining pools, but the issue is still there on my side.
For your information, I have been successful in using an LTE USB dongle in using the t-rex 0.19.4 by the time being, but not tried it yet in gminer. The Claymore has also the same issue and is working using an LTE USB dongle, as a couple of days ago it faced the errors of time out or no connection through ADSL router cable or the shared Internet of working LTE USB dongle shared through a switch.
In other words, recently all of the the sofwares in my side have faced an strange issue.
Additionally, the Internet network can easily ping the eth.2miners.com without any problems on all rigs using cable, wireless or LTE USB dongle.
As I am not aware of the inside of the mining program, so I can not find out why the no connection or time out messages can be issued even if the ping replies are OK.

I would appreciated it if you may kindly comment on this issue.

Thanks for your attention in this regards.

Hi. I'm not a network engineer, so you may want to direct your question to someone who is. What you describe sounds like a network related issue that's outside of our control. By the way, ICMP (used by ping) and TCP (used by mining software) are two different protocols, so if you don't have issues with one, that doesn't necessarily mean you won't have issues with the other.
Sorry I don't have a solution for your issue.

Many thanks for letting me know about TCP which is used by mining software. After doing the test command for TCP connection in Windows 10, which returned true, it started to work again via the cable... really strange to me but it works now.

Thanks again for your comment
trexminer
Member
**
Offline Offline

Activity: 234
Merit: 52


View Profile
December 21, 2020, 10:14:41 AM
 #1237

T-Rex 0.19.5

* ("octopus") Up to 20% performance improvements on most 20xx and 30xx series GPUs with low PL
* ("octopus") Add solo mining support
giga2020
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 24, 2020, 04:27:19 AM
 #1238

After working for some days, again with untouched and same configurations, the T-rex mining software stopped on the rig using shared LTE Internet with an error "no connection" on eth.2miners.com:2020 causing by failed to ethproxy-subscribe .... can not parse Json. However, the source rig with LTE Internet is still working without problems, firewalls are all disabled.
I have also tested the TCP connection as well as UDP connection with nmap software from nmap.org and they are successfully discovered well, specially the one related to 2020 port Huh Huh

Thanks
dirton
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
December 25, 2020, 06:09:46 AM
 #1239

Hi, I switch today to t-rex from Claymore's miner and getting 18-20 MH/s instead of 35MH/s on 1070ti no matter the setting, set highest intensity and CPU priority and no result.
Tried running benchmark with 383 epoch with which Claymore was still functioning, gettin better 27MH/s, but still not nearly good.
P00P135
Full Member
***
Offline Offline

Activity: 1035
Merit: 130


View Profile
December 25, 2020, 10:09:22 AM
 #1240

Hi, I switch today to t-rex from Claymore's miner and getting 18-20 MH/s instead of 35MH/s on 1070ti no matter the setting, set highest intensity and CPU priority and no result.
Tried running benchmark with 383 epoch with which Claymore was still functioning, gettin better 27MH/s, but still not nearly good.

Chck for newer drivers and make sure your OC settings are correct.  My 1070ti's get 33MH @120w with 150core 650Mem with HiveOS, newest Trex cuda 11.1 and 10 work for me.
Pages: « 1 ... 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 [62] 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!