From: Wolfgang Denk <wd@denx.de>
To: Cort Dougan <cort@persephone.cs.nmt.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MBX860: How to boot with initrd ?
Date: Sun, 10 Jan 1999 02:53:28 +0100 [thread overview]
Message-ID: <199901100153.CAA18725@denx.muc.de> (raw)
In-Reply-To: Your message of "Sat, 09 Jan 1999 14:40:53 MST." <Pine.LNX.3.96.990109144040.12262A-100000@persephone.cs.nmt.edu>
In message <Pine.LNX.3.96.990109144040.12262A-100000@persephone.cs.nmt.edu> you write:
> How big is your initrd? Try it with a trivial one (~2k or so) and see if
> that works.
I've been playing with a 4 MB initrd (I have 36 MB of RAM on the MBX
board). Just tried a 2kB initrd (empty, not even a filesystem in it);
but at least the kernel should boot, right? It hangs...
Hm... No luck with the latest snapshot of egcs either; it dies with
"Internal compiler error in function emit_move_insn_1"
But ok, the install of linuxppc-R4 on my PowerBook is running with
only minor problems so far...
Ok, now I tryed this with a set of native compilers: egcs-2.90.25 as
comes with linuxppc-R4, then egcs-1.1.1, and the latest egcs-19990103
snapshot:
egcs-19990103 both cross and native: "Internal compiler error in
function emit_move_insn_1" when compiling init/main.c (line
2663).
egcs-1.1.1 both cross and native: compiles fine, but the kernel hangs
egcs-2.90.25 native: compiles fine, and the kernel BOOTS!!! [*All*
configurations I failed to get running with the other
compiler versions run fine when I compile with egcs-2.90.25
from linuxppc-R4!]
Either I am too dumb to build EGCS, or ... Has anybodyy else seen
strange problems with later versions of egcs?
Wolfgang
--
Phone: (+49)-89-95720-110 Fax: (+49)-89-95720-112 wd@denx.muc.de
Office: (+49)-89-722-27328 Wolfgang.Denk@ICN.Siemens.DE
C makes it easy for you to shoot yourself in the foot. C++ makes that
harder, but when you do, it blows away your whole leg.
-- Bjarne Stroustrup
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next parent reply other threads:[~1999-01-10 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.990109144040.12262A-100000@persephone.cs.nmt.edu>
1999-01-10 1:53 ` Wolfgang Denk [this message]
[not found] <19990111114251.006245@smtp.calvacom.fr>
1999-01-11 21:38 ` MBX860: How to boot with initrd ? Wolfgang Denk
[not found] <36986420.3281E1A4@wanadoo.fr>
1999-01-10 22:29 ` Wolfgang Denk
1999-01-08 23:49 Wolfgang Denk
1999-01-09 13:29 ` Wolfgang Denk
1999-01-09 19:29 ` Cort Dougan
1999-01-10 4:57 ` Dan Malek
1999-01-10 22:46 ` Troy Benjegerdes
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=199901100153.CAA18725@denx.muc.de \
--to=wd@denx.de \
--cc=cort@persephone.cs.nmt.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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.