Ethernet unavailable or slow, Testing

If none of the more specific forums is the right place to ask

Ethernet unavailable or slow, Testing

Postby noober1983 » 2021-02-08 04:58

Hi, all.
I'm running Testing on two laptops. One has an Intel Ethernet I218-LM, and the other one has a Realtek RTL810xE (info from inxi -Nxx).
When a large upgrade is available, I connect them with the ehternet cable to download the packages. I just upgraded both of them, but the one with the Intel card took more than 30 minutes to download 2095MB of packages, whereas the other one took less than 4 minutes. Is there a way of knowing if this is inevitable, or rather if I can configure the slow ethernet device to speed up things a bit?

This slow computer has trouble recongnising the Ethernet port after resuming from hibernation. This last time I had to reboot thrice to have a working ethernet connection. When I ran the command line version of Network Manager this device appeared in gray as "unavailable". I checked both computers and the contents of /etc/network/interfaces is identical in both:

Code: Select all
# The loopback network interface
auto lo
iface lo inet loopback


I have no idea what other files to compare, I'd never had this issue before, and both laptops have been running Testing for quite a while (the fast one for almost 3 years now; the other one, almost a year).

Thanks!
Quid non intellegas aut tace aut disce.
noober1983
 
Posts: 71
Joined: 2012-04-03 00:12
Location: MX

Re: Ethernet unavailable or slow, Testing

Postby Head_on_a_Stick » 2021-02-08 10:33

Can we see
Code: Select all
# dmesg | grep e1000e

Possibly relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1038156
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 13280
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Ethernet unavailable or slow, Testing

Postby noober1983 » 2021-02-08 16:25

Head_on_a_Stick wrote:Can we see
Code: Select all
# dmesg | grep e1000e

Possibly relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1038156


Hi. This is the output:
Code: Select all
dmesg | grep e1000e
[    1.483626] e1000e: Intel(R) PRO/1000 Network Driver
[    1.483627] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.483791] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    1.679449] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[    1.744334] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) f8:ca:b8:06:b2:c5
[    1.744335] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    1.744364] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[    1.745347] e1000e 0000:00:19.0 eno1: renamed from eth0


Here's the info from the device:
Code: Select all
lspci -vvvn -k -s 00:19.0
00:19.0 0200: 8086:15a2 (rev 03)
   DeviceName:  Onboard LAN
   Subsystem: 1028:062b
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Interrupt: pin A routed to IRQ 47
   IOMMU group: 5
   Region 0: Memory at f7200000 (32-bit, non-prefetchable) [disabled] [size=128K]
   Region 1: Memory at f7243000 (32-bit, non-prefetchable) [disabled] [size=4K]
   Region 2: I/O ports at f080 [disabled] [size=32]
   Capabilities: [c8] Power Management version 2
      Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
      Status: D3 NoSoftRst- PME-Enable+ DSel=0 DScale=1 PME-
   Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
      Address: 00000000fee00338  Data: 0000
   Capabilities: [e0] PCI Advanced Features
      AFCap: TP+ FLR+
      AFCtrl: FLR-
      AFStatus: TP-
   Kernel driver in use: e1000e
   Kernel modules: e1000e


Code: Select all
ethtool -a eno1
Pause parameters for eno1:
Autonegotiate:   on
RX:      on
TX:      on


Code: Select all
ethtool -i eno1
driver: e1000e
version: 5.10.0-3-amd64
firmware-version: 0.2-3
expansion-rom-version:
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes


I just connected the ethernet cable, but the nm-applet doesn't show the machine connected to this network. I didn't resume from hibernation, this is a "fresh boot" after shutdown. After connecting I ran dmesg|grep -i eth and found this line:
Code: Select all
[   10.569394] systemd[1]: /lib/systemd/system/clamav-freshclam.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

Upon desconnecting or connecting the cable I get 46 lines with the message:
Code: Select all
[ 2124.939477] e1000e 0000:00:19.0 eno1: PHY Wakeup cause - Link Status Change

I suppose this makes sense, but why are there 46 lines with this message?
I'm running kernel 5.10.12-0 (Debian package version 5.10.0-3-amd).

EDIT: upon restart I noticed that the device is DOWN when I run ip:
Code: Select all
ip addr show dev eno1
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether f8:ca:b8:06:b2:c5 brd ff:ff:ff:ff:ff:ff
    altname enp0s25

However, ifup doesn't recognise this device:
Code: Select all
ifup eno1
ifup: unknown interface eno1

I also tried the above command with the alias given by ip (enp0s25), with the same result. So apparently I cannot even raise the interface.

Thanks!
Quid non intellegas aut tace aut disce.
noober1983
 
Posts: 71
Joined: 2012-04-03 00:12
Location: MX

Re: Ethernet unavailable or slow, Testing

Postby noober1983 » 2021-02-10 20:19

Update: On the slow one, the one with no ethernet at first, I deleted the file /etc/NetworkManager/system-connections/Wired Connection 1.nmconnection, restarted, and now I can connect to the ethernet network, but it takes exactly 6 tries everytime; the nm-applet system tray icon starts flickering, then I get a notification saying the wired network got disconnected, and on the 6th attempt it stays connected. I queried with dmesg:
Code: Select all
dmesg -H|grep eno1
dmesg -H|grep eno1
[Feb10 14:51] e1000e 0000:00:19.0 eno1: NIC Link is Down
[ +17.675677] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[  +8.599806] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[  +8.523726] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[  +8.523938] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[  +8.511955] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[Feb10 14:52] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[  +2.410293] e1000e 0000:00:19.0 eno1: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None

Again, I am able to connect to the wired network but only after exactly 6 attempts; as far as I can understand the above output, the network really does connect briefly and then it gets disconnected, but I'm not quite sure about that.

Please help!
Quid non intellegas aut tace aut disce.
noober1983
 
Posts: 71
Joined: 2012-04-03 00:12
Location: MX


Return to General Questions

Who is online

Users browsing this forum: No registered users and 13 guests

fashionable