Topic: [ mining os ] nvoc - page 125. (Read 418542 times)

The watchdog needs complete overhaul, some of its logic has no logic at all
I had cases when one GPU would hang and pretty much brings the whole rig to a crawl. Its 6x logic (x 13 GPU's for me) caused 3-4 hours of slow ~10% performance before it realized its time to reboot. Quick solution for me was to scratch its logic and change the code to reboot on any detected problem... I'd rather lose 1 minute rebooting than 4 hours of mining at 10%

I will revisit the watchdog soon, see if i can come up with some new logic for it

Check your network connectivity
can you ping google.com ?

Hey guys. Srsly nvOc Is amazing!!!
All rigs goin like monsters over here. Just one question.
One Rig does not want to launch any kind of miners.
Whenever I put "ETH" with my address and all it shows something about stratum.
Whenever I try to mine ZEC ( which is my main coin ) There is simply Nothing I Can do, it shows "there is no screen to be attached matching miner"
I double checked and still - there is no mining coming out from the rig. Anyone had this problem before?

How is OC by slot going to fix the scenario where a person just moves cards around in a rig as opposed to just removing one? Both scenarios are hardware changes and common sense dictates that the user be aware of this potential because they went down the path of path of individual OC in the first place. It is not like they went there by mistake, right?

Just wanted to say thank you to fullzero and the team! Just built my 1st rig gtx 1060 x3 mining Ubiq y’all really have a great product Thanks!

I'm sure you have thought about this long before it catch my attention, you have done awesome fix and edits to wdog.
I think the upper limit can cause too fast restart if all gpus fail
There should be a way with bash to catch and compare values by their location in the series, but I'm not sure how.

Completely disagree. This is dangerous way to overclock and could lead to catastrophic failure of your rig if a card dies on its own.. and they do.

Its discussed on the nvidia dev form with some python code that could be adopted to nvOC if anyone is interested:

https://devtalk.nvidia.com/default/topic/769851/multi-nvidia-gpus-and-xorg-conf-how-to-account-for-pci-bus-busid-change-/

Nothing to fix at all oO ...

You modified your RIG, you have to modify setting ...

Hi Guys,

I discovered a serious and potentially dangerous flaw in the way nvOC handles overclocking and would like to make a suggestion for an improvement.

We really need overclocking tied to the specific pcie slot (bus id) not an index that changes every time your hardware changes.

For example, if you have a gtx1080ti in slot 2, and a gtx1060 in slot 3, and your 1080ti goes offline for some reason or you remove it, the 1080ti overclock is now applied to what it thinks is the next card in the dumb index, and applies it to your gtx1060 potentially going POOF.

We need to apply overclocking to BUS ID:
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 00000000:02:00.0 Off |                  N/A |
| 70%   56C    P2   152W / 151W |    652MiB /  8112MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:04:00.0 Off |                  N/A |
| 70%   61C    P2   120W / 120W |    592MiB /  6072MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 1070    Off  | 00000000:05:00.0 Off |                  N/A |
| 70%   52C    P2   118W / 120W |    614MiB /  8113MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+

Oh believe me, I have thought about this one, too, and have yet to arrive and what I feel is a good solution. Having the reboot time grow proportionally to #GPU is not ideal, IMO. I am all ears if somebody wants to chime in. The best that I can come up with is an upper limit on count instead of just 6xGPU. There has to be a better way.

Great suggestion and workaround as always... Thanks mate.

There are moments that only 1 GPU wont get fully utilize and keep on going like that, problem with the current wdog on multiple GPUs is that it takes so long for wdog to restart 3 main if only one gpu fails, so on a 12 card rig it takes 72 times and while it checks every 10 seconds it will take more than 10 minutes for it to restart 3main

Any idea how to correct this?

Hello,
i added a 3rd 1080 Ti GPU in my rig. (H110 Pro BTC+)
but it stopped booting from the USB stick i use. i just hangs after the bios with the "B4" code written in the bottom right of the screen.
does it mean i have to switch to a HDD or SSD  for it to work now ? or do i need more than 4 GB of RAM ?

Please post your ubq setting from 1bash

Awesome! And thanks for the link.

Hey guys I'm pretty new at this. I imaged a USB arrive with v 19 and now it just keeps "cycling" and never starts mining. I set my coin to ubq, made up a worker name and set my wallet and mining pool. All it does is keep loading some I'm not a Jeep and something else over and over! I'm losing hair over this 😀😀

My suggestion is what I originally stated.

I admit it is confusing so here is another way of looking at. As written, the script will reset REBOOTRESET to 0 and reset RESTART to 0 every 6th time through the loop unless the miner is restarted (kill 3main) in which case only REBOOTRESET is set back to 0. My proposed change is to only reset both variables on the 6th time through the loop if there were no utilization issues found [which is what moving it "up" into the else clause does]. The REBOOTRESET=0 as a part of miner restart should remain unchanged. As written, the potential is there for RESTART to be reset to 0 even if there are still utilization issues thereby delaying potential host restart. In a nutshell, your rig could limp along longer than necessary with a GPU or 2 down over and over with miner restarts when only a host reboot will fix the problem.

Dont know about the lghts but overclock settings are in 1bash


Those values what I use for equihash mining with gigabyte 1070

So i have used the new nvoc 14, and its great

I have a Zotec Geforce GTX 1070 amp card.... and i want to know

   1. how do i switch the led lights off?
   2. How can i overclock the card in Ubuntu?

   many thanks for your help in advance

Fayaz

So whats your suggestion
Add an statement for it  after checking utilization?