disabling modules at boot time

[Wade Hampton]

On my x86 Fedora Core 4 box, I am trying to disable the wct4xxp and
zaptel drivers from starting at boot time and have removed them from
the modprobe.conf and removed the zaptel file from modprobe.d, yet
they STILL get loaded when I boot.  If I add "alias wct4xxp off" to
the modprobe.conf file, I can't modprobe them later.  Also, I added
them to the /etc/modprobe.d/blacklist-compat and they are still
loaded.

How can I disable them (so I can manually load them if I want)?  Is
there a hidden modprobe option?

Thanks,
--
Wade Hampton

[Nigel Henry]

On Wednesday 09 May 2007 20:29, Wade Hampton wrote:
>  On my x86 Fedora Core 4 box, I am trying to disable the wct4xxp and
>  zaptel drivers from starting at boot time and have removed them from
>  the modprobe.conf and removed the zaptel file from modprobe.d, yet
>  they STILL get loaded when I boot.  If I add "alias wct4xxp off" to
>  the modprobe.conf file, I can't modprobe them later.  Also, I added
>  them to the /etc/modprobe.d/blacklist-compat and they are still
>  loaded.
>
>  How can I disable them (so I can manually load them if I want)?  Is
>  there a hidden modprobe option?
>
>  Thanks,
>  --
>  Wade Hampton 
How about putting a couple of lines in /etc/rc.d/rc.local. This way you can 
remove the modules after they have been loaded, and gives you the option to 
modprobe them later.

rmmod wct4xxp
rmmod zaptel

Depending on the modules you may have to use "modprobe -r" rather than 
"rmmod".

Just a thought, and have found that rc.local has been usefull is solving a few 
problems like yours.

Nigel.

[Wade Hampton]

Good idea except when the original modprobe could cause a lockup of
the box....  I was hoping there was a clean way of preventing a module
from loading at startup via modprobe but then later being able to
modprobe the module.

My solution is to add this to /etc/modprobe.conf
  alias wct4xxp off
  alias zaptel off

And when I need them:
  /sbin/modprobe crc_ccitt
  /sbin/insmod /lib/modules/$(uname -r)/misc/zaptel.ko
  /sbin/insmod /lib/modules/$(uname -r)/misc/wct4xxp/wct4xxp.ko

Not clean at all and more of a hack.  There should be SOME way of
delaying loading of modules at powerup time.
--
W

[Matthew J. Roth]

Wade Hampton wrote:
>  Not clean at all and more of a hack.  There should be SOME way of
>  delaying loading of modules at powerup time. 
Wade,

Are you sure that the zaptel init script isn't running at boot?  What 
does "chkconfig --list zaptel" display?

Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer

[Wade Hampton]

The zaptel script is not listed (nothing is returned by the chkconfig
--list zaptel).  However, I found that I had a line in my
/etc/rc.local -- left over from WAY back....  Thanks.
--
W

[Development discussions related to Fedora]

Wade Hampton wrote:
>  Good idea except when the original modprobe could cause a lockup of
>  the box....  I was hoping there was a clean way of preventing a module
>  from loading at startup via modprobe but then later being able to
>  modprobe the module. 
After some list/bugzilla problems with trying to disable loading ipv6 on 
my machines, various mentioned the correct way would be:

in /etc/modprobe.conf:
install wct4xxp /sbin/true
install zaptel /sbin/true

I think this essentially informs the module loader that if it is asked 
to install the particular module, that it should return true {success}, 
but not actually do anything.

If you want to load it later, the same conf would be blocking the load ;(

DaveT.

[Tony Nelson]

At 2:56 PM +1000 5/12/07, David Timms wrote:
> Wade Hampton wrote:
> > Good idea except when the original modprobe could cause a lockup of
> > the box....  I was hoping there was a clean way of preventing a module
> > from loading at startup via modprobe but then later being able to
> > modprobe the module.
>
> After some list/bugzilla problems with trying to disable loading ipv6 on
> my machines, various mentioned the correct way would be:
>
> in /etc/modprobe.conf:
> install wct4xxp /sbin/true
> install zaptel /sbin/true
>
> I think this essentially informs the module loader that if it is asked
> to install the particular module, that it should return true {success},
> but not actually do anything.
>
> If you want to load it later, the same conf would be blocking the load ;( 
Maybe modprobe -i would work, or insmod which claims to be stupider than
modprobe.
-- 
____________________________________________________________________
TonyN.:'                       <mailto:[e-mail]>
      '                              <http://www.georgeanelson.com/>

[Phil Meyer]

Wade Hampton wrote:
>  On my x86 Fedora Core 4 box, I am trying to disable the wct4xxp and
>  zaptel drivers from starting at boot time and have removed them from
>  the modprobe.conf and removed the zaptel file from modprobe.d, yet
>  they STILL get loaded when I boot.  If I add "alias wct4xxp off" to
>  the modprobe.conf file, I can't modprobe them later.  Also, I added
>  them to the /etc/modprobe.d/blacklist-compat and they are still
>  loaded.
>
>  How can I disable them (so I can manually load them if I want)?  Is
>  there a hidden modprobe option?
>
>  Thanks,
>  -- 
>  Wade Hampton
>  
Isn't /etc/modprobe.d/blacklist-compat just an example file?
I think you need to put them in /etc/modprobe.d/blacklist for them to be 
blacklisted.