From: Wolfgang Denk <wd@denx.de>
To: "PAULO SELEME CORREA PAULO" <paulo.correa@siemens.com.br>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ramdisk initrd
Date: Fri, 19 Oct 2001 15:52:35 +0200 [thread overview]
Message-ID: <20011019135240.502D510CCC@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 19 Oct 2001 10:15:11 -0300." <sbcfef39.080@siemens.com.br>
Dear Paulo,
in message <sbcfef39.080@siemens.com.br> you wrote:
>
> I made the ram disk image with the following script :
>
> dd if=/dev/zero of=/dev/ram bs=1k count=4096
> mke2fs -vm0 /dev/ram 4096
> mkdir -p /mnt/ram
> (cd file_system; cp -a * /mnt/ram)
It would have been a good idea to veryfy the contents of your
/mnt/ram directory now. You could have seen that "cp -a" does not
copy special files.
Use something like this instead:
( cd file_system; find . -depth -print | cpio -pdum /mnt/ram )
> umount /mnt/ram
> rmdir /mnt/ram
> dd if=/dev/ram of=fs_images/ramdiskimage bs=1k count=4096
> gzip -v9f ramdisk.image
>
> I copied the ramdisk.image.gz to /opt/hardhat/devkit/ppc/8xx/target/boot
> and
> executed ./mkimage -n "ramdiskimage"-d ramdisk.image.gz ramdiskimage
It is really important that you list the PRECISE commands you used;
it is obvious that this is not the case here; there is not only a
space missing, you are also missing some other options (-T).
> I set the boot parameters to download the kernel via tftp to the target board so when I reset the board it runs ppcboot download the kernel uncompress it and then try to mout the root file system.
It probably _did_ mount the root filesystem, but then it died because
there was no /dev/console in your root filesystem.
> What I didn't understand is how can I download the RAMDISK image to a specific memory area during the boot so when mounting the root filesystem it can find the ramdisk image in memory.
You are worrying about the wrong things. Everything is fine, it's
just that your ramdisk image is incomplete.
> And I don't know how to download the RAMDISK image to the memory to execute the bootm command as explained in PPcboot README :
How do you download other images? There is the "tftp" command to
download over ethernet, and there are the "loads" and "loadb"
commands to download over serial line.
Where exactly is the problem?
> I tried the loads command but had no success
I really hate this sort of problem descriptions.
Which EXACT command did you use? Why didn't it work? Were there any
error messages? Which?
And why did you use "loads"? Download over ethernet is simple and
fast - why don't you use it?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"The number of Unix installations has grown to 10, with more
expected." - The Unix Programmer's Manual, 2nd Edition, June, 1972
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-19 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 13:15 Re:ramdisk initrd PAULO SELEME CORREA PAULO
2001-10-19 13:52 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 21:14 ramdisk initrd PAULO SELEME CORREA PAULO
2001-10-18 22:13 ` 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=20011019135240.502D510CCC@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulo.correa@siemens.com.br \
/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).