Re: Loadable kernel modules not unloadable
On 12 Jan 2006 00:45:10 -0800
"hillbilly" <bennitech@bluep.com.au> wrote:
> Just a question to Marc Perrudin...
> In directory /etc/ only have a modprobe.d/ directory. Should the
> 'local' file be in there or should I create an /etc/modprobe.conf/
> directory as indicated in your response and place the 'local' file in
> that one instead?
If you wanted to create modprobe.conf it should be a
file /etc/modprobe.conf, but if you create it then the stuff
in /etc/modprobe.d will stop being processed. So unless you want to
manage everyting yourself it is best just to create a file
in /etc/modprobe.d of whatever name fits the prurpose you are creating
it for. If it is specifically to keep the parport module from loading
then call it parport.
Normally the only modules I have to remove are ivtv or orinoco_pci. To
do this I open a terminal window and type one of the following:
modprobe -r ivtv
modprobe -r orinoco_pci
: All modules that were loaded as dependencies should also be removed
when this is done. For example ivtv is dependant on tuner so if I
remove ivtv tuner is also removed, but if for some reason I loaded
tuner seperately before loading ivtv then removing ivtv would not
cause tuner to be removed.
Later, Seeker
Reply to: