[ mining os ] nvoc

[citronick]

anyone has good settings for core/mem in onebash for 1070 and 1080ti

I have tried many settings with various results but tdp seems to be inconsistent.

3 x Zotac 1070 Mini around 439w from the wall, ZEC 1132sols at stock settings, no changes in onebash settings

is this expected?

[eli_lyd1]

I want to set my own os, but failed:

I run :

nvidia-settings -a [gpu:0]/GPUFanControlState=1

but failed:

ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.

Anyone know?

[citronick]

anyone has good settings for core/mem in onebash for 1070 and 1080ti

I have tried many settings with various results but tdp seems to be inconsistent.

3 x Zotac 1070 Mini around 439w from the wall, ZEC 1132sols at stock settings, no changes in onebash settings

is this expected?

It seems like there is a powerlimit of 125 with those results.  377 Sol/s is way too low for stock power, even without OC.

Note: once you have used a powerlimit at all since boot it will not turn off, until you reboot or logout: it can only be modified. Thus to return to stock TDP you would use a powerlimit of 150, or reboot/logout/in.

In EWBF the pec output will accurately tell you how much power the cards are currently using, look that and see if they likely are using a powerlimit.

Currently with the good ZEC returns; I am using cc+200 mc+900 powerlimit 135 with my zotac 1070 mini rigs.

With my 1080tis I am currently using cc+100 mc+900 powerlimit 225.

Edit: also using manual fans with 75% speed.

thanks fullzero - I am in process of setting the rigs up and running stock at the moment.

I cranked up the Gigabyte Auros 1080tis using your settings -- I see 770-780 sols per card at 310-315watts per card.

I was too ambitious in getting a 5 x 1080tis on a single rig -- however I am getting dual server psu/pico/bb to get this monster up to about 4500 sols per rig -- otherwise; 3 x 1080tis per rig probably be safer and cooler.

[LTCbusiness]

Thank you so much for your help, here is the LSPCI

m1@m1-desktop:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 5902 (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)

And here is the xorg.conf

This xorg.conf is missing large amounts of needed settings.  I think I know what the problem is / happened.  The image I made needs to NOT be using integrated graphics.

You have integrated graphics enabled in the bios or have attached a monitor to the video output on the mobo and forced an auto configuration on the mobo to start the integrated graphics.  This caused the system to create a new xorg.conf file which lacks almost all the needed changes.  Technically the one needed should be stored as the backup, but fixing this image will probably take longer than the following:

How is your monitor connected to your rig?  

If it is not attached to the second GPU please attach it there.

Then shutdown your rig.  

Unplug the usb key.  

Power on the rig, bios should post.  

Restore defaults to the bios, it should need to restart to do this.  

When it has rebooted with default configurations, make these three bios changes here and no others:

ensure 'Above 4G Decoding' is enabled in the bios.

ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.

ensure you 'Clear Secure Boot Keys' in the bios

save and reboot

Now reimage your USB key with the ASUS PRIME Z270-A image.

when it is done, attach to rig and press ctrl + alt + delete to reboot

When ubuntu starts up watch the gnome terminal and see if OC occurs correctly.  I think it will if you follow the previous steps.

If it doesn't: open the guake terminal and enter:

lspci | grep VGA

and post what it says.

If it does work also let me know.  


Edit:  note when 7 cards are connected the monitor will display all black while booting; but will display normally once ubuntu starts.

So I followed your instruction and it is working well now, just 1 problem, although the busid match 100% with other cards, onebash only recognize Gpu 0 (the one with hdmi cable plug to monitor), and only oc that card, for the remain 5 card i need to do it manually with nvidia x server app.

For the oc value. I am using galax 1080ti, each time i try to oc it with cc200 mc >600, the system is almost crashed, sometimes the card not respone. I am using powerlimit 200, should I pl 125 as you do and oc 200-900? I may try it tomorrow since I am testing the stable of the system with the current oc value 150/450 before I go to sleep.

And one more thing, the usb os is kind of quite slow, do you plan to make the os for ssd in the future? I see th e system quite laggy at the start, not sure if it can handle the 7 cards running in the long run, like 1 months continuesly.

I really thank you for your os and your support for my problem, you are the real hero, man.

[funnyboy027]

How many sols you get with this setting +100cc +900mc 200mv for 1080ti
I currently using +100cc +400cc and get 650 sol, can't increase to +900mc same as yours

[funnyboy027]

Wow, impressive result, I'm using Windows with EWBF miner but has only 650s per card. I will try to use nvOC and report here, I have 6 cards Gigabyte GeForce® GTX 1080 Ti Gaming OC 11G

How many sols you get with this setting +100cc +900mc 200mv for 1080ti
I currently using +100cc +400cc and get 650 sol, can't increase to +900mc same as yours

What OS are you using?

Note in these photos GPU 0 is an EVGA 1080ti SC and GPU 1 is a Reference EVGA 1080ti; look at the difference in temps and you will understand why its better to go with the After Market models.

Also these have active cooling, 1x server fan behind each card.  I get risers and server fans from: hawkfish007

https://s23.postimg.org/nhmbgwpez/100cc_200pl.jpg
https://s23.postimg.org/qr0qnddij/150cc_200pl.jpg
https://s23.postimg.org/fq5licl9n/100cc_225pl.jpg
https://s23.postimg.org/5vegc4hbf/150cc_225pl.jpg

[VoskCoin]

Fellow miners,

this is the build I use with my Nvidia 1000 series rigs.  I am providing it to the community 100% free, with no fees (from me at least):
(Claymore's miner still has his fee if you mine ETH or ETC; EWBF defaults to 0 fee: which you can easily change if you want to; EWBF 0.3.3b. is awesome)

Please Note:
I don't have any Maxwell cards, so I didn't test them.  According to Nvidia, the driver should support them as well.  I'm not sure if nvOC (as is) can support Maxwell Cards.

nvOC is a customized Ubuntu 16.04 build with Nvidia individual card OC and individual card powerlimit support, manual fan support, auto launching on boot, and a single easy to configure Bash Script (oneBash) which can be configured from a windows pc using wordpad.

nvOC is easy-to-use and supports mining (with the newest oneBash):

ZEC   ZCL   FTC   LBC   MUSIC   ETC   EXP   ETH   DCR   PASC
DUAL_ETC_DCR       DUAL_ETC_PASC        DUAL_ETC_LBC         DUAL_ETC_SC
DUAL_EXP_DCR       DUAL_EXP_PASC        DUAL_EXP_LBC         DUAL_EXP_SC
DUAL_ETH_DCR       DUAL_ETH_PASC        DUAL_ETH_LBC        DUAL_ETH_SC
DUAL_MUSIC_DCR   DUAL_MUSIC_PASC    DUAL_MUSIC_LBC    DUAL_MUSIC_SC

the newest oneBash Link


NOTE THE LAST VERSION OF ONEBASH WITH DUAL SC PRESETS WAS INCORRECTLY BUILT ( THANKS Roes500 FOR NOTICING ) IF YOU ARE MINING:

DUAL_ETH_SC
DUAL_EXP_SC
DUAL_ETC_SC

ENSURE THAT YOU UPDATE TO THE NEWEST ONEBASH (FIXED MAY-23rd )

nvOC uses EWBF, Claymore, sgminer, and ccminer (both tpruvot and sp-hash) and plusCPU uses cpuminer-opt;
if you want an additional algorithm or mining client post here or pm me the details and I will add it to the next version

DEMO VIDEO Link

Phil's rig DEMO VIDEO Link

Example Rig Link; 1.02$/hash (hash in sol/s) or less

amdOC_Beta_v0010 Link

Current Version: v0014

AS OF MAY 22nd: All images include plusCPU setting to enable cpuminer-opt to mine XMR on the side

Change Log:
v0014
  NOTE: this version is for USB keys only
  added individual card powerlimits
  added manual fan control
  added Guake terminal (press f12 for a standard terminal)
  fixed ccminer libcudart.so.8.0 error
  removed build error logs causing system error messages
  oneBash changes:
    moved oneBash to the Windows partition (you can now configure oneBash on the computer you image the USB key with)

v0013
  dummy plug is no longer required
  added ccminer (both tpruvot and sp-hash)
  added CUDA 8.0
  updated Claymore to 9.0
  installed Ubuntu updates
  oneBash changes:
    moved pool addresses and ports to the top section
    added individual card cc and mc OC
    added 1050 switch (use if you have 1050's in your rig)
    added LBC, DUAL_ETC_PASC  DUAL_ETC_LBC  DUAL_ETH_PASC  DUAL_ETH_LBC

v0012 (initial release)

fully supported motherboard links:

ASRock H81 PRO BTC Link

BIOSTAR TB85 Link

MSI Z270-A PRO (in stock, 6x gpu) Link

GIGABYTE GA-B250M-Gaming 3 (in stock, 4x gpu) Link

BIOSTAR TB250-BTC Link

ASUS Z270-F GAMING (in stock, 7x gpu (only 6x OC)) Link

MSI Z170A GAMING M5 (in stock, 7x gpu (only 6x OC)) Link

ASUS PRIME Z270-A (in stock, 7x gpu (only 6x OC)) Link


How to use:

If you don't have an imaging program already download HDDRawCopy (Link)


for an ASRock H81 PRO BTC or BIOSTAR TB85 use this image

If you are using an ASRock H81 PRO BTC or BIOSTAR TB85; either should work with without any changes to the bios settings. The SHA256 hash (for the zip) is:

46e53e99edb2bfa654ebd1f2d1fed53df97e41756e88898da3536590981050d8

for a MSI Z270-A PRO use this image

If you are using an MSI Z270-A PRO; ensure you enable Above 4G memory option in the bios before connecting the nvOC USB.  The SHA256 hash (for the zip) is:

b614211fabb3d94548af0d8046d96fb76336b2474db4da6becc8281c839a0860

for a GIGABYTE GA-B250M-Gaming 3 use this image

If you are using a GIGABYTE GA-B250M-Gaming 3; ensure the Audio Controller is disabled in the bios.  The SHA256 hash (for the zip) is:

5badbc7d2fbb04f245afab7de5285bfbb3f4e70f93462808ed7f79c317eefd12

for a BIOSTAR TB250-BTC use this image

If you are using a BIOSTAR TB250-BTC; ensure Miner Mode is enabled in the bios.  Also ensure Max TOLUD is set to 3.5 GB in the bios.  The SHA256 hash (for the zip) is:

14f11d32cd44837e7a46d87eb2369aaf62fb5d2d7e18a1b2136615496ab828aa

for an ASUS Z270-F GAMING use this image

If you are using an ASUS Z270-F GAMING; ensure 'Above 4G Decoding' is enabled in the bios.  Also ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.  Finally, ensure you 'Clear Secure Boot Keys' in the bios.  The SHA256 hash (for the zip) is:

213e8e1ee423cdfbac786a863394a654b1fe83a4a8138cf5ceb63ab5223bb6f4

for an MSI Z170-A GAMING M5 use this image
Note this mobo requires a skylake CPU: I recommend the G4400
It also requires you to flash the bios

If you are using an MSI Z170-A GAMING M5; ensure 'Above 4G Decoding' is enabled in the bios.  Also download, unzip and copy to a usb key ( the 2016-12-19 Version 1.D ) Bios and follow instructions to flash the bios.  The SHA256 hash (for the zip) is:

ce540d58ce5f9eb75a361d8564f5b5582db454c754f9b9b3027e08a6663a9c66

for an ASUS PRIME Z270-A  use this image

If you are using an ASUS PRIME Z270-A; ensure 'Above 4G Decoding' is enabled in the bios.  Also ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.  Finally, ensure you 'Clear Secure Boot Keys' in the bios.  The SHA256 hash (for the zip) is:

67b57b2aca9bf181f7fb4c76333d5d85b3837193a936c3106e34e0736c7aa943

for an ASUS PRIME Z270-A with 1x m2_to_pcie_adapter (total 8x cards: note all OC with this image) use this image
Ensure that you use the m2 adapter in the slot near the CPU

If you are using an ASUS PRIME Z270-A; ensure 'Above 4G Decoding' is enabled in the bios.  Also ensure PTP aware OS: is set to 'Not PTP Aware' in the bios.  Finally, ensure you 'Clear Secure Boot Keys' in the bios.  The SHA256 hash (for the zip) is:

58da134925d64f01ecd9a9cbbd803936a01361a38ee23770542215815eaea690

ENSURE THAT YOU unzip the image BEFORE YOU IMAGE YOUR USB  


Use HDDRawCopy to image the extracted img file to the 16gb or larger usb ( see this guide for an HDDRawCopy walkthru )

Image to 16gb or larger USB key.  You may have trouble setting the powerlimit if the USB key you use is slow.  You can use any 16gb or larger USB key; however, I highly recommend using the lexar drive as it was one of the fastest USB keys I tested and is less than $8.  

I tested several different USB keys; I recommend using this $8 one:
https://www.amazon.com/Lexar-JumpDrive-16GB-Flash-Drive/dp/B00S5V5PMY

NOTE: You only need to configure the oneBash file in the Windows Partition.  If you don't have a text editor with syntax highlighting: open it with wordpad.  I recommend downloading atom if you don't have a text editor with syntax highlighting .

set COIN, POWERLIMIT, CORE AND MEMORY OC, INDIVIDUAL_CLOCKS, MANUAL_FAN, YOUR ADDRESSES and WORKERS / change POOL and PORT for each COIN if desired

This is the settings portion of oneBash:



direct link to image:
oneBash settings section

When you are done configuring oneBash ensure that you save, then eject the USB.

Attach the USB key to your rig and power it on.

NOTE: first boot will take longer to start mining as oneBash must be converted

All files are in the nvOC folder Link.

nvOC uses the 378.13 Driver.

the root password for nvOC is:

    miner1

Known Limitations and Issues:

If powerlimit isn't setting after editing oneBash on your rig; stop CPU mining ( press f12 to open guake terminal then press ctrl + c to stop the process ) and close the GPU mining process.  Reopen gnome terminal to relaunch oneBash.

v0014 will not support OC on all motherboards without modifications to the xorg.conf file.  I don't have every motherboard so I can't test all of them.  If you have a problem or notice a bug / deficiency please post here or pm me with a description of the problem and the complete specs of your rig.  I can also make you an image that will fully support your motherboard; if I have your motherboard.

Some individual cards may need lower clocks, but in general these are stable OC settings and the powerlimits I use; however, my power is expensive: so you may want to use a higher powerlimit if you have cheap power.

EVGA 1080ti SC              cc 150  mc 900  powerlimit 200
EVGA 1080ti FE              cc 150  mc 900  powerlimit 200
ZOTAC mini 1070's         cc 200  mc 450  powerlimit 125
EVGA FTW 1070's           cc 100  mc 600  powerlimit 118
ZOTAC amp 1060 6gb's   cc 150  mc 600  powerlimit 100
EVGA 1060 SC 6gb's       cc 100  mc 600  powerlimit 100
EVGA 1060 SC 3gb's       cc 100  mc 350  powerlimit 75
EVGA 1050ti SC 4gb's     cc 150  mc 350  powerlimit 53

Depending on the algorithm; you may be able to overclock significantly more.  If your miner crashes at all, it is probably because your cc or mc OC is too high.  

IMO it is easier to start with a lower OC and walk up the OC until it becomes unstable, than to start at the max and walk it down to stability.

If you find nvOC helpful and would like me to expand it; please let me know.  I will make requested changes over time as I am available to.

I am planning to use this board
https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975&cm_re=Z270P-_-13-128-975-_-Product
I would like to use your software, has anyone setup their rig with this board and your software before? I do not see it on the supported OP

What is the opinion on SSD vs USB drive, it makes sense to use a usb for the HD if its fully functional for this setup, however if an SSD is needed that is not an issue however given the choice why not use USB?

[VoskCoin]

I am planning to use this board
https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975&cm_re=Z270P-_-13-128-975-_-Product
I would like to use your software, has anyone setup their rig with this board and your software before? I do not see it on the supported OP

What is the opinion on SSD vs USB drive, it makes sense to use a usb for the HD if its fully functional for this setup, however if an SSD is needed that is not an issue however given the choice why not use USB?

I will order one of these and make an image for it:  https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975

I understand why members are hesitant to try a USB key, cheap USBs are usually terrible: and fast ones are usually expensive. 

The Lexar drives I recommend are both fast and cheap.  Other members have requested I fully support SSDs again; so I am going to re-add full support for them in a later version. 

Currently you will either need to use manual intervention or make some changes to the system or bash files when using an ssd.

Personally I use all Lexar 16gb USBs with my rigs; except one has a Lexar 32gb I got to test.  I think they are the better choice over a more expensive ssd.

This is my reasoning:

The 16gb Lexar's I recommend are very fast (watch one of the nvOC demo videos if you don't believe me)

are very cheap: $8

are easy to attach to image then remove and reattach to a rig

vs a regular SSD or HDD allow you to use at least one less cable on your rig.

Finally using a usb key allows users to try nvOC without needing to install over their previous OS (no commitment needed).

Although one could use a sata to usb adapter with an ssd, or an type of usb ssd / adapter (there are a lot)  and it would match all the advantages other than cost.  I recommend spending $8 on a Lexar 16gb and seeing if it is fast enough for you; if it is (and most likely it is) then you just saved ~$30 per rig.

I would really appreciate that, I just ordered 2x boards to setup Nvidia rigs with

Thank you for the detailed explanation, I am looking forward to trying your software

I will be honest however, I do not have experience using Linux, would you recommend against using your nvOC OS because of that or is there a particular guide/link you'd recommend?

[VoskCoin]

I am planning to use this board
https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975&cm_re=Z270P-_-13-128-975-_-Product
I would like to use your software, has anyone setup their rig with this board and your software before? I do not see it on the supported OP

What is the opinion on SSD vs USB drive, it makes sense to use a usb for the HD if its fully functional for this setup, however if an SSD is needed that is not an issue however given the choice why not use USB?

I will order one of these and make an image for it:  https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975

I understand why members are hesitant to try a USB key, cheap USBs are usually terrible: and fast ones are usually expensive. 

The Lexar drives I recommend are both fast and cheap.  Other members have requested I fully support SSDs again; so I am going to re-add full support for them in a later version. 

Currently you will either need to use manual intervention or make some changes to the system or bash files when using an ssd.

Personally I use all Lexar 16gb USBs with my rigs; except one has a Lexar 32gb I got to test.  I think they are the better choice over a more expensive ssd.

This is my reasoning:

The 16gb Lexar's I recommend are very fast (watch one of the nvOC demo videos if you don't believe me)

are very cheap: $8

are easy to attach to image then remove and reattach to a rig

vs a regular SSD or HDD allow you to use at least one less cable on your rig.

Finally using a usb key allows users to try nvOC without needing to install over their previous OS (no commitment needed).

Although one could use a sata to usb adapter with an ssd, or an type of usb ssd / adapter (there are a lot)  and it would match all the advantages other than cost.  I recommend spending $8 on a Lexar 16gb and seeing if it is fast enough for you; if it is (and most likely it is) then you just saved ~$30 per rig.

I would really appreciate that, I just ordered 2x boards to setup Nvidia rigs with

Thank you for the detailed explanation, I am looking forward to trying your software

I will be honest however, I do not have experience using Linux, would you recommend against using your nvOC OS because of that or is there a particular guide/link you'd recommend?

Watch the demo videos I made.  Configuring oneBash will probably be the hardest part, but I think you will be able to do it.  If you have questions, I should be able to answer them.

Also I am reasonably sure that if an ssd is imaged while connected to the build pc with a USB-to-sata adapter and then attached to a rig via the usb-to-sata adapter that it will also work fully with all the current nvOC images.  Not sure why I didn't think of this before.

I will order the USB you rec'd and give it a go, especially since you're ordering a https://www.newegg.com/Product/Product.aspx?Item=N82E16813128975&cm_re=Z270P-_-13-128-975-_-Product to create image. I will post video results once I get it operational, I should have all my parts in by the end of next week

[funnyboy027]

In Windows with +150cc, +900mc, 200mv
temperature: 73,
gpu_power_usage: 214,
speed_sps: 671,

[bobers]

Hi, can anyone help?
I have same 4 ASUS 1060 3GB, all OC, but one works slowly then others.

ETH: 05/31/17-02:41:36 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 78.055 Mh/s, Total Shares: 7, Rejected: 0, Time: 00:06
ETH: GPU0 17.358 Mh/s, GPU1 20.249 Mh/s, GPU2 20.263 Mh/s, GPU3 20.185 Mh/s
GPU0 t=47C fan=75%, GPU1 t=52C fan=75%, GPU2 t=51C fan=75%, GPU3 t=48C fan=75%

[LTCbusiness]

So here is my lspci

m1@m1-desktop:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)


and here is my xorg.conf, as I see the busid is matched. I tried to change to value, for example, from 01:00:0 to 01:00.0, but it did not work.


# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 381.09  (buildd@lgw01-19)  Sat Apr  8 10:34:02 UTC 2017

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 378.13  (buildmeister@swio-display-x86-rhel47-05)  Tue Feb  7 19:37:00 PST 2017

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 1920 0
    Screen      2  "Screen2" 3840 0
    Screen      3  "Screen3" 5760 0
    Screen      4  "Screen4" 7680 0
    Screen      5  "Screen5" 9600 0
    Screen      6  "Screen6" 11520 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "HannStar Display Corp HE225DPB"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor4"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor5"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor6"
    VendorName     "Unknown"
    ModelName      "CLB  fit Headless"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:01:00:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:02:00:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:04:00:0"
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:05:00:0"
EndSection

Section "Device"
    Identifier     "Device4"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:06:00:0"
EndSection

Section "Device"
    Identifier     "Device5"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:08:00:0"
EndSection

Section "Device"
    Identifier     "Device6"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1050 Ti"
    BusID          "PCI:09:00:0"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-2"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-1"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen4"
    Device         "Device4"
    Monitor        "Monitor4"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen5"
    Device         "Device5"
    Monitor        "Monitor5"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen6"
    Device         "Device6"
    Monitor        "Monitor6"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

[bobers]

So here is my lspci

m1@m1-desktop:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)

Try to turn off motherbord VGA, HDMI audio. Its helped me on 2th PCs
And i think, you have to reboot PC after xorg changes, just restart miner not helped me.

[bentcrypto]

The image of nvOC is 14.9gb but the two 16gb usb sticks I have tried only have 14.7gb or 14.8gb capacity.
I keep getting errors at the end when using hddrawcopy

  

[citronick]

I have funny situation with my 6 x Zotac 1070 Minis....

doing lspci --- I see 6  x VGA devices

but EWBF mines with only 5 cards

Did I forget to change a setting in onebash for 6 cards?

Motherboard is using MSI Z270-A PRO.

Ran same rig with Win10..... same thing.... EWBF and other miners..... sees only 5 cards but this time Device Manager also sees five cards

[VoskCoin]

The image of nvOC is 14.9gb but the two 16gb usb sticks I have tried only have 14.7gb or 14.8gb capacity.
I keep getting errors at the end when using hddrawcopy

  

What USB sticks are you using? Is it this one https://www.amazon.com/Lexar-JumpDrive-16GB-Flash-Drive/dp/B00S5V5PMY?th=1 ?

[VoskCoin]

The image of nvOC is 14.9gb but the two 16gb usb sticks I have tried only have 14.7gb or 14.8gb capacity.
I keep getting errors at the end when using hddrawcopy  

What USB sticks are you using? Is it this one https://www.amazon.com/Lexar-JumpDrive-16GB-Flash-Drive/dp/B00S5V5PMY?th=1 ?

Yes; there is a link in the OP as well.

I was asking him to see if they did not have the capacity needed with some of the images, would you recommend the 32gb sticks to alleviate this issue / have you tested them? I do not mind spending 4 dollars to delete a possible headache xD

[VoskCoin]

The image of nvOC is 14.9gb but the two 16gb usb sticks I have tried only have 14.7gb or 14.8gb capacity.
I keep getting errors at the end when using hddrawcopy  

What USB sticks are you using? Is it this one https://www.amazon.com/Lexar-JumpDrive-16GB-Flash-Drive/dp/B00S5V5PMY?th=1 ?

Yes; there is a link in the OP as well.

I was asking him to see if they did not have the capacity needed with some of the images, would you recommend the 32gb sticks to alleviate this issue / have you tested them? I do not mind spending 4 dollars to delete a possible headache xD

I am not sure what USB keys bentcrypto is using.  It is unfortunate that most companies market USB keys beyond the actual usable capacity.

The 16gb Lexar USB keys I recommend have a 16.0 gb capacity, any of the nvOC images will fit on one.  

The 32gb version is marginally faster.  The only other reason I can think of to get the 32gb vs the 16gb (while the 16gb is still $8) is if you really like the color orange.

Okay that is great news, and I was contemplating the 64gb because I love green haha xD
I have 2x 16gb on order

[bentcrypto]

The image of nvOC is 14.9gb but the two 16gb usb sticks I have tried only have 14.7gb or 14.8gb capacity.
I keep getting errors at the end when using hddrawcopy

  

What USB sticks are you using? Is it this one https://www.amazon.com/Lexar-JumpDrive-16GB-Flash-Drive/dp/B00S5V5PMY?th=1 ?

No they didn't have the ones that fullzero recommended so I just bought 2 different brands and both are too small, result in errors on hdrawcopy and won't boot nvOC. I'll go and get a 32gb Tomorrow and then have another shot.

 

[Sequoia93]

What do you mean by "(only 6x OC)" for the z170/z270 boards? Can this OS support 7 cards with those boards?

and you say usb key only....does that mean an M.2 drive will not work? what size ssd is required?

edit: removed lazy question