modprobe a new driver

mstahl · 09-15-2005, 12:12 AM

I built a vt1211.ko file which I want to install using modprobe. Whenever I "modprobe vt1211" I get the error "FATAL: Module vt1211 not found."

The compiled .ko file is still in my /usr/src/vt1211 directory. Do I have to move it somewhere (or create a symlink)? How do I make modprobe find this file?

(insmod vt1211.ko works fine, but I want to use modprobe).

Thanks,
M

Matir · 09-15-2005, 12:20 AM

modprobe looks in the tree in '/lib/modules/`uname -r`/' for the modules.

ocgltd · 09-15-2005, 12:25 AM

I put a symlink in that directory, pointing to my vt1211.ko file. It still wouldn't modprobe (same error).

I don't see ANY .ko files in that dir either...

Matir · 09-15-2005, 12:49 AM

The modules directories are a whole hierarchy of modules. I'm also pretty sure that modprobe will refuse to insert (and rightly so) any modules not owned by root. And, hopefully, any modules world-writable. You don't want modules controlled by some user getting installed.

For network cards, they are often in /lib/modules/`uname -r`/kernel/drivers/net.

ocgltd · 09-15-2005, 09:20 AM

Well, I put my vt1211.ko into the appropriate subdir, and ensure the permissions and ownership were as you suggested (which also matched other .ko in the same directory). Still the same error...

Is there a command/.conf file I can check to see where modprobe is looking for .ko files? Do I have to recompile the kernel for this to be seen?

Matir · 09-15-2005, 10:45 AM

It should automatically pick it up in that directory without a problem.

mickeyboa · 09-15-2005, 09:07 PM

If you compiled the module with a different gcc than your kernel you will have this problem.
I had to do a insmod path/module.ko to get it to load module, modprobe wouldn't do it.

Jim