Quote from: Brainfruit_Me on July 11, 2018, 06:48:39 PM

Quote from: LuKePicci on July 11, 2018, 06:16:04 PM

I think it requires cuda 9.1, so we can add it but you will need to provide cuda-9-1 runtime otherwise it won't work.

Okay, yeah maybe that's why it wasn't working for me. I've never used Cuda before, does it operate independently of our nvoc bash files?
I've compiled a couple miners before but they were always straight forward

Yes, it is independent from nvOC scripts, but the last image is bundled with nvidia 390 distribution specific drivers. which means you need distribution specific cuda runtime packages.
Distribution specific means: add nvidia ppa to ubuntu and install packages from those repo. Do not install generic cuda package, always install cuda-X-Y packages to keep all versions side by side. The cuda 8.0 currently installed into all past nvOC images up to now is not installed by distribution specific package but from standalone runfile, and it was a mistake since nvidia does not support distribution spec. driver + standalone runfile cuda combination, they have to be both distribution specific or standalone runfile. So to manually add cuda-9-1 to latest nvOC images you need to:
-add nvidia cuda ppa for ubuntu 16.04 distribution specific packages
-don't need to add nvidia driver ppa for ubuntu 16.04 distribution specific packages
since it is added already into nvOC images
- install cuda-9-1 package, it will also update driver to nvidia-396
-WARNING: do it from tty session otherwise during driver install apt will kill the desktop environment and therefore also apt itself, stopping abnormally the driver install
-reboot to load the new driver module

From now on you have both cuda 8.0 and 9.1 but your /usr/local/cuda symlink will point to /usr/local/cuda-9.1, so every miner unless differently set up will run under 9.1. Support for different cuda runtimes is coming, I hope for next nvOC images also.