public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RE: start / load addresses for initrd
Date: Wed, 02 Apr 2003 22:13:09 +0200	[thread overview]
Message-ID: <20030402201314.DA679C587C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 02 Apr 2003 14:07:06 CDT." <EGEGIJHKDKJGAJMGIDPNEEGNCKAA.jwalden@digitalatlantic.com>

Jerry,

in message <EGEGIJHKDKJGAJMGIDPNEEGNCKAA.jwalden@digitalatlantic.com> you wrote:
> 
> I was getting the error:
> (RAMDISK: incomplete write (ramdisk too small?) (-28!= 32768)
>  and then I discovered the my command line option ramdisk_size=8192 needs to
>  be changed to ramdisk_size=16384.

What makes you think so? I think you are wrong.

> > ## Loading RAMDisk Image at 00200000 ...
> > Image Name:   DA Ramdisk Image
> > Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
> > Data Size:    1509352 Bytes =  1.4 MB

Given a compressed size of 1.4 MB, the contents of the  ramdisk  will
be probably in the range of 3...4 MB. Did you really create a ramdisk
16 MB big?

> > RAMDISK: Couldn't find valid RAM disk image starting at 0.
> > Freeing initrd memory: 1473k freed
> > Kernel panic: VFS: Unable to mount root fs on 01:00

Again, I see no indication that  you  really  have  a  good,  working
ramdisk image. I think you should ask MV support for help.

Alternmatively, you could try using a known-to-work ramdisk image for
a start, for example one from here:
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/



Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
I don't know if it's what you want, but it's what you get.  :-)
                      - Larry Wall in <10502@jpl-devvax.JPL.NASA.GOV>

  reply	other threads:[~2003-04-02 20:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 20:11 [U-Boot-Users] start / load addresses for kernel Jerry Walden
2003-03-25 17:45 ` [U-Boot-Users] RE: start / load addresses for initrd Jerry Walden
2003-03-25 18:17   ` Wolfgang Denk
2003-03-26 16:42     ` Jerry Walden
2003-03-26 23:42       ` Wolfgang Denk
2003-03-28  8:16     ` Stefan Roese
2003-04-01 22:34     ` Jerry Walden
2003-04-01 23:10       ` Wolfgang Denk
2003-04-01 23:36         ` Jerry Walden
2003-04-01 23:51           ` Wolfgang Denk
2003-04-01 23:53             ` Jerry Walden
2003-04-02  8:05               ` Wolfgang Denk
2003-04-02 19:07         ` Jerry Walden
2003-04-02 20:13           ` Wolfgang Denk [this message]
2003-04-02 21:18             ` Jerry Walden
2003-04-02 22:32               ` Wolfgang Denk
2003-04-02 23:13                 ` Reinhard Meyer
2003-04-21 18:02             ` [U-Boot-Users] u-boot boot options Jerry Walden
2003-04-21 18:14               ` Jim Potter
2003-04-21 18:23                 ` Jerry Walden
2003-04-21 18:54                 ` Wolfgang Denk
2003-04-21 18:52               ` Wolfgang Denk
2003-03-25 18:41   ` [U-Boot-Users] RE: start / load addresses for initrd Chris Hallinan
2003-03-26 23:11     ` [U-Boot-Users] u-boot size Jerry Walden
2003-03-26 23:48       ` Robert Schwebel
2003-03-26 23:52       ` 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=20030402201314.DA679C587C@atlas.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.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