From: Mike Flynn <hidden> Date: 2000-05-06 11:16:45
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/
From: Jim Lewis <hidden> Date: 2000-05-06 16:12:31
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
From: Jeff Millar <hidden> Date: 2000-05-07 02:13:19
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.
jeff
----- Original Message -----
From: "Jim Lewis" <redacted>
To: "Mike Flynn" <redacted>
Cc: <redacted>
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:
quoted
I need to flash an image larger than 4 megs to an Embedded Planet RPX
CLLF
quoted
(860T) board with 8 MB of flash. I'm having a problem making a RAM disk
file
quoted
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
quoted
on the CLLF board?
Thanks,
Mike Flynn
Enerdyne Technologies
From: Jim Lewis <hidden> Date: 2000-05-07 12:45:07
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" <redacted>
To: "Mike Flynn" <redacted>
Cc: <redacted>
Sent: Saturday, May 06, 2000 12:12 PM
Subject: Re: RAM disk size
quoted
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
quoted
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
quoted
your development host. Take a look at the Loopback-Root-FS How-To.
-Jim
Mike Flynn wrote:
quoted
I need to flash an image larger than 4 megs to an Embedded Planet RPX
CLLF
quoted
quoted
(860T) board with 8 MB of flash. I'm having a problem making a RAM disk
file
quoted
quoted
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
quoted
quoted
on the CLLF board?
Thanks,
Mike Flynn
Enerdyne Technologies