From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Nov 2001 12:41:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Nov 2001 12:40:58 -0500 Received: from vsdc01.corp.publichost.com ([64.7.196.123]:65028 "EHLO vsdc01.corp.publichost.com") by vger.kernel.org with ESMTP id ; Mon, 19 Nov 2001 12:39:11 -0500 Message-ID: <3BF943B9.8080300@vitalstream.com> Date: Mon, 19 Nov 2001 09:39:05 -0800 From: Rick Stevens User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 X-Accept-Language: en-us MIME-Version: 1.0 To: Linux-Kernel , Linux-SCSI Subject: Build problem Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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! - ----------------------------------------------------------------------