On Mon, Jan 25, 2016 at 12:14 PM, Robert Nelson <[email protected]> wrote: > On Mon, Jan 25, 2016 at 12:05 PM, Soapy Smith <[email protected]> wrote: >> I've always seen marginal success in USB connectivity with BBB. I recently >> acquired a couple of BBG, at first I thought these were solid, but now I am >> seeing problems. >> >> There is a difference seen in the host computer from the shell command >> ifconfig -a. >> Here is ifconfig -a for a working BBG: >> >> eth0 Link encap:Ethernet HWaddr 6c:0b:84:09:f9:de >> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 >> inet6 addr: fe80::6e0b:84ff:fe09:f9de/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:982290 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:613548 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:1196203986 (1.1 GB) TX bytes:107826806 (107.8 MB) >> Interrupt:20 Memory:f7100000-f7120000 >> >> eth1 Link encap:Ethernet HWaddr ec:24:b8:f6:e1:7c >> inet addr:192.168.7.1 Bcast:192.168.7.255 Mask:255.255.255.0 >> inet6 addr: fe80::ee24:b8ff:fef6:e17c/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:64 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:63 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:10319 (10.3 KB) TX bytes:15361 (15.3 KB) >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 Metric:1 >> RX packets:30214 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:30214 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:3210722 (3.2 MB) TX bytes:3210722 (3.2 MB) >> >> Now here is a different BBG flashed with the exact same image Debian 8.2: >> eth0 Link encap:Ethernet HWaddr 6c:0b:84:09:f9:de >> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 >> inet6 addr: fe80::6e0b:84ff:fe09:f9de/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:982671 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:613978 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:1196254756 (1.1 GB) TX bytes:107922637 (107.9 MB) >> Interrupt:20 Memory:f7100000-f7120000 >> >> eth4 Link encap:Ethernet HWaddr 68:c9:0b:ed:25:23 >> inet6 addr: fe80::6ac9:bff:feed:2523/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:42 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:6487 (6.4 KB) TX bytes:12510 (12.5 KB) >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 Metric:1 >> RX packets:30316 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:30316 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:3218638 (3.2 MB) TX bytes:3218638 (3.2 MB) >> >> The obvious difference is seen at eth4 for the non-working versus eth1 for >> the working board. >> eth1 (the working board) is getting an inet address. >> eth4 (the non-working board) is not getting an inet address.
Oh, and it's actually reversed... BBG runs the dhcp server that hands out the 192.168.7.1 ip address to your ubuntu host... Regards, -- Robert Nelson https://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 [email protected]. For more options, visit https://groups.google.com/d/optout.
