linux-mips
[Top] [All Lists]

Re: boot problem for Indy

To: "William J. Earl" <wje@fir.engr.sgi.com>
Subject: Re: boot problem for Indy
From: ralf@uni-koblenz.de
Date: Fri, 28 Aug 1998 01:20:25 +0200
Cc: Arnaud Le Neel <Arnaud.Le.Neel@cyceron.fr>, linux@cthulhu.engr.sgi.com
In-reply-to: <199808272055.NAA06365@fir.engr.sgi.com>; from William J. Earl on Thu, Aug 27, 1998 at 01:55:29PM -0700
References: <35E59FBA.96A1900C@cyceron.fr> <Pine.LNX.3.96.980827131327.10299B-100000@lager.engsoc.carleton.ca> <19980827224215.C19688@aisa.fi.muni.cz> <199808272055.NAA06365@fir.engr.sgi.com>
Sender: owner-linux@cthulhu.engr.sgi.com
On Thu, Aug 27, 1998 at 01:55:29PM -0700, William J. Earl wrote:

>       The PROM on older Indy systems, especially those with R4000
> processors, may only support MIPS ECOFF binaries.  Are you booting an
> ELF or an ECOFF kernel binary?  If you have an ELF kernel binary, and
> it cannot be converted to ECOFF, you may need a two-level loading scheme.
> Note that you could try loading sash from the local disk, and then
> have sash boot vmlinux via bootp(), since sash does know about 
> ELF binaries.

For Indys we currently only build ELF kernels.  I've implemented a clean
solution how to boot ECOFF systems because I needed that for the RC3230,
I'll publish it when it's debugged.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>