Different command. p_lkrg
. (I didn’t invent the p_
. Upstream did.) But probably just a mistake. Not the reason.
So you had kernels 4.19.0 and 4.19.122 installed. The latter, the newer kernel version 4.19.122 was loaded. Kernel module was build for 4.19.122 only. Right?
I wonder how/if this can be fixed. See the DKMS file,debian/lkrg-dkms.dkms
.
Then feel free to compare with this with other DKMS files.
Try:
sudo dkms status
Also interesting:
/var/lib/dpkg/info/lkrg-dkms.postinst
sudo sh -x /var/lib/dpkg/info/lkrg-dkms.postinst configure
Reveals what is required to debug further:
sudo sh -x /usr/lib/dkms/common.postinst lkrg 0.8.1 /usr/share/lkrg-dkms
The latter shows how list of kernels is generated. (Runs as root.)
KERNELS=$(ls /lib/modules/ 2>/dev/null || true)
Try this command.
sudo ls /lib/modules/
Perhaps apparmor-profile-everything or other issue which messes up setting of KERNELS
? xtrace of /usr/lib/dkms/common.postinst
might reveal that.
For me it builds modules for all installed kernel versions. I guess that is the default.
Dunno if DKMS in Debian only works for APT installed kernels but we’re already talking only about APT installed kernels here.
/etc/dkms/framework.conf
## Automatic installation and upgrade for all installed kernels (if set to a
## non-null value)
# autoinstall_all_kernels=""
I see there’s one caveat, the autoinstall_all_kernels variable in /etc/dkms/framework.conf can be set to build for all installed kernels, not just the current and newest. But the default is to build only for current and newest.