From: Ralf Baechle <ralf@uni-koblenz.de>
To: Robert Keller <rck@corp.home.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: after the kernel seems to live
Date: Thu, 27 May 1999 12:18:40 +0200 [thread overview]
Message-ID: <19990527121840.T866@uni-koblenz.de> (raw)
In-Reply-To: <4.1.19990526115716.03f65930@mail>; from Robert Keller on Wed, May 26, 1999 at 12:05:33PM -0700
On Wed, May 26, 1999 at 12:05:33PM -0700, Robert Keller wrote:
> It looks like I've finally been able to get the 2.2.1 kernel booting
> and trying to access its root filesystem over NFS on an NEC
> DDB-VRC5074 development board. I'm at the point where the
> kernel is trying to run /sbin/init and things die because of illegal
> instructions in init (I'm using the little endian mips root from
> linux.sgi.com)
What CPU is being used on that eval board? If it's one that isn't yet
supported in our sources then I suspect you have a problem either with the
cacheflushing routines themselfes or the calls to them in the network
driver. What NIC are you using, btw? We've got patches around for a
couple of those which are most often being used with MIPS machines.
> Where do I get the code for init, ld.so and all those vital root
> filesystem friends so that I can be sure that they are compiled
> the way I want them?
Unless you're using extremly old binaries I'm highly confident that the
binaries which you are using are ok.
Ralf
next prev parent reply other threads:[~1999-05-27 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-26 19:05 after the kernel seems to live Robert Keller
1999-05-26 20:22 ` Harald Koerfgen
1999-05-27 10:18 ` Ralf Baechle [this message]
1999-05-27 20:03 ` Robert Keller
1999-05-27 22:46 ` Ralf Baechle
1999-06-02 16:35 ` Robert Keller
1999-06-02 17:56 ` William J. Earl
1999-06-02 21:32 ` Robert Keller
1999-06-02 22:33 ` Ralf Baechle
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=19990527121840.T866@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=rck@corp.home.net \
/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.