custom kernel, can't modprobe

juanbobo · 2013-11-25 20:58:07

i've compiled a custom kernel outside of abs and have build a custom nvidia module in abs. i can't modprobe the module, but if i insmod it then it works fine. i'm running kernel 3.12.1 and the module is in /usr/lib/modules/extramodules-3.12.1-ARCH

falconindy · 2013-11-25 23:14:34

If you can't modprobe, then depmod. The former relies on output from the latter.

If that still doesn't work, then your /usr/lib/depmod.d/search.conf is suspect. It should contain only "search updates extramodules built-in" (ignoring comments).

edit: uggh, misread. You can't possibly have the module for your custom kernel in the -ARCH kernel directory and expect modprobe to be able to find it. You must install it under /usr/lib/modules/$(uname -r)/. Former advice about depmod is still mostly relevant....

Last edited by falconindy (2013-11-26 00:54:13)

juanbobo · 2013-11-26 11:15:21

thanks for your reply, i figured it out. basically i had a vanilla kernel, not from abs, and so it wouldnt utilize the extramodules directory like an abs kernel would.

falconindy · 2013-11-26 12:11:53

That doesn't make sense, but OK.

juanbobo · 2013-11-26 12:53:46

For whatever reason with a vanilla kernel modprobe will not look in the extramodules directory.

juanbobo · 2013-11-26 13:25:49

All that's going on is in the arch kernel directory there is a symlink for the extramodules directory.

falconindy · 2013-11-26 14:08:25

juanbobo wrote:

For whatever reason with a vanilla kernel modprobe will not look in the extramodules directory.

Sure it will -- it has absolutely nothing to do with the kernel itself. /usr/lib/depmod.d/search.conf ensures that the extramodules directory for any given kernel will be searched in during index creation (by depmod). Subsequent runs of modprobe will use this index and find the module in the extramodules directory.

Your misunderstanding seems to stem from the fact that you're expecting modules from one module tree to be loaded by another. That isn't how kmod (or module-init-tools for that matter) worked. It relies on finding modules under "/usr/lib/modules/$kernver" where $kernver is the magic string that identifies the kernel you're interested in. If this magical string is 3.12.1-goats, then you should only ever expect modprobe and depmod to look for modules for this kernel under /usr/lib/modules/3.12.1-goats.

Last edited by falconindy (2013-11-26 14:55:26)

juanbobo · 2013-11-26 16:01:19

depmod by default searches for the subdir extramodules in the kernel directory, which in an arch kernel package points to the directory containing the extra modules, but in a vanilla kernel this symlink has to be created manually if the modules are in that directory.

Arch Linux

#1 2013-11-25 20:58:07

custom kernel, can't modprobe

#2 2013-11-25 23:14:34

Re: custom kernel, can't modprobe

#3 2013-11-26 11:15:21

Re: custom kernel, can't modprobe

#4 2013-11-26 12:11:53

Re: custom kernel, can't modprobe

#5 2013-11-26 12:53:46

Re: custom kernel, can't modprobe

#6 2013-11-26 13:25:49

Re: custom kernel, can't modprobe

#7 2013-11-26 14:08:25

Re: custom kernel, can't modprobe

#8 2013-11-26 16:01:19

Re: custom kernel, can't modprobe

Board footer