PTRFRLL

You need to exclude the 660. There's two ways to accomplish that. 1. In the Trex config.json, there's a devices property that you can use to specify which devices to use: { ... "devices": "0,1", ... } You have two devices (0 and 1), the 660 is #1 so remove the 1 from the devices list: { ... "devices": "0", ... } OR 2. You can add the NVIDIA_VISIBLE_DEVICES variable on the docker and only enter the UUID of the 1650 you want to use

I believe you can view the min/max power limits of your card with the following command: nvidia-smi -q -d POWER Otherwise, you might play around with the memory tweak (--mt) setting for T-rex

I understand there will be a new docker with the ES/ML modules pre-configured but is there a way to get the now legacy docker working again? I receive the error "Cannot download the ES server bundle" on container startup. It was working great until recently.

Unfortunately, that's a limitation of how the Nvidia drivers are integrated in Unraid. Normally, you could use the nvidia-settings CLI but that errors out as Unraid runs headless. You might try tweaking the memory-tweak flag for T-rex but I'm not sure how much that will help

I believe for Unmineable, your username needs to use this format: ASSET:Address.Worker, so using ADA as an example, you'd set your username to: ADA:D6vEw4k7FKmw99L82QgaG1nud9woBbDURw.BenStark

Updating is manual, so you'd need to snag a new version from Pulseway's site from time to time. That said, I'm in the "if it ain't broke, don't fix it" camp given the pace of Unraid OS updates

If you have not updated to Unraid 6.9.0 yet, the latest t-rex docker update will most likely not work for you. To fix, just add the cuda 10 docker tag detailed in the 1st post: ptrfrll/nv-docker-trex:cuda10

You can adjust the power limit using nvidia-smi. As for under/overclocking, the command line utility, nvidia-settings, throws an error when I try to run it, I believe its due to how Unraid runs headless. If you wanted to maximize your hash rate, it would be better to pass it through to a VM as you could overclock the memory. I have a 3070 on a different, non-Unraid machine getting 61 Mh/s. The main reason for this Docker was so that you could continue to use the GPU in dockers like Plex for transcoding but also use it to mine at the same time. If you're not utilizing the GPU in other Dockers, the VM route is the way to go.

Can you try updating the docker to pull the cuda11 tag like so: ptrfrll/nv-docker-trex:cuda11

Thanks for the explanation. I should probably update my drivers.... I wonder how I can best support both versions of CUDA with one t-rex docker...

I believe this is a current limitation due to the Nvidia driver version installed by Unraid (at least for Unraid 6.8.3). When I run nvidia-smi I show driver version 440.59 and CUDA version 10.2. There is a t-rex version built for CUDA 11.1 but I can't use it until the Unraid Nvidia driver is updated.

Restart the container and check your log. When the container starts, it shows the wallet address and URL of the pool you are connecting to, make sure those are correct.

I had the same issue, it's almost like the config file values are not being set. I would recommend making a backup of your config.json file and then trying a new config.json file with these values (replacing any pool values with your current ones): { "pools" : [ { "pass" : "x", "url" : "REPLACE_WITH_POOL_URL", "user" : "REPLACE_WITH_WALLET_ADDRESS", "worker" : "REPLACE_WITH_WORKER_NAME" } ], "api-bind-http" : "0.0.0.0:4067" } Until the logs show: ApiServer: HTTP server started on 0.0.0.0:4067, the WebUI won't be accessible

This is correct from my understanding, the 1050Ti doesn't have enough memory to mine ethash.

Did you set the algorithm variable to kawpow?

You might try the GPU Statistics plugin but I'm pretty sure that just uses nvidia-smi

I haven't needed to do anything special with my 1660Ti, t-rex doesn't seem to utilize all the memory. Otherwise, if that's not the case for you, I'm not sure the best way to limit it. Perhaps you setup a User Script to only run it at night?

Hopefully you got is figured out by now but I just ran through the same tutorial. Rufus did not add any of those files (autoexec.bat, etc) and it worked just fine. Here's how my flash drive looked:

At present, it's not supported but I'll update the docker so it can be set

Available Applications trex-miner Container with Nvidia Driver which allows for GPU crypto mining (ETH, ETC, Zcash, etc) Use the nvidia-driver plugin to get nvidia drivers installed on your Unraid host I would recommend setting a power limit on your GPU. From the Unraid command line (not within the docker) nvidia-smi -pl 75 Here I'm setting a power limit of 75 watts IMPORTANT: You must select the proper CUDA version when installing: With stable release of Unraid 6.9.0, the latest tag now points to cuda 11 build If you need the cuda 10 build, update the docker tag to cuda10-latest ghcr.io/ptrfrll/nv-docker-trex:cuda10-latest Checking CUDA Version Run nvidia-smi on Unraid console to determine CUDA version (either CUDA 10.2 or 11+) Specify GPU If you have multiple GPUs and only want to mine with specific ones, add the NVIDIA_VISIBLE_DEVICES variable to the container with the GPU UUID that you want to use (comma separated for more than one): WebUI Password Default password for the WebUI is Password1 (you should change this via the API_PASSWORD env variable on the container) MovieMatch Webapp to help you decide what movie to watch on Plex See project docs: https://github.com/LukeChannings/moviematch Scrypted Scrypted home automation See project docs: https://github.com/koush/scrypted Add Homekit Secure Video support to unsupported cameras (Unifi, Amcrest, etc) CHANGE LOG: 3/1/2021 - Update t-rex docs, latest tag is now cuda 11 build 9/22/2021 - Add scrypted 11/6/2021 - Add API_PASSWORD to T-Rex 12/1/2021 - Add note about migration to GHCR

Summary: Support thread for all PTRFRLL's Dockers DockerHub: https://hub.docker.com/u/ptrfrll/

You just need to rename that file to simply config.xml: mv /etc/pulseway/config.xml.sample /etc/pulseway/config.xml

Looks like your config file isn't in the correct place. What's the output of: ls /etc/pulseway/

I think this is an issue with Pulseway as I've noticed it on mine as well. I think Pulseway periodically checks if the server is responding and if not, it will generate a offline notification but that check isn't always completed successfully.

Now that the docker installs versions of Yolo, can I safely remove the INSTALL_YOLO docker variables? Had to re-install the docker for other reasons and those variables are gone.