Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Module not found when I do a modprobe

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.

like image 801
robert trudel Avatar asked Jan 14 '16 22:01

robert trudel


People also ask

How do I add modules to modprobe?

In order to insert a new module into the kernel, execute the modprobe command with the module name. Following example loads vmhgfs module to Linux kernel on Ubuntu. Once a module is loaded, verify it using lsmod command as shown below. The module files are with .

How do I enable modprobe?

Use the modprobe command to add or remove modules on Linux. The command works intelligently and adds any dependent modules automatically. The kernel uses modprobe to request modules. The modprobe command searches through the standard installed module directories to find the necessary drivers.

Where is modprobe located?

modprobe looks in the module directory /lib/modules/`uname -r` for all the modules and other files, except for the optional configuration files in the /etc/modprobe.


2 Answers

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.

like image 158
thkala Avatar answered Sep 20 '22 19:09

thkala


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.

like image 29
oldone1 Avatar answered Sep 21 '22 19:09

oldone1