* Fwd: Problem with r8169 module [not found] <CAOKSTBtcsqFZTzvgF-HQGRmvcd=Qanq7r2PREB2qGmnSQZJ_-A@mail.gmail.com> @ 2020-11-02 3:36 ` Gilberto Nunes 2020-11-02 8:14 ` Heiner Kallweit 0 siblings, 1 reply; 6+ messages in thread From: Gilberto Nunes @ 2020-11-02 3:36 UTC (permalink / raw) To: netdev Hi there I am in trouble when using newer kernels than 5.4.x regarding Realtek NIC r8169 Kernel 5.9.2-050902-lowlatency (from https://kernel.ubuntu.com/~kernel-ppa/mainline/ and also compiled from kernel.org) Generic FE-GE Realtek PHY r8169-101:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling! r8169 0000:01:00.1 enp1s0f1: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx Kernel 5.4.73-050473-lowlatency (from https://kernel.ubuntu.com/~kernel-ppa/mainline/) IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f1: link becomes ready r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx Cable is ok! I double check it.... --- Gilberto Nunes Ferreira ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: Problem with r8169 module 2020-11-02 3:36 ` Fwd: Problem with r8169 module Gilberto Nunes @ 2020-11-02 8:14 ` Heiner Kallweit 2020-11-02 13:20 ` Gilberto Nunes 0 siblings, 1 reply; 6+ messages in thread From: Heiner Kallweit @ 2020-11-02 8:14 UTC (permalink / raw) To: Gilberto Nunes, netdev On 02.11.2020 04:36, Gilberto Nunes wrote: > Hi there > > I am in trouble when using newer kernels than 5.4.x regarding Realtek NIC r8169 > > Kernel 5.9.2-050902-lowlatency (from > https://kernel.ubuntu.com/~kernel-ppa/mainline/ and also compiled from > kernel.org) > > Generic FE-GE Realtek PHY r8169-101:00: Downshift occurred from > negotiated speed 1Gbps to actual speed 100Mbps, check cabling! > r8169 0000:01:00.1 enp1s0f1: Link is Up - 100Mbps/Full (downshifted) - > flow control rx/tx > > Kernel 5.4.73-050473-lowlatency (from > https://kernel.ubuntu.com/~kernel-ppa/mainline/) > > IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f1: link becomes ready > r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx > > Cable is ok! I double check it.... > The downshift hint didn't exist yet in 5.4. Can you check what the actual link speed is under 5.4 (e.g. using iperf3). Under 5.9: Does the downshift happen directly when the link is initially established, or after some time? If link speed actually differs, then please: - provide full dmesg log - ideally do a git bisect to find the offending commit (as issue most likely is chip version / system dependent) > > > > > --- > Gilberto Nunes Ferreira > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: Problem with r8169 module 2020-11-02 8:14 ` Heiner Kallweit @ 2020-11-02 13:20 ` Gilberto Nunes 2020-11-02 13:39 ` Heiner Kallweit 0 siblings, 1 reply; 6+ messages in thread From: Gilberto Nunes @ 2020-11-02 13:20 UTC (permalink / raw) To: Heiner Kallweit; +Cc: netdev Hi ethtool using 5.4 ethtool enp1s0f1 Settings for enp1s0f1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only 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: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes ethtool using 5.9 ethtool enp1s0f1 Settings for enp1s0f1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only 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: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes ethtool in 5.9.3 ethtool enp1s0f1 Settings for enp1s0f1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only 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: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d In 5.9 the downshift occurs right away when I turn the laptop on. 5.4 dmesg https://pastebin.pl/view/3eb41a4b 5.9.3 dmesg https://pastebin.pl/view/c07f6c22 --- Gilberto Nunes Ferreira Em seg., 2 de nov. de 2020 às 05:14, Heiner Kallweit <hkallweit1@gmail.com> escreveu: > > On 02.11.2020 04:36, Gilberto Nunes wrote: > > Hi there > > > > I am in trouble when using newer kernels than 5.4.x regarding Realtek NIC r8169 > > > > Kernel 5.9.2-050902-lowlatency (from > > https://kernel.ubuntu.com/~kernel-ppa/mainline/ and also compiled from > > kernel.org) > > > > Generic FE-GE Realtek PHY r8169-101:00: Downshift occurred from > > negotiated speed 1Gbps to actual speed 100Mbps, check cabling! > > r8169 0000:01:00.1 enp1s0f1: Link is Up - 100Mbps/Full (downshifted) - > > flow control rx/tx > > > > Kernel 5.4.73-050473-lowlatency (from > > https://kernel.ubuntu.com/~kernel-ppa/mainline/) > > > > IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f1: link becomes ready > > r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx > > > > Cable is ok! I double check it.... > > > The downshift hint didn't exist yet in 5.4. Can you check what the actual > link speed is under 5.4 (e.g. using iperf3). > > Under 5.9: > Does the downshift happen directly when the link is initially established, > or after some time? > > If link speed actually differs, then please: > - provide full dmesg log > - ideally do a git bisect to find the offending commit > (as issue most likely is chip version / system dependent) > > > > > > > > > > > --- > > Gilberto Nunes Ferreira > > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: Problem with r8169 module 2020-11-02 13:20 ` Gilberto Nunes @ 2020-11-02 13:39 ` Heiner Kallweit 2020-11-02 16:29 ` Gilberto Nunes 0 siblings, 1 reply; 6+ messages in thread From: Heiner Kallweit @ 2020-11-02 13:39 UTC (permalink / raw) To: Gilberto Nunes; +Cc: netdev On 02.11.2020 14:20, Gilberto Nunes wrote: > Hi > > ethtool using 5.4 > ethtool doesn't know about the actual speed, because the downshift occurs PHY-internally. Please test actual the speed. Alternatively provide the output of ethtool -d <if>, the RTL8169 chip family has an internal register refkecting the actual link speed. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: Problem with r8169 module 2020-11-02 13:39 ` Heiner Kallweit @ 2020-11-02 16:29 ` Gilberto Nunes 2020-11-02 16:50 ` Heiner Kallweit 0 siblings, 1 reply; 6+ messages in thread From: Gilberto Nunes @ 2020-11-02 16:29 UTC (permalink / raw) To: Heiner Kallweit; +Cc: netdev From kernel 5.4 ethtool -d enp1s0f1 RealTek RTL8411 registers: -------------------------------------------------------- 0x00: MAC Address 98:29:a6:e6:e5:6a 0x08: Multicast Address Filter 0xffffffff 0xffffffff 0x10: Dump Tally Counter Command 0xffffe000 0x00000000 0x20: Tx Normal Priority Ring Addr 0xff50b000 0x00000000 0x28: Tx High Priority Ring Addr 0x00000000 0x00000000 0x30: Flash memory read/write 0x00000000 0x34: Early Rx Byte Count 0 0x36: Early Rx Status 0x00 0x37: Command 0x0c Rx on, Tx on 0x3C: Interrupt Mask 0x003f LinkChg RxNoBuf TxErr TxOK RxErr RxOK 0x3E: Interrupt Status 0x0000 0x40: Tx Configuration 0x5f800f80 0x44: Rx Configuration 0x0002cf0f 0x48: Timer count 0x00000000 0x4C: Missed packet counter 0x000000 0x50: EEPROM Command 0x10 0x51: Config 0 0x00 0x52: Config 1 0xcf 0x53: Config 2 0x3c 0x54: Config 3 0x60 0x55: Config 4 0x11 0x56: Config 5 0x02 0x58: Timer interrupt 0x00000000 0x5C: Multiple Interrupt Select 0x0000 0x60: PHY access 0x00000000 0x64: TBI control and status 0x12011025 0x68: TBI Autonegotiation advertisement (ANAR) 0xf02c 0x6A: TBI Link partner ability (LPAR) 0x8000 0x6C: PHY status 0xeb 0x84: PM wakeup frame 0 0x00000000 0x00000000 0x8C: PM wakeup frame 1 0x00000000 0x00000000 0x94: PM wakeup frame 2 (low) 0x00000000 0x00000000 0x9C: PM wakeup frame 2 (high) 0x00000000 0x00000000 0xA4: PM wakeup frame 3 (low) 0x00000000 0x00000000 0xAC: PM wakeup frame 3 (high) 0x00000000 0x00000001 0xB4: PM wakeup frame 4 (low) 0x00000000 0xd205cde1 0xBC: PM wakeup frame 4 (high) 0x00000000 0x00000000 0xC4: Wakeup frame 0 CRC 0x0000 0xC6: Wakeup frame 1 CRC 0x0000 0xC8: Wakeup frame 2 CRC 0x0000 0xCA: Wakeup frame 3 CRC 0x0000 0xCC: Wakeup frame 4 CRC 0x0000 0xDA: RX packet maximum size 0x4000 0xE0: C+ Command 0x2060 VLAN de-tagging RX checksumming 0xE2: Interrupt Mitigation 0x0000 TxTimer: 0 TxPackets: 0 RxTimer: 0 RxPackets: 0 0xE4: Rx Ring Addr 0xff50f000 0x00000000 0xEC: Early Tx threshold 0x27 0xF0: Func Event 0x0000003f 0xF4: Func Event Mask 0x00000000 0xF8: Func Preset State 0x00000003 0xFC: Func Force Event 0x00000000 From kernel 5.9.3 ethtool -d enp1s0f1 RealTek RTL8411 registers: -------------------------------------------------------- 0x00: MAC Address 98:29:a6:e6:e5:6a 0x08: Multicast Address Filter 0xffffffff 0xffffffff 0x10: Dump Tally Counter Command 0xffffe000 0x00000000 0x20: Tx Normal Priority Ring Addr 0xff582000 0x00000000 0x28: Tx High Priority Ring Addr 0x00000000 0x00000000 0x30: Flash memory read/write 0x00000000 0x34: Early Rx Byte Count 0 0x36: Early Rx Status 0x00 0x37: Command 0x0c Rx on, Tx on 0x3C: Interrupt Mask 0x003f LinkChg RxNoBuf TxErr TxOK RxErr RxOK 0x3E: Interrupt Status 0x0000 0x40: Tx Configuration 0x5f800f80 0x44: Rx Configuration 0x0002cf0f 0x48: Timer count 0x00000000 0x4C: Missed packet counter 0x000000 0x50: EEPROM Command 0x10 0x51: Config 0 0x00 0x52: Config 1 0xcf 0x53: Config 2 0x3c 0x54: Config 3 0x60 0x55: Config 4 0x11 0x56: Config 5 0x02 0x58: Timer interrupt 0x00000000 0x5C: Multiple Interrupt Select 0x0000 0x60: PHY access 0x00000000 0x64: TBI control and status 0x12011025 0x68: TBI Autonegotiation advertisement (ANAR) 0xf02c 0x6A: TBI Link partner ability (LPAR) 0x8000 0x6C: PHY status 0xeb 0x84: PM wakeup frame 0 0x00000000 0x00000000 0x8C: PM wakeup frame 1 0x00000000 0x00000000 0x94: PM wakeup frame 2 (low) 0x00000000 0x00000000 0x9C: PM wakeup frame 2 (high) 0x00000000 0x00000000 0xA4: PM wakeup frame 3 (low) 0x00000000 0x00000000 0xAC: PM wakeup frame 3 (high) 0x00000000 0x00000001 0xB4: PM wakeup frame 4 (low) 0x00000000 0xd21a30de 0xBC: PM wakeup frame 4 (high) 0x00000000 0x00000000 0xC4: Wakeup frame 0 CRC 0x0000 0xC6: Wakeup frame 1 CRC 0x0000 0xC8: Wakeup frame 2 CRC 0x0000 0xCA: Wakeup frame 3 CRC 0x0000 0xCC: Wakeup frame 4 CRC 0x0000 0xDA: RX packet maximum size 0x4000 0xE0: C+ Command 0x2060 VLAN de-tagging RX checksumming 0xE2: Interrupt Mitigation 0x0000 TxTimer: 0 TxPackets: 0 RxTimer: 0 RxPackets: 0 0xE4: Rx Ring Addr 0xff583000 0x00000000 0xEC: Early Tx threshold 0x27 0xF0: Func Event 0x0000003f 0xF4: Func Event Mask 0x00000000 0xF8: Func Preset State 0x00000003 0xFC: Func Force Event 0x00000000 I also noticed this message when ran update-initramfs -k all -u when installed kernel 5.9.3. I had made a git clone from linux-firmware and copied this missed firmware but no change! W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 --- Gilberto Nunes Ferreira Em seg., 2 de nov. de 2020 às 10:40, Heiner Kallweit <hkallweit1@gmail.com> escreveu: > > On 02.11.2020 14:20, Gilberto Nunes wrote: > > Hi > > > > ethtool using 5.4 > > > ethtool doesn't know about the actual speed, because the downshift > occurs PHY-internally. Please test actual the speed. > Alternatively provide the output of ethtool -d <if>, the RTL8169 > chip family has an internal register refkecting the actual link speed. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: Problem with r8169 module 2020-11-02 16:29 ` Gilberto Nunes @ 2020-11-02 16:50 ` Heiner Kallweit 0 siblings, 0 replies; 6+ messages in thread From: Heiner Kallweit @ 2020-11-02 16:50 UTC (permalink / raw) To: Gilberto Nunes; +Cc: netdev On 02.11.2020 17:29, Gilberto Nunes wrote: >>From kernel 5.4 > > ethtool -d enp1s0f1 > RealTek RTL8411 registers: > -------------------------------------------------------- > 0x00: MAC Address 98:29:a6:e6:e5:6a > 0x08: Multicast Address Filter 0xffffffff 0xffffffff > 0x10: Dump Tally Counter Command 0xffffe000 0x00000000 > 0x20: Tx Normal Priority Ring Addr 0xff50b000 0x00000000 > 0x28: Tx High Priority Ring Addr 0x00000000 0x00000000 > 0x30: Flash memory read/write 0x00000000 > 0x34: Early Rx Byte Count 0 > 0x36: Early Rx Status 0x00 > 0x37: Command 0x0c > Rx on, Tx on > 0x3C: Interrupt Mask 0x003f > LinkChg RxNoBuf TxErr TxOK RxErr RxOK > 0x3E: Interrupt Status 0x0000 > > 0x40: Tx Configuration 0x5f800f80 > 0x44: Rx Configuration 0x0002cf0f > 0x48: Timer count 0x00000000 > 0x4C: Missed packet counter 0x000000 > 0x50: EEPROM Command 0x10 > 0x51: Config 0 0x00 > 0x52: Config 1 0xcf > 0x53: Config 2 0x3c > 0x54: Config 3 0x60 > 0x55: Config 4 0x11 > 0x56: Config 5 0x02 > 0x58: Timer interrupt 0x00000000 > 0x5C: Multiple Interrupt Select 0x0000 > 0x60: PHY access 0x00000000 > 0x64: TBI control and status 0x12011025 > 0x68: TBI Autonegotiation advertisement (ANAR) 0xf02c > 0x6A: TBI Link partner ability (LPAR) 0x8000 > 0x6C: PHY status 0xeb Thanks for the additional info. PHY status 0xeb means that a link is established at 100Mbps, see following from the driver source. Having said that the downshift happens also under 5.4, it's just not reported. /* rtl8169_PHYstatus */ TBI_Enable = 0x80, TxFlowCtrl = 0x40, RxFlowCtrl = 0x20, _1000bpsF = 0x10, _100bps = 0x08, _10bps = 0x04, LinkStatus = 0x02, FullDup = 0x01, 1Gbps needs all four cable pairs, whilst 100Mbps is happy with two. Therefore one reason could be a physical problem (e.g. corrosion) with a pin in a RJ45 port. (in case you tried other cables already and you can rule out a cable problem) > 0x84: PM wakeup frame 0 0x00000000 0x00000000 > 0x8C: PM wakeup frame 1 0x00000000 0x00000000 > 0x94: PM wakeup frame 2 (low) 0x00000000 0x00000000 > 0x9C: PM wakeup frame 2 (high) 0x00000000 0x00000000 > 0xA4: PM wakeup frame 3 (low) 0x00000000 0x00000000 > 0xAC: PM wakeup frame 3 (high) 0x00000000 0x00000001 > 0xB4: PM wakeup frame 4 (low) 0x00000000 0xd205cde1 > 0xBC: PM wakeup frame 4 (high) 0x00000000 0x00000000 > 0xC4: Wakeup frame 0 CRC 0x0000 > 0xC6: Wakeup frame 1 CRC 0x0000 > 0xC8: Wakeup frame 2 CRC 0x0000 > 0xCA: Wakeup frame 3 CRC 0x0000 > 0xCC: Wakeup frame 4 CRC 0x0000 > 0xDA: RX packet maximum size 0x4000 > 0xE0: C+ Command 0x2060 > VLAN de-tagging > RX checksumming > 0xE2: Interrupt Mitigation 0x0000 > TxTimer: 0 > TxPackets: 0 > RxTimer: 0 > RxPackets: 0 > 0xE4: Rx Ring Addr 0xff50f000 0x00000000 > 0xEC: Early Tx threshold 0x27 > 0xF0: Func Event 0x0000003f > 0xF4: Func Event Mask 0x00000000 > 0xF8: Func Preset State 0x00000003 > 0xFC: Func Force Event 0x00000000 > >>From kernel 5.9.3 > > ethtool -d enp1s0f1 > RealTek RTL8411 registers: > -------------------------------------------------------- > 0x00: MAC Address 98:29:a6:e6:e5:6a > 0x08: Multicast Address Filter 0xffffffff 0xffffffff > 0x10: Dump Tally Counter Command 0xffffe000 0x00000000 > 0x20: Tx Normal Priority Ring Addr 0xff582000 0x00000000 > 0x28: Tx High Priority Ring Addr 0x00000000 0x00000000 > 0x30: Flash memory read/write 0x00000000 > 0x34: Early Rx Byte Count 0 > 0x36: Early Rx Status 0x00 > 0x37: Command 0x0c > Rx on, Tx on > 0x3C: Interrupt Mask 0x003f > LinkChg RxNoBuf TxErr TxOK RxErr RxOK > 0x3E: Interrupt Status 0x0000 > > 0x40: Tx Configuration 0x5f800f80 > 0x44: Rx Configuration 0x0002cf0f > 0x48: Timer count 0x00000000 > 0x4C: Missed packet counter 0x000000 > 0x50: EEPROM Command 0x10 > 0x51: Config 0 0x00 > 0x52: Config 1 0xcf > 0x53: Config 2 0x3c > 0x54: Config 3 0x60 > 0x55: Config 4 0x11 > 0x56: Config 5 0x02 > 0x58: Timer interrupt 0x00000000 > 0x5C: Multiple Interrupt Select 0x0000 > 0x60: PHY access 0x00000000 > 0x64: TBI control and status 0x12011025 > 0x68: TBI Autonegotiation advertisement (ANAR) 0xf02c > 0x6A: TBI Link partner ability (LPAR) 0x8000 > 0x6C: PHY status 0xeb > 0x84: PM wakeup frame 0 0x00000000 0x00000000 > 0x8C: PM wakeup frame 1 0x00000000 0x00000000 > 0x94: PM wakeup frame 2 (low) 0x00000000 0x00000000 > 0x9C: PM wakeup frame 2 (high) 0x00000000 0x00000000 > 0xA4: PM wakeup frame 3 (low) 0x00000000 0x00000000 > 0xAC: PM wakeup frame 3 (high) 0x00000000 0x00000001 > 0xB4: PM wakeup frame 4 (low) 0x00000000 0xd21a30de > 0xBC: PM wakeup frame 4 (high) 0x00000000 0x00000000 > 0xC4: Wakeup frame 0 CRC 0x0000 > 0xC6: Wakeup frame 1 CRC 0x0000 > 0xC8: Wakeup frame 2 CRC 0x0000 > 0xCA: Wakeup frame 3 CRC 0x0000 > 0xCC: Wakeup frame 4 CRC 0x0000 > 0xDA: RX packet maximum size 0x4000 > 0xE0: C+ Command 0x2060 > VLAN de-tagging > RX checksumming > 0xE2: Interrupt Mitigation 0x0000 > TxTimer: 0 > TxPackets: 0 > RxTimer: 0 > RxPackets: 0 > 0xE4: Rx Ring Addr 0xff583000 0x00000000 > 0xEC: Early Tx threshold 0x27 > 0xF0: Func Event 0x0000003f > 0xF4: Func Event Mask 0x00000000 > 0xF8: Func Preset State 0x00000003 > 0xFC: Func Force Event 0x00000000 > > > I also noticed this message when ran update-initramfs -k all -u when > installed kernel 5.9.3. > I had made a git clone from linux-firmware and copied this missed > firmware but no change! > > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for > module r8169 > > > > --- > Gilberto Nunes Ferreira > > > > Em seg., 2 de nov. de 2020 às 10:40, Heiner Kallweit > <hkallweit1@gmail.com> escreveu: >> >> On 02.11.2020 14:20, Gilberto Nunes wrote: >>> Hi >>> >>> ethtool using 5.4 >>> >> ethtool doesn't know about the actual speed, because the downshift >> occurs PHY-internally. Please test actual the speed. >> Alternatively provide the output of ethtool -d <if>, the RTL8169 >> chip family has an internal register refkecting the actual link speed. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-11-02 16:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAOKSTBtcsqFZTzvgF-HQGRmvcd=Qanq7r2PREB2qGmnSQZJ_-A@mail.gmail.com>
2020-11-02 3:36 ` Fwd: Problem with r8169 module Gilberto Nunes
2020-11-02 8:14 ` Heiner Kallweit
2020-11-02 13:20 ` Gilberto Nunes
2020-11-02 13:39 ` Heiner Kallweit
2020-11-02 16:29 ` Gilberto Nunes
2020-11-02 16:50 ` Heiner Kallweit
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).