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

[fullzero]

First of all thanks for the awesome system.
It would be nice if you implement "Scott Alfter" mining pool hub switch https://gitlab.com/salfter/mph_switch to 1bash same as his nicehash switch.

Thanks again.

I will integrate Scott's MPH switch.

[fullzero]

Hey FZ,

I've got a problem with log files - /var/log/kern.log and /var/log/syslog logs are filling up all available space (currently each file is 22.7gb - eating up 45gb of a 64gb thumb drive).  All the errors in kern.log and syslog both seem to be of this type:

Aug  2 19:53:48 m1-desktop kernel: [  103.261020] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261021] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261025] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261028] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261033] pcieport 0000:00:1d.0: can't find device of ID00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261060] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261065] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261066] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261067] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261070] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261075] pcieport 0000:00:1d.0: can't find device of ID00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261086] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261090] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261092] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261093] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261126] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261130] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261131] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261132] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261162] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261166] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261167] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261168] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261189] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261193] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261194] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261195] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261226] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261230] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261231] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261235] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261238] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261244] pcieport 0000:00:1d.0: can't find device of ID00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261264] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261269] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Aug  2 19:53:48 m1-desktop kernel: [  103.261270] pcieport 0000:00:1d.0:   device [8086:a299] error status/mask=00000001/00002000
Aug  2 19:53:48 m1-desktop kernel: [  103.261271] pcieport 0000:00:1d.0:    [ 0] Receiver Error       
Aug  2 19:53:48 m1-desktop kernel: [  103.261277] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261282] pcieport 0000:00:1d.0: can't find device of ID00e8
Aug  2 19:53:48 m1-desktop kernel: [  103.261289] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8


How can I either disable verbose logging for these errors or prevent the log files from getting so large?  It's literally to the point where I can't even save oneBash changes because there isn't any room left. 

I’m using TB250-Pro BTC with 1050Ti and 1070 and found same error. I fixed as below steps,

 $sudo cp -p /etc/default/grub /etc/default/grub.bk
 $sudo vi /etc/default/grub
      
Add “pci=noaer” in grub 

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"


 $sudo update-grub
 $sudo reboot

The error message was gone. It’s seem no impact, my rig is normal running.

Nice fix od808

[fullzero]

Hey Guys,

Have a problem with loading the OS as it tells me "xorg PROBLEM DETECTED" and then reboots and shows:
error: unknown filesystem
grab rescue>

What can it be and how can I solve this? Used flashing tools as described and tried it at least twice. I am using ASrock h110 and at the moment just one Manli P106-100 card just so I can test if I can install the OS before installing all 13 cards.

I need one or two of the:

P106-100

to test and ensure nvOC will properly support these GPUs.  A number of members have had problems using these GPUs.  If someone is willing to sell me 1 or preferably 2 Please pm me.

[fullzero]

is it safe to change the password of m1?
i need A stronger password to put my rigs into IDC.

Yes, I do it as soon as it boots the first time. No issues.

Remember to change the root password as well; it is also miner1 by default.

[fullzero]

Hello,

first I want to say thank you very much for the amount of effort and work that you put into this software image.
I am also using v0018, but unfortunately the fan speed is not set correctly (I want to set it to 100%).

I have modified the following values in the script:

Code:

MANUAL_FAN="YES"
FAN_SPEED=100
TARGET_TEMP_0=60
TARGET_TEMP_1=60
TARGET_TEMP_2=60
TARGET_TEMP_3=60
TARGET_TEMP_4=60
ALLOWED_TEMP_DIFF=10

Additionally I can see upon startup, that nvidia-cli is setting the fan speed correctly. But however, Claymore is only showing a fan speed of 50%. Furthermore, the temperature is 70 C°, which states that the max temperature setting in the script is also not working as intended.

My hardware:

MB: Asrock Z170 Pro 4
GPU: 5x MSI GTX 1050Ti

Thanks very much in advance.
Kind regards.

To ensure fans run at 100% make sure the following settings are as such in 1bash:

Code:

Maxximus007_AUTO_TEMPERATURE_CONTROL="NO"

MANUAL_FAN="YES"         

FAN_SPEED=100

[fullzero]

Hi guys, has anyone tried to use this OS with P106-100 mining cards without video output as I keep getting  "XORG FAIL" error and the system reboots. After that it just  shows :

error: unknown filesystem
grab rescue>

Does this happen because the monitor is connected to the motherboard since I do not have any video output available, can I maybe edit the xorg.conf file to get rid of this error?

Would be very thankful for any help, been trying to work this out for 3 days now...

for now to stop the endless reboot loop; open 1bash and scroll down to the implementation section and change:

Code:

XORG="FAIL"

to

Code:

XORG="OK"

and save

[fullzero]

Ey mate any chance you're thinking about adding skunkhash raptor algo into v19?

Will do.

[fullzero]

Hey, peeps, I don't know if it's been discussed before in here but as I scored through last 15-20 pages, I didn't find any relevant answer to my query. I just want to ask if Windows 10 is giving me 24.5 MH/s on my GTX 1060 with +800 MC and -150 CC using afterburner, that's not the case with Linux. I'm getting around 22 MH/s for the same settings on Linux. Any reason why that happens? Is it because of performance mode not being on level 2 in Nvidia server X settings?

AFAIK in Linux you should try a doubled MC offset (1600 in your case), to be equivalent of the Afterburner settings in Windows. I think in Windows the offset is applied to the "base" or "real" memory clock, while in Linux it's applied to the effective clock, which is twice, since we are working with double data rate (DDR) memory. (Well, GDDR5 memory clocks are not as simple as that, but that's what I figured from reading reports here and there.)

Well, I tried your way with double MC offset but still the same results. Anyway, thanks for the reply bud.

For future reference: All of Bitcointalk is indexed by google. 

The effective powerlimit should be the same; in windows it is in %TDP and in linux in is in watts.

Also; the OC curve is different in Linux than it is in windows.  You will need to use higher clocks to achieve the same hashrate; but you can use higher clocks than you can in windows.

In your case you changed the MC and not the CC.  You also are likely using the same powerlimit setting when needing to set a higher powerlimit to actually use the same amount of power in linux.  Most 1060s have a TDP of 125 watts.

Also keep increasing the MC until you get a soft crash.

[fullzero]

Hi,
I have Lexar S75 32gb. After i installed 0018 im getting message "low disk space" I reflashed usb many times but error comes again and again

try this 1liner from _Parralax_:

Code:

sudo apt-get purge $(dpkg -l linux-{image,headers}-"[0-9]*" | awk '/ii/{print $2}' | grep -ve "$(uname -r | sed -r 's/-[a-z]+//')")

[fullzero]

Hi guys, if posted prior my apologies as I tried to search this thread and the global threads.

My question is in regards to 'Maximus007_Auto_Temperature_control'

When I have it on it doesnt matter what I set the 'target_temp' for each card at it seems to like running the cards at 70 to 80 degrees and will up and down scale the fans to keep them there.  Fans are at 30 - 35%.

I prefer a temp of 55 to 60.

Then I thought I would turn it off but even if I set manual fan to yes and the auto temp to 'no' my fan speed of 65% is not reflected so I think the script runs regardless of what you put in 1bash.

Anyone had this issue and either (a) found a way to make it respect the selected temperature or (b) disable it and allow for manual fans?


Many thanks!

change:

Code:

TARGET_TEMP_0=60

TARGET_TEMP_1=60

TARGET_TEMP_2=60

TARGET_TEMP_3=60

TARGET_TEMP_4=60

TARGET_TEMP_5=60

TARGET_TEMP_6=60

TARGET_TEMP_7=60

TARGET_TEMP_8=60

TARGET_TEMP_9=60

TARGET_TEMP_10=60

TARGET_TEMP_11=60

TARGET_TEMP_12=60

TARGET_TEMP_13=60

for b see:

https://bitcointalk.org/index.php?topic=1854250.msg20730240#msg20730240

[fullzero]

can we do skunk on this?  on zpool


do I have to add the software to mine  or is the option added.

I been tied up for days fixing my btc and my bcc. the  free money was nice.

I now would like to do some skunk on my new build here.

Phil;

the new TP ccminer is needed for this.  I will add skunk on zpool to the next 1 bash.

[fullzero]

Ok I was able to root and pull the current specs of my cards.
This is an 4x Gigabyte gtx 10606gb rig.
I have my MC set to 1050 in 1bash and if I'm reading this right it says I'm at a current clock of 8748 with a max of 8754.
How do I get more than a 750 MC increase?

If u want to mine SIGT u have to lower your MemTransferRate and up your nvclock

http://imgur.com/a/yZuOE

Be in root and

nvidia-settings -a /GPUGraphicsClockOffset[3]=value
nvidia-settings -a /GPUMemoryTransferRateOffset[3]=value

U can specify by GPU, like the other command

nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=value
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=value

I am mining Eth
Is this what I need to do to get my cards on performance level 3?

I currently have in 1bash
CC=0
MC=950
But it doesn't appear to go past a MC of 750, in the Nvidia xserver it shows level 2 as highlighted and level 0,1,3 as greyed out and level 3 shows the clock that I have set in 1bash.


Also something else I noticed this morning
I have the powerlimit set to 75w right now in1bash.
When I start up everything runs smoothly for about 15 minutes, then one of my cards changes from a PL of 75 up to 125 and my MH/s drops from 161 down to 142.

I tested the rig with the card disconnected and it still has a 15-20 MH/s drop after about 15 minutes.

I would update to the newest 1bash and watchdog linked on the op.  then ensure:

Code:

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

INDIVIDUAL_POWERLIMIT_3=75

INDIVIDUAL_POWERLIMIT_4=75

INDIVIDUAL_POWERLIMIT_5=75

INDIVIDUAL_POWERLIMIT_6=75

INDIVIDUAL_POWERLIMIT_7=75

INDIVIDUAL_POWERLIMIT_8=75

INDIVIDUAL_POWERLIMIT_9=75

INDIVIDUAL_POWERLIMIT_10=75

INDIVIDUAL_POWERLIMIT_11=75

INDIVIDUAL_POWERLIMIT_12=75

INDIVIDUAL_POWERLIMIT_13=75

for each GPU when using Maxximus007_AUTO_TEMPERATURE_CONTROL

most likely you need to use a higher powerlimit and cc to get to lvl 3.  75 watts is a low pl for a 1060; use at least a 100 for optimal hashrates.  I use 105 with most of my 1060 6gb.

[fullzero]

thanks guys i finally manage to make it run for couple of hours now, heres the new problem i plug all my 6 GPU in my Biostar TB250-BTC PRO but only 5 was working
bios already set to mining above 6gpu, pcie set to GEN1, i plug my monitor on the 1x16 pcie all fans are working. and im lost

Did you try swapping out the riser on the GPU that is still cold after mining a bit?

[fullzero]

Hi!
I'm about to build a rig with Pentium G4400.
But after reading about Skylake issues with hyper threading don't know
should I use it or better to return and exchange it with i3?

i have a rig runs 8 cards with G3900, no problem.

I have a rig with G3900 and 10 cards, but it seems that the G3900 is bottlenecking the system. First core uses 100%, the other around 20%.

Is there a way to split the workload on both cores (If I could run EWBF miner in two terminals or is there some other way)?

Can somebody please help me, i'm a noob in linux.


nvOC is a great system. Thanks for all the work.

I tried opening two miners in two screens with some change in 1bash:

screen -dmS minerX1 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 0 1 2 3 4 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;
screen -dmS minerX2 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 5 6 7 8 9 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;

After the change there are two processes in System monitor, but CPU usage is still the same (100% one core, 20% second core).

Is it possible that System monitor doesn't show the correct CPU utilization?
Will it help if I change the CPU from G3900 to i3 or perhaps i5?

Fullzero, I see You have 13 GPUs on Asrock H110 PRO BTC (I am using the same motherboard). What kind of CPU do you have so that everything is working smoothly?

Using a kabylake i5;

I'm making another 13x rig soon with a g4560; I'll let you know if it works well as well.

[fullzero]

hi,
i have Asrock H110 btc+ pro, and 13xMining/P106-100 (1060 6gb) GPU-z everything works fine and stable with other OS-es, but with your OS it keeps restarting and restarting because of not being able to see/find xorg file.

We managed to start the OS via GTX 1060 card and then added the Mining P106-100 (1060 6gb) cards, but no go with only the Mining P106-100 (1060 6gb) cards. can you look in to this ? i would like to use your OS but dont want to have a normal gaming card, don't need it when using all Mining cards.

Can you also make a explination on overckloking as we tried via the file but failed. we only managed to individually overclock via the Nvidia x server.

thank you.
BigSmurf

There is something different with the P106-100 GPUs when using X.  This isn't surprising as they have no video out.  I need 1 preferably 2 of these GPUs to test and identify what needs to be changed in the system; to ensure nvOC supports them. 

OC and PL will not work if the GPUs aren't properly recognized.

If someone is willing to sell me 1 or preferably 2 Please pm me.

[fullzero]

Hey, ty for adding teamviewer to nvOC!

But i got a problem: teamviewer never start on boot, i always need to enter this on guake terminal :

sudo teamviewer --daemon enable


My rigs are not at home, and if i need to reboot this, i can't control after the reboot :-(, please help me.

On your 1bash be sure to set

TEAMVIEWER="YES"

Oh thanks, there is a way to edit the 1bash in ubuntu ? if yes it need a restart ? thanks!

Yes, you can. It is in the home directory. Please search in home folder (where you see all miners)

EDIT:

For restart, to apply the 1bash changes you don't need to restart whole rig, you can kill the mining process using 'CTRL + c' and it should restart the process with new changes, if it doesn't just close the terminal after 'CTRL+c' and close the terminal and restart the terminal (not the rig)

press CTRL+c, it restarts 1bash, do you know how to disable this feature?
 I'd like to exit the terminal when I press CTRL+c, thanks.  

The way everything is setup; is to expect this to occur.  You can change this but; it will break a lot of other things.

When gnome terminal is open go to the top left of the screen and click terminal, then preferences, then profiles.  select mining and click edit.  Click the command tab.  Change when command exits: to Exit the terminal.

[dbolivar]

@fullzero

Have you considered moving the configuration, or at least the key configuration parameters like pools and coin to mine, to a separate file? I sometimes change pools and coins, for instance, and currently I have several "1bash_xxx" files for each configuration, controlling the active one with a symlink to "1bash". One idea would be a config file like this (for instance in INI format, but just to illustrate):

::: 1bash.conf :::
[defaults]
# Every configuration option

# Below just what's different from default. Users define their config keys,
# specifying the active one in 1bash
[zec-nanopool]
COIN="ZEC"
ZEC_POOL="zec-us-east1.nanopool.org"

[eth-dwarfpool]
COIN="ETH"
ETH_POOL="eth-us.dwarfpool.com"

::: 1bash :::
# 1) Read default options
# 2) Read user options
USER_CONF="zec-nanopool"
...

Just an idea. I may be able to help you with that, if you want and find it a good idea. I know Bash doesn't have a built-in parser for INI (or whatever) config files, but there's some code around to do that.

[damNmad]

Hi guys, if posted prior my apologies as I tried to search this thread and the global threads.

My question is in regards to 'Maximus007_Auto_Temperature_control'

When I have it on it doesnt matter what I set the 'target_temp' for each card at it seems to like running the cards at 70 to 80 degrees and will up and down scale the fans to keep them there.  Fans are at 30 - 35%.

I prefer a temp of 55 to 60.

Then I thought I would turn it off but even if I set manual fan to yes and the auto temp to 'no' my fan speed of 65% is not reflected so I think the script runs regardless of what you put in 1bash.

Anyone had this issue and either (a) found a way to make it respect the selected temperature or (b) disable it and allow for manual fans?


Many thanks!

change:

Code:

TARGET_TEMP_0=60

TARGET_TEMP_1=60

TARGET_TEMP_2=60

TARGET_TEMP_3=60

TARGET_TEMP_4=60

TARGET_TEMP_5=60

TARGET_TEMP_6=60

TARGET_TEMP_7=60

TARGET_TEMP_8=60

TARGET_TEMP_9=60

TARGET_TEMP_10=60

TARGET_TEMP_11=60

TARGET_TEMP_12=60

TARGET_TEMP_13=60

for b see:

https://bitcointalk.org/index.php?topic=1854250.msg20730240#msg20730240

Hi Fullzero,

With a fresh install of NvOC , changing target temps doesnt do anything on my rig.  The fans do move up and down but they dont maintain target temp.

For example I set target temp as per your note to 60 and the cards run at 80.  The fans go up and down on each card to maintain 80.  The expected result is that they go faster to say 55% so the card runs at 60.

If I follow the steps in (b) this doesnt do anything different.  

I am using v17 , was this an issue in 17?  Or could it be my cards causing the issue
I am in Australia and we have celcius as our default temperature and you guys use farenheit could that be an issue somewhere?

In version v15 if I set manual fans to 70% they ran at 70% - for me in this version they seem to do their own thing

I think living in Australia doesn't have anything to do with 'Maximus007_Auto_Temperature_control' script

I would suggest try V18 and try the above suggested options, there were issues in v17 (I had similar one) so better try v18.

If the issue still persists in V18 share your 1bash with me, i will compare it to mine and see if there is any issue.

EDIT :

Lets give fullzero max time on development getting done for next releases by solving the minor issues ourselves

[ivoldemar]

Hey, ty for adding teamviewer to nvOC!

But i got a problem: teamviewer never start on boot, i always need to enter this on guake terminal :

sudo teamviewer --daemon enable


My rigs are not at home, and if i need to reboot this, i can't control after the reboot :-(, please help me.

On your 1bash be sure to set

TEAMVIEWER="YES"

Oh thanks, there is a way to edit the 1bash in ubuntu ? if yes it need a restart ? thanks!

Yes, you can. It is in the home directory. Please search in home folder (where you see all miners)

EDIT:

For restart, to apply the 1bash changes you don't need to restart whole rig, you can kill the mining process using 'CTRL + c' and it should restart the process with new changes, if it doesn't just close the terminal after 'CTRL+c' and close the terminal and restart the terminal (not the rig)

press CTRL+c, it restarts 1bash, do you know how to disable this feature?
 I'd like to exit the terminal when I press CTRL+c, thanks.  

The way everything is setup; is to expect this to occur.  You can change this but; it will break a lot of other things.

When gnome terminal is open go to the top left of the screen and click terminal, then preferences, then profiles.  select mining and click edit.  Click the command tab.  Change when command exits: to Exit the terminal.

Friend, look, please. It's in your interests. I need to collect 30 farms for 12 Mining Edition cards and I want to do this on NVOC and I need to collect it before the end of the week, but without overclocking there is no sense at all.
I sent you access to private messages.

Very much I ask you, to solve a situation.

[lards]

Hey Guys,

Have a problem with loading the OS as it tells me "xorg PROBLEM DETECTED" and then reboots and shows:
error: unknown filesystem
grab rescue>

What can it be and how can I solve this? Used flashing tools as described and tried it at least twice. I am using ASrock h110 and at the moment just one Manli P106-100 card just so I can test if I can install the OS before installing all 13 cards.

I need one or two of the:

P106-100

to test and ensure nvOC will properly support these GPUs.  A number of members have had problems using these GPUs.  If someone is willing to sell me 1 or preferably 2 Please pm me.

I have solved this issue by editing the line "XORG FAIL" to XORG "OK" which worked and the system started, now I have the different problem :

When I run more then 6-7 cards on the board no matter in what miner I either get error 15 " cannot get current temperature " or the system just freezes after in about half an hour or a bit longer and the only thing that helps is to turn off/on the power socket... I have updated the drivers and now trying to wait for it to freeze on 6 cards since it works the longest out of all the set ups I tried. As soon as I try 10 or more GPUs I either get error 15 or just frozen system. I don't think it's one of the cards since I mixed them a couple of times and what I noticed is that it crashes faster as I add more GPUs.

Do you have any idea where the problem can be? I have also 2 PSUs connected together one 600W Zalmann powering motherboard and 2400W HP server PSU which was remade for GPU mining and powers risers and GPUs, both of those seem to be working fine , so I have no idea where to look for solution.

If anyone had this problem please let me know , would be greatly appreciated... Even willing to donate to somebody who's advice will help.

PS. The cards are in stock mode, so it's not OC.

UPD Been pretty stable on 6 cards , have been running for 8 hours now , probably will try and add a couple after a 16-20 hour mark...