Sorry for the late response. Here's the info you requested: maintenance@beaglebone:~$ uname -r 4.4.54-ti-r93
On Tuesday, September 29, 2020 at 9:32:20 AM UTC-4 RobertCNelson wrote: > Oh, that looks fun, specially with no errors over dmesg.. > > Which kernel version? > > uname -r ? > > Regards, > > On Tue, Sep 29, 2020 at 8:24 AM suprock tech <techs...@gmail.com> wrote: > > > > Sorry it took a few days but heres some logs. > > > > > > Working beaglebone, Unit #1542: > > dmesg output when plugging in a cable: > > [ 74.039867] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - > > flow control off > > [ 74.040069] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > > [ 74.162638] 8021q: 802.1Q VLAN Support v1.8 > > [ 74.162796] 8021q: adding VLAN 0 to HW filter on device eth0 > > > > maintenance@beaglebone:~$ ifconfig > > eth0 Link encap:Ethernet HWaddr 38:d2:69:52:69:10 > > inet addr:192.168.2.155 Bcast:192.168.2.255 Mask:255.255.255.0 > > inet6 addr: 2601:18d:8901:ec80:3ad2:69ff:fe52:6910/64 > > Scope:Global > > inet6 addr: fe80::3ad2:69ff:fe52:6910/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > > RX packets:34 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:90 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:4103 (4.0 KiB) TX bytes:15847 (15.4 KiB) > > Interrupt:173 > > > > Iperf works as a server: > > maintenance@beaglebone:~$ iperf -s > > ------------------------------------------------------------ > > Server listening on TCP port 5001 > > TCP window size: 85.3 KByte (default) > > ------------------------------------------------------------ > > [ 4] local 192.168.2.155 port 5001 connected with 192.168.2.188 port > 11268 > > [ ID] Interval Transfer Bandwidth > > [ 4] 0.0-10.0 sec 114 MBytes 94.9 Mbits/sec > > > > Iperf works as a client too: > > maintenance@beaglebone:~$ iperf -c 192.168.2.188 > > ------------------------------------------------------------ > > Client connecting to 192.168.2.188, TCP port 5001 > > TCP window size: 43.8 KByte (default) > > ------------------------------------------------------------ > > [ 3] local 192.168.2.155 port 45668 connected with 192.168.2.188 port > 5001 > > [ ID] Interval Transfer Bandwidth > > [ 3] 0.0-10.0 sec 113 MBytes 94.7 Mbits/sec > > > > > > > > Unit #5788: > > dmesg output when plugging in a cable: > > [ 73.783078] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - > > flow control rx/tx > > [ 73.783175] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > > [ 73.873892] 8021q: 802.1Q VLAN Support v1.8 > > [ 73.873966] 8021q: adding VLAN 0 to HW filter on device eth0 > > > > Despite what's shown in dmesg the beaglebone auto negotiates with the > > switch to 100Mbps at half duplex (not full). The link lights on both > > ends (beaglebone and switch) are on. The device cannot get an address: > > maintenance@beaglebone:~$ ifconfig > > eth0 Link encap:Ethernet HWaddr 04:79:b7:ac:27:ba > > inet6 addr: fe80::679:b7ff:feac:27ba/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > > RX packets:1 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:590 (590.0 B) TX bytes:6374 (6.2 KiB) > > Interrupt:173 > > > > > > > > Unit #5104: > > dmesg output when plugging in a cable: > > [ 106.355039] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - > > flow control off > > [ 106.355138] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > > [ 106.430626] 8021q: 802.1Q VLAN Support v1.8 > > [ 106.430698] 8021q: adding VLAN 0 to HW filter on device eth0 > > > > does get an address: > > maintenance@beaglebone:~$ ifconfig > > eth0 Link encap:Ethernet HWaddr 04:79:b7:a3:6b:e8 > > inet addr:192.168.2.151 Bcast:192.168.2.255 Mask:255.255.255.0 > > inet6 addr: fe80::679:b7ff:fea3:6be8/64 Scope:Link > > inet6 addr: 2601:18d:8901:ec80:679:b7ff:fea3:6be8/64 Scope:Global > > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:87 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:4151 (4.0 KiB) TX bytes:17119 (16.7 KiB) > > Interrupt:173 > > > > Iperf works as a server (using iperf -c 192.168.2.151 on the other end): > > maintenance@beaglebone:~$ iperf -s > > ------------------------------------------------------------ > > Server listening on TCP port 5001 > > TCP window size: 85.3 KByte (default) > > ------------------------------------------------------------ > > [ 4] local 192.168.2.151 port 5001 connected with 192.168.2.188 port > 10788 > > [ ID] Interval Transfer Bandwidth > > [ 4] 0.0-10.0 sec 113 MBytes 94.7 Mbits/sec > > > > Iperf locks up completely when the roles are reversed. I had to > > terminate the process on the other computer, and it gave crazy results > > on the beagle: > > maintenance@beaglebone:~$ iperf -c 192.168.2.188 > > ------------------------------------------------------------ > > Client connecting to 192.168.2.188, TCP port 5001 > > TCP window size: 43.8 KByte (default) > > ------------------------------------------------------------ > > [ 3] local 192.168.2.151 port 53494 connected with 192.168.2.188 port > 5001 > > [ ID] Interval Transfer Bandwidth > > [ 3] 0.0-139.2 sec 4.00 GBytes 247 Mbits/sec > > > > Clearly it's having problems sending packets in one of the directions. > > > > > > > > Unit #1900: > > No dmesg change when plugging in cable. > > No link lights (on either end). > > No address: > > maintenance@beaglebone:~$ ifconfig > > eth0 Link encap:Ethernet HWaddr ec:24:b8:9a:7e:9c > > UP BROADCAST MULTICAST DYNAMIC MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > Interrupt:173 > > > > On Tuesday, September 15, 2020 at 6:49:01 PM UTC-4 RobertCNelson wrote: > >> > >> On Mon, Sep 14, 2020 at 12:58 PM suprock tech <techs...@gmail.com> > wrote: > >> > > >> > beagle bone black, rev c > >> > >> When you say "fail" can you provide any dmesg info or kernel log, or > >> serial log or, or... > >> > >> 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 beagleboard...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/64bbd315-34f5-49c1-b541-ea637a38bd15n%40googlegroups.com > . > > > > -- > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/2c29d15c-0e87-42d4-84a3-ed8c9e75b2bbn%40googlegroups.com.