PTRFRLL Posted February 18, 2022 Author Share Posted February 18, 2022 8 minutes ago, Ystebad said: Need help with Trex docker. I have to manually enter my pool information each time it starts or it won't connect/mine. In the unraid docker edit there is only one field named "server" and here I have entered eth-us-east.flexpool.io However it won't connect unless I go into the actual GUI after it's started and select SSL then enter the pool above and enter the port 5555. Then it works fine, until the docker is restarted at which time it won't connect again. I tried editing the config.json under the tree-miner folder of appdata with the following: "pools" : [ { "pass" : "x", "url" : "stratum+ssl://eth-us-east.flexpool.io:5555", However this doesn't seem to work. What am I missing/doing wrong? advTHANKSance! You should be able to pass that entire URL, port included, via the "server" variable. This is what my "server" var looks like: stratum+ssl://us2.ethermine.org:5555 1 Quote Link to comment
mtgeekman Posted March 1, 2022 Share Posted March 1, 2022 What needs to be done to be able to use the -mt config option in this container? I am running with a privileged container. 20220301 14:59:22 20220301 14:59:22 + GPU #0: [00:03.0|1b80] GeForce GTX 1080, 8119 MB 20220301 14:59:22 20220301 14:59:22 WARN: DevFee 1% (ethash) 20220301 14:59:22 20220301 14:59:22 URL : XXXXXXXXXXXXXXXXXXXXXXXX 20220301 14:59:22 USER: XXXXXXXXXX 20220301 14:59:22 PASS: x 20220301 14:59:22 WRK : XXXXXXXXXXXXXXXXXXXXXXXX 20220301 14:59:22 20220301 14:59:22 Starting on: ethash.na.mine.zergpool.com:9999 20220301 14:59:22 ApiServer: HTTP server started on 0.0.0.0:4067 20220301 14:59:22 ---------------------------------------------------- 20220301 14:59:22 For control navigate to: http://172.17.0.4:4067/trex 20220301 14:59:22 ---------------------------------------------------- 20220301 14:59:22 GPU #0: intensity 22, mtweak 1 20220301 14:59:24 Using protocol: stratum1. 20220301 14:59:24 Authorizing... 20220301 14:59:24 Authorized successfully. 20220301 14:59:24 ethash epoch: 331, block: 9933729, diff: 999.98 M 20220301 14:59:26 GPU #0: generating DAG 3.59 GB for epoch 331 ... 20220301 14:59:26 GPU #0: generating DAG 3.59 GB for epoch 331 ... 20220301 14:59:37 �[0;36mGPU #0: DAG generated [crc: da3cf25b�[0m�[0;36m, time: 11097 ms], memory left: 4.24 GB �[0m20220301 14:59:37 TREX: Can't find nonce with device [ID=0, GPU #0], cuda exception: CUDA_ERROR_ILLEGAL_INSTRUCTION, try to reduce overclock to stabilize GPU state 20220301 14:59:37 WARN: Miner is going to shutdown... 20220301 14:59:37 Main loop finished. Cleaning up resources... 20220301 14:59:37 ApiServer: stopped listening on 0.0.0.0:4067 20220301 14:59:39 T-Rex finished. 20220301 14:59:41 WARN: WATCHDOG: T-Rex does not exist anymore, restarting... 20220301 14:59:41 T-Rex NVIDIA GPU miner v0.25.6 - [Linux] 20220301 14:59:41 r.e2b4b01ffa83 20220301 14:59:41 20220301 14:59:42 20220301 14:59:42 NVIDIA Driver v510.54 Quote Link to comment
PTRFRLL Posted March 1, 2022 Author Share Posted March 1, 2022 3 hours ago, mtgeekman said: What needs to be done to be able to use the -mt config option in this container? I am running with a privileged container. 20220301 14:59:22 20220301 14:59:22 + GPU #0: [00:03.0|1b80] GeForce GTX 1080, 8119 MB 20220301 14:59:22 20220301 14:59:22 WARN: DevFee 1% (ethash) 20220301 14:59:22 20220301 14:59:22 URL : XXXXXXXXXXXXXXXXXXXXXXXX 20220301 14:59:22 USER: XXXXXXXXXX 20220301 14:59:22 PASS: x 20220301 14:59:22 WRK : XXXXXXXXXXXXXXXXXXXXXXXX 20220301 14:59:22 20220301 14:59:22 Starting on: ethash.na.mine.zergpool.com:9999 20220301 14:59:22 ApiServer: HTTP server started on 0.0.0.0:4067 20220301 14:59:22 ---------------------------------------------------- 20220301 14:59:22 For control navigate to: http://172.17.0.4:4067/trex 20220301 14:59:22 ---------------------------------------------------- 20220301 14:59:22 GPU #0: intensity 22, mtweak 1 20220301 14:59:24 Using protocol: stratum1. 20220301 14:59:24 Authorizing... 20220301 14:59:24 Authorized successfully. 20220301 14:59:24 ethash epoch: 331, block: 9933729, diff: 999.98 M 20220301 14:59:26 GPU #0: generating DAG 3.59 GB for epoch 331 ... 20220301 14:59:26 GPU #0: generating DAG 3.59 GB for epoch 331 ... 20220301 14:59:37 �[0;36mGPU #0: DAG generated [crc: da3cf25b�[0m�[0;36m, time: 11097 ms], memory left: 4.24 GB �[0m20220301 14:59:37 TREX: Can't find nonce with device [ID=0, GPU #0], cuda exception: CUDA_ERROR_ILLEGAL_INSTRUCTION, try to reduce overclock to stabilize GPU state 20220301 14:59:37 WARN: Miner is going to shutdown... 20220301 14:59:37 Main loop finished. Cleaning up resources... 20220301 14:59:37 ApiServer: stopped listening on 0.0.0.0:4067 20220301 14:59:39 T-Rex finished. 20220301 14:59:41 WARN: WATCHDOG: T-Rex does not exist anymore, restarting... 20220301 14:59:41 T-Rex NVIDIA GPU miner v0.25.6 - [Linux] 20220301 14:59:41 r.e2b4b01ffa83 20220301 14:59:41 20220301 14:59:42 20220301 14:59:42 NVIDIA Driver v510.54 In theory, just adding the -mt to the config should do it. What did you set as the value? Quote Link to comment
mtgeekman Posted March 1, 2022 Share Posted March 1, 2022 I have tried 1 and 2 for values in there. every attempt has resulted in the error in my last post. Quote Link to comment
mtgeekman Posted March 3, 2022 Share Posted March 3, 2022 is there any thing special I would need to do with my docker configuration to get this to work? losing out on ~10mh/s is a bit painful for efficiency. Quote Link to comment
PTRFRLL Posted March 8, 2022 Author Share Posted March 8, 2022 (edited) On 3/3/2022 at 4:01 PM, mtgeekman said: is there any thing special I would need to do with my docker configuration to get this to work? losing out on ~10mh/s is a bit painful for efficiency. I don't personally use the mt option so I can't really speak to getting it working. I thought someone else in this thread was able to get it working but after skimming back through, I can't find a definitive answer. Perhaps someone else can chime in to help. Otherwise, you could look at using this container (or copying/modifying it to add overclocking abilities to T-rex): https://github.com/olehj/docker-nsfminerOC Edited March 8, 2022 by PTRFRLL Quote Link to comment
volcs0 Posted March 26, 2022 Share Posted March 26, 2022 For TubeSync, I'm getting this error repeatedly: Invalid HTTP_HOST header: '127.0.0.1:8080'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. Bad Request: /healthcheck I added 127.0.0.1 to ALLOWED_HOSTS, along with localhost and the IP for my unRAID. Any other fixes? Does this error matter? Thanks. Quote Link to comment
Twinkie0101 Posted March 28, 2022 Share Posted March 28, 2022 On 3/26/2022 at 7:02 PM, volcs0 said: For TubeSync, I'm getting this error repeatedly: Invalid HTTP_HOST header: '127.0.0.1:8080'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. Bad Request: /healthcheck I added 127.0.0.1 to ALLOWED_HOSTS, along with localhost and the IP for my unRAID. Any other fixes? Does this error matter? Thanks. I had the same issue. I removed the external database and django variables as I didin't plan to use them and was able to get to the GUI. 1 Quote Link to comment
doxdump Posted April 5, 2022 Share Posted April 5, 2022 On 3/27/2022 at 10:56 PM, Twinkie0101 said: I had the same issue. I removed the external database and django variables as I didin't plan to use them and was able to get to the GUI. thanks for this! Quote Link to comment
karldonteljames Posted April 7, 2022 Share Posted April 7, 2022 (edited) Are there any plans for TubeSync to support emby as a notification source? I also wondered if it is possible to use a subfolder under the channel with the year (basically so it can be seen as a season in emby)? I tried the following, but even I create the folder, (2022 in this case) tube sync throws an error saying the out file doesn't exist. /{yyyy}/{yyyy_mm_dd} - {title_full}.{ext} edit: Removing the proceeding '/' allows the video to go into the correct folder, however the supporting metadata (thumbnail and nfo) is stored in the folder above. I've tried adding the variable to the directory, but that just creates a new folder called {yyyy} so I assume that isn't parsed into the location. is there a way round this at all? Also, is it possible to run a scheduled task manually? Edited April 7, 2022 by karldonteljames Quote Link to comment
Ashepp Posted April 20, 2022 Share Posted April 20, 2022 Hi Folks, I don't seem to be able to get my trex-miner docker running on Unraid since I recently had a graphics card die on me. The error is : ERROR: Can't start T-Rex, number of specified <arg> doesn't match the number of GPUs I tried to adjust the devices field from "devices" : "0,0", to "devices" : "0", but no dice. I'm including my config.json below with obfuscated details. Appreciate any help. Quote { "ab-indexing" : false, "algo" : "ethash", "api-bind-http" : "***OBFUSCATED***", "api-bind-telnet" : "***OBFUSCATED***", "api-key" : "***OBFUSCATED***", "api-read-only" : false, "autoupdate" : false, "back-to-main-pool-sec" : 600, "coin" : "", "cpu-priority" : 2, "dag-build-mode" : "0,0", "devices" : "0", "exit-on-connection-lost" : false, "exit-on-cuda-error" : true, "exit-on-high-power" : 0, "extra-dag-epoch" : "-1,-1", "gpu-init-mode" : 0, "gpu-report-interval" : 30, "gpu-report-interval-s" : 0, "hashrate-avr" : 60, "hide-date" : false, "intensity" : "0,0", "keep-gpu-busy" : false, "kernel" : "0,0", "lock-cclock" : "0,0", "log-path" : "", "low-load" : "0,0", "monitoring-page" : { "graph_interval_sec" : 3600, "update_timeout_sec" : 10 }, "mt" : "0,0", "no-color" : false, "no-hashrate-report" : false, "no-nvml" : false, "no-strict-ssl" : false, "no-watchdog" : false, "pci-indexing" : false, "pl" : "130,0", "pools" : [ { "pass" : "***OBFUSCATED***", "url" : "***OBFUSCATED***", "user" : "***OBFUSCATED***", "worker" : "***OBFUSCATED***" } ], "protocol-dump" : false, "reconnect-on-fail-shares" : 10, "retries" : 3, "retry-pause" : 10, "script-crash" : "", "script-epoch-change" : "", "script-exit" : "", "script-low-hash" : "", "script-start" : "", "send-stales" : false, "sharerate-avr" : 600, "temperature-color" : "67,77", "temperature-limit" : 0, "temperature-start" : 0, "time-limit" : 0, "timeout" : 300, "validate-shares" : false, "watchdog-exit-mode" : "", "worker" : "***OBFUSCATED***" } Quote Link to comment
PTRFRLL Posted April 21, 2022 Author Share Posted April 21, 2022 21 minutes ago, Ashepp said: Hi Folks, I don't seem to be able to get my trex-miner docker running on Unraid since I recently had a graphics card die on me. The error is : ERROR: Can't start T-Rex, number of specified <arg> doesn't match the number of GPUs I tried to adjust the devices field from "devices" : "0,0", to "devices" : "0", but no dice. I'm including my config.json below with obfuscated details. Appreciate any help. I believe you need to adjust all the parameters in the config file that reference the second GPU. Any that have a comma (dag-build-mode, mt, pl, etc), e.g. "0,0", should be changed to remove the second number Quote Link to comment
Ashepp Posted April 22, 2022 Share Posted April 22, 2022 That worked. Thank you! Quote Link to comment
letrain Posted May 1, 2022 Share Posted May 1, 2022 (edited) its been a while. I'm not back to wanting to mine in a nice t-rex docker with 1 gpu... only now i'm getting this error. 20220501 15:15:29 TREX: Can't find nonce with device [ID=0, GPU #0], cuda exception: CUDA_ERROR_OUT_OF_MEMORY its is a p2000. i mined just fine before, and have been happily mining with it in windows up until now. its worked fine for ETH mining. its right at the GB limit. i did have to run the special script in windows so its was "headless" and would be 100% free to mine. but i've never had this issue in t-rex and have no idea how to fix. EDIT: UnRaid Version: 6.10.0-rc5 so... went to "ptrfrll/nv-docker-trex:cuda10-latest" and it seems to be working. i was on "latest" because nvidia-smi = NVIDIA-SMI 495.46 Driver Version: 495.46 CUDA Version: 11.5 so i was using latest t-rex because cuda 11. is this going to be an issue going forward? Edited May 1, 2022 by letrain tried something Quote Link to comment
Pducharme Posted May 4, 2022 Share Posted May 4, 2022 @PTRFRLL Will you upgrade T-rex to Latest 0.25.15 ? You should add an Environment Variable that we could use to specify a version of T-REX, this way you won't have to update it as often Quote Link to comment
sreknob Posted May 6, 2022 Share Posted May 6, 2022 FYI, on latest tag just pushed, I'm now getting ERROR: Can't start T-Rex, LHR autotune increment interval must be positive Cheers! Quote Link to comment
PTRFRLL Posted May 6, 2022 Author Share Posted May 6, 2022 3 minutes ago, sreknob said: FYI, on latest tag just pushed, I'm now getting ERROR: Can't start T-Rex, LHR autotune increment interval must be positive Cheers! Ugh. Wonderful. Thanks for the heads up. Quote Link to comment
PTRFRLL Posted May 6, 2022 Author Share Posted May 6, 2022 5 minutes ago, sreknob said: FYI, on latest tag just pushed, I'm now getting ERROR: Can't start T-Rex, LHR autotune increment interval must be positive Cheers! Can you check your config.json and see what the value is set to? I don't use LHR and it seems to run just fine for me. I'm guessing the new lhr-autotune-interval param isn't set 1 Quote Link to comment
sreknob Posted May 6, 2022 Share Posted May 6, 2022 8 minutes ago, PTRFRLL said: Can you check your config.json and see what the value is set to? I don't use LHR and it seems to run just fine for me. I'm guessing the new lhr-autotune-interval param isn't set You are correct - I was having a look while you were as well. Tag cuda10-latest works fine but 4.2 and latest give the autotune error My config had both lhr-autotune-interval and lhr-autotune-step-size set to "0", which are both invalid. I also don't use autotune but it was set to auto "-1" from the default config that I used. I set the following in my config to resolve it "lhr-autotune-interval" : "5:120", "lhr-autotune-mode" : "off", "lhr-autotune-step-size" : "0.1", For those that do use autotune, you should leave "lhr-autotune-mode" at "-1" Thanks for the update and having a look. Perhaps this will also help someone else 🙂 2 1 Quote Link to comment
cypres0099 Posted May 11, 2022 Share Posted May 11, 2022 @PTRFRLL I'm having some trouble getting t-rux up and running on my unraid server. Not sure where I'm going wrong. Here's what I'm getting in the log 20220511 01:04:18 API CALL: change config /config/config.json: { "pools" : [ { "pass" : "x", "url" : "stratum+ssl://us2.ethermine.org:5555", "user" : "0x838E9a9E66E8b398C24dB41b597ecb9f515a0A19", "worker" : "cypres0099" } ] } 20220511 01:04:21 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:21 ERROR: No connection with us2.ethermine.org:5555, retry after 10 seconds ------------20220511 01:04:26 ------------- Mining at us1.ethermine.org [no connection] GPU #0: GTX 750 Ti - 0.00 H/s, [T:31C, P:0W, F:33%] Shares/min: 0 Uptime: 5 mins 35 secs | Algo: ethash | Driver: 510.68.02 | T-Rex 0.25.15 WD: 6 hours 55 mins 10 secs, shares: 0/0 , restarts 31 WD: ======== GPU CRASH LIST ======== WD: GPU#0: 21 WD: ======== GPU IDLE LIST ======== WD: GPU#0: 5 20220511 01:04:31 Using protocol: stratum1. 20220511 01:04:31 Authorizing... 20220511 01:04:31 Authorized successfully. 20220511 01:04:32 WARN: GPU #0: GeForce GTX 750 Ti is idle, last activity was 5 mins 41 secs ago 20220511 01:04:33 ethash epoch: 491, block: 14751851, diff: 4.29 G 20220511 01:04:35 TREX: Can't find nonce with device [ID=0, GPU #0], GPU #0: not enough free memory to mine ethash at epoch 491 20220511 01:04:35 WARN: Miner is going to shutdown... 20220511 01:04:35 Main loop finished. Cleaning up resources... 20220511 01:04:35 ApiServer: stopped listening on 0.0.0.0:4067 20220511 01:04:37 T-Rex finished. 20220511 01:04:38 WARN: WATCHDOG: T-Rex does not exist anymore, restarting... 20220511 01:04:38 T-Rex NVIDIA GPU miner v0.25.15 - [Linux] 20220511 01:04:38 r.ad2c22e1edee 20220511 01:04:38 20220511 01:04:38 20220511 01:04:38 NVIDIA Driver v510.68.02 20220511 01:04:38 20220511 01:04:38 + GPU #0: [00:0d.0|1380] GeForce GTX 750 Ti, 2001 MB 20220511 01:04:38 20220511 01:04:38 WARN: DevFee 1% (ethash) 20220511 01:04:38 20220511 01:04:38 URL : us1.ethermine.org 20220511 01:04:38 USER: 0x838E9a9E66E8b398C24dB41b597ecb9f515a0A19 20220511 01:04:38 PASS: x 20220511 01:04:38 WRK : cypres0099 20220511 01:04:38 20220511 01:04:38 Starting on: us1.ethermine.org 20220511 01:04:38 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:38 ERROR: No connection with us1.ethermine.org, retry after 10 seconds 20220511 01:04:38 ApiServer: HTTP server started on 0.0.0.0:4067 20220511 01:04:38 ---------------------------------------------------- 20220511 01:04:38 For control navigate to: http://172.17.0.6:4067/trex 20220511 01:04:38 ---------------------------------------------------- 20220511 01:04:38 GPU #0: intensity 22 20220511 01:04:48 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:48 ERROR: No connection with us1.ethermine.org, retry after 10 seconds 20220511 01:04:58 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:58 ERROR: No connection with us1.ethermine.org, retry after 10 seconds Quote Link to comment
PTRFRLL Posted May 11, 2022 Author Share Posted May 11, 2022 15 hours ago, cypres0099 said: @PTRFRLL I'm having some trouble getting t-rux up and running on my unraid server. Not sure where I'm going wrong. Here's what I'm getting in the log 20220511 01:04:18 API CALL: change config /config/config.json: { "pools" : [ { "pass" : "x", "url" : "stratum+ssl://us2.ethermine.org:5555", "user" : "0x838E9a9E66E8b398C24dB41b597ecb9f515a0A19", "worker" : "cypres0099" } ] } 20220511 01:04:21 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:21 ERROR: No connection with us2.ethermine.org:5555, retry after 10 seconds ------------20220511 01:04:26 ------------- Mining at us1.ethermine.org [no connection] GPU #0: GTX 750 Ti - 0.00 H/s, [T:31C, P:0W, F:33%] Shares/min: 0 Uptime: 5 mins 35 secs | Algo: ethash | Driver: 510.68.02 | T-Rex 0.25.15 WD: 6 hours 55 mins 10 secs, shares: 0/0 , restarts 31 WD: ======== GPU CRASH LIST ======== WD: GPU#0: 21 WD: ======== GPU IDLE LIST ======== WD: GPU#0: 5 20220511 01:04:31 Using protocol: stratum1. 20220511 01:04:31 Authorizing... 20220511 01:04:31 Authorized successfully. 20220511 01:04:32 WARN: GPU #0: GeForce GTX 750 Ti is idle, last activity was 5 mins 41 secs ago 20220511 01:04:33 ethash epoch: 491, block: 14751851, diff: 4.29 G 20220511 01:04:35 TREX: Can't find nonce with device [ID=0, GPU #0], GPU #0: not enough free memory to mine ethash at epoch 491 20220511 01:04:35 WARN: Miner is going to shutdown... 20220511 01:04:35 Main loop finished. Cleaning up resources... 20220511 01:04:35 ApiServer: stopped listening on 0.0.0.0:4067 20220511 01:04:37 T-Rex finished. 20220511 01:04:38 WARN: WATCHDOG: T-Rex does not exist anymore, restarting... 20220511 01:04:38 T-Rex NVIDIA GPU miner v0.25.15 - [Linux] 20220511 01:04:38 r.ad2c22e1edee 20220511 01:04:38 20220511 01:04:38 20220511 01:04:38 NVIDIA Driver v510.68.02 20220511 01:04:38 20220511 01:04:38 + GPU #0: [00:0d.0|1380] GeForce GTX 750 Ti, 2001 MB 20220511 01:04:38 20220511 01:04:38 WARN: DevFee 1% (ethash) 20220511 01:04:38 20220511 01:04:38 URL : us1.ethermine.org 20220511 01:04:38 USER: 0x838E9a9E66E8b398C24dB41b597ecb9f515a0A19 20220511 01:04:38 PASS: x 20220511 01:04:38 WRK : cypres0099 20220511 01:04:38 20220511 01:04:38 Starting on: us1.ethermine.org 20220511 01:04:38 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:38 ERROR: No connection with us1.ethermine.org, retry after 10 seconds 20220511 01:04:38 ApiServer: HTTP server started on 0.0.0.0:4067 20220511 01:04:38 ---------------------------------------------------- 20220511 01:04:38 For control navigate to: http://172.17.0.6:4067/trex 20220511 01:04:38 ---------------------------------------------------- 20220511 01:04:38 GPU #0: intensity 22 20220511 01:04:48 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:48 ERROR: No connection with us1.ethermine.org, retry after 10 seconds 20220511 01:04:58 WARN: Can't connect to the mining pool, wrong url format 20220511 01:04:58 ERROR: No connection with us1.ethermine.org, retry after 10 seconds I don't think you can mine ethash using a 750Ti, you need more memory Quote Link to comment
cypres0099 Posted May 11, 2022 Share Posted May 11, 2022 38 minutes ago, PTRFRLL said: I don't think you can mine ethash using a 750Ti, you need more memory hmmm ok, so do you think that's the problem I'm having or just a side note that maybe it's not worth trying to fix the issue because mining won't really work with my card? Quote Link to comment
sreknob Posted May 17, 2022 Share Posted May 17, 2022 On 5/11/2022 at 1:24 PM, cypres0099 said: hmmm ok, so do you think that's the problem I'm having or just a side note that maybe it's not worth trying to fix the issue because mining won't really work with my card? Hard to do much with a 750 with 2GB. Options are something with a small DAG file size (UBIQ) or a coin without a DAG file, like TON. T-rex doesn't support either of those options, however. Quote Link to comment
Elembemedia Posted May 19, 2022 Share Posted May 19, 2022 Hey all, I am having an issue with my Unraid install like mentioned up above. After a recent update the miner will no longer startup and I get the following error. 20220519 02:54:19 GPU #0: intensity 20 20220519 02:54:19 GPU #0: generating DAG 3.37 GB for epoch 304 ... 20220519 02:54:22 TREX: Can't unlock GPU [ID=0, GPU #0], thread terminated, error code 3 20220519 02:54:22 WARN: Miner is going to shutdown... I have tried rolling the nvidia driver back to 510 and also have pulled my lock clock and LHR settings from the config. This is all with a 3060. Any help would be awesome! Quote Link to comment
eagle470 Posted May 21, 2022 Share Posted May 21, 2022 On 5/18/2022 at 10:19 PM, Elembemedia said: Hey all, I am having an issue with my Unraid install like mentioned up above. After a recent update the miner will no longer startup and I get the following error. 20220519 02:54:19 GPU #0: intensity 20 20220519 02:54:19 GPU #0: generating DAG 3.37 GB for epoch 304 ... 20220519 02:54:22 TREX: Can't unlock GPU [ID=0, GPU #0], thread terminated, error code 3 20220519 02:54:22 WARN: Miner is going to shutdown... I have tried rolling the nvidia driver back to 510 and also have pulled my lock clock and LHR settings from the config. This is all with a 3060. Any help would be awesome! I'm having the same issue. externally, it looks like there is a process that has the GPU locked up. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.