public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SPATZ1@t-online.de (Frank Schneider)
To: "Mark A. Tagliaferro" <be_lak@yahoo.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problems with compiling kernel.
Date: Thu, 30 Aug 2001 19:31:29 +0200	[thread overview]
Message-ID: <3B8E7871.81CF6E13@t-online.de> (raw)
In-Reply-To: <20010830103609.96135.qmail@web14701.mail.yahoo.com>

"Mark A. Tagliaferro" schrieb:
> 
> 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.
> 
(..)
> Any idea as to what I'm doing wrong?

Not clearly, but try the following:
Configure your Kernel and then add in the Toplevel-Makefile
(/usr/src/linux/Makefile) an "extra-Subrevision", e.g. 

-------
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 3
EXTRAVERSION = -12-TEST
 
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
---------

Then compile.
The effect is, that now all the module-path and revision-numbers contain
this extra-info and you can easily track were the "right" modules are
stored and build.

Before you do a "make modules_install", delete the complete old
Module-Path (save the modules in another place if your are unsure), so
even the path has to be made new.
I had already strange problems with "make modules_install" not
overwriting old modules or deleting old ones that are not used any more.

> 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)?

If you have "/" on a SCSI-Disk, you cannot boot and then load the
module...you would have to build a initrd-ramdisk, but i would suggest
to build in the SCSI-Support.
If you have "/" on an IDE-Drive you can build the SCSI-Support as Module
and then load it during bootup.

Solong..
Frank.

--
Frank Schneider, <SPATZ1@T-ONLINE.DE>.                           
Microsoft isn't the answer.
Microsoft is the question, and the answer is NO.
... -.-

      parent reply	other threads:[~2001-08-30 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 10:36 Problems with compiling kernel Mark A. Tagliaferro
2001-08-30 13:05 ` Luigi Genoni
2001-08-30 17:31 ` Frank Schneider [this message]

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=3B8E7871.81CF6E13@t-online.de \
    --to=spatz1@t-online.de \
    --cc=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