Ubuntu Beagleboard sdhc setup

I am trying to get my beagleboard setup with ubuntu's arm
distribution. I have been trying to follow these instructions with
little success. https://wiki.ubuntu.com/ARM/OmapNetbook. I have been
able to get the sd card formated and get to the serial terminal
console for the board. the lights for the sd card are lit and it
attempts to do an auto boot and returns this information. It seems
like the sd card is formated correctly or something but I am confused.
Could anyone point me in the right direction either to a more up to
date tutorial or possibly what I might be doing wrong. Thanks I
believe my board revision is B because the sticker on it is a B right
next to the rev. word on the pcb but I am not 100% certain. here is
what is returned by the serial console upon boot up.

Also my reason for suspecting partition issues is when i use the mmc
list command it shows 1 device but if i do mmc part 0 to show its
partitions it says unknown partition table. Any help asap would be
extremely appreciated.

Thanks
-TJ

<------------ Quoted --->
Texas Instruments X-Loader 1.5.0 (Apr 11 2011 - 09:47:05)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2011.03 (Apr 20 2011 - 07:19:53)

OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev A
No EEPROM on expansion board
Die ID #2d5000011ff00000015739eb0901f00f
Hit any key to stop autoboot: 0
mmc_send_cmd: timedout waiting for cmddis!
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
mmc_send_cmd: timedout waiting for cmddis!
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
Booting from nand ...

no devices available
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #
<------------ Quoted--------->

Did you get this resolved? I have encountered the same issue.
-Steve

That was fixed in mainline u-boot...

Regards,