On Thu, Jan 16, 2014 at 1:41 PM,  <smith.winston....@gmail.com> wrote:
> On Thursday, January 16, 2014 12:10:35 PM UTC-5, smith.wi...@gmail.com
> wrote:
>>
>>
>> Fantastic, thanks for this, I'm in the process of running my first build.
>>
>
> Success! ... I think.  Don't seem to have working ethernet, here's the
> console output:
>
> [    0.361322] omap2_mbox_probe: platform not supported
> [    0.528826] tps65217-bl tps65217-bl: no platform data provided
> [    0.593518] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [    0.630626] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [    0.667733] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [    0.704842] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [    0.720846] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN
> conflict P8.45 (#5:BB-BONELT-HDMI)
> [    0.730428] bone-capemgr bone_capemgr.9: slot #6: Failed verification
> [    0.737160] bone-capemgr bone_capemgr.9: loader: failed to load slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [    0.753514] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
> failed
> [    0.816446] pinctrl-single 44e10800.pinmux: pin 44e10854 already
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [    0.828157] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
> -22
> [    0.835441] pinctrl-single 44e10800.pinmux: could not request pin 21 on
> device pinctrl-single
> Loading, please wait...
> Scanning for Btrfs filesystems
> systemd-fsck[201]: rootfs: clean, 32162/111104 files, 140904/444160 blocks
> [    6.087883] libphy: PHY 4a101000.mdio:01 not found
> [    6.092953] net eth0: phy 4a101000.mdio:01 not found on slave 1

Give it a few more seconds, currently "wicd" is under control of eth0
(not /etc/network/interfaces) on 3.8 it takes wicd about 2-3 calls
before it gets it..

The only reason i'm using wicd over /etc/network/interfaces is to
remove the 2 minute timeout if eth0 isn't connected...

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

Reply via email to