Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#77154 - [dkms] uninstall/remove doesn’t remove module

Attached to Project: Arch Linux
Opened by Norbert Pfeiler (npfeiler) - Monday, 16 January 2023, 11:04 GMT
Last edited by freswa (frederik) - Thursday, 19 January 2023, 14:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


/updates/dkms/wl.ko.zst remains in the modules directory

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
sudo dkms remove broadcom-wl/ --all
ll /usr/lib/modules/*/updates/dkms/wl.ko.zst
This task depends upon

Closed by  freswa (frederik)
Thursday, 19 January 2023, 14:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  dkms-3.0.10-1
Comment by Toolybird (Toolybird) - Wednesday, 18 January 2023, 03:23 GMT
This doesn't appear specific to "broadcom-wl-dkms". I just tested with another dkms module and see the same. If anything, this looks like a "dkms" regression because it apparently works fine with dkms-3.0.8. Can you confirm? If yes, it will need to be reported upstream.

Related:  FS#76295 
Comment by Norbert Pfeiler (npfeiler) - Wednesday, 18 January 2023, 04:17 GMT
i have several modules that seem to clean up fine (e.g. vboxhost)

broadcom-wl-dkms is the only one where this appears for me

seems like it looks in the wrong directory:

Module vboxhost-7.0.6_OSE for kernel 6.1.6-arch1-3 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

- Uninstallation
- Deleting from: /usr/lib/modules/6.1.6-arch1-3/updates/dkms/


Module broadcom-wl- for kernel 6.1.6-arch1-3 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

- Uninstallation
- Module was not found within /usr/lib/modules/6.1.6-arch1-3/
Comment by Toolybird (Toolybird) - Wednesday, 18 January 2023, 05:22 GMT
I saw the issue with "acpi_call-dkms". Could you please test that one?
Comment by freswa (frederik) - Wednesday, 18 January 2023, 11:29 GMT
Can you also check this commit [0] or 3.0.10 (in [testing])?


It throws an error for some modules and since we use the output of dkms in our hooks, this could be the culprit.
Comment by Henrique Custódio (henriqueffc) - Wednesday, 18 January 2023, 14:14 GMT
I had the same problem when upgrading dkms to version 3.0.10 and kernel 5.15.89-1-lts. I need to install xpad ( for my controller to work.

Sign command: /usr/lib/modules/5.15.89-1-lts/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/
Creating symlink /var/lib/dkms/xpad/0.4/source -> /usr/src/xpad-0.4

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=5.15.89-1-lts KVERSION=5.15.89-1-lts...
Signing module /var/lib/dkms/xpad/0.4/build/xpad.ko
Cleaning build area...

Running module version sanity check.
Module version for xpad.ko.zst
exactly matches what is already found in kernel 5.15.89-1-lts.
DKMS will not replace this module.
You may override by specifying --force.
Error! Installation aborted.

I ran the command below and dkms performed the installation without any problems.

sudo dkms install -m xpad -v 0.4 --force

In previous versions of dkms I didn't have this problem on kernel upgrade.
Comment by Norbert Pfeiler (npfeiler) - Thursday, 19 January 2023, 03:06 GMT
3.0.10 seems to work fine for me, thx