Re: [beagleboard] BeagleBone Black: Ethernet transmits packets but does not receive them

8086 views
Skip to first unread message

Gerald Coley

unread,
Jun 10, 2013, 11:52:07 AM6/10/13
to beagl...@googlegroups.com
Request an RMA.

Gerald


On Mon, Jun 10, 2013 at 10:23 AM, <necron...@gmail.com> wrote:
I'm having a strange problem with my new BeagleBone black: I can transmit packets from the Ethernet port but not receive them.

When using DHCP, I can see (via a sniffer) the DHCP DISCOVER packet sent from the 'bone (via a network sniffer). I can see my DHCP server (dnsmasq 2.59 on stock Ubuntu 12.04 LTS 64-bit server) send a DHCP OFFER. But the 'bone acts like it never hears the offer; it just sends out more DISCOVERs at intervals. (The same DHCP server is working fine for dozens of clients from various vendors. There are plenty of leases left in the pool.)

If I set a static address and try to ping something, I see the 'bone send an ARP who-has, I see the target reply with an ARP is-at, but the 'bone just keeps ARP-ing, and never gets an entry in its ARP table.

In the ifconfig output, the eth0 interface shows 0 packets received and 0 errors. (The number transmitted is non-0.) Nothing suspicious in the dmesg output that I can see.

I've repeated the tests with both the latest Angstrom and with Ubuntu booted off an SD card. Same results. I've tried two different cables, and two different ports on two different Ethernet switches from different vendors. (All ports and cables verified to work fine with my laptop.)

One interesting observation: the port seems to always end up on 10Mbps, even when plugged into 100Mbps- (or gigabit-) capable ports. So, it looks like autonegotiation isn't working either.

I'm running on a 2A 5.00V regulated bench supply, and the DC looks clean on the o-scope.

Other 'bone functions (USB host, USB target, HDMI, LEDs) all seem to work fine.

I'm starting to suspect a hardware problem (busted PHY or magnetics; incomplete or bridged trace).

Any suggestions for stuff I should try before I RMA the poor little guy? (I'm an experienced Linux user and reasonably competent electronics hobbyist, if that matters.)

--
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Gerald
 

Gerald Coley

unread,
Jun 12, 2013, 7:29:43 PM6/12/13
to beagl...@googlegroups.com, necron...@gmail.com
Would you be willing to request an RMA and have us look at it to see if it really a HW issue?

Gerald



On Wed, Jun 12, 2013 at 6:20 PM, <rfe...@everestkc.net> wrote:
I'm also having the same issue.  It was working, then stopped after a few hours.  Tried the stock Linux, Ubuntu, and Debian.  It's a hardware issue.  Mine is going back to Newark.  See posts here for same problem:

Gerald Coley

unread,
Jun 12, 2013, 7:35:45 PM6/12/13
to beagl...@googlegroups.com, necron...@gmail.com
Or would you be willing to work with me to find a solution for this issue? There is a simple test to prove out your theory if you are interested.

Gerald

Kathryn Adeney

unread,
Jun 13, 2013, 12:27:09 PM6/13/13
to beagl...@googlegroups.com, necron...@gmail.com
I see a similar issue on my Beaglebone Black.  eth0 comes up initially but if I take it down it won't come back without a reboot.  When it is in this state, Wireshark can see packets coming to and from the BBB on the wire, but TX and RX stats displayed in ifconfig do not increase.  

I have tried this with:
-  two different BBBs, 
 - three different Linux 3.8 loads (the 3.8.11 it shipped with, 3.8.13 (2013-06-06, booting from SD), and a Debian demo image (3.8.13-bone20). 
 - 5V1A supply or USB power. 
 - I have the serial FTDI cable.

Example:

--- after boot (just the eth0 dmesg shown): ----

root@beaglebone:~# dmesg 
 ...  // just the eth -related ones (I think)
[   12.843873] net eth0: initializing cpsw version 1.12 (0)
[   12.848216] net eth0: phy found : id is : 0x7c0f1
[   12.848248] libphy: PHY 4a101000.mdio:01 not found
[   12.853364] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   12.920613] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.926429] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[   15.926491] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

// eth0 did dhcp and came up automatically 

root@beaglebone:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:B6:B0:AB  
          inet addr:10.10.10.100  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::caa0:30ff:feb6:b0ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16 errors:0 dropped:1 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2421 (2.3 KiB)  TX bytes:5349 (5.2 KiB)
          Interrupt:56 

// take it down. 

root@beaglebone:~# ifconfig eth0 down
root@beaglebone:~# ifconfig -a eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:B6:B0:AB  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:21 errors:0 dropped:1 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3119 (3.0 KiB)  TX bytes:5841 (5.7 KiB)
          Interrupt:56

// take it back up. 
//  TX and RX stop incrementing, even though when we do 
// udhcpc we can see traffic to and from the bone on the wire!. 
// ( note I think the libphy messages about mdio:01 are a red herring,
// relating to the not-present second slave port??  )

root@beaglebone:~# ifconfig eth0 up
[   46.543648] libphy: PHY 4a101000.mdio:01 not found                            
[   46.548717] net eth0: phy 4a101000.mdio:01 not found on slave 1
root@beaglebone:~# 
root@beaglebone:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:B6:B0:AB  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21 errors:0 dropped:1 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3119 (3.0 KiB)  TX bytes:5841 (5.7 KiB)
          Interrupt:56 

root@beaglebone:~# udhcpc -i eth0
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Sending discover...
^C
root@beaglebone:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:B6:B0:AB  
          inet addr:169.254.66.231  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21 errors:0 dropped:1 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3119 (3.0 KiB)  TX bytes:5841 (5.7 KiB)
          Interrupt:56 

// new dmesg after ifconfig eth0 down and then ifconfig eth0 up: 

[  250.747282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[  264.214253] net eth0: initializing cpsw version 1.12 (0)

[  264.217970] net eth0: phy found : id is : 0x7c0f1

[  264.218000] libphy: PHY 4a101000.mdio:01 not found

[  264.223112] net eth0: phy 4a101000.mdio:01 not found on slave 1

[  264.234179] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[  266.223290] libphy: 4a101000.mdio:00 - Link is Up - 100/Full

[  266.223348] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready


When testing it with the debian image I also tried

network restart /etc/init.d/network restart, same results.

I have found eth0 is very stable on the Beaglebone White and from the schematic nothing has changed, so I am wondering about the driver changes under 3.8 kernel ... but can't find any known issues or patches or anything.   Linux Noob so maybe looking in the wrong places.

Thanks -

Kathryn.


Message has been deleted

rfe...@everestkc.net

unread,
Jun 15, 2013, 12:23:18 PM6/15/13
to beagl...@googlegroups.com, necron...@gmail.com
I submitted the paperwork to Newark for a RMA, but they never sent me an RMA, just refunded my credit card.  Oh well!  Do you want me to send the thing to you?

rfe...@everestkc.net

unread,
Jun 15, 2013, 12:25:29 PM6/15/13
to beagl...@googlegroups.com, necron...@gmail.com

I requested an RMA from Newark, but they never sent me one, just refunded my credit card.  Do you want me to mail it to you?

Gerald Coley

unread,
Jun 15, 2013, 9:08:33 PM6/15/13
to beagl...@googlegroups.com

Dale Schaafsma

unread,
Jun 19, 2013, 3:27:40 PM6/19/13
to beagl...@googlegroups.com, necron...@gmail.com
I can reproduce this behavior as well...note that I'm not on the 2013-06-06 image, but on the 2013.05.27 (I'm waiting to upgrade to 2013.06.17).
Initially I suspected that this was due to interaction with connman (which is quite poorly documented) however I'm not so sure.

In short, if "ifconfig eth0 down" is ever run, reboot is required to recover the ethernet port (even disconnecting/reconnecting the cable won't recover the port)
Also it behaves as the OP and Kathryn noted (transmit counted in ifconfig counts, but no rx counts).

So perhaps there's a software bug here? maybe something is not re-configured properly after "ifconfig eth0 up" or some power management interaction?

FWIW, the following will disconnect/reconnect without issues..but note the interface is not marked down.
Connman flags are: * = favorite, A = autoconnect, R = ready, O = online
root@beaglebone:~# /usr/lib/connman/test/test-connman services
* AO Wired                      { ethernet_c8a030aec6a8_cable }
root@beaglebone:~# /usr/lib/connman/test/test-connman disconnect ethernet_c8a030aec6a8_cable
root@beaglebone:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:AE:C6:A8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2317 (2.2 KiB)  TX bytes:10628 (10.3 KiB)
          Interrupt:56

root@beaglebone:~# /usr/lib/connman/test/test-connman state
System is idle
root@beaglebone:~# /usr/lib/connman/test/test-connman services
* A  Wired                      { ethernet_c8a030aec6a8_cable }
root@beaglebone:~# /usr/lib/connman/test/test-connman connect ethernet_c8a030aec
6a8_cable
root@beaglebone:~# /usr/lib/connman/test/test-connman services
* AO Wired                      { ethernet_c8a030aec6a8_cable }
root@beaglebone:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr C8:A0:30:AE:C6:A8
          inet addr:192.168.3.200  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::caa0:30ff:feae:c6a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4634 (4.5 KiB)  TX bytes:20521 (20.0 KiB)
          Interrupt:56

root@beaglebone:~# ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
64 bytes from 192.168.3.1: icmp_req=1 ttl=64 time=0.275 ms



-Dale

PLyttle

unread,
Jun 19, 2013, 4:54:21 PM6/19/13
to beagl...@googlegroups.com, necron...@gmail.com
Similar story here.
running Arch, Ethernet connnects once with DHCP (both dhcpcd and dhclient), either at boot or when plugged in (using netctl-ifplugd). after replugging, or down - up  no more received packets.
the same configuration on a raspberry pi works without a hitch (off course the raspi is armv6l and kernel 3.6.11 (no device tree)). I don't think I made a configuration error.

running Arch, kernel 3.8.13-bone21 (home built) and kernel 3.8.13-3 (stock) same behavior on both
It is clearly not limited to one distro.

LP

rfe...@everestkc.net

unread,
Jun 20, 2013, 10:30:24 PM6/20/13
to beagl...@googlegroups.com
I submitted an RMA request at that link, but nothing happens after I click submit.  Maybe I'll get an email confirmation.

Gerald Coley

unread,
Jun 20, 2013, 10:34:13 PM6/20/13
to beagl...@googlegroups.com
It have not seen it come through. Enter all the information requested into an email and send that to r...@beaglebopard.org.

Gerald

rfe...@everestkc.net

unread,
Jun 21, 2013, 10:33:42 PM6/21/13
to beagl...@googlegroups.com
OK sent in the RMA request (S/N 019132935333).  The web form didn't work since I have no email client installed on my lab PC.

Gerald Coley

unread,
Jun 22, 2013, 10:37:49 AM6/22/13
to beagl...@googlegroups.com
RMA received. Should be approved by Monday.

Gerald

nemanja

unread,
Jun 24, 2013, 12:47:04 PM6/24/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
PLyttle,

I'm having the exact same issue with those kernels. I tried RCN's Ubuntu and Debian images and both have the issue, and another with my own custom kernel based on that one. Unplugging the ethernet for >30 seconds and plugging back in makes it no longer work, and doing ifconfig eth0 down, then up and it never works, dhclient can't get another IP.
But it does work on startup the once, like you said.

I'm not sure it is a hardware issue though because it happens on both of my rev A5A BBB boards with Ubuntu/Debian but NOT with the Angstrom image, that one seems to come back up with Ethernet no problem.

Robert Nelson

unread,
Jun 24, 2013, 12:51:55 PM6/24/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
On Mon, Jun 24, 2013 at 11:47 AM, nemanja <ne...@nemik.net> wrote:
> PLyttle,
>
> I'm having the exact same issue with those kernels. I tried RCN's Ubuntu and
> Debian images and both have the issue, and another with my own custom kernel
> based on that one. Unplugging the ethernet for >30 seconds and plugging back
> in makes it no longer work, and doing ifconfig eth0 down, then up and it
> never works, dhclient can't get another IP.
> But it does work on startup the once, like you said.
>
> I'm not sure it is a hardware issue though because it happens on both of my
> rev A5A BBB boards with Ubuntu/Debian but NOT with the Angstrom image, that
> one seems to come back up with Ethernet no problem.

I believe it's a problem in the cpsw ethernet driver.. As the
beaglebone (classic) seems to have the same issue with v3.8.x, where
it worked fine with the old v3.2.x board tree..

Regards,

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

nemanja

unread,
Jun 24, 2013, 1:55:07 PM6/24/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
Thank you Robert, that would make sense. 
I suspected there may be problems with the SMSC LAN8710 driver and tried this patch: http://www.spinics.net/lists/netdev/msg218399.html on the 3.8.13-22 kernel (newest pull from git) but it did not appear to fix it.

nemanja

unread,
Jun 24, 2013, 2:06:43 PM6/24/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
I guess the driver isn't fully supported by the kernel? According to http://processors.wiki.ti.com/index.php/AM335x_CPSW_(Ethernet)_Driver's_Guide  I should be able to change things like Interrupt Pacing, but it says it is not supported:
"
ubuntu@arm:~$ sudo ethtool -C eth0 rx-usecs 500
Cannot get device coalesce settings: Operation not supported

nemanja

unread,
Jun 24, 2013, 2:50:40 PM6/24/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
I did notice one more curious thing. Sometimes after I unplug and plug the Ethernet cable back in and cannot ping the BBB, if I connect the USB to establish the USB gadget ethernet, it forces the other one to come back up and respond.

If I do this over and over a few times, it eventually stops working, but for a couple of tries, it did somehow force the main PHY to recover.

PLyttle

unread,
Jun 25, 2013, 3:28:12 AM6/25/13
to beagl...@googlegroups.com, necron...@gmail.com, rkst...@gmail.com
I compiled a kernel with the cpsw driver as a module. This needs fixing of the davinci_cpdma.c source, because it does not export the symbols GPL(cpdma_ctlr_int_ctrl); GPL(cpdma_ctlr_eoi); GPL(cpdma_control_set). Fortunately Internet is a big help here :-)

when booting in this new kernel with netctl for eth0 enabled (standard dynamic profile)
modprobe ti_cpsw
netctl start eth0

everything works normally even unplugging and replugging the RJ-45 cable re-initiates the network (improvement here)

netctl stop eth0 stops the interface without apparent mishap, but when followed by netctl start eth0 no more received packets, which shows up as a failed dhcp lease attempt and net...@eth0.service entering a failed state.

The reason why I attempted a modular driver was to try to unload the module at this point an reload it to see if that would re-create a working interface, but this results in a kernel bug
[ 1734.862884] kernel BUG at net/core/dev.c:6286!                              
[ 1734.867528] Internal error: Oops - BUG: 0 [#1] ARM

and a segment error upon reboot.
Unable to handle kernel NULL pointer dereference at virtual address 00000000

I saved the stack trace if someone is interested.

LP

eskimobob

unread,
Jun 25, 2013, 1:27:04 PM6/25/13
to beagl...@googlegroups.com, necron...@gmail.com
I have found the same issue and there is another separate discussion about this in the group (see thread here).   I'd been thinking it was a problem with connman but after reading this thread, it seems that it is something more fundamental.

My findings:
1) If I boot without LAN cable attached then LAN is never available even after plugging LAN in.
2) If after booting with LAN attached, I unplug LAN for a few seconds then plug back in, the connection is re-established providing I add "Restart=on-failure" and "RestartSec=5" to the connman service control/launch file.
3) If after booting with LAN attached, I unplug LAN for more than 5 seconds, the connman service restarts but then the connection can never be re-established without reboot.

Happy to try things if suggestions are offered :-)

tlas...@gmail.com

unread,
Jul 7, 2013, 10:23:42 AM7/7/13
to beagl...@googlegroups.com, necron...@gmail.com
Any resolutions to this issue?  I am experiencing the same thing on BBB running Ubuntu 13.04.  When booted without a cable plugged in, the board can never get an IP address.

Thanks,

-Tom

eskimobob

unread,
Jul 7, 2013, 3:00:28 PM7/7/13
to beagl...@googlegroups.com, necron...@gmail.com, tlas...@gmail.com
I too have seen the problem both with Angstrom and Ubuntu (13.04).  RobertCNelson suggests:  "I believe it's a problem in the cpsw ethernet driver." (see above).  Presumably both Angstrom and Ubuntu pull in the same low level driver.  

It is not clear (to me at least) whether that means it is a problem which the community can/should fix or whether it is something that TI need to be made aware of so that they can fix it.
Can anyone clarify?

Louis Brown

unread,
Jul 7, 2013, 4:58:53 PM7/7/13
to beagl...@googlegroups.com

I RMA'd mine and they diagnosed a faulty ethernet controller, but nothing more specific yet.

eskimobob

unread,
Jul 8, 2013, 3:06:40 AM7/8/13
to beagl...@googlegroups.com, rfe...@everestkc.net
Interesting Louis, presumably you have received a new board now - can you confirm whether you see the same problem of no reconnection when you unplug the LAN for some seconds?
I have 3 BBB boards here (2 x A5A and 1 x A5B) which all do it so if it is a fault with the ethernet controller, there must be a bad batch - seems more likely to be SW though.

Kathryn Adeney

unread,
Jul 8, 2013, 10:42:40 AM7/8/13
to beagl...@googlegroups.com
Yes I have the same question - is there actually a h/w fix?  

There are some pretty relevant-sounding cspw driver fixes logged in Tony Lindgren's repo: http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/drivers/net/ethernet/ti.  I think they are against a 3.11 kernel so maybe they are coming (soon I hope? - testing them on BBB exceeds my linux chops / available time).   But this blog post says Beagleboard.org will have a 3.11 build this summer: http://linuxgizmos.com/introducing-the-new-beaglebone-black-kernel/

So my current strategy is to wait it out.  But if there is a h/w fix or better strategy I'd sure like to know.

Kathryn.


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/mfQwHdfHyoo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Gerald Coley

unread,
Jul 8, 2013, 10:50:24 AM7/8/13
to beagl...@googlegroups.com
There is no HW fix for this as the boards work fine as far as I know. I always make sure the cable is plugged in at power up when I use Ethernet  We test these boards before shipping and we have shipped a lot of them and not seen the issue at all.

Gerald



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...@googlegroups.com.

Kathryn Adeney

unread,
Jul 8, 2013, 11:01:13 AM7/8/13
to beagl...@googlegroups.com
HI Gerald, I think if the ethernet is plugged in when you power up you will never see the issue - and this is the right workaround to be sure.  The issue only occurs if ethernet is either unplugged or replugged, OR if it is taken down by software and then taken back up again.  These use cases would be supported by a "fully-functioning" ethernet interface, and and from the postings here it seems they are not working on the current BBB.  But it also seems very likely to be a driver problem in the 3.8 kernel, and not a hardware problem.

Kathryn.

Gerald Coley

unread,
Jul 8, 2013, 11:05:46 AM7/8/13
to beagl...@googlegroups.com
I would lean toward SW as well. 

I just plugged in the Ethernet after boot up. I am looking at www.foxnews.com.

Gerald

eskimobob

unread,
Jul 8, 2013, 11:10:31 AM7/8/13
to beagl...@googlegroups.com
Gerald, would you be able to unplug your ethernet cable for say 15 seconds then plug it back in.  Does it bring the lan back up?
In my case it does not on 3 boards running either the latest Angstrom or Ubuntu images.

Gerald Coley

unread,
Jul 8, 2013, 11:20:05 AM7/8/13
to beagl...@googlegroups.com
Worked fine. It was closer to 20 seconds.

Gerald

Kathryn Adeney

unread,
Jul 8, 2013, 11:26:30 AM7/8/13
to beagl...@googlegroups.com
That is very interesting!  What kind of switch is it plugged into?  I am using a little Netgear Gig-E ... maybe I should try 10/100 ...

Kathryn.

eskimobob

unread,
Jul 8, 2013, 11:29:18 AM7/8/13
to beagl...@googlegroups.com
Interesting indeed.  I am plugged into a 10/100 switch so doubt it is that.
What image are your running on that board Gerald? - if it is not the same as me then it is worth me trying that image.  I'd love to narrow down this problem.

Gerald Coley

unread,
Jul 8, 2013, 11:31:06 AM7/8/13
to beagl...@googlegroups.com
I am using a Trendnet TE100-S5. I am actually running right now the 7_4 test image. Before that it was the 6_20 image. No issues there that I can recall.

Gerald


--

eskimobob

unread,
Jul 8, 2013, 11:51:50 AM7/8/13
to beagl...@googlegroups.com
Oops - now I'm confused by those image numbers.  The Angstrom images seem to have 2013-06-06 release numbers so not sure what your numbers relate to.
if it helps uname -a gives me:
Linux beaglebone 3.8.13 #1 SMP Mon May 20 17:07:58 CEST 2013 armv7l GNU/Linux

Jason Kridner

unread,
Jul 8, 2013, 12:05:44 PM7/8/13
to beagl...@googlegroups.com
Do 'cat /etc/dogtag' from the shell to see the version or visit http://beagleboard.org/support/bone101/dog tag with your board connected over USB. 
--

Gerald Coley

unread,
Jul 8, 2013, 12:06:44 PM7/8/13
to beagl...@googlegroups.com
It is the date. It is explained at http://circuitco.com/support/index.php?title=Updating_The_Software

6_20 is the latest official version.

Gerald


--

eskimobob

unread,
Jul 8, 2013, 12:29:43 PM7/8/13
to beagl...@googlegroups.com
Thanks guys, I should have spotted that.
On this board, I have Cloud9 GNOME Image 2013.05.20

But the same thing happens on:
05_08
05_28


Unplugging LAN for more than 5 seconds then doing dmesg | tail shows:
[ 1736.786361] libphy: 4a101000.mdio:00 - Link is Down
[ 1736.905444] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
it never returns

root@beaglebone:~# ifup eth0

udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing

I'm sure I've tried it on 06_06 image too but can't find the card with it on so will download the latest and try again with that.
Will report :-)

Gerald Coley

unread,
Jul 8, 2013, 12:42:29 PM7/8/13
to beagl...@googlegroups.com
Might as well just move onto the 6_20 release.

Gerald

Louis Brown

unread,
Jul 8, 2013, 12:34:02 PM7/8/13
to beagl...@googlegroups.com
Just to clarify, on mine that was diagnosed with a bad Ethernet, I can transmit packets, but could not receive them. There was never an issue, on all three distros, getting it up to transmit. The Ethernet died after a couple of hours.

Louis Brown

unread,
Jul 8, 2013, 12:48:54 PM7/8/13
to beagl...@googlegroups.com
Not yet, it's supposed to be delivered today, however have people visiting so may not get to it until later this week.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/mfQwHdfHyoo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

William Park

unread,
Jul 8, 2013, 2:02:41 PM7/8/13
to beagl...@googlegroups.com
That's strange.  Because, "hotplugging" does not work for me at all.  This is true for ethernet and USB disk.  They have to be plugged in before boot.  I've tried Angstrom, Ubuntu, Debian, all latest version.

eskimobob

unread,
Jul 8, 2013, 5:28:48 PM7/8/13
to beagl...@googlegroups.com
Ok, now reflashed an A5A BBB to the 6_20 image (boy that takes some time to complete!).
Rebooted and cat /etc/dogtag shows (Cloud9 GNOME Image 2013.06.20) so I know I am on an image that Gerald has found to work.

However I get the same result as before - If I unplug the LAN cable for some seconds (more than 5) and then plug it back in, the LAN connection is lost for good.

I thought I'd try and restart connman:
root@beaglebone:/etc/systemd/system/multi-user.target.wants# systemctl restart connman
root@beaglebone:/etc/systemd/system/multi-user.target.wants# [ 882.359973] libphy: PHY 4a101000.mdio:01 not found
[ 882.365022] net eth0: phy 4a101000.mdio:01 not found on slave 1

Looking in dmesg shows:
[ 882.019827] Bridge firewalling registered
[ 882.355689] net eth0: initializing cpsw version 1.12 (0)
[ 882.359939] net eth0: phy found : id is : 0x7c0f1
[ 882.359973] libphy: PHY 4a101000.mdio:01 not found
[ 882.365022] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 882.380732] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

As another test, I thought I'd boot without the LAN connected and then try "hotplugging" it.  Upon boot, I see:

[ 6.529286] libphy: PHY 4a101000.mdio:01 not found
[ 6.534345] net eth0: phy 4a101000.mdio:01 not found on slave 1

if I book again with the LAN cable attached then I see in dmesg:

[ 6.588487] net eth0: initializing cpsw version 1.12 (0)
[ 6.590679] net eth0: phy found : id is : 0x7c0f1
[ 6.590698] libphy: PHY 4a101000.mdio:01 not found
[ 6.595752] net eth0: phy 4a101000.mdio:01 not found on slave 1
<snip>
[ 6.649978] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
<snip>
[ 10.736270] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 10.736322] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Does any of that help?

Kathryn Adeney

unread,
Jul 8, 2013, 5:38:20 PM7/8/13
to beagl...@googlegroups.com
Thanks Martin, it helps me ... to avoid replicating those steps!   I'll try upgrading when the 7_4 load Gerald is using becomes available.  

(I've been assuming the "mdio:01 not found" log is expected, because there is no second phy ...) 

Kathryn.


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/mfQwHdfHyoo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Gerald Coley

unread,
Jul 8, 2013, 7:21:07 PM7/8/13
to beagl...@googlegroups.com
Just go ahead and request and RMA.



Gerald


--

eskimobob

unread,