CUDA 11.2 + Driver 460.xx
Graham Inggs
ginggs at debian.org
Sat Jan 23 13:46:50 GMT 2021
On Tue, 19 Jan 2021 at 21:36, Graham Inggs <ginggs at debian.org> wrote:
> I will do a trial run in an Ubuntu PPA and see if there's any
> breakage. That might help you decide whether to push forward in
> Debian.
Although this isn't a transition, I rebuilt all reverse-dependencies
to check for build failures.
Below is a list packages and architectures where the builds were successful.
astra-toolbox: amd64 arm64 ppc64el
gr-fosphor: everywhere*
hwloc-contrib: amd64
magma: amd64 arm64 ppc64el
nvtop: amd64
pycuda: amd64
relion-cuda: amd64
starpu-contrib: amd64 arm64 ppc64el
* gr-fosphor has a build dependency on ocl-icd-opencl-dev |
amd-opencl-dev | nvidia-opencl-dev
I've tested upgrading an Ubuntu 21.04 (hirsute) am64 system, with all
of the above packages installed, to nvidia-cuda-toolkit 11.2.0-1 built
in my PPA and didn't find any issues.
On Mon, 18 Jan 2021 at 19:31, Andreas Beckmann <anbe at debian.org> wrote:
> 11.2 is on its way to NEW/experimental, but it might be a bit late for
> still getting this into bullseye, or do you have a good reason why we
> definitively should have 11.2 instead of 11.1.1 in bullseye?
Let's turn the question around. Seeing this isn't a transition, is
there any good reason not to get 11.2 into bullseye?
I'm currently waiting for 11.1.1-4 to migrate in Ubuntu. The latest
packages took several retries on each architecture before they built.
They failed without logs and I suspect the time taken to download the
source packages is becoming an issue. It seems to take more retries
every release. Once 11.1.1-4 has migrated, I will consider a sync of
11.2.0-1 from experimental.
More information about the pkg-nvidia-devel
mailing list