Yup same for me here, it gets stuck after
hwclock: can't open '/dev/misc/rtc': No such file or directory
Sat May 21 00:08:00 UTC 2011
hwclock: can't open '/dev/misc/rtc': No such file or directory

Chumby One board

Yup just downloaded another image from the EC2 instance and that doesn't work,but that's because I did a git pull on openembedded earlier.

Can anyone tell me what the openembedded git version is on the Chumby EC2 Instance image?

Pretty please...

This might go better on the Wiki, I've just noticed the default 'chumby-starter-image' does not include the wifi firmware or any of the kernel modules required for Falconwing...

The following is an image recipe for me playing around with Python + Pygame
------

#Angstrom bootstrap image

IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"

ANGSTROM_EXTRA_INSTALL ?= ""

ZZAPSPLASH = ' ${@base_contains("MACHINE_FEATURES", "screen", "psplash-zap", "",d)}'

DISTRO_SSH_DAEMON ?= "dropbear"
PREFERRED_PROVIDER_virtual/libgl = "mesa-xlib"

DEPENDS = "task-base \
           task-base-extended \
           ${SPLASH} \
           ${ZZAPSPLASH} \
config-util regutil-${CNPLATFORM} \
       "

IMAGE_INSTALL = "task-base \
           task-base-extended \
           rt73-firmware kernel-modules avahi-utils\
           bash vim ${DISTRO_SSH_DAEMON} file \
           python-pyserial \
           python-pyopengl python-pygame python-stringold python-ctypes \
           python-compile python-core python-dev python-distutils \
           python-netclient python-numeric python-numpy python-readline \
           python-shell python-textutils python-threading python-unittest \
           python-pprint python-fcntl libgl libglu \
           networkmanager cnetworkmanager wpa-supplicant python-netclient \
           tslib tslib-calibrate tslib-conf \
           ${ANGSTROM_EXTRA_INSTALL} \
       ${SPLASH} \
       ${ZZAPSPLASH} \
config-util regutil-${CNPLATFORM} \
        "

IMAGE_LINGUAS = ""

inherit image

The recipe is a BitBake configuration script which OpenEmbedded uses to construct a bootable disk image.  For example if you are using the VMWare image to build, you could save the recipe as meta-chumby/recipes/images/chumby-py.bb and build the image with a command like:

bitbake chumby-py

If you are not using the VMWare build, you need to make sure you check out a version of OpenEmbedded which works with the Chumby kernel.  The latest version of OE does NOT build a usable falconwing kernel.   This version issue is, I believe, responsible for the boot-time hang you are seeing.  Use the git hash shown above to get the right version out of git.

Because this is all so fussy, I've created a git repository at https://github.com/clearwater/chumby-oe#readme which automatically pulls in working versions of OpenEmbedded, BitBake, Kernel Sources, etc.

I would expect it to boot too.  I tried to find some confirmation that it should work.  Here's the best I can find:
In this thread on insigniaproducts.com the support member refers the poster to "Falconwing Software version 1.0.7, build 1.0.3454" which is the same source that forms the basis of the chumby-oe build.  (As an aside, I'm mystified by the poster saying "cross-compiled and booted in < 30 min" given how long the build takes for me!)

Certainly chumby-oe has been used to build images for other non-CHB devices (like the Silvermoon Infocast 8), but I've
only personally worked with the Chumby Hackers Boards.

Since I can't offer much direct help, let me re-state one issue that can cause boot-time hangs, just in case you have taken some shortcut that landed you with a non-standard build environment.  This thread starts with a reference to the wiki instructions that, if followed, would pull in the latest version of the openembedded tools, which are known to generate unbootable images.  The chumby-oe repository pulls in a specific fork of the openembedded tools during the setup process and does not have that problem.