I think it's best that you first try out nvOC default miners and compare it with others or whattomine reported hashrates.
Then start playing with OC, power limit and changing miners in 0miner.

Hahaha don't be sorry bruv, I don't think any one will get offended by your name, i was just expressing it in a funny way

Yep, you only asked for explanation, but I have answered in general perspective.


Can you please give an example, illustrating the above statement, sorry i didn't quite get that to be honest.

So, this as well just a general explanation (not just for you but for any new miners to understand) of how actually 1bash, 0miner or 3main works.

We add all the coin details and they are stored/attached to variables.

We call those variables in 3main or 0miner and shape them up according to how pool expects.

We follow the same procedure for every single coin.

Feel free to ask any further questions you have.

I use it in dual-boot with windows with no kind of issue, you have to burn the old non-shrinked image so that it will not auto-expand. If you have not installed windows yet, burn nvOC first, then install windows on the second partition, then restore grub in the mbr of the drive and from nvOC let grub detect the windows install as a second boot option. As an alternative you can sue windows boot manager do manage dual-booting, i.e. leaving windows boot loader in the mbr and adding nvOC as BCD record.

If you already have windows installed, just dd the main partition only from the image (you need to mount the raw disk as loopback device and dd the rightdev/loopbackX to unallocated ssd space), then create missing boot records in your favorite bootloader.

Another viable option would be to just installa a standard dual boot from ubuntu live media, install all needed packages and clone the nvOC git repo in your ~ directory.

It all depends on your noob level :-) (but please, avoid buying a second ssd for that, in the worst case you can enable raid in your motherboard controller such that you see two separate full drives)

It can be done, however it takes a lot of steps and advanced user to do it. This is beyond the simplicity of nvoc's plug-n-play structure and general support from the community. We can't support custom solutions.

If it's just to evaluate nvoc the easiest way is to burn it on USB stick and try if it performs well for you. If it does, consider installing it on dedicated SSD. Otherwise, what's the point of dual booting on dedicated mining rig that will mine 24/7?

If you still want to dual boot (let's say you have some miner that works on windows only), the easiest solution is to install nvOC first, then create new partition and install Windows on it and update grub bootloader to list windows as well. Installing nvoc as secondary OS on SSD that already has Windows it's more complicated.

The other options listed, like cloning nvoc from git on freshly installed Ubuntu won't work properly as there are other manually tweaked settings to Ubuntu (e.g. cuda environment variable, autostart, auto-update settings...) and extra packages installed (cuda, nvidia drivers, compilers...) that are not included on git.

I am not aware of raid level that lets you split hdd to see it as two separate hard drives. Usually raid is used for mirroring and redundancy and not all motherboards have raid controller built in.

Didn´t work because it puts the "\" into the address like this
and that fails because the pool is not expecting to see the "\" in there. It only expects to see the "+" expression in between the etnaddress and the workername.

Am a newbie to mining and setting up my first rig.  Have an extensive Windows background.  Have zero Linux background (except for the immersion course I'm in the middle of trying to get nvOC v2.0 set up and running ).

I got nvOC up and running but my issue is, somewhere along the way, the LAN controller ceased being recognized.

My setup:

• Attempting a 6-card build with all 1080ti's, largely following Vosk's "How to Build a 6x 1080 TI Mining Rig with ATX & Server PSU's" (https://www.youtube.com/watch?v=2MxNVySpbcw)
• Motherboard = Gigabyte Z270P-D3
• PSU (to power risers) = EVGA Supernova 650 P2
• PSU (to power cards) = Bitmain APW3++
• Harddrive = Lexar 32G USB 3.0 memory stick

I'm initially working to get one card set up and running.  It is plugged into a riser that is connected to the primary PCI slot on the mobo, both of which (riser and card) are powered by the EVGA PSU (once I get one card running I'll work up to all six cards and then power the risers solely with the EVGA and the cards with the Bitmain).  I have the most current BIOS for the mobo installed, 1bash is configured to mine SMART and I can boot & have the miner software functioning.  But my current issue is that the LAN controller is not visible to the OS.

I've had fits and starts thru this process, re-imaging the USB probably 4 or 5 times, for various things I hadn't done correctly (e.g., hadn't updated the BIOS before booting, had plugged my monitor into the mobo HDMI instead of the cards's HDMI and dealt with Xorg issues, etc.).  I know that at one point, the LAN controller was working (green light flashing on controller, which BTW, is a Realtek® GbE LAN chip (10/100/1000 Mbit))-- I'm just not sure when it quit working to be able to exactly determine what I might have changed that caused the issue.

Diagnostics & Steps I've Taken To Address

• Re-imaged nvOC
• Reset CMOS (including pulling mobo battery for about 30 minutes)
• ifconfig -a only shows a "lo" entry, no WLAN
• sudo lshw -c network flashes "PCI (sysfs)" real quickly and then flashes "USB" real quickly and then returns to the command prompt
• And yes, I have tried plugging in an ethernet cable that was live and working in another computer sitting right next to my rig

I guess the issue could be a fried controller, but this is a brand new mobo.  The only other thing I did differently at one point was change the mouse I was using from a USB mouse to an older wireless mouse where the wireless receiver plugs into the light green mouse port on the back of the mobo instead of being a USB mouse.  But I've re-imaged, reset CMOS, etc. since then and even went without using a mouse on a couple of attempts to see if that had caused some issue.

Anyway, I would greatly appreciate any assistance and guidance the Community might have to offer.

Thank you!

When I run that command, it flashes "PCI (sysfs)" real quickly & disappears and then flashes "USB" real quickly & disappears and then returns to the command prompt of m1@m1-sesktop:~$

Yes, I'm using Guake! terminal.

And to your question about running lspci -nnk | grep -iA2 eth, that returns nothing; it just returns to a command prompt and sudo catetc/network/interfaces yields:

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

Will head to Discord

You're right, as I said it depends on how much a noob he feels, but if he really need dual-booting I had pleasure in giving him some hints. As you said, I think the quickest way to do it is the first option, nvOC first then windows. About the RAID, I remember that all my old intel mobo's which have onboard RAID controllers available, all worked the same way and would allow you to create mirrored/striped RAID volumes across arbitrary disks portions shaping what Intel called a "Matrix", even if you choose to do a full raid0 or full raid1 across two disks you will see a virtual disk (a "vector" of the matrix) in boot menu and os instead of the two real one. Maybe it wouldn't allow to create "scalar" volumes, i.e. non-RAID volumes from a single disk.