NVIDIA Driver Broken After Latest Debian 12 TemplateVM Update

Hello,
I had setup a couple of Debian12 VMs with HVM fora Nvidia CPU and NVIDIA proprietary drivers.
Today I let Qubes update my Debian12 template/VMs.
And all these machine now don’t see anymore the GPU.

When I execute:

nvtop

“No GPU to Monitor”

nvidia-smi -l

“NVIDIA_SMI has failed because it coudln’t communicate with the NVIDIA driver…”

I suspect the new Debian update has installed/enabled some noncompatible drivers (nouveau kernel module?)

Do you have any suggestions on how to proceed and identify/fix the issue? And prevent this type of situation happening at a later Debian update?

thanks!

2 Likes

How did you install NVIDIA driver in the first place?

If you used the .run to install it manually, it will break at each kernel update because you will need to repeat the NVIDIA driver installation every time.

2 Likes

Thank you @solene for the quick reply!

Honestly, my NVIDIA driver installation was a bit messy (switched between open and proprietary drivers, etc) but this is basically what I did (I have just reproduced these steps on a new HVM to be sure):

# Make sure that NVIDIA GPU is there
# sudo apt-get install pciutils
# lspci 

wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb

sudo dpkg -i cuda-keyring_1.1-1_all.deb
sudo apt-get update

sudo apt-get -y install cuda-toolkit-12-8
sudo apt-get upgrade
sudo apt-get install nvidia-kernel-dkms cuda-driver
sudo apt-get upgrade
sudo apt-get install nvtop
# If docker is needed
# sudo apt-get install -y nvidia-container-toolkit

After a reboot, nvtop correctly prints the name of my GPU and its status.

PS: :face_with_raised_eyebrow: :tired_face: Not sure why but now the new VM where I just did this does not open a terminal from the Qubes menu… :man_facepalming: I had to open a console, after the reboot, to see the result of nvtop. But I guess this is a different issue.
EDIT: To avoid adding too much complexity to this thread, I have create another one devoted to this separate issue.

2 Likes