All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Stevens <rstevens@vitalstream.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>,
	Linux-SCSI <linux-scsi@vger.kernel.org>
Subject: Build problem
Date: Mon, 19 Nov 2001 09:39:05 -0800	[thread overview]
Message-ID: <3BF943B9.8080300@vitalstream.com> (raw)

This is a repost, as I've not seen a response.  Feel free to respond
to me directly if it seems more appropriate.  I've done a bit of
updating too, as this ugly beast reared it's head on a second machine
this weekend.  This has been driving me nuts for days!  I need some
help!

This may or may not have been discussed.  Yesterday, I was building
2.4.14 (yes, a bit behind the time) for a system where the root
filesystem lives on a Symbios 53c8xx SCSI drive.  I built the system
as fully modularized (the root driver and such were modules).  When
I finally got around to building the initrd image, I noticed that
the scsi_mod.o and sd_mod.o drivers were NOT loaded into the ramdisk
image.

Hmmm, I said to myself.  I looked at the
/lib/modules/2.4.14/kernel/drivers/scsi directory and discovered that
scsi_mod.o and sd_mod.o weren't present!  Looking back at the source
tree, they had indeed been built.  Apparently the "make modules_install"
didn't move them to the /lib tree.  So I copied them manually,
re-depmoded it and re-built the initrd image.  This time, the scsi_mod
and sd_mod modules WERE inserted into the ramdisk image.  However, when
booting using that image, neither scsi_mod nor sd_mod are loaded.  The
sym53c8xx driver DOES load, but we have an instant panic because the
root filesystem can't be found.

ADDITION: Same bloody thing happened on a different machine where the
root filesystem lives on a dpt_i2o SCSI RAID module.

What am I doing wrong here?  Is "make modules_install" broken in 2.4.14?
Am I suffering from a short between the keyboard and floor?  For
further info, this is a baseline RedHat 7.1 system, but I want the
2.4.14 kernel (the virtual memory system seems to work better for
our purposes than that found in kernels <= 2.4.9 and no, I don't
want to get into a discussion about the merits of the aa and ac
VM systems).


P.S. I'm posting this to linux-kernel and linux-scsi.  Someone should
be able to tell me what I did wrong.

----------------------------------------------------------------------
- Rick Stevens, SSE, VitalStream, Inc.      rstevens@vitalstream.com -
- 949-743-2010 (Voice)                    http://www.vitalstream.com -
-                                                                    -
-      Try to look unimportant--the bad guys may be low on ammo!     -
----------------------------------------------------------------------


             reply	other threads:[~2001-11-19 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 17:39 Rick Stevens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-07  5:45 build problem kapetr
2014-05-07  6:22 ` Hans Verkuil
2002-05-12 15:32 Ken Martwick
2002-05-12 18:47 ` Riley Williams
     [not found] <Pine.GSU.4.21.0205102245180.1389-100000@garcia.efn.org>
2002-05-12  8:06 ` Riley Williams
2002-05-08 21:14 Ken Martwick
2002-05-09  8:29 ` Javier Sedano
2002-05-10 21:47 ` Riley Williams
2001-11-16 23:56 Build problem Rick Stevens

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=3BF943B9.8080300@vitalstream.com \
    --to=rstevens@vitalstream.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.