From: "hyding" <nari_dhy@nari-china.com>
To: "ARIBAUD Albert" <a.aribaud@giat-industries.fr>
Cc: "linuxppc-embed" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: RAMDISK: incomplete write (ramdisk too small?)
Date: Wed, 10 Dec 2003 21:11:56 +0800 [thread overview]
Message-ID: <001801c3bf1f$30180dc0$4844900a@hydingnb1> (raw)
In-Reply-To: 158EF4B20EA8C84D9DC71A55216D2E1C066C54@csy-exchange1.giat.intra
hi, Albert
Thanks a lot.
It doesn't complain now and mounts initrd now. But it still has some problem.
It immediately umount initrd and mount disk fs. I think there is no program in ramdisk. I only installed busybox into the ramdisk.
What more is needed to make up of the ramdisk.
Thanks!
----- Original Message -----
From: "ARIBAUD Albert" <a.aribaud@giat-industries.fr>
To: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, December 10, 2003 4:30 PM
Subject: RE: RAMDISK: incomplete write (ramdisk too small?)
>
> > -----Message d'origine-----
> > De : owner-linuxppc-embedded@lists.linuxppc.org
> > [mailto:owner-linuxppc-embedded@lists.linuxppc.org]De la part
> > de hyding
> > Envoyé : mercredi 10 décembre 2003 02:51
> > À : linuxppc-embed
> > Objet : RAMDISK: incomplete write (ramdisk too small?)
> >
> >
> >
> > hi,all
> > I made an initrd but failed to boot.The process about making the
> > initrd is as follows:
> > dd if=/dev/zero of=/tmp/ramdisk.image bs=1k count=8192
>
> Looks like you're building a ramdisk bigger than 4megs.
> The kernel need a RAMDISK_SIZE=8192k command line argument for your
> 8meg ramdisk to work, I think.
>
> Albert.
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-10 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 8:30 RAMDISK: incomplete write (ramdisk too small?) ARIBAUD Albert
2003-12-10 13:11 ` hyding [this message]
2003-12-10 13:44 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 1:50 hyding
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='001801c3bf1f$30180dc0$4844900a@hydingnb1' \
--to=nari_dhy@nari-china.com \
--cc=a.aribaud@giat-industries.fr \
--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).