FlamongOle

You should mainly not get incorrect at all. I think expected hashrates for 3060Ti is the same as 3070, so ~60-61. You rather have a bit lower hashrates and power consumption than incorrect results. Fa controllers might vary, often 3 fan cards still uses only 2 controllers. There's commands to figure out that, but you might write them under "Console" in the docker container. nvidia-settings -q fans

Hard to say, I think I am running HW transcoding with my P2000 5GB MEM in Emby. So maybe memory just have to be just enough above the DAG size and transcoding requirements (which might vary from file to file). Mining is a heavy workload, so it won't surprise me that transcoding might not work properly or at all. But at least you can turn off one single docker/mining when not transcoding, instead of all of them

You install the container multiple times (one per card), and keep them card specific. After first install, you can click "Add container", then select the "NsfminerOC" template and adjust values accordingly. "nvidia-smi" in terminal will show you the GPU ID for the specific card.

The docker just runs nsfminer and sets up the overclocking etc. No other ways it is controlled. Source code is out there.

No relevant questions for this docker container, all infomation about mining and wallets you will find at ethermine.org or other mining sites. Google is your friend here. This is more than I am willing to support.

1) yes 2) any name (it appears as a name for the worker, so you can separate multiple GPUs) 3) Probably, google it 4) Perfectly normal for Quadro cards as they can't be overclocked/they are locked.

Google it, and you will find the answer. Everybody has asked that before, so do some effort yourself, thanks

This is beyond of what I am going to support here, it's strictly the docker container. However, for others and your reference, enter your address at https://ethermine.org/ to check your current hashrate etc. The website has a lot of information about payouts and you can google different ethereum mining calculators out there for expected income. You will find all your information there, and it's more accurate than the info I can give you. Happy mining

Yes

Then you have too less GPU memory, as you see, it requires minimum 4.23 GB and your GPU has 2 GB (1.95 GB) total.

Not sure what you mean about the app? It shouldn't take too long before you get DAG and hashrates available.. 5 minutes tops I expect. Also check that it did detect CUDA at the start of the worker process, without it, it will always generate 0. Some older cards might not be supported by newer CUDA versions, I have no overview of this.

Yes it works container and application wise. Now you should detect hashrates like the ones in green after the DAG file has been created, it might take some time depending on your GPU:

Sadly yes, the memory requirements has surpassed 4GB memory. I will add that as a note at frontpage

@RazorX @Natebur Check for docker updates and install the new ones. Please report back if success or not, and which driver you are using. It is supposed to accept whatever driver you choose. I currently made it running again with 460.67 with GTX 1070 + P2000.

There's no need to do anything just yet, lots of BS going on in the docker now for troubleshooting

currently working on it with a glass of rum&coke

It's a fault happening currently, I am not sure what it is as I have rolled back the docker version I had before I made some changes. It happened to me after a reboot.. not sure if something underlying happened with the nvidia drivers, or if it's something else.

Plugin updates, then refresh the nvidia plugin page?

Should be 460.67 or else it won't work at all. Make sure you have the latest nvidia package, and maybe it require Unraid 6.9.1.

It means I have currently messed it up. Hopefully should be working soon again, and make sure the Nvidia versions matches as stated on the front page.

I give up for now, the driver installs and detect versions etc. But nvidia-settings and nvidia-xconfig seems be be separated from the package, and I'm not into compiling these trough docker right now. So I just reverted it to default behavior, so drivers still have to match (at least slightly)

It will be executed more or less as you have it (script file), dockerhub is creating a build now, see if that works through.

I have everything squeezed inside the Dockerfile, but I think I'll manage to shrink and add this in as well

If you have the code for copy&paste I'll do it 😛 I'm lazy

0