Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 4. (Read 418247 times)

Updated nvOC 3.0-stable Gminer to 1.25 with Cuckaroo29 and Cuckoo support.

Updated  1bash.template and 0miner to support Grincoin (GRIN) and Aeternity (AE).

Update your nvOC with:

Edit and add new arguments from 1bash.template to your 1bash. (Changes shown in the link above)

Please let us know if there was any problems here or in GitHub issues

hashrate stable. I'il try what you say.

If the hashrate is still stable despite the warnings, just lower the warning threshold in 1bash.

Fri Jan 25 07:07:21 MST 2019 - [WARNING] - GPU0 under 75% threshold - UTILIZATION: 0%
Fri Jan 25 07:07:22 MST 2019 - [WARNING] - GPU1 under 75% threshold - UTILIZATION: 0%
Fri Jan 25 07:07:22 MST 2019 - [WARNING] - GPU2 under 75% threshold - UTILIZATION: 0%

Thu Jan 24 14:03:10 MST 2019 - [WARNING] - GPU0 under 75% threshold - UTILIZATION: 72%
Thu Jan 24 16:57:42 MST 2019 - [WARNING] - GPU0 under 75% threshold - UTILIZATION: 71%
Thu Jan 24 17:04:04 MST 2019 - [WARNING] - GPU0 under 75% threshold - UTILIZATION: 70%

What is the cause of this problem.
How can I fix.

I would like to underline that you basically have various ways of testing the next beta, pick that one you are more comfortable with:

• by reimaging the drive: use a stable official image of your choice, edit firstboot.json selecting "3.1-dev" branch in place of "release", add a new 1bash from the template ont the [urlhttps://github.com/papampi/nvOC_by_fullzero_Community_Release/tree/3.1-dev]github 3.1-dev repo[/url] and go
  
• by firstboot re-run: this will only work on official nvoc images, basically this has the very same effect as the first point here but you won0t need to reimage or detach the drive from the rig, just edit the same files (firstboot.json and 1bash in the FAT partition), switch gnome-terminal profile to "firstboot" (you should have this already on official recent images) and reboot.
  
• by cloning from git: you can get some general instruction about this in the github wiki, this will allow you to quickly switch back to the stable setup where you were running before

I will now report here some hints for 3.1 beta testers I already posted some days ago in the discord channel that will also let you get a preview of what has been worked on in the past few months. Please, don't care any technical detail below if you just love the "easy-to-use" nature of nvOC, you will not be required to know about such things to get nvOC up and running when this becomes stable.

- Foreman monitoring integration: here is just something new, so by definition, no regressions are expected on this

- Selective GPU disable: this is totally new also, but has been worked on for a while and no regressions are expected when you don't select any specific gpu set

- Tempcontrol: its behavior has been changed in order to let it run regularly for other gpus during the grace period of a failed single one. Please note that by its parallel construction if a gpu stops responding for more than an entire loop period you could see more than an alert about the same gpu which is not responding. Just let it go and report if you ever see any patterns like this: thread:1->GPU1->ko | thread:2->GPU1->ko | thread:1->GPU1->ok | thread:2->GPU1-> still ko, reboot

- Pluggable miners: all miners which have been ported to PM has been removed from the legacy places to avoid confusion, there may be some newer versions that have been upgraded in the stable branch and not yet on the beta branch, report if any. You are also invited to try updating on your own meanwhile to see if everything works as expected with the updated/added miner. I'm not sure if you are already familiar wth our new PM approach, but if you ever had the necessity or the wish of adding a new miner for a new algo to nvOC you will be quite happy to see that after "a bit" of rework you should now be able to achieve this with no edits to nvOC scripts of code.

Scheduled mining added to 3.1-dev beta testing.

You can check and use nnvOC setup from a git clone to test/use 3.1-dev or wait for next stable release.

Good to know there is a problem with Windows 8.1.  I only tested Windows 10. 

Sometimes on any OS after imaging (with any image) , mounting will not occur correctly.  It is always a good idea to disconnect and reattach a USB if it fails to mount after imaging. 

Also, a USB key can sometimes become too hot after imaging and will not work correctly while hot, but will work normally after it has cooled down. Some USB keys models are more likely than others to have this problem.

That would be absolutely amazing, thank you for all your hard work!

Hi Fullzero,

Thank you for your clarification.

After trying many times , there are no other partition show up on Win8.1 for me.

But it works fine on Win10 and already start mining on my testing rig.

Thank you.

Good to know there is a problem with my setup guide.  Please let me know if this helps or not:

Depending on how many storage devices your windows computer has the partition you are looking will be recognized as a different letter drive

Most likely it will be Local Disk (E:)

Open file explorer (type file in the search field at the left of the Windows taskbar)

On the left you should see:  This PC

If it is not expanded left click it to expand

Start with Local Disk (E:), left click it and see if there is a file named: "put your 0rig here"

When you find the correct Disk, login to your openrig.net account, open Rig List and look at the right hand side of your rigs

Ensure that you are not using Firefox.  There is a bug that will prevent downloads from triggering

You will see a 0rig button for each rig you have created

Click the 0rig button for the rig you are imaging

A download should occur without a prompt

Open your downloads folder, copy the 0rig file to the correct Disk with the file named: "put your 0rig here"

Eject the disk and attach it to your rig

Hi mate,

Nice to see you back to coding for miners again.

Will test and report as soon as I can.

Will try to add it to next release,
In the mean time you can check this github pull request to get some ideas if you want to add it yourself

Hi Fullzero,

Please kindly recommend how to copy that the 0rig file to usb key on Windows.

Cos I read that the Setup Guide and stuck on this step...
"when using Windows; after imaging is complete, you will be prompted to format the primary partition of the newly imaged usb. Close or ignore this window, this occurs because windows does not support the Ext4 filesystem."

"when imaging is complete, one of the partitions on the usb will contain a text file named: "put your 0rig here""

Thank you very much.

Having a look ...

Very interested!

#crysx

I made a new management website / OS.

Oros makes it easy to configure, edit, reboot, update, and monitor rigs from your pc, tablet, or smartphone.

oros thread OP

Why you should try openrig.net/oros:

At current exchange rates/difficulty: a 1% fee is approximately $0.12 to $0.18 a month per GPU, depending on what coin is mined.  I may reduce this in the future depending on actual overhead costs.  I believe any free Mining Management Service (MMS) is either selling your information or waiting to reach a user threshold before charging users (bait and switch).

My Ethash client should match or exceed Claymore’s hashrate (for 1000 series Nvidia GPUs) + has no fee.

Both openrig.net and oros are extremely secure.

Oros has almost no writes; so the USB key is unlikely to need servicing / reimaging / replacement.  Put otherwise; oros is reliable with a USB key.

When developing openrig.net/oros I focused on automating the processes an individual follows when they monitor rigs.  Oros's execution is controlled by a no-compromises watchdog that will self heal from almost any problem.

Oros has low network utilization.

Algorithm specific OC works without problems and is easy to use.  After configuring a group for Algo specific OC you need only switch the group coin, and your chosen OC for that algorithm will be set automatically.

It is extremely easy to configure a rig with openrig.net/oros.

Hi guys,

I have been using nvOC for many months, it is absolutely rock solid, thank you to all the dev team.
I am looking for some help with hopefully a basic request.
I have solar on my roof and would like to be able to schedule the mining to run only between sunrise and sunset, or alternatively between times I specify (say 7am to 7PM). The idea is free energy during the day of course.

I've had a look through 1bash but could not see anything to that effect. Of course, most people will want to run the rigs non stops, so probably not useful for most.

Perhaps ideally the rig would go into sleep mode while not mining to really cut it to the bone, but just pausing the mining would be good enough.

Can someone recommend an approach?

Thanks!

Miners Update:


Claymore updated to latest version: Claymore-v12.0

Changelog:

T-Rex updated to latest version: T-Rex 0.8.9
Changelog:

CryptoDredge  updated to latest version: CryptoDredge 0.15.1
changelog:

To get nvOC latest miners run:

@zloyneo: have you done this?

You can override default wallet separator '.' with '/' on a per-coin basis. Just do it for every coin you mine at nanopool.

There is new kk003_telegram (v1.5) here:
https://pastebin.com/UPGs2HRu

Tested on: Nvoc 0.19 (little mods have to be done mainly about paths for later versions)

the main novelty is that it supports PhoenixMiner 4.0b + some esthetic improvements

Thx.