From: Tom Woelfel <eedthwo@eede.ericsson.se>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: eedthwo@eede.ericsson.se, linux@cthulhu.engr.sgi.com
Subject: Re: Illegal f_magic number while install-procedure
Date: Wed, 10 Mar 1999 10:20:19 +0100 [thread overview]
Message-ID: <199903100920.KAA01213@sun168.eu> (raw)
In-Reply-To: <19990309000234.A2804@alpha.franken.de>
Thomas Bogendoerfer writes:
> On Mon, Mar 08, 1999 at 01:47:03PM +0100, Tom Woelfel wrote:
> > Cannot load bootp()/vmlinux
> > Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC.
>
> your prom is too old to understand ELF files. To solve this problem you
> need either a newer prom or an Indy kernel in ECOFF format.
>
> I've successful booted a converted kernel a few minutes ago and will upload
> this kernel to
>
> ftp://ftp.linux.sgi.com/pub/linux/mips/test/vmlinux-indy-2.2.1-990226.ecoff.gz
>
> Please try it.
My Indy has seen the light ;-). The kernel boots and goes it's way
through the device checking. All disk's are recognized and the
mount-request for the root-file-system is send to the server. The
(root)-dir is mounted from the Indy. (I can see this in the server-log)
Then the prom-memory is freed and the last thing I see is:
freeing unused kernel memory 52k
Then nothing happens anymore. I think the next thing to come should be
the 'init' process (init doesn't need to be an ECOFF - exec ?).
Or do I nedd a modified init to jump into setup?
partial sucess,
Tom
next prev parent reply other threads:[~1999-03-10 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-08 12:47 Tom Woelfel
1999-03-08 12:47 ` Tom Woelfel
1999-03-08 23:02 ` Illegal f_magic number while install-procedure Thomas Bogendoerfer
1999-03-10 9:20 ` Tom Woelfel [this message]
1999-03-10 16:53 ` ralf
1999-03-10 23:27 ` Thomas Bogendoerfer
1999-03-12 7:44 ` Tom Woelfel
-- strict thread matches above, loose matches on Subject: below --
1999-03-08 13:16 Tom Woelfel
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=199903100920.KAA01213@sun168.eu \
--to=eedthwo@eede.ericsson.se \
--cc=linux@cthulhu.engr.sgi.com \
--cc=tsbogend@alpha.franken.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.