BeagleBoard boot issue

I followed the directions on http://elinux.org/BeagleBoardUbuntu to setup my BeagleBoard. I did the Flash first and then did the Linux.

When it boots I get this:

U-Boot 2014.07-00014-gae1db02 (Jul 22 2014 - 10:58:18), Build: jenkins-github_Bootloader-Builder-371
OMAP3530-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 128 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
Beagle Rev Ax/Bx
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Die ID #311400020000000004013e8803024013
Net: usb_ether
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt …
Checking for: /boot/uEnv.txt …
44 bytes read in 30 ms (1000 Bytes/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
Running uname_boot …
loading /boot/vmlinuz-3.15.3-armv7-x4 …
4678776 bytes read in 4259 ms (1 MiB/s)
loading /boot/dtbs/3.15.3-armv7-x4/omap3-beagle.dtb …
60325 bytes read in 215 ms (273.4 KiB/s)
loading /boot/initrd.img-3.15.3-armv7-x4 …
3659108 bytes read in 3314 ms (1.1 MiB/s)
Kernel image @ 0x80300000 [ 0x000000 - 0x476478 ]

Flattened Device Tree blob at 815f0000

Booting using the fdt blob at 0x815f0000
Loading Ramdisk to 86baf000, end 86f2c564 … OK
Using Device Tree in place at 815f0000, end 81601ba4
Starting kernel …
[ 2.040924] edma-dma-engine edma-dma-engine.0: Can’t allocate PaRAM dummy slo
t
[ 3.038360] ehci-omap 48064800.ehci: Can’t get PHY device for port 1: -517
[ 3.137084] omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu_iv
a
[ 3.144775] omap2_set_init_voltage: unable to set vdd_mpu_iva
[ 3.150909] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
[ 3.158294] omap2_set_init_voltage: unable to set vdd_core
[ 3.184631] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
[ 4.177520] omap_i2c 48060000.i2c: controller timed out
[ 4.226745] Error: Driver ‘tfp410’ is already registered, aborting…
[ 4.361785] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 4.369476] sr_init: platform driver register failed for SR
Scanning for Btrfs filesystems
hwclock: Cannot access the Hardware Clock via any known method.
hwclock: Use the --debug option to see the details of our search for an access method.
[ 6.005981] mmcblk0: error -84 transferring data, sector 40960, nr 264, cmd response 0x900, card status 0xb00
[ 6.214813] mmcblk0: error -84 transferring data, sector 41224, nr 32, cmd response 0x900, card status 0xb00

Then it repeats the last two lines until I remove power from the beagleboard.

Can anyone point me in the right direction?

Yes I do realize that this is old hardware.

Thanks.

Get a newer/less used mmc card. For some reason all my omap3's have
become much more picker about their mmc card. Vs omap4/imx6's with
v3.15.x+

Regards