Documentation - NvEZOS

Here wij will voorkant some significant things you should know about NvEZOS functionality spil well spil include a few tutorials. This will be expanded upon ter the future. If you have suggestions for future tutorials/information, please voeling mij at [email protected]

I mention it ter the install instructions, but Ill add it again here. During setup you Voorwaarde set the user you create to login automatically, the reason for this is the nvidia-settings directions used to set the overclock offset values requires a running x session to truss to. By having the user login automatically it provides a persistent environment to run thesis guidelines against insuring overclocking works consistently.

For those of you who know Linux, I’ll provide some insight into how the miners work. Its fairly ordinary indeed, when you waterput te the instruction you want that miner to run, a shell script is saved with the directive you created for that miner. Each miner (1-10) has an associated systemd service which runs each miner script spil a daemon. The miner control area simply stops and disables all of thesis services then enables and starts the one(s) you wish to have running – this also insures the selected service(s) will commence on reboot. All services except the dev miner service are disabled by default. When you begin your very first miner, or klapper zekering all services, the dev miner will be stopped and disabled, only to be re-enabled if you do it by hand. Each miner is also logged to its own loom te /nvezos/logs which is purged every 24hrs. You can access thesis via ssh for extra information if needed.

NvEZOS V1.03+ has reverted to using Ubuntu-Gnome 16.04.Two LTS. This emerges to provide better stability without any loss of functionality. During setup you may notice an “Unexpected Error” that will popup (it can also come up on very first boot) you can klapper proceed or just leave it te the background, it can be securely disregarded – it has to do with one of the dependencies of cuda 8 and some compatibility issues with 16.04.Two.

NvEZOS V1.02+ has reverted to nvidia-375 drivers due to some issues with overclocking on 384 drivers. There is no longer a need to zekering the miner to apply the overclock and the overclock will automatically apply on reboot within 3-4 minutes of utter blast.

When using the multi-mine option, each miner guideline you create needs to have a flag set specifying which GPU it uses. I’ve tested, and yes, you can technically run numerous miners on a single GPU (or all miners on all GPUs), but the spectacle is horrible, Claymore does this through a proprietary system, it is not simply running two miners on the same GPU, but using ingewikkeld task scheduling. What multi-mine permits you to do is use different GPU’s to mine different currencies, so to set it up you would want to set one miner to use say GPU 0 and 1, while another uses GPU Two and Trio, well get into some examples of this te the tutorial below.

EWBF is utterly slow to update the loom (sometimes Ten minutes inbetween updates) due to the buffer and the utterly low amount of loom output. This can cause the EWBF hashrate to be fairly a bit behind spil well spil the loom output. Just keep this ter mind when using EWBF. I’m working to see if there’s a way to address this, but it seems unlikely.\

When setting up the miner instructions, you’ll notice a field for the “Miner Status Page”. This is where you can waterput te a url that linksom to the instrumentenbord pagina for the mining pool associated with the miner. Te previous versions, when you clicked the Pool Status button it would open the instrumentenbord pagina ter an iframe, however, most pools are blocking cross-site iframe linking, so now when clicking the Pool Status button the instrumentenbord pagina will simply open te a fresh tabulator. Keep te mind this only works with single mining, spil it will open the instrumentenbord pagina for the last miner daemon that gets began. Also, this field is entirely optional, if you don’t want to use it, you don’t have to.

You can chose to run the dev miner at any time to help support the NvEZOS project, however, it will never be ran again automatically after the very first boot. If you use the multi-mine feature, when the dev miner is enabled, it will only run on GPU 0 (using the flag -cuda-devices 0), so you can help support NvEZOS while you mine normally on the surplus of your GPU’s. (Just be sure to use the suitable device flags on the surplus of your miner directives – see below)

This seems to be the most confusing part about NvEZOS – setting up the miner directions, so I wished to address this very first, then extra tutorials will be posted down the road.

Very first off, there are numerous ways to setup a miner, but te the end it’s accomplishing the same thing. If you mine via cli te a Windows or Linux OS you are launching the miner with a directive. Whether you use a bat or sh script to do this or just write out a instruction for the miner, it’s the same thing. You’re doing the same thing here, providing the daemon with the guideline to run te order to mine. So let’s get into building the very first miner directive.

The very first part of any miner instruction is the location of the actual miner opstopping, for all default NvEZOS installs this will be spil follows…

So let’s say wij want to begin with something basic, one of the easiest pools to configure, mining eth via ethermine.org

Te this case, wij’ll commence off with the location of the miner /ethminer/cpp-ethereum/build/ethminer/ethminer then add the surplus of the variables they want us to add….

Wij’ll embark with the example they give…

ethminer.exe -farm-recheck 200 -G -S eu1.ethermine.org:4444 -FS us1.ethermine.org:4444 -O Your_Ethereum_Address.RigName

And the guideline wij’ll use…

/ethminer/cpp-ethereum/build/ethminer/ethminer -farm-recheck 200 -U -S eu1.ethermine.org:4444 -FS us1.ethermine.org:4444 -O Your_Ethereum_Address.RigName

Notice the switches, ethminer.exe is switched to the total path to the ethminer (ethminer.exe is windows, linux ethminer has no extension). Wij also switched the -G to -U spil this will use CUDA instead of OPENCL. At this point, you are ready to go, you just need to switch the address and equipment name to your own!

But wait… What if wij want to enable multimining and mine eth on GPU 0-3 and Zen on GPU 4-7…

Let’s embark by building our ZenCash directive. Suprnova, the pool I personally use, provides this example –

miner.exe -server zen.suprnova.cc -user suprnova.1 -pass x -port 3618 -cuda_devices 0 1 Two Three

Now edited to the decent path to ewbf and switching to the keurig GPU’s wij want to use (4-7), wij’ll call this command1 –

/ewbf/miner -server zen.suprnova.cc -user suprnova.1 -pass x -port 3618 -cuda_devices Four Five 6 7

So now wij also need to make our Eth miner only use GPUs 0-3, wij can do this using the -cuda-devices flag. (Almost the same spil with ewbf, but with – instead of _), wij’ll call this command2 –

/ethminer/cpp-ethereum/build/ethminer/ethminer -farm-recheck 200 -U -S eu1.ethermine.org:4444 -FS us1.ethermine.org:4444 -O Your_Ethereum_Address.RigName -cuda-devices 0 1 Two Trio

So now wij have miner 1 setup with command1 and miner Two setup with the command2. Now you can enable multi-mine, check both miners, and kasstuk begin. Both miners should commence running and hashrates should show up shortly on the monitoring pagina. You can also get more informatie by rolling inbetween the logs on the monitoring pagina.

A tutorial for Claymore will be coming soon. I personally dont have a loterijlot of practice with Claymore, so if you do, feel free to write something up and send it to mij!

Related movie: Como ganar dinero con Adfly | 630$ cobrados