PTRFRLL

Looks like the new T-Rex supports v520. I'll get an update pushed up here soon

That's odd the NVIDIA_VISIBLE_DEVICES variable isn't working. Can you post your Docker config (omit any sensitive info)?

I don't think you can mine ethash using a 750Ti, you need more memory

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

Ugh. Wonderful. Thanks for the heads up.

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

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

In theory, just adding the -mt to the config should do it. What did you set as the value?

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

My only guess would be something related to that latest driver (510.39.01). You might try downgrading that OR seeing if the new container build (3.8) helps at all

Try this link (substitute your IP and PORT): https://IP:PORT/endpoint/@scrypted/core/public/#/

I believe you add the -i flag to the command to specify the id or index of the GPU you want. Use nvidia-smi to print all cards and grab the GPU ID: nvidia-smi -i 0 -pl 125 #assuming card 0 is the one you want

I don't believe there is a way to sort at present. You could submit an issue on the project for consideration: https://github.com/LukeChannings/moviematch

I have not found a good way to include nvidia-settings and X11 into the container without requiring a specific version of nvidia drivers. I hesitate to do that as it would cause compatibility issues with many who use this container. I'm open to suggestions though.

Yes, anything in /etc/pulseway will not persist after a reboot, so you should always edit the one in /boot/pulseway. That said, if you just want to test that your config.xml changes work, you could edit the /etc/pulseway file so you don't have to reboot after ever change Correct, just place the new version in that directory and it will be installed on the next boot See #1 I've seen this warning as well but as you mentioned Pulseway is not available via NerdPack. I believe putting the package in /boot/extra is still the recommended way to install packages at boot, so you should be able to ignore this particular warning Hope that helps!

@repomanz I've got the container updated to use a new CUDA version. ptrfrll/nv-docker-trex:latest Also, as @Rhomax pointed out, make sure you don't have the 'disable NVML' option set in your config

Oops! I forgot to set the container as public. Give it a try now.

Can you try this tag and see if it works. I updated the base image and bumped the T-Rex version (note: I moved it to Githubs Container Registry, so you'll need to include the ghcr.io part): ghcr.io/ptrfrll/nv-docker-trex:test

Try using the ptrfrll/nv-docker-trex:latest tag (or if you want to keep a consistent version use: ptrfrll/nv-docker-trex:3.5.2). I tweaked the tags a bit with the newer version. its possible you're on the old version without the NVML package

What CUDA version are you using? This error came up with a newer version of T-Rex and I had to add a manual install NVML into the CUDA 11 container. The problem is, that package has not been back-ported to a version compatible with the CUDA 10 version

You can run nvidia-smi -pl 75 on Unraid itself (not within the container)

oh I see. Yes, all the variables (wallet, password, also, etc) overwrite the config file. I’ll update the image so that doesn’t happen.

I've updated some of the docker image tags. If you still use CUDA-10. Be sure to update your image tag, otherwise you won't get updates going forward: ptrfrll/nv-docker-trex:cuda10-latest

When you make a change in the WebUI, it should modify the config.json file so that it persists. If you make a change on the WebUI, do you see that change in the config.json file?

As far as I'm aware, setting autoupdate: false in the config file should do the trick. { ... "autoupdate": false }