All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Bizarre initrd problem on CLLF860T
Date: Mon, 17 Apr 2000 09:12:00 -0400	[thread overview]
Message-ID: <38FB0DA0.DDE9098C@embeddededge.com> (raw)
In-Reply-To: 20000417070226.92BE33C961@elph.research.canon.com.au


Graham Stoney wrote:

> Today though, I can't for the life of me work out why the initrd stuff isn't
> working.

So, what's different in your configuration?  Is this the same kernel
and ramdisk?  Like I requested in a previous message, the the sources
from MontaVista.  They are the most recent.


> Sending BOOTP requests..... OK
> IP-Config: Got BOOTP answer from 10.2.2.90, my address is 10.2.0.21
> IP-Config: Guessing netmask 255.0.0.0
> RAMDISK: Compressed image found at block 0

IP-Config with Ramdisk is a pretty weird configuration.  At the
'Linux/PPC Load:' enter 'root=/dev/ram ip=off'.


	-- Dan

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

  parent reply	other threads:[~2000-04-17 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-17  7:02 Bizarre initrd problem on CLLF860T Graham Stoney
2000-04-17  8:23 ` Marcus Sundberg
2000-04-17  8:42   ` Graham Stoney
2000-04-17 11:02     ` Jason Wohlgemuth
2000-04-17 13:12 ` Dan Malek [this message]
2000-04-17 13:54   ` Wolfgang Denk
2000-04-18  7:57   ` Graham Stoney
2000-04-18  8:58     ` Marcus Sundberg
2000-04-18  9:10       ` Marcus Sundberg
2000-04-18 16:01       ` Dan Malek
2000-04-18 15:55     ` Dan Malek

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=38FB0DA0.DDE9098C@embeddededge.com \
    --to=dan@netx4.com \
    --cc=greyham@research.canon.com.au \
    --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 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.