No, I don't.

That's the reason I posted about the old modules in the first place.
I didn't understand why these files pertaining to 4.9.0-8-amd64 and 4.19.0-14-amd64 were still around.

More importantly, why in spite of having manually removed the old kernels (each time) these files were there.
Still don't know the reason, but they are not there anymore:

[root@devuan groucho]# dpkg -S /lib/modules/*
linux-image-4.19.0-16-amd64, linux-headers-4.19.0-16-amd64: /lib/modules/4.19.0-16-amd64
[root@devuan groucho]# 

Thanks for your input.

Best,

A.

dpkg -S, --search filename-search-pattern...
  Search for a filename from installed packages.

So must still have that kernel installed. Updating to a newer release will not purge your kernels for you, you have to manually do this.

I think that is the idea.
Unneccesary modules which for some reason are still there.
I found them by sheer chance while wrestling with the e1000e module issue I have. (more module stuff in a next thread)

The dpkg -S /lib/modules/* stanza checks to see if all the modules in /lib/modules/* are properly referenced.
If there are any which are not, it informs that there was no matching path.
ie: a path to the corresponding kernel-image (?) among other things (?).

Thanks a lot for your input.

Best,

A.

~$ dpkg -S /lib/modules/*
linux-image-4.19.0-14-amd64: /lib/modules/4.19.0-14-amd64
linux-image-4.19.0-16-amd64: /lib/modules/4.19.0-16-amd64
linux-image-4.19.0-6-amd64: /lib/modules/4.19.0-6-amd64

For instance i still have linux-image-4.19.0-6-amd64 on my system, once i purge that kernel the modules are also purged.

I use ..

# apt purge linux-image-4.19.0-6-amd64

~$ dpkg -S /lib/modules/*
linux-image-4.19.0-14-amd64: /lib/modules/4.19.0-14-amd64
linux-image-4.19.0-16-amd64: /lib/modules/4.19.0-16-amd64

Yes, makes sense.
But you never know.

Found this a while ago:

https://unix.stackexchange.com/question … ib-modules

You run # dpkg -S /lib/modules/* to check whether any installed package matches those directories.
Then you can delete any directory for which the above says: dpkg-query: no path found matching pattern /lib/modules/...

Thanks for your input.

Best,

A.

Can't be a coincidence ...

My box runs the last Devuan:

groucho@devuan:~$ uname -a
Linux devuan 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
groucho@devuan:~$ 

But I have just found out that the old e1000e driver module from 4.9.0-8 is still in my system.

groucho@devuan:~$ locate e1000e.ko
/lib/modules/4.19.0-16-amd64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
/lib/modules/4.9.0-8-amd64/updates/drivers/net/ethernet/intel/e1000e/e1000e.ko
groucho@devuan:~$ 

Apparently it is the only module that has been left behind ...

groucho@devuan:~$ locate /updates/drivers
/lib/modules/4.9.0-8-amd64/updates/drivers
/lib/modules/4.9.0-8-amd64/updates/drivers/net
/lib/modules/4.9.0-8-amd64/updates/drivers/net/ethernet
/lib/modules/4.9.0-8-amd64/updates/drivers/net/ethernet/intel
/lib/modules/4.9.0-8-amd64/updates/drivers/net/ethernet/intel/e1000e
/lib/modules/4.9.0-8-amd64/updates/drivers/net/ethernet/intel/e1000e/e1000e.ko
groucho@devuan:~$ 

apt autoremove,  apt autoclean and apt purge come up empty.

And synaptic shows no residual configurations.

Do I just zap it?

Thanks in advance,

A.