All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Lewis <jlewis@mvista.com>
To: Jeff Millar <jeff@wa1hco.mv.com>
Cc: Mike Flynn <mike.psc@connectnet.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: RAM disk size
Date: Sun, 07 May 2000 07:45:07 -0500	[thread overview]
Message-ID: <39156553.12AD9956@mvista.com> (raw)
In-Reply-To: 000601bfb7c9$d40a0840$0201a8c0@home


Jeff Millar wrote:

> We had some trouble with ramdisk larger than 4096K when used as initial
> ramdisks.  Don't remember if they have problems when just created, mounted
> and used.  This occured with the Dan Malek kernels from late 1999, don't
> know if MontaVista has addressed this issue.  The symptoms were that the
> creation went fine but caused mysterious failures when mounted during boot.

I just created and mounted an 8 M initial ramdisk on a CLLF. So I guess that
whatever the problem was, it is fixed now.
-Jim

>
>
> jeff
>
> ----- Original Message -----
> From: "Jim Lewis" <jlewis@mvista.com>
> To: "Mike Flynn" <mike.psc@connectnet.com>
> Cc: <linuxppc-embedded@lists.linuxppc.org>
> Sent: Saturday, May 06, 2000 12:12 PM
> Subject: Re: RAM disk size
>
> >
> > Hello Mike,
> >
> > The default max ramdisk size is 4096K. You can change this using the
> > ramdisk_size boot parameter. You will definitely need to change this
> default on
> > the target.
> >
> > On the host, another way to create a ramdisk image is to use the loopback
> > filesystem. This will allow you to avoid having to change the Ramdisk-size
> of
> > your development host. Take a look at the Loopback-Root-FS How-To.
> >
> > -Jim
> >
> > Mike Flynn wrote:
> >
> > > I need to flash an image larger than 4 megs to an Embedded Planet RPX
> CLLF
> > > (860T) board with 8 MB of flash. I'm having a problem making a RAM disk
> file
> > > image larger than 4 MB on a LinuxPPC host preceding the download to the
> > > target:
> > >
> > > mkfs -m 0 /dev/ram XXXX
> > > or
> > > mke2fs -c /dev/ram XXXX
> > >
> > >  with XXXX anything more than 4000 returns the following message:
> > >
> > > "Filesystem larger than apparent filesystem size.
> > > Proceed anyway? (y,n)"
> > >
> > > Proceeding "anyway" seems to work until any activity that would put more
> > > than 4 MB in /dev/ram (mounted as /mnt) yields:
> > >
> > > "No space left on device"
> > >
> > > How do I get beyond this host limitation to use more of the available
> flash
> > > on the CLLF board?
> > >
> > > Thanks,
> > > Mike Flynn
> > > Enerdyne Technologies
> > >
> >
> >
> >
> >
>


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

  reply	other threads:[~2000-05-07 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-06 11:16 RAM disk size Mike Flynn
2000-05-06 16:12 ` Jim Lewis
2000-05-07  2:13   ` Jeff Millar
2000-05-07 12:45     ` Jim Lewis [this message]
2000-05-08  2:20 ` Graham Stoney

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=39156553.12AD9956@mvista.com \
    --to=jlewis@mvista.com \
    --cc=jeff@wa1hco.mv.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mike.psc@connectnet.com \
    /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.