Took a long time to respond today: because I have been busy working. Wink

Quote from: UberDaemon on June 27, 2017, 01:36:14 AM

Quote from: car1999 on June 27, 2017, 01:11:26 AM

Hi fullzero,
I followed this guild(https://bitcointalk.org/index.php?topic=1854250.msg19503300#msg19503300) to use SSH, it works well.
But I don't know how to exit the screen session and restart it. So I googled and found a stackoverflow thread https://stackoverflow.com/questions/1509677/kill-detached-screen-session, there are multiple methods, could you update your "official" way to the origin guide?

thanks.

To detach from a screen (i.e. you want to close the SSH connection while mining continues afterwards) it's

Code:

CTRL + a + d

To reattach to a screen (resume connection) it's

Code:

screen -x [name you gave the screen session] # once you've typed 3-4 characters hit the tab key and it will fill out the rest and save you some typing

If you can't remember what you named the session use:

Code:

screen -ls

If you're new to screen you may not know you can open a 2nd shell and switch back and forth (i.e. your miner is running on one shell and you open a 2nd to run nvidia-smi):

once in screen you create a 2nd shell (or 3rd, 4th, etc) with

Code:

CTRL + a + c

To switch back and forth use:

Code:

CTRL + a + n

I will update that guide more soon; Thanks for the detailed explanation UberDaemon

Quote from: Funkyanimal on June 27, 2017, 03:46:59 AM

I setup Groestcoin (GRS) in the onebash file and used ccminer using the groestl algo. Is SGccminer the best miner to use? I see most pools recommend sgh-sgminer and was hoping someone could enlighten me if that is the same thing I have specified. I'm currently mining GRS on miningpoolhub. Thanks in advance, I am a a little new to the alt coin arena.

I haven't tried GRS; I will add it to the list.

Quote from: tempgoga on June 27, 2017, 08:35:53 AM

Hey fullzero, first i wanted to thank you for all your work, nvOC is pretty great, but i do have some questions,

i recently built a 7 x gigabyte gtx 1070 FE mining rig, running on an asus prime z270-a and i've encountered some problems,

First problem is with Teamviewer, on nvOC v15 i installed teamviewer and added it to startup applications and it worked just fine, but with nvOC v16 i'm having problems, enabling it in oneBash doesn't allow me to connect by itself, after the script enables the service.daemon i have to manually click the Teamviewer icon on the sidebar to be able to connect to the rig, and i want teamviewer to go live as soon as the rig is up.

adding teamviewer to startup application doesn't work on nvOC v16 since startup applications loads teamviewer and oneBash at the same time roughly, the script hasnt had the chance to initiate the teamviewer service.daemon and all you get is an error message telling you that the service.daemon isnt running when it attempts to open teamviewer..

Second problem, and this might actually be a problem with claymore, but commands like "-tt" and "-ttdcr" and most importantly "-tstop" dont work, i have no temp control other then setting the fans and hoping for the best, is there a way for me to at least shut everything down in case things overheat?

Last problem is that when i dual mine sometimes the whole system freezes, or at least slows down to a crawl, with nvOC v15 when this happened the hashrate would drop to 0 for GPU 0, GPUs 1-5 would be at 50% hashrate and GPU 6 would be at 25% hashrate, i'm not sure if this is due to me undervolting/overclocking too much but this only happens in dual mining, i got no error messages in the logs... i also cant find the logs in v16?

i run the GPUs at a pl of 120 and clocks of 200/1800, this works fine when i only mine ETH but i'm having problems in dual mining ETH/SIA

Thanks again..

I would launch teamviewer from oneBash rather than adding it to startup applications; after the daemon switch implementation,

Some of the claymore cmds only work with AMD; you will have to talk to Claymore about that. The Nvidia driver will (barring something epically failing) should shutdown the cards when temp flag is hit.

I removed the logs in v0016 as they were decreasing stability; you can re enable them by removing this argument from the launch line:

Code:

-dbg -1

When dual mining you need Alot more power. 120 watts is probably not enough for 1070s; this is most likely resulting in the soft crashes you are seeing.

Quote from: tempgoga on June 27, 2017, 12:27:36 PM

Quote from: Nexillus on June 27, 2017, 11:43:04 AM

Quote from: Tasbi on June 27, 2017, 09:02:33 AM

Hello guys,

I read this, they say that can increase performance by 15 to 30% on a gtx 1060....

https://www.reddit.com/r/EtherMining/comments/6jjhob/ethereum_code_optimized_for_some_nvidian_cards/

https://github.com/Genoil/cpp-ethereum/pull/228#issuecomment-310918630

Is it true, anyone tried yet?

I researched into it and from what people are reporting it is true. 1060 gets the best increase upwards of 15-30% (like you saw) Average hash from what people were reprtong was about 29-31MH/s for a 1060. while 1070 gets about 3-5% and 1080TI gets 2%

Thats insane.. 30Mh/s from a 1060? figures after i just bought 7 1070s, 1060 are considerably cheaper then 1070 in my country..

Quote from: OverEasy on June 27, 2017, 12:42:29 PM

Sounds like we need to get Genoil implemented into nvOC

While this implementation can get crazy high hashrates; it is not stable with them; It is capable of better hashrates than claymore and has no fee. You will be able to use it in v0017 shortly.

Quote from: f00ch0w on June 27, 2017, 01:25:00 PM

Any way to add additional parameters for EWBF? Like --api so I can enable it?

at the end of the worker: leave a space then enter the argument:

for example if my worker is:

Code:

ZEC_WORKER="nvOC"

I would change it to:

Code:

ZEC_WORKER="nvOC --api"

Quote from: Emony-Dax on June 27, 2017, 01:29:32 PM

Quote from: fullzero on June 26, 2017, 11:48:52 PM

Quote from: Emony-Dax on June 26, 2017, 06:36:08 PM

I am at my wits end trying to get this to boot. I have managed to get it to boot a couple of times, but each time it does it freezes after failing to connect to EWBF(as I currently do not have a connection set up, I need to make some changes to make my wifi dongle work but cannot do this due to the issues) - following restarting it results in a kernel error. About 95% of the time after reflashing to attempt again it doesn't boot and I just get a blank screen after it attempts to boot into Ubuntu (no loading screen).

This happens with both OC and non-OC. Mostly attempting to get this to work on default settings moving forward.

I am using a MSI z170a SLI and 2x GTX 1060's (6gb) with a DVI monitor. Using a SanDisk Extreme 64GB USB stick.
Above 4G decoding is enabled and BIOS has been flashed to the latest 3.A version (issue occured before the flash too).

Has anyone encountered similar problems?

When Above 4G decoding is enabled it is normal to see a black screen while ubuntu is loading.

Maybe this will work:

Ensure the monitor is connected to the primary GPU ( the one in the 16x slot closest to the CPU )

Disconnect the USB or SSD/HHD from the rig.

Fully power off everything: including the PSU.

Press the power button several times to clear any remaining power in the mobo.

Turn the PSU powerswitch back to | "on".

power on (without the USB attached)

See if the bios posts; if you get nothing in 20 seconds; press ctrl + alt + del repeatedly until the system reboots.

Wait and see if the bios posts.

If the bios posts attach the USB key to a USB 2.0 port and press ctrl + alt + delete.

if it boots; stop the mining process before it starts mining:

then go to the top left and click the ubuntu button

type u

and click on software updater

run updates

reboot

Let me know if this works.

Thank you for the help on this.

I have now connected this to ethernet.

I've managed to get it to boot without 4G Encoding enabled, though the mining process won't start. Following this I saw your post, I re-enabled 4G Encoding and tried the steps listed.

BIOS posts, but the black screen is present after and it doesn't boot no matter how long I leave it on. Either that or it is not outputting display, but it seems to be the former since the mining process doesn't start (GPU fans don't go to 75%).

EDIT: I have got it working!!

I found that Newbie2017 encountered a similar issue.

I disabled onboard audio, switched PCI-E mode to Gen 1, and enabled Windows 10/8.1 support in the boot settings.

EDIT2: Froze up after 5 minutes of the miner running. GPU0 temp seemed to get quite high(80C) - might be this? Or perhaps that the USB 3.0 key was in a 2.0 port which is too slow for the OS?

EDIT3: Tried closing the mining process and installing updates, but it froze when installing updates.

I'm not sure exactly what is going wrong. I high recommend getting one of the fully supported motherboards on the OP (the 270 chipset is the best IMO) ; the z170 chipset is terrible for mining.

Quote from: damNmad on June 27, 2017, 02:30:11 PM

BTW I have another question, currently in my bash file I have only added 1 pool, is there any way to add more pools (for eg ethermine has 2 eu pools, would like to add backup pool to send more shares)?

You can use the Claymore implementation for this for now; I will make my own eventually: it is on the list.

Quote from: OverEasy on June 27, 2017, 04:00:51 PM

Quote from: fullzero on June 26, 2017, 11:43:36 PM

Quote from: OverEasy on June 26, 2017, 07:22:00 PM

Loving this! What's the trick for RDP? I set it up on the Linux side but cannot connect RDP from my Windows machine.
Thanks

try this guide:

https://www.lifewire.com/setup-ubuntu-remote-desktop-4129666

Let me know if this guide is good or not.

I followed the guide but still no luck. So far the only thing that has worked has been TeamViewer but its so slow its not really usable.
Today I installed Xrdp and managed to get a desktop but not the running one! A completely different one.

I just can't understand why I can't make a simple Windows RDP connection to the nvOC Ubuntu box on my local network. The research and trail and error continues I guess...

I will add making an RDP guide to the list.

Quote from: xleejohnx on June 27, 2017, 06:31:06 PM

Quote from: ATCkit on June 27, 2017, 04:54:19 PM

So I've imaged my USB, set up onebash & plugged the USB into my rig. The monitor immediately showed " grub rescue".

Questions:
1. I assume this the process of converting the file from windows to linux- correct?

2. If so, this process has been running for 30 minutes. How long should it take?

This shouldn't happen.
Try flashing the USB again

xleejohnx is right; it should never take more than 7-8 minutes.

Did you forget to extract the image from the zip before imaging?