[9309] in linux-scsi channel archive
Re: Kernel Panic at Boot
daemon@ATHENA.MIT.EDU (Eddie Williams)
Mon Aug 7 08:31:06 2000
Message-Id: <200008071222.IAA02119@aslan.sc.steeleye.com>
To: linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
In-Reply-To: Message from andy thomas <andy@ic.ac.uk>
of "Mon, 07 Aug 2000 11:01:03 BST." <Pine.LNX.4.20.0008071057090.10778-100000@anahata.ma.ic.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 07 Aug 2000 08:22:12 -0400
From: Eddie Williams <Eddie.Williams@SteelEye.com>
>
You can still have the SCSI driver as a module but you will need a RAM disk
(with the SCSI module on the RAM disk of course) so that the driver can be
loaded. Compiling the driver into the kernel does simplify things in that you
may not have to need to worry about a RAM disk which can be a pain to build on
a system. However having a RAM disk makes life a lot easier if you are doing
any kind of "generic" builds.
Eddie
>
> On Sun, 6 Aug 2000, Mahesh Mahadevan wrote:
>
> > Hi All,
> >
> > Please ignore my previous mail.
> >
> > I figured out the cause and solution of the problem (I
> > had to compile the scsi controller driver into the
> > kernel, rather than having it as a module -- which is
> > the default).. sorry for that junk mail..
>
> Systems that boot from a SCSI disk should always have the SCSI driver
> compiled into the kernel. Loading it as a module won't work as how can
> the kernel access the module file from the disk if it has no SCSI driver?
>
> I've seen this happen ;-)
>
> cheers,
>
> Andy
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
