What modules are you loading, and what order are you trying to load them in?
I'm guessing that you're trying to load a module that depends on another
module, so insmod won't work unless you get the order right, while modprobe
will check modules.dep and make sure that the symbols are resolved by
loading any dependent modules first.
Good luck,
B. Allyn
on 8/11/00 8:46 PM, Kenneth E. Lussier at [EMAIL PROTECTED] wrote:
> 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?
>
> Kenny
>
> **********************************************************
> 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
> **********************************************************
>
**********************************************************
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
**********************************************************
