Package Details: lkrg-dkms 0.9.9-1

Git Clone URL: https://aur.archlinux.org/lkrg-dkms.git (read-only, click to copy)
Package Base: lkrg-dkms
Description: Linux Kernel Runtime Guard (DKMS)
Upstream URL: https://lkrg.org/
Licenses: GPL-2.0-only
Submitter: rgacogne
Maintainer: rgacogne
Last Packager: rgacogne
Votes: 13
Popularity: 0.72
First Submitted: 2020-03-16 16:39 (UTC)
Last Updated: 2024-11-03 09:23 (UTC)

Latest Comments

1 2 3 Next › Last »

rgacogne commented on 2024-10-02 14:55 (UTC)

@Strykar Yes, lkrg will have to issue a new release to fix that. In the meantime lkrg-dkms-git seems to work for me.

Strykar commented on 2024-10-02 01:38 (UTC)

Aur package builds fine but DKMS fails with:

==> dkms install --no-depmod lkrg/0.9.8 -k 6.11.1-arch1-1
Error! Bad return status for module build on kernel: 6.11.1-arch1-1 (x86_64)
Consult /var/lib/dkms/lkrg/0.9.8/build/make.log for more information.
==> WARNING: `dkms install --no-depmod lkrg/0.9.8 -k 6.11.1-arch1-1' exited 10

$ cat /var/lib/dkms/lkrg/0.9.8/build/make.log
./include/linux/workqueue.h:746:17: warning: call to ‘__warn_flushing_systemwide_wq’ declared with attribute warning: Please avoid flushing system-wide workqueues. [-Wattribute-warning]
  746 |                 __warn_flushing_systemwide_wq();                        \
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/lkrg/0.9.8/build/src/modules/integrity_timer/p_integrity_timer.c:55:4: note: in expansion of macro ‘flush_workqueue’
   55 |    flush_workqueue(system_unbound_wq);
      |    ^~~~~~~~~~~~~~~
make[2]: *** [/usr/lib/modules/6.11.1-arch1-1/build/Makefile:1926: /var/lib/dkms/lkrg/0.9.8/build] Error 2
make[1]: *** [Makefile:224: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.11.1-arch1-1/build'
make: *** [Makefile:101: all] Error 2

rgacogne commented on 2024-05-21 15:06 (UTC)

@ruonim: Would you mind looking at dmesg right after getting this error? It should tell us more about what is going on. It would be very useful if you could tell us the exact version of the kernel you are running.

ruonim commented on 2024-05-21 05:10 (UTC)

modprobe: ERROR: could not insert 'lkrg': No buffer space available

rgacogne commented on 2023-12-06 19:17 (UTC)

@dubster: You are completely right, it should be fixed now! Many thanks!

dubster commented on 2023-12-06 16:59 (UTC)

Awesome, thanks for getting this updated @rgacogne!

The one thing I'll note is that the systemd service (when installed by a package) might need to be installed in /usr/lib/systemd/system. I believe that /etc/systemd/system is for admin user management, but packages install files into /usr/lib/systemd/system.

You can see an example of this in the mullvad-vpn package: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mullvad-vpn-cli#n116

MartinX3 commented on 2023-12-06 14:37 (UTC) (edited on 2023-12-06 14:37 (UTC) by MartinX3)

Seems to be related to the zen kernel.
https://github.com/lkrg-org/lkrg/issues/225

rgacogne commented on 2023-12-06 14:36 (UTC)

It works as expected for me on 6.6.4-arch1-1:

● lkrg.service - Linux Kernel Runtime Guard
     Loaded: loaded (/etc/systemd/system/lkrg.service; enabled; preset: disabled)
     Active: active (exited) since Wed 2023-12-06 14:40:24 CET; 55min ago
       Docs: https://lkrg.org
   Main PID: 33300 (code=exited, status=0/SUCCESS)
        CPU: 409ms

systemd[1]: Starting Linux Kernel Runtime Guard...
modprobe[33300]: insmod /lib/modules/6.6.4-arch1-1/updates/dkms/lkrg.ko.zst
systemd[1]: Finished Linux Kernel Runtime Guard.

MartinX3 commented on 2023-12-06 14:33 (UTC)

Service errors out:

Starting Linux Kernel Runtime Guard...
modprobe: ERROR: could not insert 'lkrg': No buffer space available
modprobe[5095]: insmod /lib/modules/6.6.4-zen1-1-zen/updates/dkms/lkrg.ko.zst
lkrg.service: Main process exited, code=exited, status=1/FAILURE
lkrg.service: Failed with result 'exit-code'.
Failed to start Linux Kernel Runtime Guard.

rgacogne commented on 2023-12-06 13:59 (UTC)

@dubster: I just added the systemd service and the default configuration file to the package. I'm not going to enable the LKRG service automatically, though, as per Arch policy. Thanks for the hint!