linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dmalek@jlc.net>
To: Wolfgang Denk <wd@denx.muc.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MBX860: How to boot with initrd ?
Date: Sat, 09 Jan 1999 23:57:11 -0500	[thread overview]
Message-ID: <36983326.EA43D05F@jlc.net> (raw)
In-Reply-To: 199901082349.AAA13864@denx.muc.de


Wolfgang Denk wrote:

> ....  But  I  must be missing something, because such an image will
> not boot; all I see is:

Hmmm.  I know initrd works because I use it quite often.  All of the
memory relocation looks OK.  Cort had a good suggestion, can you
build a kernel that boots using NFS (or at least boots to the point of
trying to mount the root fs).


>         Linux/PPC load: console=tty0 console=ttyS0,9600n8

This looks a little weird.  It should not be necessary and I
don't know what happens when it is used.


> Any help appreciated...

Look for  'log_buf' in your System.map.  It will have an address
something like 'c00daa78'.  When you reset the MBX, use the
EPPC-Bug to dump the memory starting at daa78 (in this example).
This is the text of the kernel printk until the serial device is
initialized.  It may hold some clues.

You could also use 'noinitrd' on the command line to determine
if the problem is related to initrd or something else.


> Let's assume that I want to populate the `initrd'  with  exactly  the
> same  files  as  included  in the `mbxroot.min.tgz' example. [This is
> what I'm  testing  with,  additionally  I  have  only  added  a  link
> `/linuxrc' which points to `/bin/sh'].

That should work fine.


> What might be missing? I'm sure it's just  a  minor  detail,  however
> critical :-(

They always are :-).  One wrong bit can screw up everything......
and you have a 50% change of getting it right :-).


    -- Dan



[[ 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 ]]

  parent reply	other threads:[~1999-01-10  4:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-08 23:49 MBX860: How to boot with initrd ? Wolfgang Denk
1999-01-09 13:29 ` Wolfgang Denk
1999-01-09 19:29 ` Cort Dougan
1999-01-10  4:57 ` Dan Malek [this message]
1999-01-10 22:46   ` Troy Benjegerdes
     [not found] <Pine.LNX.3.96.990109144040.12262A-100000@persephone.cs.nmt.edu>
1999-01-10  1:53 ` Wolfgang Denk
     [not found] <36986420.3281E1A4@wanadoo.fr>
1999-01-10 22:29 ` Wolfgang Denk
     [not found] <19990111114251.006245@smtp.calvacom.fr>
1999-01-11 21:38 ` Wolfgang Denk

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=36983326.EA43D05F@jlc.net \
    --to=dmalek@jlc.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=wd@denx.muc.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 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).