Summary:
After a system update to kernel 6.16.3-76061603-generic, the proprietary NVIDIA drivers fail to build and load. The system falls back to the nouveau software rendering driver, and any attempt to install a compatible driver from the Pop!_OS repositories or external PPAs fails with a DKMS build error stating the kernel is not supported.
System Information:
- OS: Pop!_OS 22.04 LTS
- Problematic Kernel:
6.16.3-76061603-generic
- GPU: NVIDIA GeForce GTX 1080 (Pascal Architecture)
Steps to Reproduce:
- Start with a working Pop!_OS 22.04 system with a Pascal-based NVIDIA GPU and an earlier kernel version.
- Perform a full system update via the Pop!_Shop or
sudo apt full-upgrade, which installs the 6.16.3 kernel.
- Reboot the system into the new kernel.
Expected Behavior:
The system should boot normally with the proprietary NVIDIA drivers loaded and active. The nvidia-smi command should function correctly.
Actual Behavior:
The system boots with the nouveau driver. nvidia-smi fails to communicate with the driver. All attempts to install any NVIDIA driver package result in the same DKMS build failure.
Key Error Logs:
The dkms build process fails with the following error:
ERROR (dkms apport): kernel package linux-headers-6.16.3-76061603-generic is not supported
Error! Bad return status for module build on kernel: 6.16.3-76061603-generic (x86_64)
The kernel log (dmesg) shows the driver probe failing:
NVRM: The NVIDIA GPU 0000:29:00.0 (PCI ID: 10de:1b06)
NVRM: nvidia.ko because it does not include the required GPU
...
nvidia 0000:29:00.0: probe with driver nvidia failed with error -1
Troubleshooting Steps Taken:
Extensive troubleshooting has confirmed this is a package/kernel incompatibility issue. The following methods have all failed on the 6.16.3 kernel:
- Purging and reinstalling
system76-driver-nvidia.
- Attempting to install legacy
nvidia-driver-535 packages, which led to dependency conflicts caused by the Pop!_OS repository metapackages.
- Adding the
ppa:graphics-drivers/ppa and attempting to install from it, which was overridden by the Pop!_OS repository's higher apt priority.
- Forcing the installation of specific driver versions from the Ubuntu repositories, which still failed at the DKMS build stage due to the unsupported kernel.
Furthermore, the standard recovery method of booting into the previous kernel via oldkern.conf and attempting to reinstall the drivers has also failed to produce a working system, suggesting the multiple failed installations have left packages in a deeply inconsistent state. Currently, there appears to be no reliable workaround.
Summary:
After a system update to kernel
6.16.3-76061603-generic, the proprietary NVIDIA drivers fail to build and load. The system falls back to thenouveausoftware rendering driver, and any attempt to install a compatible driver from the Pop!_OS repositories or external PPAs fails with a DKMS build error stating the kernel is not supported.System Information:
6.16.3-76061603-genericSteps to Reproduce:
sudo apt full-upgrade, which installs the6.16.3kernel.Expected Behavior:
The system should boot normally with the proprietary NVIDIA drivers loaded and active. The
nvidia-smicommand should function correctly.Actual Behavior:
The system boots with the
nouveaudriver.nvidia-smifails to communicate with the driver. All attempts to install any NVIDIA driver package result in the same DKMS build failure.Key Error Logs:
The
dkmsbuild process fails with the following error:The kernel log (
dmesg) shows the driver probe failing:Troubleshooting Steps Taken:
Extensive troubleshooting has confirmed this is a package/kernel incompatibility issue. The following methods have all failed on the
6.16.3kernel:system76-driver-nvidia.nvidia-driver-535packages, which led to dependency conflicts caused by the Pop!_OS repository metapackages.ppa:graphics-drivers/ppaand attempting to install from it, which was overridden by the Pop!_OS repository's higheraptpriority.Furthermore, the standard recovery method of booting into the previous kernel via
oldkern.confand attempting to reinstall the drivers has also failed to produce a working system, suggesting the multiple failed installations have left packages in a deeply inconsistent state. Currently, there appears to be no reliable workaround.