Topic: [ mining os ] nvoc - page 262. (Read 418549 times)

In that case, it is probably x intermittently launching or not launching most likely do to modification of the xorg.conf.  It is probably best to only conditionally change the xorg; but making / testing a configuration that works more smoothly will be much easier with my own p106-100 rig. I set the current p106-100 1bash to always modify the xorg.conf to avoid potential infinite boot loop problems vs only having a single boot that doesn't OC.

When remoting in; it is important to realize that you can SSH in before all system init has occurred.  Think of when you are watching nvOC load on a monitor.  When Ubuntu is loading; there is a period where you cannot use the keyboard or mouse / guake has not started / 2unix (via gnome-terminal) hasn't launched.  You can SSH in before this interval in system init.  If you do, this act alone may change the init sequence, or it might only be launching bash earlier which may do this.

It could also be something else entirely; such as x intermittently launching or not launching which is causing the problem.  This is the type of thing It will be much easier to isolate with my own p106-100 test rig.

For now I would try waiting longer after reboot before SSHing into the rig and seeing if that resolves the problem.  Let me know how it goes.

What version of nvOC are you using?

Looking at this list of errors they are all essentially 1 error; which if I am correct is the equivalent of when you try to go to a webpage and are getting a certificate error from your browser.

When I directly use the url in a browser:  https://api.coinbase.com/v2/exchange-rates?currency=BTC the api is working; I would try doing this on your rig in a browser and see if it responds with a json.

Let me know if it does.

Any idea guys??

UPDATE :

Now I'm not getting the above error but get different issue; main terminal says mining starts in guake terminal; but on guake 'There is no screen to be resumed matching miner' error appears.

Will compare it with latest 1bash and see if there are any differences.

EDIT :

Sorry, I've overlooked, I'm still getting the above error and on guake getting this 'There is no screen to be resumed matching miner'

Hello.

Please help me solve the problem:
GPU UTILIZATION: Unable to determine the device for GPU 0000: 09: 00.0: GPU is lost. Reboot the system to recover this GPU.

 I'm new in Linux, tell me how to fix this?

I have got multiple biostar tb250 btc pro mobos.

I am going to run this with 12 gtx 1070 hours.
Is this possible with nvos?
 Driver wise?

So 12 gtx 1070 one motherboard?

Is there anything special I need to do in order to get a pci 1x 1slot to 3 slot adaptor to work?

http://1stminingrig.com/pci-express-1-to-3-pci-e-1x-slots-riser-card-is-it-worth-it/

I'm uploading a copy I'd originally downloaded from Google Drive (or was it Mega?) to my VPS.  I'll post a link once it's up.  SHA256 hash on the file is d11929368d186acf73651be1b9d90234cfe6ef8a097eff56668dee4cbbe69e8c, as announced here.

Hi all,
I can also confirm that all 13*P106-100 are working.
Dual mining ETH/PASC at CC 0, MC 1300, Powerlimit 115, i get eth 307/pascal 3070. 6 hours stable.

Hey everyone.

As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours )  , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.

Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.

Can you advise on what should I do in that case?

Download the pure P106-100 1bash for headless SSH operation from the link on the OP; replace the 1 bash on your rig with it.  

Add your pool / addresses / workername to the 1bash.

Note: for this version don't use:

Maxximus007_AUTO_TEMPERATURE_CONTROL

or

IAmNotAJeep_and_Maxximus007_WATCHDOG

ensure they are both set to "NO"

Run the mining process; it should not OC at this time.  This is expected; it will alter the xorg.conf as needed.  

Note the Rig IP; write it down.

If you are not already running fully headless; ensure that you reboot: disconnecting any monitor from integrated graphics on the mobo before the rig reboots.

With your rig IP ssh into the rig after it boots ( see guide on the OP for more information on how to do this.  If from a linux system use the cmd from terminal:


you will be prompted

enter:


the password is:

once you are logged in via SSH; enter:


if there is already a screen named miner use the cmd:


to reconnect to the mining process and ignore the rest of this guide


if there is not; enter the cmd:


to launch the mining process

once you see the message:


hit


then enter:


If you have problems with this; let me know.  I can't test this directly as I don't have these GPUs; but this should work unless I made a typo in the 1bash.


Also; you can edit the 1bash via SSH with the cmd:


note this is a visual editor; again see the SSH guide for more info on nano.

It appears the site previously used extremely limits bandwidth on large downloads

nvOC 17 high speed download below
https://www.mediafire.com/download/oi84ue7e6z9epn9