I would like to use atop for network monitoring, which requires loading additional kernel module from netatop package (AUR).
When I do
$ sudo insmod /usr/lib/modules/3.9.3-1-ARCH/extramodules/netatop.ko
kernel module loads correctly and all is fine. Next I want to load this module during boot (echo netatop > /etc/modules-load.d/netatop.conf), but following command produces error:
$ sudo insmod netatop insmod: ERROR: could not load module netatop: No such file or directory
Looks like insmod does not know such kernel module name. How do I fix this error? Thank you!
Last edited by studentik (2013-05-25 08:55:08)
Looking at the man page, insmod seems to require a filename. Why don't you use the more common modprobe (which takes a modulename)?
Most users will want to use modprobe(8) instead, which is more clever and can handle module dependencies.
$ sudo modprobe netatop modprobe: FATAL: Module netatop not found.
Okay, I had a look at the PKGBUILD and there is no install file, which would typically run depmod to update the list of modules. After you run it manually you should be good to go.
Thanks! It helped Maybe this should be reported to PKGBUILD maintainer?
One more problem. I tried
$ sudo systemctl start netatop.service
Which lead to following error:
-- Unit netatop.service has begun starting up. localhost insmod: insmod: ERROR: could not load module /lib/modules/extramodules--ARCH/netatop.ko: No such file or directory localhost systemd: netatop.service: control process exited, code=exited status=1 localhost systemd: Failed to start advanced interactive monitor.
Is this buggy PKGBUILD too (there is mistake in path of netatop.ko file)?
Yes, path is wrong (note the double dash). I suppose the service file (contained in PKGBUILD) could also just use the module name (with modprobe) or if you load the module yourself (or via modules-load.d) the ExecStartPre line is not necessary.
And sure, you can report it to the maintainer (maybe link to this thread).
Last edited by Raynman (2013-05-24 11:40:35)
I had some trouble properly installing the module on boot; obviously the .service wasn't the correct method of doing this. I have uploaded a new package