Some modules require things that are provided by other modules.
modprobe loads all required modules, and insmod doesn't. Simple enough..
;-P If you do a modprobe, you'll notice that most likely there is at least
one other module that has the module you loaded in the 'used by'. If you
then instead insmod the needed modules, and THEN the module you where
attempting to load, they load fine.. And example is many of the card
specific modules, in my case emu10k1. Nearly all of the sound drivers also
require a module named soundcore. soundcore provides symbols required by
the sound driver. If it is not loaded first, then the insmod fails. In the
case of modprobe, it sees that the sound driver requires symbols provided
for by soundcore, and loads soundcore first.
----- Original Message -----
From: Kenneth E. Lussier <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 11, 2000 10:46 PM
Subject: modprobe Vs. insmod
> All,
>
> I have never seen this before, but I'm betting someone else
> has.... I built a kernel, and none of the modules load at boot
> time. Not unusual, since they aren't really needed. However, if I
> use insmod to try to load them, then I get a list of unresolved
> symbols. But, if I use modprobe, they load with no complaints.
> Does anyone know why this is?
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
