From: "Mark A. Tagliaferro" <be_lak@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Problems with compiling kernel.
Date: Thu, 30 Aug 2001 11:36:09 +0100 (BST) [thread overview]
Message-ID: <20010830103609.96135.qmail@web14701.mail.yahoo.com> (raw)
I'm using SuSE 7.1 and I had to compile the kernel to include SCSI support.
That part is all well and good. The problems started when I tried to set up
masquerading. Modprobe is returning the following error:
modprobe: Can't open dependencies file /lib/modules/2.4.2/modules.dep (No such
file or directory)
I looked in /lib/modules/ and there the directory is called 2.4.2-4GB and not
2.4.2
I tried to fool it by creating a virtual link to the directory with the name
2.4.2 but then the modprobe returns a large number of kernal mismatch errors
that the particular modules (iptable_nat) I am trying to run were written for
kernel version 2.4.2-4GB and not 2.4.2
It looks like modprobe is looking for kernel version 2.4.2 but the modules are
for kernel 2.4.2-4GB.
Incidentally I have another machine with the standard kernel that YaST installs
on which modprobe works well and the directory in /lib/modules/ is calle
2.4.2-4GB.
Any idea as to what I'm doing wrong?
Did I have to recompile the kernel to load the aic7xxx or could I have added a
command in some initialisation file to load it as a module (insmod)?
Regards
Mark
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
next reply other threads:[~2001-08-30 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 10:36 Mark A. Tagliaferro [this message]
2001-08-30 13:05 ` Problems with compiling kernel Luigi Genoni
2001-08-30 17:31 ` Frank Schneider
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=20010830103609.96135.qmail@web14701.mail.yahoo.com \
--to=be_lak@yahoo.co.uk \
--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