Re: How to check if driver is in-built or module?

[Greg KH <greg@kroah.com>]

On Sat, Mar 04, 2006 at 04:49:43AM +0200, juuso.alasuutari@tamperelainen.org wrote:
> > > How can I tell udev to modprobe <module> only if <module> exists and hasn't
> > been
> > > compiled in the kernel? In my experience modules are visible to udev only
> > when
> > > and after they are loaded, which makes finding a solution to my problem a
> > bit
> > > of a paradox.
> >
> > Look in /sys/module/  That will have the module name if the module is
> > loaded _or_ if the module is built into the kernel.
> >
> > If it's not there, then it should be safe to load it.
> 
> Thanks, that helped a lot. I wrote the following rules for snd_pcm_oss and rtc
> based on your hint:
> 
> # Load ALSA OSS emulation sound module if not already loaded.
> KERNEL!="snd_pcm_oss", SUBSYSTEM!="module", ACTION="add", RUN+="/sbin/modprobe
> snd_pcm_oss"
> 
> # Load real time clock module if not already loaded.
> KERNEL!="rtc", SUBSYSTEM!="module", RUN+="/sbin/modprobe rtc"

No, this kind of thing belongs in your distro's "load these modules at
boot time" list.  Everyone has this, it's just in different locations
(/etc/sysconfig/modules in SuSE, /etc/modules.autoload/kernel-2.6/ for
Gentoo, etc.)

Don't mess with udev rules for things like this, it's just not worth it.
Use the infrastructure that is already present and solves this today.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel