.\" This manpage has been automatically generated by docbook2man .\" from a DocBook document.  This tool can be found at:.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>..TH "MODPROBE" "8" "17 January 2004" "" "".SH NAMEmodprobe \- program to add and remove modules from the Linux Kernel.SH SYNOPSIS\fBmodprobe\fR [ \fB-v\fR ] [ \fB-V\fR ] [ \fB-C \fIconfig-file\fB\fR ] [ \fB-n\fR ] [ \fB-i\fR ] [ \fB-q\fR ] [ \fB-o \fImodulename\fB\fR ] [ \fB\fImodulename\fB\fR ] [ \fB\fImodule parameters\fB\fR\fI ...\fR ]\fBmodprobe\fR [ \fB-r\fR ] [ \fB-v\fR ] [ \fB-n\fR ] [ \fB-i\fR ] [ \fB\fImodulename\fB\fR\fI ...\fR ]\fBmodprobe\fR [ \fB-l\fR ] [ \fB-t \fIdirname\fB\fR ] [ \fB-a\fR ] [ \fB\fIwildcard\fB\fR ]\fBmodprobe\fR [ \fB-c\fR ].SH "DESCRIPTION".PP\fBmodprobe\fR intelligently adds or removes amodule from the Linux kernel: note that for convenience, thereis no difference between _ and - in module names.\fBmodprobe\fR looks in the module directory\fI/lib/modules/`uname -r`\fR for allthe modules and other files, except for the optional\fI/etc/modprobe.conf\fR configuration file(see \fBmodprobe.conf\fR(5))..PPNote that this version of \fBmodprobe\fR does notdo anything to the module itself: the work of resolving symbolsand understanding parameters is done inside the kernel.  Somodule failure is sometimes accompanied by a kernel message: see\fBdmesg\fR(8)..PP\fBmodprobe\fR expects an up-to-date\fImodules.dep\fR file, as generated by\fBdepmod\fR (see \fBdepmod\fR(8)).  This file lists what other modules eachmodule needs (if any), and \fBmodprobe\fR uses thisto add or remove these dependencies automatically.  See\fBmodules.dep\fR(5))..PPIf any arguments are given after the\fImodulename\fR, they are passed to thekernel (in addition to any options listed in the configurationfile)..SH "OPTIONS".TP\fB-v --verbose \fRPrint messages about what the program is doing.  Usually\fBmodprobe\fR only prints messages ifsomething goes wrong.This option is passed through \fBinstall\fRor \fBremove\fR commands to other\fBmodprobe\fR commands in theMODPROBE_OPTIONS environment variable..TP\fB-C --config \fRThis option overrides the default configuration file(\fI/etc/modprobe.conf\fR).This option is passed through \fBinstall\fRor \fBremove\fR commands to other\fBmodprobe\fR commands in theMODPROBE_OPTIONS environment variable..TP\fB-c --showconfig \fRDump out the configuration file and exit..TP\fB-n --dry-run \fRThis option does everything but actually insert ordelete the modules (or run the install or removecommands).  Combined with \fB-v\fR, it isuseful for debugging problems..TP\fB-i --ignore-install --ignore-remove \fRThis option causes \fBmodprobe\fR toignore \fBinstall\fR and\fBremove\fR commands in theconfiguration file (if any), for the module on thecommand line (any dependent modules are still subjectto commands set for them in the configuration file).See \fBmodprobe.conf\fR(5)..TP\fB-q --quiet \fRNormally \fBmodprobe\fR will report an errorif you try to remove or insert a module it can't find (andisn't an alias or\fBinstall\fR/\fBremove\fRcommand).  With this flag, \fBmodprobe\fRwill simply ignore any bogus names (the kernel uses thisto opportunistically probe for modules which might exist)..TP\fB-r --remove \fRThis option causes \fBmodprobe\fR to remove,rather than insert a module.  If the modules it depends onare also unused, \fBmodprobe\fR will try toremove them, too.  Unlike insertion, more than one modulecan be specified on the command line (it does not makesense to specify module parameters when removing modules).There is usually no reason to remove modules, but somebuggy modules require it.  Your kernel may not supportremoval of modules..TP\fB-V --version \fRShow version of program, and exit.  See below for caveats when run on older kernels..TP\fB-f --force \fRTry to strip any versioning information from the module,which might otherwise stop it from loading: this is thesame as using both \fB--force-vermagic\fR and\fB--force-modversion\fR.  Naturally, thesechecks are there for your protection, so using this optionis dangerous.This applies any modules inserted: both the module (oralias) on the command line, and any modules it depends on..TP\fB--force-vermagic \fREvery module contains a small string containing importantinformation, such as the kernel and compiler versions.  Ifa module fails to load and the kernel complains that the"version magic" doesn't match, you can use this option toremove it.  Naturally, this check is there for yourprotection, so this using option is dangerous.This applies any modules inserted: both the module (oralias) on the command line, and any modules it depends on..TP\fB--force-modversion \fRWhen modules are compiled with CONFIG_MODVERSIONS set, asection is created detailing the versions of everyinterface used by (or supplied by) the module.  If amodule fails to load and the kernel complains that themodule disagrees about a version of some interface, youcan use "--force-modversion" to remove the versioninformation altogether.  Naturally, this check is therefor your protection, so using this option is dangerous.This applies any modules inserted: both the module (oralias) on the command line, and any modules it depends on..TP\fB-l --list \fRList all modules matching the given wildcard (or "*"if no wildcard is given).  This option is provided forbackwards compatibility: see\fBfind\fR(1) and\fBbasename\fR(1) for a more flexible alternative..TP\fB-a --all \fRInsert all modules matching the given wildcard.  Thisoption is provided for backwards compatibility: see\fBfind\fR(1) and\fBbasename\fR(1) for a more flexible alternative..TP\fB-t --type \fRRestrict \fB-l\fR or \fB-a\fR to modulesin directories matching the\fIdirname\fR given.  This optionis provided for backwards compatibility: see\fBfind\fR(1)and\fBbasename\fR(1) or a more flexible alternative..TP\fB-s --syslog \fRThis option causes any error messages to go through thesyslog mechanism (as LOG_DAEMON with level LOG_NOTICE)rather than to standard error.  This is also automaticallyenabled when stderr is unavailable.This option is passed through \fBinstall\fRor \fBremove\fR commands to other\fBmodprobe\fR commands in theMODPROBE_OPTIONS environment variable..TP\fB--set-version \fRSet the kernel version, rather than using\fBuname\fR(2) to decide on the kernel version (which dictates where tofind the modules).  This also disables backwardscompatibility checks (so \fBmodprobe.old\fR(8) will never be run)..TP\fB--show-depends \fRList the dependencies of a module (or alias), includingthe module itself.  This produces a (possibly empty) setof module filenames, one per line.  It does not run anyinstall commands which might apply.  Note that\fBmodinfo\fR(8)can be used to extract dependencies of a module from themodule itself, but knows nothing of aliases..TP\fB-o --name \fRThis option tries to rename the module which is beinginserted into the kernel.  Some testing modules canusefully be inserted multiple times, but the kernelrefuses to have two modules of the same name.  Normally,modules should not require multiple insertions, as thatwould make them useless if there were no module support..TP\fB--first-time \fRNormally, \fBmodprobe\fR will succeed (and donothing) if told to insert a module which is alreadypresent, or remove a module which isn't present.  This isbackwards compatible with the modutils, and ideal forsimple scripts.  However, more complicated scripts oftenwant to know whether \fBmodprobe\fR reallydid something: this option makes modprobe fail for thatcase..SH "BACKWARDS COMPATIBILITY".PPThis version of \fBmodprobe\fR is for kernels2.5.48 and above.  If it detects a kernelwith support for old-style modules (for which much of the workwas done in userspace), it will attempt to run\fBmodprobe.old\fR in its place, so it iscompletely transparent to the user..SH "ENVIRONMENT".PPThe MODPROBE_OPTIONS environment variable can also be used topass arguments to \fBmodprobe\fR..SH "COPYRIGHT".PPThis manual page Copyright 2002, Rusty Russell, IBM Corporation..SH "SEE ALSO".PP\fBmodprobe.conf\fR(5),\fBlsmod\fR(8),\fBmodprobe.old\fR(8)