[LCP]how to obtain a list of installed device drivers on a Li nux box

[Luciano A. Stertz]

    The available device drivers are located on the /lib/modules/`uname -r`/ directory.
    The used/loaded device drivers can be seen thru the /proc/modules file, or with the
lsmod command. However, any device driver built-in on the kernel will not be shown. I have
no idea about how to discover what modules are running on the kernel. The tip is to look
the /proc/devices file. But many device drivers don't register any device...

    Sorry the bad english...

    Luciano


On Tue, 26 Mar 2002 09:01:50 -0600
Shalabh_Sharma at Dell.com wrote:

> Quer ter seu próprio endereço na Internet?
> Garanta já o seu e ainda ganhe cinco e-mails personalizados.
> DomíniosBOL - http://dominios.bol.com.br
> 
> 
> 
> 
> 
> 
> I am trying to make a tool which tells the user which device drivers are
> installed on his/her system and which of those a currently being
> used/loaded.
> This is possible in windows, I just want to know is there a way to do this
> in Linux ?
> 
> -----Original Message-----
> From: mulix [mailto:mulix at actcom.co.il]
> Sent: Monday, March 25, 2002 4:51 PM
> To: linuxcprogramming at lists.linux.org.au
> Subject: Re: [LCP]how to obtain a list of installed device drivers on a
> Li nux box
> 
> 
> On Mon, Mar 25, 2002 at 04:48:22PM -0600, Shalabh_Sharma at Dell.com wrote:
> > 
> > I know that lsmod will give the list of loaded modules, but it also gives
> a
> > list of file systems loaded eg: ext-3, smbfs.
> > I want to know which device drivers are currently installed on the system,
> > and which of those are being used currently minus the file systems.
> > If possible I would also like to get their location, description and
> version
> > info. modinfo gives this to a certain degree, but not for the device
> drivers
> > which are installed but are not currently loaded.
> 
> i'm afraid that in the context of linux, your question makes no
> sense. some "device drivers" can be compiled into the kernel, some can
> be modules which are loaded into the kernel, some can be modules which
> are in a non standard location, some can be compiled as the system is
> running and automatically loaded into the kernel, etc, etc. 
> 
> again, please explain what you're trying to do. you're asking the
> wrong question, and therefore getting the wrong answer. 
> 
> hope this helps, 
> -- 
> The ill-formed Orange
> Fails to satisfy the eye:       http://vipe.technion.ac.il/~mulix/
> Segmentation fault.             http://syscalltrack.sf.net/
> 
> _______________________________________________
> This is the Linux C Programming List
> :  http://lists.linux.org.au/listinfo/linuxcprogramming List
> 
> _______________________________________________
> This is the Linux C Programming List
> :  http://lists.linux.org.au/listinfo/linuxcprogramming List
>