linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Habermann <MHabermann@gmx.de>
To: Dan Malek <dan@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Uncompress Ok, but cannot run linux kernel...
Date: Tue, 08 May 2001 16:02:24 +0800	[thread overview]
Message-ID: <5.0.2.1.0.20010508155109.00a01ec0@pop.gmx.de> (raw)
In-Reply-To: <3AF748FF.E308BF0C@mvista.com>


At 09:16 PM 5/7/2001 -0400, Dan Malek wrote:

> > I have the same problem on an FADS board.
>
>What "same" problem?  How are you loading and tracing the kernel?

The same problem is that the kernel doesn't survive until the welcome
messge is printed.
The kernel is loaded with ppcboot and the tftpboot commando. To trace, I
used mpc8bug.

I use the Montavista linux-2.4.0-test2-1.2.0-1 kernel.
I set a breakpoint at the entry of the __start routine. After passing
the turn_on_mmu label, it returns with an rfi and hangs.
It is maybe ment to be started from a power_on interrupt, because in
this context, I don't see the sense for an rfi. But I don't know much details.


I believe there is a working FADS port in the FSM Labs BitKeeper
>sources.  If not, you can download the older 2.4.0-test2 LSP from
>MontaVista and use it as a guide for updating a later kernel.  The
>changes are very minor.

The Montavista is the one I used. I also tried one from Bitkeeper, but I
didn't found support
for the FADS board. Even when I compiled for MBX, I got no image in
arch/ppc/coffboot.
Which is the machine type I should configure for a MPC860FADS?

It would be nice if you could help me. So far I couldn't start any kernel.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-05-08  8:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06  1:01 Uncompress Ok, but cannot run linux kernel machael thailer
2001-05-07 19:10 ` Dan Malek
2001-05-08  1:36   ` machael thailer
2001-05-10  3:08   ` machael thailer
2001-05-10 10:45     ` Matt Porter
2001-05-08  0:58 ` Michael Habermann
2001-05-08  1:16   ` Dan Malek
2001-05-08  8:02     ` Michael Habermann [this message]
2001-05-08  8:06       ` machael thailer
2001-05-08  8:43         ` Wolfgang Denk
2001-05-08 10:06           ` machael thailer
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08 10:43 Zehetbauer Thomas
2001-05-08 11:51 ` machael thailer
     [not found] <439B3F1E9095D41193DE00D0B74FF30601CE7900@xpr01.prd.hp.com>
2001-05-08 13:50 ` Freddy Lugo
2001-05-08 15:21   ` Wolfgang Denk
2001-05-08 21:21     ` Freddy Lugo
2001-05-10  3:40 machael thailer
2001-05-10  4:16 ` Paul White

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=5.0.2.1.0.20010508155109.00a01ec0@pop.gmx.de \
    --to=mhabermann@gmx.de \
    --cc=dan@mvista.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).