Hey Pap and All:
It has been a long time and it would appear that lots of work has been done.
What is the best way to get started from nothing and get up to the latest version? My rigs are all on 19.2.0 and I just want to start over and hopefully get the latest Ubuntu and Cuda toolkit. I want to play around with mining RVN and the latest Z-enemy miner seems to require at least Cuda 9 and I am stuck at Cuda 8 with my older versions.
Thanks in advance.
Hi mate
Long time...
Have a look at
nvOC GitHub readme if you want to make a new image or check
This Post to just get the latest nvOC
Both 16.04 and 18.04 images download and set latest release point at first boot.
There is some issue on ubuntu 18.04 with tempcontrol which fans wont update and we gets multiple instances of it on some rigs after running for a while and we cant figure out why it happens.
My test rig with 3 cards shows no problem, but rigs with 6+ cards does.
If you have time to install 18.04 and see if you can pinpoint the problem would be a big help
I followed the directions as per the README.md, specifically "For insiders: Pre-built images targeting beta/pre-release branches". I couldn't find good documentation for the firstboot.json mods. I had a question about the release naming and could not find it anywhere. So I ended up with a bunch of failures:
Thu Oct 25 03:07:35 EDT 2018 - nvOC FirstBoot start
+ Looking for the small fat partition
/media/m1/12D3-A869 is not a mountpoint
++ mounting fat partition
+ Parsing firstboot.json
++ selected branch: '3.0'
++ nvOC will install to: '/home/m1'
+ Wait for internet connection to continue nvOC setup
Connection to google.com 443 port [tcp/https] succeeded!
+ Cloning '3.0' nvOC branch intohome/m1
++ Checking if selected branch actually exists...
+++ Selected branch not found, falling back to 'release'
++home/m1 already exists, cleaning up
rm: cannot remove '/home/m1/.config/enchant': Permission denied
rm: cannot remove '/home/m1/firstboot/tmplogs': Device or resource busy
fatal: destination path '/home/m1' already exists and is not an empty directory.
+ Updating miners submodule
++ No cache found inhome/m1/.miners-cache
fatal: not a git repository (or any of the parent directories): .git
+ Checking free space
++ Available free space in root partition: 100773288 KB
+ Installing miners (recompile: true)
/home/m1/firstboot/firstboot.sh: line 118: pushd:home/m1/miners: No such file or directory
bash: nvOC_miner_update.sh: No such file or directory
/home/m1/firstboot/firstboot.sh: line 129: popd: directory stack empty
+ Looking for your customized 1bash
dos2unix: converting filehome/m1/1bash to Unix format...
+ Setting 2unix as custom-command for gnome-terminal 'mining' profile
bash:home/m1/firstboot/profile-manager.sh: No such file or directory
+ Determining if firstboot can be disabled
++ FAILURE: keeping firstboot as default gnome-terminal profile
++ This script will run again on the next reboot.
++ Check your fat partition contents or internet connectivity.
+ Saving firstboot_90ccfd.log to small fat partition andhome/m1/firstboot
Thu Oct 25 03:07:36 EDT 2018 - Done.
cp: cannot stat '/home/m1/firstboot/tmplogs/firstboot.log': No such file or directory
cp: cannot stat '/home/m1/firstboot/tmplogs/firstboot.log': No such file or directory
I used value "3.0" and home of "/home/m1" but that was a guess as it could have been lots and lots of things - "nvOC-19.3.0", nvoc-19_3.0" and on and on. It also looks like the script defaulted to "release" which was promising but still failed.
What is the secret release to use for this field? Also, is it problem to use home "/home/m1"? I don't like having superfluous extra subdirectories if not absolutely necessary.
