[OS] nvOC easy-to-use Linux Nvidia Mining

[Joykiller]

Anyone come across random nvidia GPU Fallen off the bus messages before?

I've been logging them over the past few days to see if i can break down as to what is making it fail.

Code:

Aug  8 03:42:57 m1-desktop kernel: [105074.572611] NVRM: GPU Board Serial Number: 
Aug  8 03:42:57 m1-desktop kernel: [105074.572620] NVRM: Xid (PCI:0000:05:00): 79, GPU has fallen off the bus.
Aug  8 03:42:57 m1-desktop kernel: [105074.572626] NVRM: GPU at 0000:05:00.0 has fallen off the bus.

Second Time

Code:

Aug  9 22:18:43 m1-desktop kernel: [122030.262423] NVRM: GPU Board Serial Number: 
Aug  9 22:18:43 m1-desktop kernel: [122030.262433] NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus.
Aug  9 22:18:43 m1-desktop kernel: [122030.262439] NVRM: GPU at 0000:01:00.0 has fallen off the bus.

So its not the same GPU's each time its a new Bus, and GPU, Anyone got any Ideas? I was thinking maybe the 1070s not playing nice with the newest drivers or maybe the riser or its components failing? Thoughts?

[gs777]

No. My 1070 rig works fine, no problem.
I had problem with other rig
and when I switch gpu0 and gpu12 usb3 connection it stopped crushing.
Don't know is it the case for your rig, but its working for me
 

[LuKePicci]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

[Joykiller]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

[Joykiller]

No. My 1070 rig works fine, no problem.
I had problem with other rig
and when I switch gpu0 and gpu12 usb3 connection it stopped crushing.
Don't know is it the case for your rig, but its working for me
 

Thanks, Yeah I was thinking maybe it was something to do with either USB/x1 Connector/ the riser its self or Drivers. I got spares to replace them, Just continuing to test to see if more than just these two are causing the bus failure to see how many Risers i may have to replace.

[LuKePicci]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

[Joykiller]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.

[WaveFront]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.

No. What LukePicci was meaning is that in boards where the pcie connectors are close to each other, the side of the x1 connector, might touch the flat part of usb female connector of next x1 connector. This might disable the slot at best, or create short circuits.
in order to prevent this you should place isolating tape on the side of the x1 connector. You should cover with tape the parts highlited in red in the picture.


If you exclude too aggressive overclocking, 90% of the instability problems on a rig are coming from poor power distribution. Two pieces of advice:

1) the pcie cable to SATA provided with the risers is generally of crappy quality. In any case the SATA connector cannot take more than 50-55W, so you should connect the pcie riser to a 6pin PCI cable directly to the power supply or through a pcie splitter.


2) If you have a dual power supply configuration, you should power the motherboard and all PCI risers with the same power supply. You will use the second power supply to power the top connectors of the GPUs only. This will prevent ground loops and many headaches.

[Joykiller]

@joykiller check that your connectors in motherboard pcie sockets do not touch each other.

You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.

No. What LukePicci was meaning is that in boards where the pcie connectors are close to each other, the side of the x1 connector, might touch the flat part of usb female connector of next x1 connector. This might disable the slot at best, or create short circuits.
in order to prevent this you should place isolating tape on the side of the x1 connector. You should cover with tape the parts highlited in red in the picture.
https://cdn.pbrd.co/images/HyM9NAj.jpg

If you exclude too aggressive overclocking, 90% of the instability problems on a rig are coming from poor power distribution. Two pieces of advice:

1) the pcie cable to SATA provided with the risers is generally of crappy quality. In any case the SATA connector cannot take more than 50-55W, so you should connect the pcie riser to a 6pin PCI cable directly to the power supply or through a pcie splitter.
https://cdn.pbrd.co/images/HyMadEJ.jpghttps://cdn.pbrd.co/images/HyMcXqw.jpg

2) If you have a dual power supply configuration, you should power the motherboard and all PCI risers with the same power supply. You will use the second power supply to power the top connectors of the GPUs only. This will prevent ground loops and many headaches.

ah right, well I already know about the connectors, been running a few GPU rigs for over a year already no problems. Problem seems to be be fixed it was more or less a power issue i believe as its going now for 48h no interuptions. (Undervolted)

Interesting about the USB I dont seem to have that issue tho.

[gs777]

Trying to run new Bminer but It doesn't start
I have this message all the time

Code:

 SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/bminer/latest/bminer -uri stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575
invalid value "stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575" for flag -uri: Unsupported scheme
Bminer: When Crypto-mining Made Fast (v9.1.0-9f41d5c)

Can anyone help me, what I did wrong?

[papampi_2]

Trying to run new Bminer but It doesn't start
I have this message all the time

Code:

 SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/bminer/latest/bminer -uri stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575
invalid value "stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575" for flag -uri: Unsupported scheme
Bminer: When Crypto-mining Made Fast (v9.1.0-9f41d5c)

Can anyone help me, what I did wrong?

Set correct coin protocol
COIN_POOL_PROTOCOL="................."

From 1bash.template:

Code:

#        If using bminer for equihash or ethash use these protocols:
#        Equihash Stratum: "stratum", Equihash Stratum+SSL:"stratum+ssl" 
#        Ethash Stratum:"ethash", Ethash Stratum+SSL:"ethash+ssl", Ethereum Proxy:"ethproxy" ethereum Stratum:"ethstratum"

[whiteman85]

Hi
I downloaded latest image nvOC_V19-2.1beta_U16.04_N390_D180707. When i try mining ETH or ETC with claymore I get
nvOC_V19-2.1beta_U16.04_N390_D180707

[WARNING] - Attempting to launch miner for an undefined algo

LAUNCHING:  MINER (coin: ETH, algo: UNDEFINED)


COIN/ALGO not found, Check your settings
Miner not started, Stopping watchdog

This is not my first time with NVOC, but now I get confused.

[Spiralx]

Latest NVOC 2.1 beta is still using Teamviewer 12, any plans to include Teamviewer 13 instead? I'm not sure if I can just uninstall 12 and install 13 without breaking anything?

[papampi_2]

Hi
I downloaded latest image nvOC_V19-2.1beta_U16.04_N390_D180707. When i try mining ETH or ETC with claymore I get
nvOC_V19-2.1beta_U16.04_N390_D180707

[WARNING] - Attempting to launch miner for an undefined algo

LAUNCHING:  MINER (coin: ETH, algo: UNDEFINED)


COIN/ALGO not found, Check your settings
Miner not started, Stopping watchdog

This is not my first time with NVOC, but now I get confused.

Please run nvOC upgrade and update your 1bash with latest 1bash.template and check again.

Code:

bash ~/NVOC/mining/nvOC upgrade

If upgrade doesn't ask to check miners too, run it again.

[alex_nv]

I have nvOC_V19-2.0, about 6 months old... I was trying to update it with:

bash ~/NVOC/mining/nvOC upgrade

and

cd ~/NVOC/mining
git pull

and

cd ~/NVOC/mining
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/nvOC
bash nvOC upgrade

and all I get is "no such file or directory" message
there is no /home/m1/NVOC folder
is my OS too outdated, or what's going on?  and if it's that old, is there a different set of commands that I can run, or I have to reinstall NVOC completely?

[Coongcoonggg]

Top is showing that I'm not using more than about 1.2GB with four cards.  I'll test this weekend on my 6 GPU system, but doubt it would use more than 2GB

[fk2]

1. couple of rigs gained in the last months. I need to step up my monitoring game, currently I am just getting telegrams twice a day which is bad because I loose attention on these. I am dreaming of a http GUI with some graps and telegram only if a rig is nA/low utili./problematic. anyone?

2. I have a rig with 2.0 stable release. I patched up2date and try to run nicehash on this one. nothing happens after fresh reboot. when I run 'bash nvOC stop' and 'bash 2unix' some output appears and it stops here:

Code:

....
(guake:3127): libglade-WARNING **: unknown attribute `swapped' for <signal>.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

Then I hit CTRL+C and the rest of the script starts up and I see everything running as desired. What to do here?

[papampi_2]

Latest NVOC 2.1 beta is still using Teamviewer 12, any plans to include Teamviewer 13 instead? I'm not sure if I can just uninstall 12 and install 13 without breaking anything?

Will update it in next image release.
In the meantime you should be able to update it from inside teamviewer menus > help > check for update

[papampi_2]

I have nvOC_V19-2.0, about 6 months old... I was trying to update it with:

bash ~/NVOC/mining/nvOC upgrade

and

cd ~/NVOC/mining
git pull

and

cd ~/NVOC/mining
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/nvOC
bash nvOC upgrade

and all I get is "no such file or directory" message
there is no /home/m1/NVOC folder
is my OS too outdated, or what's going on?  and if it's that old, is there a different set of commands that I can run, or I have to reinstall NVOC completely?

There is no NVOC folder in 19-2.0
And there are no major updates for 19-2.0, you can use 19-2.1 GitHub wiki to update to 19-2.1 or use nvOC_V19-2.1beta_U16.04_N390_D180707.img


nvOC Community Edition - Quick start how-to



Latest image will be released in a week (hopefully) with Ubuntu 18.04, Dual Cuda 8.0/9.2 with auto switch for older miners, latest Nvidia drivers, miners and so many improvements.

[alex_nv]

nvOC Community Edition - Quick start how-to

thank you

I am editing new bash file now, and I noticed this:

Code:

WTM_AUTO_SWITCH_SYNC_INTERVAL="3"             # Time to sync with WTM for best coin, minimum 3 minutes.

WTM_PROFIT_CHECK_INTERVAL="30"                # interval between checking profit for web info

WTM_MIN_DIFFERENCE="6"                        # Mininumum difference in percent when switch to new coin, to prevent too many switches.

WTM_MINIMUM_MINING_TIME="1800"               # Minimum mining time before checking and switching to prevent fast switches.

WTM_LOWER_MIN_DIFFERENCE="3"                  # When Minimum Mining time passed, next top coin will switch with lower difference

WTM_FORCE_SWITCH="8"                          # If profit gain is more than this value make the switch and dont wait for minimum mining time.

WTM_CURRENCY="USD"                            # USD, AUD, BRL, CAD, CHF, CLP, CNY, DKK, EUR, GBP, HKD, INR, ISK, JPY, KRW, NZD, PLN, RUB, SEK, SGD, THB, TWD

more specifically

Code:

WTM_MINIMUM_MINING_TIME="1800"  

is it in seconds or in minutes? looks like everything else is in minutes, and if minimum mining time is also in minutes, isn't it a little too much?