All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jake Griesbach <griesbac@gamera.colorado.edu>
Cc: linux@cthulhu.engr.sgi.com, ralf@uni-koblenz.de
Subject: Re: Linux/Mips installation
Date: Thu, 11 Mar 1999 01:00:22 +0100	[thread overview]
Message-ID: <19990311010022.A1006@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.3.96.990310155606.22494A-100000@gamera.colorado.edu>; from Jake Griesbach on Wed, Mar 10, 1999 at 04:02:08PM -0700

On Wed, Mar 10, 1999 at 04:02:08PM -0700, Jake Griesbach wrote:
> That was it!  I removed the CDROM and internal floptical drive, and the
> installation proceeded.  However, now I get the prom error when rebooting
> that is caused by elf kernels on old proms:
> 
> Cannot load bootp()/vmlinux
> Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC.

The kernel worked before the installation and doesn't afterwards ? Strange.

> I tried downloading the ecoff kernel you posted in the test directory, but
> I still get the error.  Maybe I haven't installed it correctly, or maybe I
> am not typing the correct boot command.

Really the same error ? The 0x7f45 is part of the elf magic, which the
ECOFF doesnt contain for sure (at least not at the beginning of the file).

> I have unzipped the ecoff kernel and placed it in the installation (remote
> computer's) root directory.  (It does boot over NFS into the installation

If you boot via tftp, you need to put new kernel in your /tftp directory 
(like you did it with the other kernel).

> script.)  I have verified the kernel installed on the local drive after
> installation is the same size.  (I simply copied it over to the local
> drive.)  Do I have to run something equivalent to lilo??

Right now, you have two choices for booting the kernel. Either use
bootp/tftp or put it on your Irix root partition and boot with 
"boot vmlinux root=/dev/sdc1" (or the approriate /dev/sdxx).

Thomas.

-- 
   This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
                                        [Martin `MJ' Mares on linux-kernel]

  reply	other threads:[~1999-03-11  0:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-08 16:57 Linux/Mips installation Jake Griesbach
1999-03-09 20:47 ` Thomas Bogendoerfer
1999-03-09 21:34   ` Jake Griesbach
1999-03-09 22:11     ` Thomas Bogendoerfer
1999-03-09 22:43       ` Jake Griesbach
1999-03-09 23:22         ` Thomas Bogendoerfer
1999-03-10 23:02           ` Jake Griesbach
1999-03-11  0:00             ` Thomas Bogendoerfer [this message]
1999-03-11 17:44               ` Jake Griesbach
1999-03-11 22:25                 ` ralf

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=19990311010022.A1006@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=griesbac@gamera.colorado.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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.