- - ALL UNSTABLE / TESTING THREADS SHOULD BE POSTED HERE - - This sub-forum is the dedicated area for the ongoing Unstable/Testing releases of Debian. Advanced, or Experienced User support only. Use the software, give, and take advice with caution.
Loading new nvidia-current-535.183.01 DKMS files...
Building for 6.9.12-amd64 6.10.3-amd64
Module build for kernel 6.9.12-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.
Building initial module for 6.10.3-amd64
Error! Bad return status for module build on kernel: 6.10.3-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/535.183.01/build/make.log for more information.
It's Unstable, this happens regularly when the nvidia driver build doesn't keep up with the new kernel. It won't build for 6.10 kernels currently. You will have to keep using the 6.9 kernel until a new nvidia driver package is available.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
Tas_Mania wrote: 2024-08-11 08:55
I'm using testing (Trixie)
How does one know when a nvidia driver is available for kernel 6.10.3? Does it appear on an nvidia list or a debian one?
The situation with Testing is the same as with Unstable as in OP's case, except it will take a little longer. Driver upgrades will happen with the normal upgrade process when they become available. Don't hold your breath.
Nvidia driver issues were one of the main reasons I now happily use Stable after being on Unstable for years.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
I did what @ttila did and used the Nvidia Cuda APT repository. I followed Method 2 from this page.
Also had to update linux headers with 'sudo apt install linux-headers-amd64'. Then kernel 6.10.3 completed successfully. Lucky we have the boot chooser
I appreciate sunrats advice - this could get tedious.
I don't install the full CUDA thing but just the one that comes with the driver. I found it's too big and add more big programs and the root partition fills up.
Backported and built on bookworm and bullseye bases for MX 21 and 23. In our staging repository at the moment. Debian may decide to push them to Bookworm as an update anyway, like the last 535 driver.
Had to reinstall Trixie on my laptop, and the kernel 6.10.3 has been installed in addition to 6.9.10 that is included in the netinst ISO. And when attempting to install the nVidia drivers, I have run into the same problem as the OP describes.
sunrat wrote: 2024-08-10 08:48
You will have to keep using the 6.9 kernel until a new nvidia driver package is available.
This is what I would like to do, but when I tried to get the matching kernel headers, I saw that the linux-headers-6.9.10-amd64 package is no longer available in the Trixie and Sid repositories. Is there any chance to still get this package from somewhere?
stevepusser wrote: 2024-08-16 07:03
Debian should update the drivers first, then the kernel that needs them, IMHO.
That would be nice. It's generally only an issue for development versions rather than Stable though. Except for that one time a few point releases ago...
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
@sunrat: In other words, no way to go back one or two notches... Yes, I have seen that thread, and it is probably the same problem that has pushed me to reinstall: after updating, there were many red lines in the boot log, and due to my blocked root account (left root password empty during install, and forgot to set one later), I could not even attempt to do something about it.
I have also looked at the driver site that wizard10000 has linked to, and since after a short glance I could not see there any time-related information, I will just trust his observation that a new driver will come soon enough. And once I will have it installed again, I will have to teach myself to use 'apt dist-upgrade' much more sparingly.
When using Unstable or Testing with Nvidia, I would remove the linux-image-amd64 and linux-headers-amd64 metapackages to prevent automatic kernel upgrades. Then regularly check for new kernels manually. This way old kernels are not removed automatically so you can just remove any new kernel for which modules don't build and boot the earlier kernel.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
Thanks, sunrat, I will definitely do this! Regarding Trixie, to which I am still quite new, I feel like I am here to stay, and I will eagerly collect any tips and techniques to to maximize the time when my machine is up and running, and not locked down by some kernel-driver mismatches... Such as now... I guess that the best that I can do while waiting for a new nVidia driver is to try to find out why my OpenGL code that runs quite fine on nVidia does not even start on nouveau, which is advertised by
Finally! The nVidia driver version 535.183.06-1 amd64 became available (edit: for Trixie)(535.183.01-1 was the problematic one); no problems during installation, no problems during rebooting, and my OpenGL code runs again!
Without nVidia drivers, the problem was shader compilation failure. I have looked at the nouveau site, and it looks like nouveau is not involved in shader compilation, and probably in no OpenGL matters at all... It is the Mesa 3D Library that I may want to look at next time I run into a no-nVidia situation.
In our staging repository at the moment. Debian may decide to push them to Bookworm as an update anyway, like the last 535 driver.
