Driver compatiblity cuda 12.1

Accelerated Computing CUDA CUDA Setup and Installation
1

Is the 525.105.17 driver compatible with the latest CUDA?

Because if I try to run my PTX, I get the error:

the provided PTX was compiled with an unsupported toolchain.

My nvcc version:

$ /usr/local/cuda/bin/nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:16:06_PDT_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0

My driver version:

$ inxi -G
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] driver: nvidia
    v: 525.105.17
  Display: server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa dri: swrast
    gpu: nvidia,nvidia-nvswitch resolution: 1: 3840x2160~60Hz 2: 1280x768~60Hz
  API: OpenGL v: 4.5 Mesa 23.0.2 renderer: llvmpipe (LLVM 15.0.7 256 bits)

OS: Ubuntu 23.04

CUDA packages: Index of /compute/cuda/repos/ubuntu2204/x86_64

2

You would need at least an R530 (530.xx.xx) driver for CUDA 12.1 see here table 3. (in the general case, that is, not considering the use of compatibility libraries. The compatibility library path is not available for your GeForce card.)

1 Like
3

Thanks.

$ sudo apt install nvidia-driver-530
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help resolve the situation:

The following packages have unmet dependencies:
 libnvidia-extra-525 : Conflicts: libnvidia-extra
 libnvidia-extra-530 : Conflicts: libnvidia-extra
 nvidia-kernel-common-525 : Conflicts: nvidia-kernel-common
 nvidia-kernel-common-530 : Conflicts: nvidia-kernel-common
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
4

Installing via package manager means that the history of the machine matters. I won’t be able to walk you through this in detail, as the way that I know of to solve it is a matter of trial and testing. The basic process I would follow is covered here. I’m unlikely to be able to offer further suggestions, I usually find that I have to be sitting at the machine running commands in order to make sense of it. But the process of chasing the dependency chain is fairly mechanical.

1 Like
5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.