<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" face="Tahoma">Here is my network boot messages on one of my systems....<br><br>[ 9.018101] net eth0: initializing cpsw version 1.12 (0)<br>[ 9.022485] net eth0: phy found : id is : 0x7c0f1<br>[ 9.022523] libphy: PHY 4a101000.mdio:01 not found<br>[ 9.027620] net eth0: phy 4a101000.mdio:01 not found on slave 1<br>[ 9.101282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready<br>[ 9.254230] usbcore: registered new interface driver snd-usb-audio<br>[ 12.098811] libphy: 4a101000.mdio:00 - Link is Up - 100/Full<br>[ 12.098876] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<br><br>This system is working normally. So as I mentioned the not found messages can be ignored. Does your boot look like this? Also do an 'ifconfig' and send the output so we can see it.<br id="FontBreak"></font><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div>> Date: Sun, 27 Jul 2014 20:45:48 -0700<br>> From: ar@dseven.org<br>> To: arm-allstar@hamvoip.org<br>> Subject: Re: [arm-allstar] Network Configuration<br>> <br>> You don't necessarily need a serial cable - you can see them in<br>> `dmesg` (kernel messages). Here's what mine says...<br>> <br>> [ 9.907251] net eth0: initializing cpsw version 1.12 (0)<br>> [ 9.910123] net eth0: phy found : id is : 0x7c0f1<br>> [ 9.910153] libphy: PHY 4a101000.mdio:01 not found<br>> [ 9.915279] net eth0: phy 4a101000.mdio:01 not found on slave 1<br>> [ 9.956453] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready<br>> [ 11.916167] libphy: 4a101000.mdio:00 - Link is Up - 100/Full<br>> [ 11.916242] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<br>> <br>> If John's not seeing "Link is Up", there may be a physical problem<br>> (bad cable, switch, etc.), or maybe some config issue that's causing<br>> the NIC to not get initialised....<br>> <br>> 73,<br>> <br>> ~iain / N6ML<br>> <br>> <br>> On Sun, Jul 27, 2014 at 8:32 PM, Doug Crompton <doug@crompton.com> wrote:<br>> > John,<br>> ><br>> > I believe those errors can be safely ignored. I will be hooking up my<br>> > serial cable tomorrow and I will check but as I remember I have seen them on<br>> > all boots and the network works.<br>> ><br>> > Can you describe your network issues again? What router, isp, static or<br>> > dhcp? Unless you are setting something wrong in the BBB it should work as<br>> > it has for everyone else. Perhaps we can sked or talk on the phone. Node<br>> > 27225 works for me if you have a node that works.<br>> ><br>> > 73 Doug<br>> > WA3DSP<br>> > http://www.crompton.com/hamradio<br>> ><br>> ><br>> > ________________________________<br>> > Date: Sun, 27 Jul 2014 21:34:52 -0500<br>> > From: wb5nfc@gmail.com<br>> > To: arm-allstar@hamvoip.org<br>> > Subject: [arm-allstar] Network Configuration<br>> ><br>> ><br>> > I have been struggling with router and basic network setup for several weeks<br>> > thinking that I have a major router configuration problem. I finally got<br>> > USB-serial communication established with my BBB tonight. The following<br>> > (apparent) errors appear at the very end of the boot process:<br>> ><br>> > [ OK ] Started Automatic wired network connection using netctl profiles.<br>> > [ 6.203253] libphy: PHY 4a101000.mdio:01 not found<br>> > [ 6.208395] net eth0: phy 4a101000.mdio:01 not found on slave 1<br>> ><br>> > Arch Linux 3.8.13-24-ARCH (ttyO0)<br>> ><br>> > bbb2186 login: [ 11.527052] libphy: PHY 4a101000.mdio:01 not found<br>> > [ 11.532149] net eth0: phy 4a101000.mdio:01 not found on slave 1<br>> ><br>> > Arch Linux 3.8.13-24-ARCH (ttyO0)<br>> ><br>> > bbb2186 login: root<br>> > Password: xxxxxxx<br>> > BBB Allstar Release Version 1.1 June 25, 2014 WA3DSP<br>> ><br>> > -------------------------<br>> ><br>> > What do these error messages mean and how do I correct them?<br>> ><br>> > Thanks in advance for any guidance you can provide.<br>> > --<br>> > John Kenney<br>> ><br>> > _______________________________________________ arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB<br>> > web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> ><br>> > _______________________________________________<br>> ><br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> ><br>> > Visit the BBB web page -<br>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br></div> </div></body>
</html>