sworcery Posted June 5, 2022 Share Posted June 5, 2022 I'm having an issue. I've defined the NVIDIA_VISIBLE_DEVICES variable and targeted only one of the 2 GPU I have in my system, a Quadro P2200 and an RTX 2080. I would like to only target the RTX 2080 for mining, however even after defining the GPU to target in the docker variables, both the P2200 and RTX 2080 show. When I try to disable the P2200 in Trex settings, I received an error message of: Edit config error (number of specified LHR tuning values in config doesn't match the number of GPUs) This error happens with or without the NVIDIA_VISIBLE_DEVICES defined in the docker settings. I've thought about manually pausing the P2200 but then I run the same error above when I try to limit power on the 2080. Quote Link to comment
PTRFRLL Posted June 5, 2022 Author Share Posted June 5, 2022 7 hours ago, sworcery said: I'm having an issue. I've defined the NVIDIA_VISIBLE_DEVICES variable and targeted only one of the 2 GPU I have in my system, a Quadro P2200 and an RTX 2080. I would like to only target the RTX 2080 for mining, however even after defining the GPU to target in the docker variables, both the P2200 and RTX 2080 show. When I try to disable the P2200 in Trex settings, I received an error message of: Edit config error (number of specified LHR tuning values in config doesn't match the number of GPUs) This error happens with or without the NVIDIA_VISIBLE_DEVICES defined in the docker settings. I've thought about manually pausing the P2200 but then I run the same error above when I try to limit power on the 2080. That's odd the NVIDIA_VISIBLE_DEVICES variable isn't working. Can you post your Docker config (omit any sensitive info)? Quote Link to comment
sworcery Posted June 5, 2022 Share Posted June 5, 2022 (edited) 1 hour ago, PTRFRLL said: That's odd the NVIDIA_VISIBLE_DEVICES variable isn't working. Can you post your Docker config (omit any sensitive info)? I've also tried wiping on the config file that gets created, and both with or without the NVIDIA_VISIBLE_DEVICES variable defined, I end up with the same issues. Edited June 5, 2022 by sworcery Quote Link to comment
sworcery Posted June 7, 2022 Share Posted June 7, 2022 (edited) Could it be that having my P2200 in a higher PCI-e slot that it is overriding the GPU variable? I have the RTX 2080 on my bottom slot because otherwise I would blocking a needed PCI-e slot. I could get a riser cable and try placing the 2080 in a higher slot. The GPU variable was working before until a recent update however. The most recent one I have a record of was on May 15 and the GPU variable was working before a reboot about 5 days ago and updates are done nightly. Edited June 7, 2022 by sworcery Quote Link to comment
ksnell Posted June 14, 2022 Share Posted June 14, 2022 (edited) On 2/15/2022 at 2:18 AM, BigHairyWookie said: Thanks, 3.8 seems to have fixed the issue, must've been a driver thing like you say. Can you tell me how you fixed this? I am running into the same issue currently and on drivers v510.73.05 and CUDA 11.6. I'm decently familiar with building new imagine and have used the Dockerfile to build with `nvidia/cuda:11.6.2-base-ubuntu20.04` but still no success. Of note: `sudo docker run --rm --gpus all nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi` does return the output of `nvidia-smi` so the gpu can be passed to the container. EDIT: Ok new information. Tag 3.8 from Docker Hub works with my drivers stated above but 4.2 and beyond do not. [ptrfrll/nv-docker-trex Tags | Docker Hub](https://registry.hub.docker.com/r/ptrfrll/nv-docker-trex/tags) Apologies, the number 3.8 threw me off before as it is the same version my compose files are on! Edited June 14, 2022 by ksnell Update Quote Link to comment
eagle470 Posted August 2, 2022 Share Posted August 2, 2022 My Trex miner keeps stopping immediately after starting it. Looking at the t-rex fold under appdata, there is nothing there but the json file. I'm not getting any logs. Any ideas what the issue might be? Quote Link to comment
eagle470 Posted August 2, 2022 Share Posted August 2, 2022 1 hour ago, eagle470 said: My Trex miner keeps stopping immediately after starting it. Looking at the t-rex fold under appdata, there is nothing there but the json file. I'm not getting any logs. Any ideas what the issue might be? Looks like version 3.8 works fine, but nothing else will crunch or start. I'll just stay on that I guess. Quote Link to comment
ziggie216 Posted August 28, 2022 Share Posted August 28, 2022 I'm trying to add a port for Scrypted and for some reason, the container port field is missing. https://imgur.com/FXNT4cs Any idea why? Quote Link to comment
shdwstrk Posted October 13, 2022 Share Posted October 13, 2022 Trex Miner: Currently the NVIDIA plugin for UNRAID only has v520.xx and 515.xx (or 470.xx) and not 510.xx. Whenever I try to use either one TREX complains about being unable to unlock the GPU and just tells me to install 510.xx before killing itself. I'm using the latest version of ptrfrll/nv-docker-trex, which is 4.3 according to dockerhub. Here is what the log looks like (515.xx is exactly the same except the 20 is a 15): 20221013 01:08:41 T-Rex NVIDIA GPU miner v0.26.4 - [Linux] 20221013 01:08:41 r.ff9b0053718b 20221013 01:08:41 20221013 01:08:41 20221013 01:08:41 NVIDIA Driver v520.56.06 20221013 01:08:41 20221013 01:08:41 + GPU #0: [00:01.0|2208] GeForce RTX 3080 Ti, 12042 MB 20221013 01:08:41 20221013 01:08:41 WARN: DevFee 1% (etchash) 20221013 01:08:41 20221013 01:08:41 URL : xxxxxxxx 20221013 01:08:41 USER: xxxxxxxx 20221013 01:08:41 PASS: x 20221013 01:08:41 WRK : ur1 20221013 01:08:41 20221013 01:08:41 Starting on: xxxxxx 20221013 01:08:41 ApiServer: HTTP server started on 0.0.0.0:4067 20221013 01:08:41 ---------------------------------------------------- 20221013 01:08:41 For control navigate to: http://172.17.0.3:4067/trex 20221013 01:08:41 ---------------------------------------------------- 20221013 01:08:41 Using protocol: stratum1. 20221013 01:08:41 Authorizing... 20221013 01:08:41 Authorized successfully. 20221013 01:08:41 etchash epoch: 268, block: 16128169, diff: 4.00 G 20221013 01:08:41 GPU #0: intensity 22 20221013 01:08:43 etchash epoch: 268, block: 16128170, diff: 4.00 G 20221013 01:08:43 GPU #0: generating DAG 3.09 GB for epoch 268(536) ... 20221013 01:08:46 GPU #0: DAG generated [crc: 07441b28, time: 3070 ms], memory left: 8.42 GB 20221013 01:08:47 TREX: Can't unlock GPU [ID=0, GPU #0], install 510.xx version of the video driver 20221013 01:08:47 WARN: Miner is going to shutdown... 20221013 01:08:47 Main loop finished. Cleaning up resources... 20221013 01:08:47 ApiServer: stopped listening on 0.0.0.0:4067 20221013 01:08:50 T-Rex finished. Any suggestions on getting it working, since I can't get 510.xx? Quote Link to comment
PTRFRLL Posted October 14, 2022 Author Share Posted October 14, 2022 (edited) On 10/13/2022 at 1:31 AM, shdwstrk said: Trex Miner: Currently the NVIDIA plugin for UNRAID only has v520.xx and 515.xx (or 470.xx) and not 510.xx. Whenever I try to use either one TREX complains about being unable to unlock the GPU and just tells me to install 510.xx before killing itself. I'm using the latest version of ptrfrll/nv-docker-trex, which is 4.3 according to dockerhub. Here is what the log looks like (515.xx is exactly the same except the 20 is a 15): 20221013 01:08:41 T-Rex NVIDIA GPU miner v0.26.4 - [Linux] 20221013 01:08:41 r.ff9b0053718b 20221013 01:08:41 20221013 01:08:41 20221013 01:08:41 NVIDIA Driver v520.56.06 20221013 01:08:41 20221013 01:08:41 + GPU #0: [00:01.0|2208] GeForce RTX 3080 Ti, 12042 MB 20221013 01:08:41 20221013 01:08:41 WARN: DevFee 1% (etchash) 20221013 01:08:41 20221013 01:08:41 URL : xxxxxxxx 20221013 01:08:41 USER: xxxxxxxx 20221013 01:08:41 PASS: x 20221013 01:08:41 WRK : ur1 20221013 01:08:41 20221013 01:08:41 Starting on: xxxxxx 20221013 01:08:41 ApiServer: HTTP server started on 0.0.0.0:4067 20221013 01:08:41 ---------------------------------------------------- 20221013 01:08:41 For control navigate to: http://172.17.0.3:4067/trex 20221013 01:08:41 ---------------------------------------------------- 20221013 01:08:41 Using protocol: stratum1. 20221013 01:08:41 Authorizing... 20221013 01:08:41 Authorized successfully. 20221013 01:08:41 etchash epoch: 268, block: 16128169, diff: 4.00 G 20221013 01:08:41 GPU #0: intensity 22 20221013 01:08:43 etchash epoch: 268, block: 16128170, diff: 4.00 G 20221013 01:08:43 GPU #0: generating DAG 3.09 GB for epoch 268(536) ... 20221013 01:08:46 GPU #0: DAG generated [crc: 07441b28, time: 3070 ms], memory left: 8.42 GB 20221013 01:08:47 TREX: Can't unlock GPU [ID=0, GPU #0], install 510.xx version of the video driver 20221013 01:08:47 WARN: Miner is going to shutdown... 20221013 01:08:47 Main loop finished. Cleaning up resources... 20221013 01:08:47 ApiServer: stopped listening on 0.0.0.0:4067 20221013 01:08:50 T-Rex finished. Any suggestions on getting it working, since I can't get 510.xx? Looks like the new T-Rex supports v520. I'll get an update pushed up here soon Edited October 14, 2022 by PTRFRLL 1 Quote Link to comment
mr2web Posted October 28, 2022 Share Posted October 28, 2022 (edited) Hi, I just updatet to the latest t-rex image, 4.4, and t-rex no longer recognised the nvidia driver, NVIDIA Driver v515.76 running on Unraid Version 6.11.1 2022-10-06. Rebooting the system did not make any difference at all. After rolling back to t-rex image 4.3 all is back up and running... Just thought I let u all know. Edited October 28, 2022 by mr2web Quote Link to comment
RichardU Posted November 11, 2022 Share Posted November 11, 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. Worked for me too. Thanks. 1 Quote Link to comment
XenoUniv3rse Posted September 22, 2023 Share Posted September 22, 2023 Hey, where can I find the Mining URL? 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.