On Fri, May 25, 2018 at 3:19 AM, Michael Yartys <michael.yar...@protonmail.com> wrote: > Hi > > The connection doesn't work and I get no traffic. I tried rebooting with the > cable plugged in, but I still experience no connectivity. Here's the dmesg > output from e1000e: > > [telia@lulz ~]$ dmesg | grep -e1000e > [ 3.011443] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k > [ 3.011444] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. > [ 3.011686] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode > [ 3.147937] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered > PHC clock > [ 3.268727] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) > 5c:26:0a:4b:03:24 > [ 3.268730] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection > [ 3.268768] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 3041FF-0FF > [ 3.270527] e1000e 0000:00:19.0 eno1: renamed from eth0 > [ 70.656028] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: > Rx/Tx > [ 70.656040] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO > > -------------------------------------------------------------------------------------- > > Output of ethtool eno1: > > > Settings for eno1: > Supported ports: [ TP ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Supported pause frame use: No > Supports auto-negotiation: Yes > Supported FEC modes: Not reported > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Advertised pause frame use: No > Advertised auto-negotiation: Yes > Advertised FEC modes: Not reported > Speed: 10Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 1 > Transceiver: internal > Auto-negotiation: on > MDI-X: on (auto) > Supports Wake-on: pumbg > Wake-on: g > Current message level: 0x00000007 (7) > drv probe link > Link detected: yes
Some additional information that might be useful would be "ethtool -S eno1" output. That should show if the interface is receiving any packets or not. > -------------------------------------------------------------------------------------- > > In my case the driver appears to be stuck in some kind of DHCP-loop as seen > in the router logs: > > Fri May 25 12:05:46 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:05:46 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:05:50 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:05:50 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:09 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:09 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:31 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:31 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:31 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:31 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:36 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:36 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:50 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:06:50 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:13 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:13 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:13 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:13 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:20 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:20 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:32 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:32 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:51 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:51 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:58 2018 daemon.info dnsmasq-dhcp[3555]: DHCPDISCOVER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 > Fri May 25 12:07:58 2018 daemon.info dnsmasq-dhcp[3555]: DHCPOFFER(br-lan) > 192.168.1.112 5c:26:0a:4b:03:24 So from this we know that it is able to transmit traffic at least, but it may not be receiving it. We can use the "ethtool -S" output to verify that. We may also want to run something like "tcpdump -i eno1 -n" to verify if you are seeing transmits but no receives. Also you may want to verify that the router is seeing the same 10/Full link from its side. If it isn't that might be on of the reasons why traffic from it is not being received. > > I also occasionally get a gnome notification saying "Activation of network > connection failed". Whenever that happens the system freezes for about 2 > seconds. That is probably the DHCP timing out if it isn't receiving the offer from the router. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
