Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

2016-03-29 Thread Alois Schloegl
In order to fix the installation of glx-alternative-nvidia, and fix some other cuda related issues, I tried to update cuda to jessie-backports. The update did not work out of the box, e.g After uninstalling nvidia-cuda and reinstallung with apt-get -t jessie-backports install nvidia-cuda-tool

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

2016-03-02 Thread Alois Schloegl
I was able to revert to a working state of cuda 6.5, by using dpkg -i and the packges in /var/cache/apt/archives. Below are the output of nvidia-smi and the gpuinfo test program. The package list is attached in "pkglist.nvidia.working.txt". Configuration of glx-alternative-nvidia failed with this

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

2016-02-29 Thread Alois Schloegl
On 2016-02-29 16:08, lumin wrote: > Hi, > > Thank you for reporting this bug. > > It seems like a GCC ABI issue, rather than that of CUDA > or nvidia-driver. > If the nvidia-driver package ships binary then they are > linked by GCC-5, which requires an different ABI to > the one of Jessie. Hence

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

2016-02-29 Thread lumin
Hi, Thank you for reporting this bug. It seems like a GCC ABI issue, rather than that of CUDA or nvidia-driver. If the nvidia-driver package ships binary then they are linked by GCC-5, which requires an different ABI to the one of Jessie. Hence installing stuff from unstable into Jessie may basic

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

2016-02-29 Thread Alois Schloegl
Package: nvidia-cuda-toolkit Version: 7.0.28-4 Severity: important Dear Maintainer, I tried to upgrade the nvidia-drivers from 352.41-1 to the current version "352.79-3" and nvidia-cuda-toolkit to a matching version, cuda became unusable. Rebooting the machine did not help. I used the follow