From: Brian Waite <bwaite@cspi.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: trying to boot linux on a MVME5100
Date: Wed, 29 Aug 2001 17:23:28 -0400 [thread overview]
Message-ID: <200108292131.RAA06726@orchid.cspi.com> (raw)
In-Reply-To: <85256AB7.00710F8A.00@pine.cspi.com>
I just tried again and no zImage.inird.* gets created. I am going to pull the
newest 2.4.10pre1 changes and see if those help.
Thanks
Brian
--
Brian Waite
Looking for a TeraFLOP in a closet
www.fastcluster.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-08-29 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85256AB7.00710F8A.00@pine.cspi.com>
2001-08-29 21:23 ` Brian Waite [this message]
[not found] <85256AB7.00607D65.00@pine.cspi.com>
2001-08-29 20:02 ` trying to boot linux on a MVME5100 Brian Waite
2001-08-29 16:58 ` Matt Porter
2001-08-29 21:26 ` Scott Anderson
2001-08-29 23:32 ` Tom Rini
2001-08-30 0:31 ` Tom Rini
2001-08-29 14:50 Xavier Grave
2001-08-29 15:56 ` Matt Porter
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=200108292131.RAA06726@orchid.cspi.com \
--to=bwaite@cspi.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).