Module not found when I do a modprobe

linux linux-device-driver
robert trudel picture robert trudel · Jan 14, 2016 · Viewed 67.3k times · Source

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.

Answer

thkala picture thkala · Jan 14, 2016

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.

Related questions

"FATAL: Module not found error" using modprobe

I have a problem with modprobe command... I compiled the hello world module and loaded it with insmod, it works fine and when I do lsmod, I can see it in the output list. But when I insert this module …

Read More
IOCTL Linux device driver

Can anyone explain me, What is IOCTL? What is it used for? How can I use it? Why can't I define new function that does the same work as IOCTL?

Read More
why is u8 u16 u32 u64 used instead of unsigned int in kernel programming

I see u8 u16 u32 u64 data types being used in kernel code. And I am wondering why is there need to use u8 or u16 or u32 or u64 and not unsigned int?

Read More