trexminer / t-rex Goto Github PK
View Code? Open in Web Editor NEWT-Rex NVIDIA GPU miner with web control monitoring page
T-Rex NVIDIA GPU miner with web control monitoring page
Hi
I p2pool developer.
Please, add --no-extranonce option to you miner
http://p2p-spb.xyz:6102/static/ - Raven node for check
hi where can dowload the new version?
Do you plan on supporting the new RavenCoin hardfork?
https://github.com/RavenCommunity
Since T-Rex 0.10.2 runs an error, the previous version is OK.
20190906 15:48:26 WATCHDOG: initialize error, memory dump: eyJhIjoiUVMrS1hta2I0b0NiSyttblJ5VEdMa3BHNmJrYWZXNUJFb2dsdHZ3MmVLd2xBTlVIeVNuYS9PSU5nWmdncGgyOXpnekIzZm9tVkluVzIrMXFyZHFvc0YwRE44a0hTWlMvQXAzQ1F3S2ozNmQxNmpvL3U4RXBlNVJ3OWlXcElSSmtIdHRxUlNmczh6M1ZpNlNmckM5ZlV3PT0iLCJiIjoib1RZSHBiL1RpRVZDSzBJSW1PeXBTQT09In0K
20190906 15:48:26 WARN: Messy shutdown...
Hi
I have a 10 GPU rig...
I get the following in my logs after submitting a bunch of successful shares:
LOGS IN NEXT REPLY
Any ideas?
Why is there no more detail? I tried --no-watchdog but doesn't fix it :-/
Thanks
When AMD?
Should AMD.
Many downloads more.
Such hashes much blocks
hi tried a few latest releases, looks like has to be recompiled:
./t-rex: /lib64/libcurl.so.4: no version information available (required by ./t-rex)
./t-rex: /lib64/libssl.so.1.0.0: version OPENSSL_1.0.0' not found (required by ./t-rex) ./t-rex: /lib64/libcrypto.so.1.0.0: version
OPENSSL_1.0.0' not found (required by ./t-rex)
./t-rex: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by ./t-rex) ./t-rex: /lib64/libstdc++.so.6: version
GLIBCXX_3.4.21' not found (required by ./t-rex)
I can't connect to SSL with Nanopool or 2miners pool. I have contacted support at Nanopool and they have verified that my settings are correct. They also tried to connect to SSL and failed with T-rex miner. Will there be support added for this? Otherwise I will be switching to a mining software that supports SSL connections. Thanks, any help with this would be appreciated. I have tired on Versions 14.6 and 14.4 with no luck.
Can you compile for macOS (10.12 & 10.13 since 10.14 doesn't support newer nvidia gpus yet). I can help. I'm running a few miners I compiled on my hackintosh.
有没有视频教程之内的啊,不怎么会弄
Hi
If I enable benchmark mode, the program will close itself.
The command I am using is: .\t-rex.exe --algo x16r --devices 3 --benchmark --time-limit 60
While mining is working without any issues.
Could you please look into it?
Thank you and have a great day!
Please add an algorithm x16rv2
RVN将在10月1日升级为x16rv2算法
I am mining on nvOC (Ubuntu) so I had to rename the executable from "t-rex" to "ccminer". I am seeing this in the output constantly:
WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
I suspect the issue is the renaming. I am currently using the "--no-watchdog" option to get around the issue and it is mining just fine. Does the watchdog implementation look for the name of the executable as a process or is my problem elsewhere?
ERROR: Can't initialize device [ID=0, GPU #0], cuda exception in [Mtp::allocate_extra_memory, 59], out of memory
Error "Result for ... does not alidate on CPU" occurs when using the CUDA 9.2 T-Rex binary and at least the following cards:
The CUDA 10.0 binary works well. But the average hashrate with CUDA 9.2 seems to be slightly highter. This bug is critical for automated solutions that launch miners.
Example error log:
20190425 00:23:45 Shares/min: 9.782 (Avr. 9.139), Avr.Power: 0W, Avr.Efficiency: -1TH/W
20190425 00:23:45 Uptime: 32 secs | Algo: x16r | T-Rex v0.9.2
20190425 00:23:46 [ OK ] 6/6 - 49.21 MH/s, 52ms
20190425 00:23:48 [ OK ] 7/7 - 49.27 MH/s, 53ms
20190425 00:23:50 [ OK ] 8/8 - 49.30 MH/s, 53ms
20190425 00:23:59 [ OK ] 9/9 - 49.37 MH/s, 53ms
20190425 00:23:59 [ OK ] 10/10 - 49.36 MH/s, 53ms
20190425 00:23:59 GPU #0: 27.54 MH/s
20190425 00:23:59 GPU #1: 21.82 MH/s
20190425 00:23:59 Shares/min: 14.104 (Avr. 12.881), Avr.Power: 0W, Avr.Efficiency: -1TH/W
20190425 00:23:59 Uptime: 46 secs | Algo: x16r | T-Rex v0.9.2
20190425 00:23:59 [ OK ] 11/11 - 49.36 MH/s, 53ms
20190425 00:24:01 WARN: GPU #1: result for 20e86518 does not validate on CPU!
20190425 00:24:20 WARN: GPU #1: result for 38fd47a4 does not validate on CPU!
Continuing from here #41 (same hardware and software specs)
After more tests on other algos as well, all 0.14.x versions are behaving really badly on my nodes that have many GPUs (like 13 GPUs) ... the nvidia driver is humped and the miner ends up hogging a single cpu core at 100% while the other cpu cores are idle. It seems it overloads the kernel with driver requests.
Trying to execute nvidia-smi just hangs.
0.12 does not have these issues. Executing nvidia-smi works fine and is quick, and I can see the miner uses all cpu cores at about 30-50% utilization.
This happens on algos such as x21s as well.
how do i run it, is there a start.bat file?
OSX HighSierra is faster than Windows8.1 for CPU Only algorithms like Argon2D-256.
same machine MacPro5,1, intel 2nd gen i7.
since Nvidia has CUDA drivers for OSX, im curious to know:
OSX vs. Win8.1 with X13-BCD.
front page has the port as 3637 and the miner will not connect, it should be 3737 for anyone who may have trouble
Windows 10 v1903 Defender reports virus Behavior.Win32/Generic.KL!ml is in this release.
Watchdog is continuously restarting my instances for no reason, utilizing --no-watchdog does not result in any crashed miners.
Could you add reporting per-device accepted and rejected shares in the /summary
API?
This is useful for diagnosing which GPU is responsible for the rejected shares.
There are several Tesla model cards like the M2050, M2070, K10, and K20, that are passive cooled in a rack or have their own fans attached.
They don't report back a call to the query for fan speed.
When T-rex is launched with CUDA 9 or 10 in Windows 10 x64. There is no response to the fan check query through the driver. Mining is stopped since it can't read the fan rpm.
However, other miner applications out there do have an ignore option for this.
Assuming the user is fully understanding that they can monitor their own cards.
Also, some of the older Fermi Tesla cards don't even report temperature. I did check to see if the --temperature-limit 0 works. But it won't get to that point since the miner app wants an rpm count from nvsmi first.
But it would also be nice to disable that. Some of us miners already have the cards in a wind tunnel or oil bath cooling these cards with external hardware based controls that are outside of a software call.
Also tried with --nowatchdog and --nonvml options. Didn't make a difference.
I updated to 0.9.2, win 10, cuda 10, and for x16rt the hashrate droped from 97 to 92 mh/s on my 7 GPU rig (1060 3GB). This is the average HR on MiningRigRentals during the rental period, after 24 h.
You give the error:
20190518 14:29:50 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating...
But it doesn't say which GPU#, so I dont' know which one is the culpri tin order to reduce overclock for that particular GPU only.
Could you please include the GPU# in the error?
Please release source code. Source contain readme.md
I want to build T-Rex for Slackware Linux 14.2 - 64 and 32 Bit with different CUDA
Thank You
When displaying the version, please include what version of Cuda it was compiled for.
For Example:
T-Rex NVIDIA GPU miner v0.9.1 CUDA v10.0
RVN is switching to the new x16rV2 algo on October, 1.
https://coindar.org/en/event/ravencoin-rvn-hard-fork-23616
Do you plan on supporting it?
能更新 支持Lyra2v3算法吗
挖VTC
no matter what I do I cannot get this to mine locally do you have any ideas?
Can you check?
t-rex file work fine
20181122 17:10:10 20181122 17:10:10 20181122 17:10:11 T-Rex NVIDIA GPU miner v0.8.0 - [CUDA v9.20] 20181122 17:10:11 20181122 17:10:11 NVIDIA Driver v396.44 20181122 17:10:11 CUDA devices available: 12 20181122 17:10:11 20181122 17:10:11 URL : stratum+tcp://rvn-pool.beepool.org:9531 20181122 17:10:11 USER: RRpoESGMjdfMEJ73GLLhU5hkSBKQZMXdmT.rig1 20181122 17:10:11 PASS: x 20181122 17:10:11 20181122 17:10:11 WARN: Temperature limit is activated. Limit is set to 70C. 20181122 17:10:11 20181122 17:10:11 Starting on: rvn-pool.beepool.org:9531 20181122 17:10:11 WARN: GPU #0: ASUS GeForce GTX 1070 Ti, intensity set to 20 20181122 17:10:11 WARN: GPU #1: ASUS GeForce GTX 1070 Ti, intensity set to 20 20181122 17:10:12 WARN: GPU #2: ASUS GeForce GTX 1070 Ti, intensity set to 20 20181122 17:10:12 WARN: GPU #3: ASUS GeForce GTX 1070 Ti, intensity set to 20 20181122 17:10:12 WARN: WATCHDOG: inuse sign disappeared, restart T-Rex 20181122 17:10:12 WATCHDOG: terminating process 7769 20181122 17:10:12 WARN: WATCHDOG: T-Rex was killed 20181122 17:10:12 WARN: WATCHDOG: detected crash on start. Watchdog deactivated. 20181122 17:10:12 WATCHDOG: watchdog finished
upgraded from trex v 0.11 to v0.14.4 to support the rvn fork, and now the miner wont stay up. on centos 7, Driver Version: 430.50 CUDA Version: 10.1,
I tried checking and adding DNS in /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
not sure where to look as to why it can't connect for dev fee
Ubuntu 16.04, Cuda 10, Nvidia 415.27, i3-7100, 8GB ram. Below is an example where GPU 13 dropped hashrate after 27 minutes by 60-70%. It never recovers. There was no error whatsoever. Kernel reported no Xid errors either. Then after a longer while GPU 8 hashrate also drops (see further down). The after a while GPU 3 drops hashrate too. You can notice the other GPUs have dropped a little hashrate too, though not 60%.
If I restart t-rex then they all start with max hashrate again and then after a while some GPUs again drop hashrate one by one. The GPUs are not always the same. There are never any errors (either reported by t-rex or driver errors in kern.log).
Before this starts happening, the t-rex process uses about 30% of each CPU thread (it's clearly multi-threaded). After this starts happenning, the t-rex process is no longer multi-thread and uses only a single thread at 100% utilization, while the other threads are idle.
This started happening ever since 0.12.1 if I recall correctly.
I also tried --no-nvml and --no-watchdog as well.
I manage numerous such machines (each with 13 GPUs). They all behave the same. This isn't a hardware fault.
Clearly this is a bug in t-rex, some leak or something, dropping the mining hashrate by 30% within a few hours as GPUs drop hashrate one by one. It may be related to your devfee mining (it's all very ominous, including that single thread at 100% utilization)
20191007 02:58:41 [ OK ] 79/80 - 25.95 MH/s, 412ms
20191007 02:58:41 GPU # 0: Zotac GTX 1070 - 2000.85 kH/s
20191007 02:58:41 GPU # 1: Zotac GTX 1070 - 1989.10 kH/s
20191007 02:58:41 GPU # 2: Zotac GTX 1070 - 2027.67 kH/s
20191007 02:58:41 GPU # 3: Zotac GTX 1070 - 1969.05 kH/s
20191007 02:58:41 GPU # 4: Zotac GTX 1070 - 1958.94 kH/s
20191007 02:58:41 GPU # 5: Zotac GTX 1070 - 1955.58 kH/s
20191007 02:58:41 GPU # 6: Zotac GTX 1070 - 2003.88 kH/s
20191007 02:58:41 GPU # 7: Zotac GTX 1070 - 1982.01 kH/s
20191007 02:58:41 GPU # 8: Zotac GTX 1070 - 1997.89 kH/s
20191007 02:58:41 GPU # 9: Zotac GTX 1070 - 2050.20 kH/s
20191007 02:58:41 GPU #10: Zotac GTX 1070 - 2048.89 kH/s
20191007 02:58:41 GPU #11: Zotac GTX 1070 - 2016.11 kH/s
20191007 02:58:41 GPU #12: Zotac GTX 1070 - 1946.92 kH/s
20191007 02:58:41 Shares/min: 2.542 (Avr. 2.868)
20191007 02:58:41 Uptime: 27 mins 32 secs | Algo: mtp | T-Rex v0.14.4
20191007 02:58:52 [ OK ] 80/81 - 25.95 MH/s, 424ms
20191007 02:59:38 [ OK ] 81/82 - 25.96 MH/s, 448ms
20191007 02:59:48 [ OK ] 82/83 - 25.96 MH/s, 420ms
20191007 03:00:10 [ OK ] 83/84 - 25.95 MH/s, 472ms
20191007 03:00:11 [ OK ] 84/85 - 25.95 MH/s, 480ms
20191007 03:00:15 [ OK ] 85/86 - 25.95 MH/s, 408ms
20191007 03:00:48 [ OK ] 86/87 - 24.82 MH/s, 388ms
20191007 03:00:58 [ OK ] 87/88 - 23.54 MH/s, 384ms
20191007 03:02:37 [ OK ] 88/89 - 24.57 MH/s, 408ms
20191007 03:02:50 [ OK ] 89/90 - 24.55 MH/s, 420ms
20191007 03:02:50 GPU # 0: Zotac GTX 1070 - 1999.21 kH/s
20191007 03:02:50 GPU # 1: Zotac GTX 1070 - 1988.70 kH/s
20191007 03:02:50 GPU # 2: Zotac GTX 1070 - 2026.95 kH/s
20191007 03:02:50 GPU # 3: Zotac GTX 1070 - 1964.51 kH/s
20191007 03:02:50 GPU # 4: Zotac GTX 1070 - 1949.70 kH/s
20191007 03:02:50 GPU # 5: Zotac GTX 1070 - 1942.56 kH/s
20191007 03:02:50 GPU # 6: Zotac GTX 1070 - 2003.88 kH/s
20191007 03:02:50 GPU # 7: Zotac GTX 1070 - 1960.53 kH/s
20191007 03:02:50 GPU # 8: Zotac GTX 1070 - 1980.65 kH/s
20191007 03:02:50 GPU # 9: Zotac GTX 1070 - 2049.86 kH/s
20191007 03:02:50 GPU #10: Zotac GTX 1070 - 2047.69 kH/s
20191007 03:02:50 GPU #11: Zotac GTX 1070 - 2013.97 kH/s
20191007 03:02:50 GPU #12: Zotac GTX 1070 - 616.95 kH/s
20191007 03:02:50 Shares/min: 2.238 (Avr. 2.807)
20191007 03:02:50 Uptime: 31 mins 42 secs | Algo: mtp | T-Rex v0.14.4
20191007 03:02:58 mtp block 203886, diff 7713.171
20191007 03:58:37 GPU # 0: Zotac GTX 1070 - 1998.96 kH/s
20191007 03:58:37 GPU # 1: Zotac GTX 1070 - 1989.48 kH/s
20191007 03:58:37 GPU # 2: Zotac GTX 1070 - 2025.73 kH/s
20191007 03:58:37 GPU # 3: Zotac GTX 1070 - 1953.06 kH/s
20191007 03:58:37 GPU # 4: Zotac GTX 1070 - 1933.27 kH/s
20191007 03:58:37 GPU # 5: Zotac GTX 1070 - 1930.60 kH/s
20191007 03:58:37 GPU # 6: Zotac GTX 1070 - 2002.62 kH/s
20191007 03:58:37 GPU # 7: Zotac GTX 1070 - 1933.50 kH/s
20191007 03:58:37 GPU # 8: Zotac GTX 1070 - 1968.77 kH/s
20191007 03:58:37 GPU # 9: Zotac GTX 1070 - 2049.38 kH/s
20191007 03:58:37 GPU #10: Zotac GTX 1070 - 2047.80 kH/s
20191007 03:58:37 GPU #11: Zotac GTX 1070 - 2010.47 kH/s
20191007 03:58:37 GPU #12: Zotac GTX 1070 - 617.10 kH/s
20191007 03:58:37 Shares/min: 2.311 (Avr. 2.618)
20191007 03:58:37 Uptime: 1 hour 27 mins 29 secs | Algo: mtp | T-Rex v0.14.4
20191007 03:59:03 [ OK ] 230/231 - 24.48 MH/s, 400ms
20191007 03:59:26 [ OK ] 231/232 - 24.49 MH/s, 408ms
20191007 03:59:26 [ OK ] 232/233 - 24.49 MH/s, 228ms
20191007 03:59:28 [ OK ] 233/234 - 24.48 MH/s, 340ms
20191007 03:59:41 [ OK ] 234/235 - 23.57 MH/s, 384ms
20191007 03:59:46 [ OK ] 235/236 - 23.37 MH/s, 376ms
20191007 04:00:08 [ OK ] 236/237 - 22.53 MH/s, 400ms
20191007 04:00:25 [ OK ] 237/238 - 21.76 MH/s, 400ms
20191007 04:00:30 [ OK ] 238/239 - 21.84 MH/s, 416ms
20191007 04:00:31 [ OK ] 239/240 - 21.58 MH/s, 392ms
20191007 04:00:31 GPU # 0: Zotac GTX 1070 - 1331.81 kH/s
20191007 04:00:31 GPU # 1: Zotac GTX 1070 - 1903.67 kH/s
20191007 04:00:31 GPU # 2: Zotac GTX 1070 - 1914.89 kH/s
20191007 04:00:31 GPU # 3: Zotac GTX 1070 - 1891.04 kH/s
20191007 04:00:31 GPU # 4: Zotac GTX 1070 - 1891.09 kH/s
20191007 04:00:31 GPU # 5: Zotac GTX 1070 - 1810.03 kH/s
20191007 04:00:31 GPU # 6: Zotac GTX 1070 - 1906.10 kH/s
20191007 04:00:31 GPU # 7: Zotac GTX 1070 - 1880.92 kH/s
20191007 04:00:31 GPU # 8: Zotac GTX 1070 - 978.07 kH/s
20191007 04:00:31 GPU # 9: Zotac GTX 1070 - 1890.05 kH/s
20191007 04:00:31 GPU #10: Zotac GTX 1070 - 1821.98 kH/s
20191007 04:00:31 GPU #11: Zotac GTX 1070 - 1744.99 kH/s
20191007 04:00:31 GPU #12: Zotac GTX 1070 - 615.69 kH/s
20191007 09:22:04 GPU # 0: Zotac GTX 1070 - 1377.37 kH/s
20191007 09:22:04 GPU # 1: Zotac GTX 1070 - 2072.70 kH/s
20191007 09:22:04 GPU # 2: Zotac GTX 1070 - 2079.40 kH/s
20191007 09:22:04 GPU # 3: Zotac GTX 1070 - 2083.41 kH/s
20191007 09:22:04 GPU # 4: Zotac GTX 1070 - 1403.87 kH/s
20191007 09:22:04 GPU # 5: Zotac GTX 1070 - 1715.46 kH/s
20191007 09:22:04 GPU # 6: Zotac GTX 1070 - 2086.17 kH/s
20191007 09:22:04 GPU # 7: Zotac GTX 1070 - 1649.44 kH/s
20191007 09:22:04 GPU # 8: Zotac GTX 1070 - 620.76 kH/s
20191007 09:22:04 GPU # 9: Zotac GTX 1070 - 1281.27 kH/s
20191007 09:22:04 GPU #10: Zotac GTX 1070 - 2000.77 kH/s
20191007 09:22:04 GPU #11: Zotac GTX 1070 - 1652.71 kH/s
20191007 09:22:04 GPU #12: Zotac GTX 1070 - 609.56 kH/s
20191007 09:22:04 Shares/min: 2.278 (Avr. 2.477)
20191007 09:22:04 Uptime: 6 hours 50 mins 55 secs | Algo: mtp | T-Rex v0.14.4
20191007 09:22:04 [ OK ] 1019/1021 - 20.64 MH/s, 828ms
20191007 09:22:09 [ OK ] 1020/1022 - 20.80 MH/s, 500ms
20191007 09:22:20 [ OK ] 1021/1023 - 20.56 MH/s, 520ms
20191007 09:22:33 mtp block 203964, diff 7637.608
20191007 09:23:06 [ OK ] 1022/1024 - 18.67 MH/s, 516ms
20191007 09:24:45 mtp block 203965, diff 7637.608
20191007 09:25:41 [ OK ] 1023/1025 - 20.40 MH/s, 668ms
20191007 09:25:41 [ OK ] 1024/1026 - 20.39 MH/s, 552ms
20191007 09:25:43 [ OK ] 1025/1027 - 20.37 MH/s, 468ms
20191007 09:26:29 [ OK ] 1026/1028 - 19.18 MH/s, 448ms
20191007 09:26:47 [ OK ] 1027/1029 - 19.08 MH/s, 796ms
20191007 09:27:11 [ OK ] 1028/1030 - 19.14 MH/s, 696ms
20191007 09:27:11 GPU # 0: Zotac GTX 1070 - 1605.56 kH/s
20191007 09:27:11 GPU # 1: Zotac GTX 1070 - 2087.89 kH/s
20191007 09:27:11 GPU # 2: Zotac GTX 1070 - 1622.91 kH/s
20191007 09:27:11 GPU # 3: Zotac GTX 1070 - 695.92 kH/s
20191007 09:27:11 GPU # 4: Zotac GTX 1070 - 1470.74 kH/s
20191007 09:27:11 GPU # 5: Zotac GTX 1070 - 1718.56 kH/s
20191007 09:27:11 GPU # 6: Zotac GTX 1070 - 2088.02 kH/s
20191007 09:27:11 GPU # 7: Zotac GTX 1070 - 1296.54 kH/s
20191007 09:27:11 GPU # 8: Zotac GTX 1070 - 675.54 kH/s
20191007 09:27:11 GPU # 9: Zotac GTX 1070 - 2017.34 kH/s
20191007 09:27:11 GPU #10: Zotac GTX 1070 - 1681.75 kH/s
20191007 09:27:11 GPU #11: Zotac GTX 1070 - 1561.43 kH/s
20191007 09:27:11 GPU #12: Zotac GTX 1070 - 614.43 kH/s
#1. i have a GTX Titan 6GB, i want to test with x13bcd or argon2d-256...
#2. latest Nvidia driver that fully works for W8.1 or W7 is v388.71, all modern drivers have CUDA 64-Bit broken,
tested with CUDA-Z, GPU-Z, GPU-Capsviewer, etc...
"i dont have W10, i havent tested, but probably is the same."
#3. GTX Titan 6GB is a GTX 700 series, GK110 GPU has Compute Capability v3.5
https://en.wikipedia.org/wiki/CUDA
CUDA SDK 9.0 – 9.2 support for compute capability 3.0 – 7.2 (Kepler, Maxwell, Pascal, Volta)
CUDA SDK 10.0 – 10.2 support for compute capability 3.0 – 7.5 (Kepler, Maxwell, Pascal, Volta, Turing). Last version with support for compute capability 3.x (Kepler). 10.2 is the last official release for macOS, as support will not be available for macOS in newer releases.
#4. No GPU miner tested so far, None works, all say: Compute Capability Not Supported.
i know GTX1060 is the same and eats less power, but... still i want to test Nvidia drivers with & without Double Precision, just for curiosity.
Hi,
Using T-Rex with MTP, I found that I lose the connection to have the information about my GPU Stats.
I show some pictures… GPU 3 goes down in MSI Afterburner… but the Hash stills the same.
My command line is:
t-rex.exe --no-watchdog --no-nvml -b 127.0.0.1:4068 -a mtp --quiet -r 10 --cpu-priority 4 ….
The problema is that I made an autorestart if the GPU Temp goes down to 0... so it is autorestarting all the time. That problem I don't have it with other miners.
Many thanks
Please add support for client.reconnect. I can't get it connected to port 3333 on MiningRigRentals. I must use an individual port, that expires after 2 days.
/usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found.
You're using an obsolete version of OPENSSL_3. If your program is repaired with sudo apt-get install libcurl3 then it breaks BOINC 7.9.3. BOINC is more important so I'm done deploying your program to my fleet until it's updated. TIA
When will CUDA support for 10.1 be released for Linux? I have been unable to get anything working so far...
I were mining SUQA on x22i algo before the fork, transitioning to Sinovate on x25x. Miner dont work and error appears.
trex.log
请问0.92版本支持GTX2060、GTX2070 GTX2080 GTX2080TI 吗?
如果支持需要加什么参数?
如果不支持,请问能出个支持的版本吗?
So i tried benchmarking my GTX 1060 6gb with Kawpow for the upcoming Ravencoin fork, and im getting this error,
C:\Users\arkad>t-rex.exe` -a kawpow --benchmark
20200506 11:09:25 T-Rex NVIDIA GPU miner v0.15.4 - [CUDA v10.0]
20200506 11:09:25 r.d54ad77b45a7
20200506 11:09:25
20200506 11:09:25 NVIDIA Driver v442.59
20200506 11:09:25 CUDA devices available: 1
20200506 11:09:25
20200506 11:09:25 WARN: DevFee 1% (kawpow)
20200506 11:09:25
20200506 11:09:25 WARN: GPU #0: Gigabyte GeForce GTX 1060 6GB
20200506 11:09:25 ERROR: Can't find nonce with device [ID=0, GPU #0], kernel doesn't match progpow algo type
20200506 11:09:25 WARN: Messy shutdown...
20200506 11:09:25 Main loop finished
Won't seem to start up on an Ubuntu 16.04 system with P100, getting this error:
20190403 05:36:43 ERROR: Can't find share with device [ID=1, GPU #1], cuda exception in [skein_init, 448], invalid device symbol
20190403 05:36:43 ERROR: Can't find share with device [ID=0, GPU #0], cuda exception in [skein_init, 448], invalid device symbol
20190403 05:36:43 WARN: Messy shutdown...
Everything looks good otherwise AFAIK:
# nvidia-smi
Wed Apr 3 05:36:25 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.104 Driver Version: 410.104 CUDA Version: 10.0 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla P100-PCIE... Off | 00000000:00:07.0 Off | 0 |
| N/A 33C P0 29W / 250W | 0MiB / 16280MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 Tesla P100-PCIE... Off | 00000000:00:08.0 Off | 0 |
| N/A 35C P0 27W / 250W | 0MiB / 16280MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
Not sure what else I can provide to help debug this one.
Just started while miners were running on two different machines.
ERROR: Cuda error on device [ID=0, GPU #0], invalid configuration argument
from log
20191020 14:45:16 WARN: GPU #0: GeForce GTX 1060 6GB, intensity set to 50 20191020 14:45:16 Authorizing... 20191020 14:45:16 Authorized successfully. 20191020 14:45:17 WARN: New difficulty: 16 (0.06250) 20191020 14:45:17 x16r block 935049, diff 158051.152 20191020 14:45:17 Hash order 6174715F8AF7DBBD 20191020 14:45:37 x16r block 935050, diff 158357.917 20191020 14:45:37 ERROR: Cuda error on device [ID=0, GPU #0], invalid configuration argument
config file
`
// ""ravencoin.conf""
{
"pools": [
{
"user": "RWwppzjrLFCd6yTrDdBbBpHTS1Ffhrccat.worker", // CHANGETHIS to your username or wallet address, rename worker to this rig's name
"url": "stratum+tcp://us.rvn.minermore.com:4501", // <-- US
"pass": "x"
}
],
"api-bind-telnet": "0.0.0.0:4068", // Set to "0" to disable Telnet API
"api-bind-http": "0.0.0.0:4067", // Set to "0" to disable HTTP API
"json-response": false,
"retries": 3,
"retry-pause": 3,
"timeout": 120,
"algo": "x16r",
"intensity": 50,
"hashrate-avr": 30, // Set to 3600 to get average over an hour
"log-path": "t-rex.log",
"cpu-priority": 2,
"exit-on-connection-lost": false,
"reconnect-on-fail-shares": 10,
"protocol-dump": false, // Set to true to turn it on.
"gpu-report-interval": 5,
"no-color": false,
"quiet": false,
"time-limit": 0,
"temperature-limit": 0,
"temperature-start": 0,
"back-to-main-pool-sec": 600
`}``
I am requesting the server_name
extension be added to the T-Rex miner to be SNI compliant.
Using wire shark to determine the current TCP extensions, under SSL, the miner should have the server_name
extension added in order to properly determine the ownership service of a domain name under a single load balancer IP address.
Without the server_name
extension, it is impossible for the load balancer to know which service to direct the traffic.
As you can see above, wireshark only sees the following extensions: ec_points_formats, supported_groups, session-ticket, signature_algorithms, extended_master_secret.
The packets sniffed by wireshark above on the successful handshake with the loadbalancer presented with a default certificate as it didn't know which certificate to present to the miner without the server_name
extension.
Anyone else reading this can see the wiki page on SNI compliance https://en.wikipedia.org/wiki/Server_Name_Indication.
Keep getting this error on my card. what can I do to fix it? card is a little older (2012) but strong Quadro
my computer is gtx1050 win10,then run to a certain time to stop,can you help me?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.