So why can't modprobe find any of the modules - if indeed that's the problem - cause they're certainly where they're supposed to be.
Looking through the output of
~$ depmod ~$ modprobe -a \*
again suggests to me that it's some sort of dependency or configuration problem... the same comment appears again and again in the output
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
What's that all about?!
--- Russell Shaw <[EMAIL PROTECTED]> wrote: > Simon Tod wrote:
Surely I don't need to do "make modules" and "make modules_install" when I'm not compiling a kernel,
just
installing a pre-built one 2.4.20-686 (and the corresponding kernel-pcmcia-modules file)!? The
output
of
~$ depmod ~$ modprobe -a \*
gives me the lengthy output in the attached file.
How
does this help?
Can you verify this module is actually here?:
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o
What does uname -a show? Don't top-post.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]