Docker: nsfminerOC (unsupported)


113 posts in this topic Last Reply

Recommended Posts

On 5/3/2021 at 4:25 PM, Rolucious said:

I updated the driver in the nvidia pluging to 465.27, but that caused nvidia-smi to not properly report the GPU's for some reason, resulting that the cards weren't able to overclock.

In the end the only nvidia driver I found working was 460.73.

 

It's currently working correctly

 

Ye, had the same experience here. Not so much I can do about it. Maybe there's some conflict with the 465 drivers between docker and unraid even if it's built from the same source, or just a bug. Won't use time to investigate this as it's probably at the near end of the ethereum mining era. Stable 460 drivers work, so I'll write a note about it at the front page. Thanks for the info trhough.

Link to post
  • Replies 112
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This container will no longer be maintained or supported as of 23.07.2021. Fork it, modify it, do whatever with it if you need it.   Docker container for Ethereum mining with CUDA (nsfminer)

Thanks to @ich777 for the nvidia driver download script for complete driver version support.

currently working on it with a glass of rum&coke

Posted Images

12 hours ago, corgan said:

in the latest release v1.3.13 of nsf they added premetheus /metric support of the api. Is it possible to use this on this container?

If it requires additional start up flag, then probably not. If it just requires open ports/port mapping, you can set that up manually yourself in the template setup and check if you can connect to it. I won't be using more time with this docker container unless it stops working.

Link to post
23 hours ago, olehj said:

If it requires additional start up flag, then probably not. If it just requires open ports/port mapping, you can set that up manually yourself in the template setup and check if you can connect to it. I won't be using more time with this docker container unless it stops working.

 

in the docs of the original nsfminer i found this

 

Quote

Introduction

 

nsfminer implements an API (Application Programming Interface) interface which allows to monitor/control some of the run-time values endorsed by this miner. The API interface is available under the following circumstances:

If you're using a binary release downloaded from the releases section of this repository

If you build the application from source ensuring you add the compilation switch -D APICORE=ON

 

Activation and Security

Whenever the above depicted conditions are met you can take advantage of the API support by adding the --api-bind argument to the command line used to launch nsfminer. The format of this argument is --api-bind address:port where nnnn is any valid TCP port number (1-65535) and is required, and the address dictates what ip the api will listen on, and is optional, and defaults to "all ipv4 addresses". Examples:

./nsfminer [...] --api-bind 3333

 

so i think it must be started with --api-bind 3333

May this be possible with this container?

Link to post
  • 1 month later...

just installed.. every time the container starts it says driver mismatch and has to download drivers. i have the nvidia-plugin drivers installed that are listed in the op. the one in the docker is higher and says it has to download the lower version i have installed..

 

-Trying to get Nvidia driver version---
---Successfully got driver version: 460.84---
---Checking Xwrapper.config---
---Configuring Xwrapper.config---
---Driver version missmatch, currently installed: v465.19.01, driver on Host: v460.84---
---Downloading and installing Nvidia Driver v460.84---

 

op says not to use 465...

Link to post
9 hours ago, letrain said:

just installed.. every time the container starts it says driver mismatch and has to download drivers. i have the nvidia-plugin drivers installed that are listed in the op. the one in the docker is higher and says it has to download the lower version i have installed..

 

-Trying to get Nvidia driver version---
---Successfully got driver version: 460.84---
---Checking Xwrapper.config---
---Configuring Xwrapper.config---
---Driver version missmatch, currently installed: v465.19.01, driver on Host: v460.84---
---Downloading and installing Nvidia Driver v460.84---

 

op says not to use 465...

Don't use that version on the host (if you want to OC), haven't tried 470. The container handles the rest and are setup with default nvidia driver which will likely be replaced regardless - hence the missmatch. Nothing to worry about what's happening inside the container.

Link to post
  • 2 weeks later...

Hello, 

 

I am getting some notice in logs every few minutes. 

15:50:13 miner GPU 0 gave incorrect result. Lower overclocking values if it happens frequently.

 

Normally it will show as below:

16:01:29 miner Job: 32957e43 blk: 12826862 eth-us-east.flexpool.io:5555
16:01:30 miner 0:21 A0:F25 60.46 Mh - cu0 60.46 55C 65% 129.86W
16:01:32 miner Job: ffc6a8b3 blk: 12826862 eth-us-east.flexpool.io:5555
16:01:35 miner 0:21 A0:F25 60.45 Mh - cu0 60.45 55C 65% 129.90W
16:01:35 miner Job: 4e13f4c0 blk: 12826862 eth-us-east.flexpool.io:5555

 

I am having RTX 3070 Gigabyte gaming. Here are my settings:

 

Power: 130

GPU Clock: -503

Mem Clock: 2300

Fan Speed: 65%

Nvidia Driver:  v460.73.01

 

Please let me know how to fix this if anyone knows. 

 

Thanks

Edited by SaranG
Link to post
8 minutes ago, SaranG said:

Hello, 

 

I am getting some notice in logs every few minutes. 


15:50:13 miner GPU 0 gave incorrect result. Lower overclocking values if it happens frequently.

 

Normally it will show as below:


16:01:29 miner Job: 32957e43 blk: 12826862 eth-us-east.flexpool.io:5555
16:01:30 miner 0:21 A0:F25 60.46 Mh - cu0 60.46 55C 65% 129.86W
16:01:32 miner Job: ffc6a8b3 blk: 12826862 eth-us-east.flexpool.io:5555
16:01:35 miner 0:21 A0:F25 60.45 Mh - cu0 60.45 55C 65% 129.90W
16:01:35 miner Job: 4e13f4c0 blk: 12826862 eth-us-east.flexpool.io:5555

 

I am having RTX 3070 Gigabyte gaming. Here are my settings:

 

Power: 130

GPU Clock: -503

Mem Clock: 2300

Fan Speed: 65%

Nvidia Driver:  v460.73.01

 

Please let me know how to fix this if anyone knows. 

 

Thanks

 

It sort of says it.. either lower mem clock, or increase power and/or fan speeds and see if that helps.. GPU's are individual, try different values..

Link to post
  • 2 weeks later...
1 minute ago, nimaim said:

v460.73.01 is no longer available in the nvidia-driver plugin. Any other versions on the Unraid host confirmed working with this?

I haven't tried and likely won't. I'll leave the docker and the page up, but I will end the "support" now due to decreasing popularity in mining and the dockerhub won't build for free automatic anymore.

Link to post
  • olehj changed the title to Docker: nsfminerOC (unsupported)
6 minutes ago, olehj said:

I haven't tried and likely won't. I'll leave the docker and the page up, but I will end the "support" now due to decreasing popularity in mining and the dockerhub won't build for free automatic anymore.

Understandable, thank  you for your work on this! It was the only thing that worked for me to OC + set fan speed in a docker container. I'll migrate over to passing the cards through in a VM.

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.