sorry...mistake in my question...just i want to know from which path the "modules" are loaded when kernel boots?

by using google i found that /etc/modprobe.d/aliases is the path to load the modules when kernel boots....but i saw the file /etc/modules i get confussed...
The o/p of that file tells that its the file used to load the modules when kernel boots...i dont know which is the correct one...can anyone help me...

I believe you need more than usbcode to make your usb device work. What you need depends on then device...

No friend...just i know the content of the above files and purpose of that above files..so that i can easyly do my work...

Ok, here goes:

/etc/modules for your distribution is likely where the list of modules that are loaded at boot time resides.
/etc/modprobe.d/alias (on my box its /lib/modules/2.6.24.5/modules.alias) is a list of module names linked to the path of the module on the HDD (Hence why it is called alias. Aliasing is a common theme in linux, especially when it comes to configuring bash).
Those aliases are what you call when you use the modprobe command, i.e.

root@yourbox:/# modprobe usbserial

usbserial is an alias for on of the usb modules, which is actually located at /lib/modules/2.6.24.5/kernel/drivers/usb/serial/usbserial.ko. As you can see, typing usbserial as opposed to the full path is much more convenient, so modprobe and depmod maintain the alias list for you to make things a bit easier :-).

Thanks a lot gankoji
you said that /etc/modules for my distribution will have the list of modules which is used to load at boot time...but there is no modules list..only "fuse" and "lp" is there..can you tell me why it is like that?

Dont know what to do...kindly refer my post and reply me.....so confussed due to this.....

Because fuse and lp are modules. That's apparently the complete list in your file. I think other modules can get loaded when the relevant hardware is detected during the boot process, but it's been awhile since I dealt with this and how it's done depends on the distro.

Anyhow, modprobe looks for modules in /lib/modules/(your kernel version) ... you can get your kernel version with the uname -r command. The module files themselves generally have a .ko extension for version 2.6 kernels.

WOAH!

This thread is going nowhere fast.

The context: Please read shariefbe's previous post here: http://www.linuxquestions.org/questi...dprobe-690332/

shariefbe has recompiled the kernel (we haven't been told how or why)

Now things aren't working as expected (Surprise!?)

So please do not assume (s)he is running a standard kernel.

Mods, can you please merge these two threads?

yes tredegar....please see post number 11 in this thread.....i already said the things which i done previously...so i want the solution for this thread question...

i will tell the things...please tell me whether it is correct or not..actually the kernel looks up from "/etc/modprobe.d/aliases" for the modules...from that if that modules needs any dep module then it will search in "/lib/modules/uname -r"...This "/etc/modpobe.d/aliases" modules installed after the dep module is installed from the kernel path....

i dont know whether am i right or not...if am wrong please forgive me and correct it...Thanks