DKMS ERROR: Missing 5.16.0-1-MANJARO kernel headers for module nvidia/515.48.07

[DAC324]

Hello all,

I just installed kernel 5.19 using the Manjaro settings tool. As I, of course, got errors saying that my nvidia and nvidia-modeset kernel modules were missing for that new kernel, I re-installed nvidia-dkms.
So far, so good, it installed the nvidia kernel modules for all installed kernels as required.
Currently, I have kernels 5.10, 5.15, 5.18, and 5.19 installed.
As of now, the system is running flawlessly with kernel 5.19 and the nvidia-dkms driver package.

However, I also got the following error message while re-installing nvidia-dkms:

ERROR: Missing 5.16.0-1-MANJARO kernel headers for module nvidia/515.48.07

This is a bit strange as kernel 5.16 was removed using Manjaro settings a long time ago following the announcement that it is no longer supported.
Apparently, the tool did not remove some configuration entries used by dkms for that kernel 5.16.

How do I get rid of that error message without breaking anything?

Thank you very much and kind regards.

[DAC324]

Just found this thread while searching for a solution to a similar problem:

ERROR: Missing 5.16.0-1-MANJARO kernel headers for module nvidia/515.48.07

Problem is that kernel 5.16 is not installed as I removed it long time ago following the applicable recommendations. How do I get rid of this error message?

[Mirdarthos]

@DAC324

How do I get rid of this error message?

If you can still boot, boot up and then install kernel version 5.15 as it is an LTS version.

If you are unable to boot, boot with a thumb drive into a live environment and start a chroot session. From there, install the new kernel, version 5.15.

Start a new thread if you require assistance, please. Do not necro-bump. See Forum Rules - Manjaro

[DAC324]

@Mirdarthos

Start a new thread if you require assistance, please. Do not necro-bump.

Thank you very much for making me aware. In lots of other forums, it is just the opposite: You get blamed if you start a new thread asking for something that is already discussed elsewhere.

[Mirdarthos]

You are welcome! I understand perfectly. We try not to make threads too long, and that can happen easily like this.

@DAC324

Problem is that kernel 5.16 is not installed as I removed it long time ago following the applicable recommendations. How do I get rid of this error message?

Let’s see if there are any remnants in the /boot directory. Please provide the output of:

ls -l /boot

[DAC324]

@Mirdarthos

Please provide the output of:

ls -l /boot

$ ls -l /boot
insgesamt 471856
-rw-r--r-- 1 root root    43520 15. Jan 2021  acpi_override
-rw-r--r-- 1 root root    42373 15. Jan 2021  dsdt.aml
drwxr-xr-x 5 root root     4096 17. Jun 11:35 grub
-rw------- 1 root root 61420079 27. Dez 2018  initramfs-4.20.0-1-MANJARO.img
-rw------- 1 root root 69637723 17. Jun 11:26 initramfs-5.10-x86_64.img
-rw------- 1 root root 69704218 17. Jun 11:27 initramfs-5.15-x86_64.img
-rw------- 1 root root 71849270 17. Jun 11:27 initramfs-5.18-x86_64.img
-rw------- 1 root root 91905287 17. Jun 11:27 initramfs-5.19-x86_64-fallback.img
-rw------- 1 root root 71848266 17. Jun 11:27 initramfs-5.19-x86_64.img
-rw-r--r-- 1 root root  5174272 10. Mai 20:27 intel-ucode.img
-rw-r--r-- 1 root root       23 16. Jun 14:33 linux510-x86_64.kver
-rw-r--r-- 1 root root       22 16. Jun 14:32 linux515-x86_64.kver
-rw-r--r-- 1 root root       21 16. Jun 14:27 linux518-x86_64.kver
-rw-r--r-- 1 root root       38  6. Jun 15:11 linux519-x86_64.kver
drwxr-xr-x 2 root root     4096 18. Jun 2021  memtest86+
-rw-r--r-- 1 root root  9411872 17. Jun 09:02 vmlinuz-5.10-x86_64
-rw-r--r-- 1 root root 10461504 17. Jun 09:02 vmlinuz-5.15-x86_64
-rw-r--r-- 1 root root 10696512 17. Jun 09:02 vmlinuz-5.18-x86_64
-rw-r--r-- 1 root root 10919584 17. Jun 11:16 vmlinuz-5.19-x86_64

[Mirdarthos]

Then I suspect it’s something in your /lib/modules directory as per your other post. Let’s continue there, so as not get confused and end up ready to murder each other from the frustration.

[DAC324]

@Mirdarthos

Then I suspect it’s something in your /lib/modules directory as per your other post.

Indeed, that seems to be the case. After moving all the unneeded folders away, that error is gone as well.
So thanks a lot again for your good advice!

For all other readers: If you encounter errors similar to the one discussed here, just check if there are leftovers from kernels you already uninstalled, in /lib/modules and move them out of the way. That should solve it.

[straycat]

By move them out of the way do you mean delete them.

[Mirdarthos]

Move them to a backup file or directory, so that they’re no longer accessible at the location, and if everything continues working as it should, then delete them. If not, restore the backup.

[straycat]

Thank you