When installing the proprietary nvidia driver recommended by the the official debian page for Debian Bookwork, apt seems to want to install a new kernel. I actually did this before (since this is my second time installing debian on here) and this new kernel messes with the display server somehow, disabeling all monitors but one, limiting the resolution, removing all the UI animations and so on. So I don’t want to do that again. My current kernel is the Debain 12 default: linux-image-6.1.0-18-amd64. Am I doing something terribly wrong, is the website perhaps outdated, or what is going on here?
SOLUTION:
This is a problem not with the operating system, but rather the nvidia DKMS. It can easily be fixed by replacing some lines in the apt sources located here:
/etc/apt/sources.list
. The line update-security has to be replaced by these two:deb http://deb.debian.org/debian/ bookworm-updates main non-free contrib non-free-firmware deb-src http://deb.debian.org/debian/ bookworm-updates main non-free contrib non-free-firmware
Here is a link to where this solution was found: https://forums.developer.nvidia.com/t/debian-12-and-nvidia-driver-nvidia-linux-x86-64-470-223-02-run/282473/2
After updating the sources there, simple run
sudo apt
update andsudo apt upgrade
. Then it should finally compile the drivers for your kernel, the extra kernel in the grub menu (if it appeared on your machine) should disappear, and your original kernel (in my case 6.1.0-18-amd64) will have the module in it. So your monitors and stuff should work as they did before.I had the same issue updating yesterday, apparently it’s bugged. I’m using the previous kernel for now and it’s running fine.
Thats the bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063675
Will be fixed in the next dot release
The proprietary Nvidia driver has kernel modules that are specific to a single version of the Linux kernel. With pre-built packages that’s typically whatever the standard kernel is for your distro. If that kernel isn’t booted then you’ll have no graphics driver.
This is solved by DKMS, which will build those kernel modules for every kernel you have installed. You’ll need the kernel headers for the kernel you want to build for, as well as the
nvidia-kernel-dkms
package which the wiki you linked only offhandedly mentions. Whenever the kernel or driver updates it should build the required modules.Oh yeah, I completely missed the DKMS. I just installed the nvidia-kernel-dkms package, and it seemed to try to build the module, but then failed:
Building for 6.1.0-18-amd64 Building initial module for 6.1.0-18-amd64 Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information. dpkg: error processing package nvidia-kernel-dkms (--configure): installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-driver: nvidia-driver depends on nvidia-kernel-dkms (= 525.147.05-4~deb12u1) | nvidia-kernel-525.147.05 | nvidia-open-kernel-525.147.05 | nvidia-open-kernel-525.147.05; however: Package nvidia-kernel-dkms is not configured yet. Package nvidia-kernel-525.147.05 is not installed. Package nvidia-kernel-dkms which provides nvidia-kernel-525.147.05 is not configured yet. Package nvidia-open-kernel-525.147.05 is not installed. Package nvidia-open-kernel-525.147.05 is not installed. dpkg: error processing package nvidia-driver (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: nvidia-kernel-dkms nvidia-driver E: Sub-process /usr/bin/dpkg returned an error code (1)
It says that something hasn’t been configured yet, even though I am just installing it…
If you want the latest Nvidia driver without apt conflicts, you have to use their installer which builds dkms live.
Where would get that installer?
Don’t use the NVIDIA installer, as it conflicts with the package manager. Use the
nvidia-kernel-dkms
package from the official Debian repositoryTurns out that the repository one is broken. This is an issue with a specific version of the nights driver, which has just been fixed. If you want more info, have a look at the solved content I made on this post.