Module Not Found When I Do a Modprobe
I Am Trying to Install This Module: 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...
I am trying to install this module:
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.
4 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.
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.
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;
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.
Sarah Jenkins is a veteran tech journalist with over 12 years of experience covering artificial intelligence, mobile innovations, and digital ethics. Her insights have appeared in leading technology publications worldwide.
