5 ms·
The solution is to install the latest CUDA driver (which is always 100% backward compatible) but have multiple version of the libraries in /usr/local. Granted i
by the_svd_doctor 3y ago
The solution is to install the latest CUDA driver (which is always 100% backward compatible) but have multiple version of the libraries in /usr/local. Granted it can get messy with various package manager doing their own things.
- dheera 3y agoUsually the CUDA versions end up uninstalling other CUDA versions and drivers due to package manager issues. I wish nvidia would just release a `sudo apt install cuda-all` that just keeps you updated with ALL possible cuda versions simultaneously. I know it would be 20GB but that's fine, it's a drop in the bucket compared to the datasets I play with.
- cburdick13 3y agoIf you use the run files rather than the package manager files it's always installed in completely separate folders inside /use/local/cuda. What you're describing with an "all" install can somewhat be accomplished with containers right now and none of the dependency problems.
- dheera 3y agoBut containers, X forwarding, visualization, and OpenGL is a complete shitshow. I have apps that work outside of a container but freeze the UI that the mouse pointer won't even work when run from within a container.
- touisteur 3y ago+1 for runfiles but beware of the multi-gigabyte installer + installed footprint. Not complaining per-se, just plan for it.
- dheera 3y agoProblem with runfiles is I've run into other .deb packages that I'd like to use that are marked as dependent on 'cuda'. Using a runfile is ditching the package manager on a package-managed system, instead of using the package manager correctly.