From: Israel Alvarez <ia@innovatech.dk>
To: linux-kernel@vger.kernel.org
Subject: can't find module ...
Date: Tue, 5 Feb 2002 16:03:28 +0100 [thread overview]
Message-ID: <02020516032802.01346@leon> (raw)
Hi!,
I've just compile the kernel 2.4.17 in my linux 7.2 and installed it in my
embedded device running 2.2.18. I have followed all the instructions about
make modules install_modules and so on.
-> I have the modutils 2.1.121.
-> I have the modules in
/lib/modules/2.2.17/...
-> and I have also updated my modules.conf with the new paths, something like:
path[drivers]=/lib/modules/2.4.17/kernel/drivers/
path[net]=/lib/modules/2.4.17/kernel/net/
and so on
Errors:
-> My modules.dep is empty, and I know I have several dependencies and depmod
-a is executed while loading.
-> If I use insmod with the absolute path, then it works, but if I try to use
modprobe, it does not work ( can't locate module...).
-> When I use modprobe -c I get three differents paths for each
modue:
path[drivers]=/lib/modules/2.4.17/kernel/drivers/
...
path[drivers]=/lib/modules
....
path[drivers]=/lib/modules/default
So, What happens here? Is there any other file still storing the old paths
and I should modify it? Are these paths stored in the kernel itself so is
impossible to change then?
Thanks in advance.
ia
reply other threads:[~2002-02-05 15:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02020516032802.01346@leon \
--to=ia@innovatech.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox