Package Details: mkmm 0.4.0-1

Git Clone URL: https://aur.archlinux.org/mkmm.git (read-only, click to copy)
Package Base: mkmm
Description: Moviuro's Kernel Module Manager
Upstream URL: https://git.sr.ht/~moviuro/mkmm
Licenses: MIT
Submitter: Moviuro
Maintainer: Moviuro
Last Packager: Moviuro
Votes: 9
Popularity: 0.000556
First Submitted: 2021-06-08 12:24 (UTC)
Last Updated: 2024-03-11 15:01 (UTC)

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

1 2 3 Next › Last »

JisuWoniu commented on 2024-12-23 02:20 (UTC)

It seems that the problem is in /var/lib/dkms. After I remove all files & directories with version numbers 6.6.5* and 6.11.9 in them, the problem is gone.

But do I have to run the "find and remove" commands every time I upgrade the kernel? Or is there a way to automatically get it done?

Moviuro commented on 2024-12-22 16:37 (UTC)

@JisuWoniu : looks like you have lots of stray directories. During normal operation, you should at most have one extra modules' dir (the one that contains the current kernel's modules). Inspect them and remove (rm -rf) the ones that are unnecessary:

% uname -a
% pacman -Qo /usr/lib/modules/*

Also check /usr/lib/mkmm - there should be only one dir in it. Try mkmm bleach.

JisuWoniu commented on 2024-12-22 15:56 (UTC)

When I run dkms status, I got this error in my terminal:

find: '/usr/lib/modules/6.6.50-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.50-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.50-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.50-2-lts/': No such file or directory
find: '/usr/lib/modules/6.6.50-2-lts/': No such file or directory
find: '/usr/lib/modules/6.6.50-2-lts/': No such file or directory
find: '/usr/lib/modules/6.6.51-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.51-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.51-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.52-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.52-1-lts/': No such file or directory
find: '/usr/lib/modules/6.6.52-1-lts/': No such file or directory
find: '/usr/lib/modules/6.11.9-zen1-1-zen/': No such file or directory
find: '/usr/lib/modules/6.11.9-zen1-1-zen/': No such file or directory
find: '/usr/lib/modules/6.11.9-zen1-1-zen/': No such file or directory
(Many more...)

How can I fix it?

Moviuro commented on 2024-03-13 08:00 (UTC)

@liljaylj -- this sadly sounds like a git(1) issue, but it is indeed repeatable:

% git tag -v 0.4.0
object 1e7f5fe4f3439d50d68e53fa17a86e98a93a4738
type commit
tag 0.4.0
tagger Moviuro <moviuro+git@gmail.com> 1685094977 +0200

Breaking change: mkmm will no longer remove directories that were not marked as managed by mkmm
gpg: Signature made 2023-05-26T11:56:51 CEST
gpg:                using EDDSA key 03A5D629F62B7AE323A753E0D280BD7ACDF8CE52
[...]
gpg: Note: This key has expired!
Primary key fingerprint: 2CD9 6FEE 343C 6799 B9CE  AFAD 6200 9A2E 0C22 D9AB
     Subkey fingerprint: 03A5 D629 F62B 7AE3 23A7  53E0 D280 BD7A CDF8 CE52
% echo $?
1
  • The tag was created in May 2023, and signed with my then yearly subkey (03A5D629F62B7AE323A753E0D280BD7ACDF8CE52 valid from 2022-10-26T15:15:15Z until 2024-01-01T15:15:15Z)
  • GnuPG considers artifacts signed before the expiration of the key to be valid: this tag should be valid.

Also, slight issue within the error message (%s).

I will reach out to git(1) devs and pacman(8) devs to discuss this.

flying-sheep commented on 2024-03-12 12:57 (UTC)

yup, key error is back

liljaylj commented on 2024-03-12 06:01 (UTC) (edited on 2024-03-12 06:01 (UTC) by liljaylj)

@Moviuro, hello. i have problem building this package with makepkg.

==> Making package: mkmm 0.4.0-1 (Tue Mar 12 10:59:25 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mkmm git repo...
  -> Found mkmm.install
==> Validating source files with sha256sums...
    mkmm ... Skipped
    mkmm.install ... Passed
==> Verifying source file signatures with gpg...
    mkmm git repo ... %s is unable to verify the signature.
git
==> ERROR: One or more PGP signatures could not be verified!

can only build with --skippgpcheck flag

eNV25 commented on 2022-12-22 21:27 (UTC)

@Moviuro

pacman -Qo will tell you that no package owns the directory.

True, pacman -Qo is a fine alternative. I guess nothing needs to change.

I have not found documentation about the pkgbase file in /usr/lib/modules/*/; and it's unclear how that removal might interfere with other pieces of software (dkms?...)

I don't think any files other than *.ko are useful. Isn't the whole point of this, for the dynamic loading of modules to continue to work after an update?

Moviuro commented on 2022-12-22 20:53 (UTC)

@eNV25: pacman -Qo will tell you that no package owns the directory. I have not found documentation about the pkgbase file in /usr/lib/modules/*/; and it's unclear how that removal might interfere with other pieces of software (dkms?...)

eNV25 commented on 2022-12-22 13:36 (UTC)

An indicator that restored kernels are not from pacman would be useful. The pkgbase file could be removed, for example.

whynothugo commented on 2021-08-24 12:19 (UTC)

git is missing as a build dependency:

diff --git a/PKGBUILD b/PKGBUILD
index d0bbec0..1eaf953 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,6 +8,7 @@ arch=('any')
 license=('MIT')
 url="https://git.sr.ht/~moviuro/${pkgname}"
 install="${pkgname}.install"
+makedepends=('git')
 validpgpkeys=('2CD96FEE343C6799B9CEAFAD62009A2E0C22D9AB')
 # https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x62009A2E0C22D9AB
 source=("git+${url}?signed#tag=${pkgver}"

1 2 3 Next › Last »