Scott
   find is your friend, at least is was for me. Not knowing a lot about the OE directory layout I did a lot of finds.
  cd to your gumstix directory and type
      find . -name "*mkimage*"
 As to the size of the ramdisk, even though the name is ramdisk.img its actually a ramfs (see http://www.linuxdevices.com/articles/AT4017834659.html) which are dynamically sized as opposed to the old ramdisks which were of fixed size.

gord u

On Wed, May 14, 2008 at 11:52 AM, Scott Lerman <smlerman@gmail.com> wrote:
What size does the ramdisk image need to be?

I found one email message that says that the ramdisk.img also needs to
be initialized with

/opt/gumstix-buildroot/build_arm-iwmmxt-linux-gnueabi/u-boot-1.2.0/tools/mkimage
-T ramdisk -C gzip -n "rootfs" -d ramdisk.img.gz -A ARM uRamdisk

If so, do you know offhand where the easiest place to find/get mkimage would be?

On Wed, May 14, 2008 at 1:56 PM, Gord Urquhart <gordurq@gmail.com> wrote:
> Scott
>     Aas far as I know you need three files in the vfat partition,
>         gumstix-factory.script
>         uImage
>         ramdisk.img
>
> The ramdisk.img is a ramfs filesystem that gets mounted by the kernel (which
> was extracted from uImage) as /, used in the initial boot and then once
> everything is ready  the system executes the init file which then mounts the
> ext2 partition from CF onto a mount point in the ramfs (usually /rfs) and
> then does a  switch_root to /rfs making that the new /.
>
> As to your observations about the files on the CF, the uimage in /boot is
> not used, and /var/log is empty because the system creates another tempfs in
> ram and mounts it under /var/log to save wear and tear on the flash.
>
> gord u
>
> On Wed, May 14, 2008 at 7:56 AM, Scott Lerman <smlerman@gmail.com> wrote:
>>
>> I got the CF card partitioned and unzipped the kernel and rootfs
>> archives to the two partitions, but as far as I can tell, the gumstix
>> doesn't finish booting. /var/log on the CF card is empty, so I'm not
>> sure what would be wrong. I did notice in /boot on the file system
>> partition that there's a link uImage -> uImage-2.6.21, but that's the
>> only thing in the directory (there is no uImage-2.6.21 in the
>> directory). Not sure if that's a problem or not. Any other ideas?
>>
>>
>> --
>> Scott Lerman
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>



--
Scott Lerman

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users