Module not found when I do a modprobe

Question

I am trying to install this module: https://github.com/mkottman/acpi_call

I did a make, make install.

I then saw acpi_call.ko is in /lib/modules/4.3.3-5-default/extra/.

When I do a

modprobe acpi_call

I get

modprobe: FATAL: Module acpi_call not found in directory /lib/modules/4.3.3-5-default

Tried putting acpi_call.ko in /lib/modules/4.3.3-5-default but got the same result.

I would like to make it persistent so that when I reboot, module is loaded. I think it's possible only with modprobe.

score 73 · Accepted Answer · edited Aug 03 '20 at 04:39

73

If the module .ko file is really under /lib/modules/4.3.3-5-default/extra/ and 4.3.3-5-default is indeed your current kernel version, then the problem may simply be that you need to run depmod to re-create the module dependency list. Run:

sudo depmod

and try again to modprobe the module.

edited Aug 03 '20 at 04:39

chris

1,831
18
33

answered Jan 14 '16 at 22:18

thkala

84,049
23
157
201

12

Running `depmod` without any flags worked for me. `-a` is the default anyway and `-e` doesn't do anything without either `-E` or `-F`. – Karel Vlk Jan 04 '17 at 09:26
How to I probe it if the kernel is not running right now? – Ali Asgari Aug 16 '17 at 13:04
@AliAsgari You can list the loaded modules using the `lsmod` command. – jibin_raj24 Jun 18 '20 at 15:03
1

This really saved me. Please upvote. – Danijel Apr 06 '22 at 13:12
# depmod depmod: ERROR: could not open directory /lib/modules/4.4.35_ecoo_81080868: No such file or directory depmod: FATAL: could not search modules: No such file or directory – CS QGB Mar 03 '23 at 01:17
Note to people who read this: This says `depmod`, not `depend`. – PoolloverNathan Mar 28 '23 at 02:33

score 1 · Answer 2 · edited Nov 25 '20 at 12:50

My solution is unique, but in my system I rebuilt the kernel and took out a module. I installed the vendors module and could not get the system to boot using the vendors module. In my case I forgot to move all the /lib/modules info, so modules.builtin still had the module, that I was upgrading. Manually removing the module from modules.builtin and doing the depmod -a fixed my problem.

score -1 · Answer 3 · answered Feb 23 '23 at 16:09

This will solve it for ubuntu/debian

sudo apt install linux-generic -y 
sudo apt install --reinstall linux-image-$(uname -r) -y;
sudo apt install --reinstall linux-modules-$(uname -r) -y;
sudo apt install --reinstall linux-modules-extra-$(uname -r) -y;

score -2 · Answer 4 · answered Jan 14 '16 at 22:14

-2

Try running make && sudo make install in the source directory. That should install the module in the right place using the Makefile that comes with your kernel headers.

answered Jan 14 '16 at 22:14

Steven

5,654
1
16
19

Module not found when I do a modprobe

4 Answers4