loading modules in Fedora 6

[Al Graziano]

Thank you. I was already doing that but my problem at the moment is that 
I have a driver for my wireless card, ipw3945 and that gets loaded even 
if I don't specify it in the modprobe.conf

I installed the driver through rpm so it must have have copied itself to 
a directory where modules are read at boot time. As far as I know 
modules to be loaded are contained in /lib/modules/'uname -r'/... or 
/etc/rc.modules

but when I searched for the ipw3945 driver it, I found it in the 
following directory

/proc/irq/17/ipw3945
/sys/module/ipw3945
/sys/bus/pci/drivers/ipw3945

I cannot find any of the above directories in the init boot scripts ( I 
may not have looked good enough) and that's why I was trying to 
understand how Fedora 6 loads modules at boot time

Thanks again
Al


Antonio Olivares wrote:
> --- Al Graziano <al.graziano at gmail.com> wrote:
>
>   
>> Hello,
>>
>> can anybody point me to some reading to better
>> understand how Fedora 
>> loads modules, in which order and from which
>> directories etc., 
>> especially with regards to Fedora 6. I've read a lot
>> around but nothing 
>> that gives me a firm idea
>>
>> I am trying to understand how I can install certain
>> modules at boot up 
>> and conversely how I can  change a  module from 
>> being installed 
>> automatically to manually using modprobe. In order
>> to do that I need to 
>> know more about modules that installed at bootup
>>
>> Thanks in advance
>> Al
>>
>> -- 
>> fedora-list mailing list
>> fedora-list at redhat.com
>> To unsubscribe:
>> https://www.redhat.com/mailman/listinfo/fedora-list
>>
>>     
>
> If you want to add some modules at bootup, you need to
> add them to /etc/modprobe.conf with a particular line
> for them.  For instance, I have a smartlink modem,
> which gets loaded automatically with the line added to
> modprobe.conf.
>
> [olivares at localhost ~]$ cat /etc/modprobe.conf
> alias eth0 3c59x
> alias snd-card-0 snd-ali5451
> options snd-card-0 index=0
> options snd-ali5451 index=0
> remove snd-ali5451 { /usr/sbin/alsactl store 0
>   
>> /dev/null 2>&1 || : ; }; /sbin/modprobe -r
>>     
> --ignore-remove snd-ali5451
> install slamr modprobe --ignore-install
> ungrab-winmodem ;  modprobe --ignore-install slamr;
> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0
> c 242 0 2>/dev/null && chgrp uucp /dev/slamr0)
>
> To not automatically load them at bootime, there is a
> file /etc/modprobe.d/blacklist which lists the one
> that you do not want loaded at bootup time,
>
> [olivares at localhost ~]$ cat /etc/modprobe.d/blacklist
> #
> # Listing a module here prevents the hotplug scripts
> from loading it.
> # Usually that'd be so that some other driver will
> bind it instead,
> # no matter which driver happens to get probed first. 
> Sometimes user
> # mode tools can also control driver binding.
> #
> # Syntax:  driver name alone (without any spaces) on a
> line. Other
> # lines are ignored.
> #
>
> # watchdog drivers
> blacklist i8xx_tco
>
> # framebuffer drivers
> blacklist aty128fb
> blacklist atyfb
> blacklist radeonfb
> blacklist i810fb
> blacklist cirrusfb
> blacklist intelfb
> blacklist kyrofb
> blacklist i2c-matroxfb
> blacklist hgafb
> blacklist nvidiafb
> blacklist rivafb
> blacklist savagefb
> blacklist sstfb
> blacklist neofb
> blacklist tridentfb
> blacklist tdfxfb
> blacklist virgefb
> blacklist vga16fb
>
> # ISDN - see bugs 154799, 159068
> blacklist hisax
> blacklist hisax_fcpcipnp
>
> Hope this helps,
>
> Antonio 
>
>
>  
> ____________________________________________________________________________________
> 8:00? 8:25? 8:40? Find a flick in no time 
> with the Yahoo! Search movie showtime shortcut.
> http://tools.search.yahoo.com/shortcuts/#news
>
>