Some more information, i decided to give it a try with the image Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz<http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz> available at http://www.angstrom-distribution.org/demo/beaglebone/.
Surprisingly this is what i'm getting: -Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03) I2C: ready DRAM: 256 MiB No daughter card present NAND: HW ECC Hamming Code selected 16 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment Net: cpsw Hit any key to stop autoboot: 0 SD/MMC found on device 0 reading uEnv.txt 33 bytes read Loaded environment from uEnv.txt Importing environment from mmc ... reading uImage 3137440 bytes read ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Angstrom/3.2/beaglebone Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3137376 Bytes = 3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK XIP Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.068294] _omap_mux_get_by_name: Could not find signal uart1_cts.uart1_cts [ 0.068315] omap_hwmod_mux_init: Could not allocate device mux entry [ 0.068465] _omap_mux_get_by_name: Could not find signal uart2_cts.uart2_cts [ 0.068483] omap_hwmod_mux_init: Could not allocate device mux entry [ 0.068644] _omap_mux_get_by_name: Could not find signal uart3_cts_rctx.uart3_cts_rctx [ 0.068728] omap_hwmod_mux_init: Could not allocate device mux entry [ 0.106314] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver [ 0.261139] _omap_mux_get_by_name: Could not find signal leds-gpio [ 0.651272] omap2_set_init_voltage: unable to get clk dpll1_ck [ 0.657458] omap2_set_init_voltage: unable to set vdd_mpu_iva [ 0.663475] omap2_set_init_voltage: unable to get clk l3_ick [ 0.669409] omap2_set_init_voltage: unable to set vdd_core [ 0.927024] hub 1-0:1.0: over-current condition on port 1 [ 1.186994] hub 1-0:1.0: over-current condition on port 1 [ 1.447002] hub 1-0:1.0: over-current condition on port 1 [ 1.706975] hub 1-0:1.0: over-current condition on port 1 [ 1.966988] hub 1-0:1.0: over-current condition on port 1 [ 2.226976] hub 1-0:1.0: over-current condition on port 1 [ 2.486983] hub 1-0:1.0: over-current condition on port 1 [ 2.746982] hub 1-0:1.0: over-current condition on port 1 [ 3.006980] hub 1-0:1.0: over-current condition on port 1 [ 3.266980] hub 1-0:1.0: over-current condition on port 1 [ 3.526979] hub 1-0:1.0: over-current condition on port 1 [ 3.786975] hub 1-0:1.0: over-current condition on port 1 [ 4.046994] hub 1-0:1.0: over-current condition on port 1 [ 4.306975] hub 1-0:1.0: over-current condition on port 1 [ 4.566981] hub 1-0:1.0: over-current condition on port 1 [ 4.827045] hub 1-0:1.0: over-current condition on port 1 [ 5.086988] hub 1-0:1.0: over-current condition on port 1 [ 5.346982] hub 1-0:1.0: over-current condition on port 1 [ 5.606985] hub 1-0:1.0: over-current condition on port 1 [ 5.866990] hub 1-0:1.0: over-current condition on port 1 [ 6.126976] hub 1-0:1.0: over-current condition on port 1 [ 6.386980] hub 1-0:1.0: over-current condition on port 1 [ 6.646976] hub 1-0:1.0: over-current condition on port 1 [ 6.906974] hub 1-0:1.0: over-current condition on port 1 [ 7.166987] hub 1-0:1.0: over-current condition on port 1 [ 7.427043] hub 1-0:1.0: over-current condition on port 1 [ 7.687078] hub 1-0:1.0: over-current condition on port 1 [ 7.947139] hub 1-0:1.0: over-current condition on port 1 [ 8.207116] hub 1-0:1.0: over-current condition on port 1 [ 8.467097] hub 1-0:1.0: over-current condition on port 1 [ 8.727113] hub 1-0:1.0: over-current condition on port 1 [ 8.987448] hub 1-0:1.0: over-current condition on port 1 systemd-fsck[56]: Angstrom-Cloud9-: clean, 28959/874496 files, 748256/3494137 blocks [ 9.247089] hub 1-0:1.0: over-current condition on port 1 [ 9.507206] hub 1-0:1.0: over-current condition on port 1 For what i've read online about this: 1. too much current is being consumed by whatever is plugged into that port or 2. the power FET (U13?) for the USB port has been damaged causing it to indicate an over current condition On my design (BB-based), P1 (i'm assuming it's referring to P10 Ethernet connector) is not soldered. And i doubt it's due to the power FET. Maybe if i compile the kernel without davinci_mdio? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
