Page 1 of 4 123 ... LastLast
Results 1 to 10 of 40

Thread: Update with kernel 5.4 - No Intel RJ45 network anymore

  1. #1

    Angry Update with kernel 5.4 - No Intel RJ45 network anymore

    Hi!

    Updated a Dell Latitude

    Code:
    lspci
    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
    00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
    00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
    00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
    00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
    00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 04)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
    09:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05)
    09:00.1 SD Host controller: O2 Micro, Inc. OZ600RJ0/OZ900RJ0/OZ600RJS SD/MMC Card Reader Controller (rev 05)
    09:00.2 Mass storage controller: O2 Micro, Inc. O2 Flash Memory Card (rev 05)
    subsequently no network connection:


    https://paste.opensuse.org/43716487

    The router does not even see a request for an IP.

    Switching to Wicked did not help. Rebooting to old 5.3 kernel and network is back. Also if I add a RJ45-USB adapter, networking is working as expected...

    Is there a known bug with Intel networkadapters in 5.4? (didn't look for other changes comming in with the kernel updates, some 200 packages being updated...).
    Kind regards

    raspu

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,964

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    What failures do dmesg and journalctl report?
    Code:
    sudo journalctl -b | grep -A7 ailed
    dmesg | grep -A7 ailed
    When did you reboot last?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  3. #3

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Hi and thanks!

    Code:
    sudo journalctl -b | grep -A7 ailed
    Jan 11 12:57:36 asdfg kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
    Jan 11 12:57:36 asdfg kernel: PCI host bridge to bus 0000:00
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
    Jan 11 12:57:36 asdfg kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
    --
    Jan 11 12:57:39 asdfg systemd[1]: haveged.service: Failed with result 'exit-code'.
    Jan 11 12:57:39 asdfg systemd[1]: plymouth-switch-root.service: Succeeded.
    Jan 11 12:57:39 asdfg systemd[1]: Started Plymouth switch root service.
    Jan 11 12:57:39 asdfg systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart.
    Jan 11 12:57:39 asdfg systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1.
    Jan 11 12:57:39 asdfg systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Jan 11 12:57:39 asdfg systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Jan 11 12:57:39 asdfg systemd[1]: Starting Switch Root...
    --
    Jan 11 11:57:46 asdfg systemd[1]: haveged.service: Failed with result 'exit-code'.
    Jan 11 11:57:46 asdfg systemd[1]: initrd-switch-root.service: Succeeded.
    Jan 11 11:57:46 asdfg kernel: EXT4-fs (sda7): re-mounted. Opts: acl,user_xattr
    Jan 11 11:57:46 asdfg systemd-journald[446]: Journal started
    Jan 11 11:57:46 asdfg systemd-journald[446]: Runtime Journal (/run/log/journal/3b2d469a8f60451893ad90f8553f1636) is 16.0M, max 391.5M, 375.5M free.
    Jan 11 11:57:45 asdfg systemd[1]: systemd-journald.service: Succeeded.
    Jan 11 11:57:46 asdfg haveged[451]: haveged: listening socket at 3
    Jan 11 11:57:46 asdfg systemd[1]: Starting Flush Journal to Persistent Storage...
    --
    Jan 11 11:57:53 asdfg systemd-udevd[725]: controlC0: Process '/usr/sbin/alsactl restore 0' failed with exit code 99.
    Jan 11 11:57:53 asdfg systemd[1]: Started Network Time Synchronization.
    Jan 11 11:57:53 asdfg systemd[1]: Reached target System Initialization.
    Jan 11 11:57:53 asdfg systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance.
    Jan 11 11:57:53 asdfg systemd[1]: Started Watch for changes in CA certificates.
    Jan 11 11:57:53 asdfg systemd[1]: Started CUPS Scheduler.
    Jan 11 11:57:53 asdfg systemd[1]: Started Watch for changes in smartmontools sysconfig file.
    Jan 11 11:57:53 asdfg systemd[1]: Started Daily Cleanup of Snapper Snapshots.
    --
    Jan 11 11:58:32 asdfg kded5[1810]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
    Jan 11 11:58:32 asdfg kded5[1810]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon
    Jan 11 11:58:32 asdfg NetworkManager[1289]: <info>  [1578740312.5764] device (enp0s25): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
    Jan 11 11:58:32 asdfg NetworkManager[1289]: <info>  [1578740312.6115] dhcp4 (enp0s25): canceled DHCP transaction
    Jan 11 11:58:32 asdfg NetworkManager[1289]: <info>  [1578740312.6116] dhcp4 (enp0s25): state changed unknown -> done
    Jan 11 11:58:32 asdfg NetworkManager[1289]: <info>  [1578740312.6140] manager: NetworkManager state is now DISCONNECTED
    Jan 11 11:58:32 asdfg ksmserver[1844]: Qt: Session management error: networkIdsList argument is NULL
    Jan 11 11:58:32 asdfg ksmserver[1844]: Configuring Lock Action
    --
    Jan 11 11:59:04 asdfg dbus-daemon[1132]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
    Jan 11 11:59:04 asdfg pulseaudio[1898]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Jan 11 11:59:04 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 11:59:04 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 11:59:06 asdfg NetworkManager[1289]: <info>  [1578740346.6076] device (enp0s25): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
    Jan 11 11:59:06 asdfg NetworkManager[1289]: <info>  [1578740346.6355] dhcp4 (enp0s25): canceled DHCP transaction
    Jan 11 11:59:06 asdfg NetworkManager[1289]: <info>  [1578740346.6356] dhcp4 (enp0s25): state changed unknown -> done
    Jan 11 11:59:06 asdfg NetworkManager[1289]: <info>  [1578740346.6375] manager: NetworkManager state is now DISCONNECTED
    Jan 11 11:59:07 asdfg NetworkManager[1289]: <info>  [1578740347.2702] device (enp0s25): carrier: link connected
    --
    Jan 11 12:04:12 asdfg NetworkManager[1289]: libndp: ndp_sock_open: Failed to create ICMP6 socket.
    Jan 11 12:04:12 asdfg NetworkManager[1289]: <error> [1578740652.5233] device (enp0s29u1u4): addrconf6: failed to start neighbor discovery: failure creating libndp socket: Address family not supported by protocol (97)
    Jan 11 12:04:12 asdfg kded5[1810]: plasma-nm: Unhandled active connection state change:  1
    Jan 11 12:04:13 asdfg ModemManager[1283]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4': not supported by any plugin
    Jan 11 12:04:16 asdfg plasmashell[1856]: qrc:/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/PopupDialog.qml:75:27: QML ConnectionItem: Binding loop detected for property "height"
    Jan 11 12:04:16 asdfg plasmashell[1856]: qrc:/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/PopupDialog.qml:75:27: QML ConnectionItem: Binding loop detected for property "height"
    Jan 11 12:04:16 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 12:04:16 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 12:04:19 asdfg plasmashell[1856]: qml: temp unit: 0
    --
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.7778] device (enp0s29u1u4): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.7797] manager: NetworkManager state is now DISCONNECTED
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <warn>  [1578740697.7817] device (enp0s29u1u4): Activation: failed for connection 'Wired connection 2'
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.7823] device (enp0s29u1u4): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8035] dhcp4 (enp0s29u1u4): canceled DHCP transaction
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8036] dhcp4 (enp0s29u1u4): state changed timeout -> done
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8051] policy: auto-activating connection 'Wired connection 2' (adb9375f-e6f2-3137-9939-eda154828448)
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8063] device (enp0s29u1u4): Activation: starting connection 'Wired connection 2' (adb9375f-e6f2-3137-9939-eda154828448)
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8067] device (enp0s29u1u4): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8075] manager: NetworkManager state is now CONNECTING
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <info>  [1578740697.8081] device (enp0s29u1u4): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    --
    Jan 11 12:04:57 asdfg NetworkManager[1289]: libndp: ndp_sock_open: Failed to create ICMP6 socket.
    Jan 11 12:04:57 asdfg NetworkManager[1289]: <error> [1578740697.8543] device (enp0s29u1u4): addrconf6: failed to start neighbor discovery: failure creating libndp socket: Address family not supported by protocol (97)
    Jan 11 12:04:57 asdfg kded5[1810]: plasma-nm: Unhandled active connection state change:  1
    Jan 11 12:05:01 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 12:05:04 asdfg plasmashell[1856]: qml: temp unit: 0
    Jan 11 12:05:14 asdfg kernel: usb 2-1.4: USB disconnect, device number 5
    Jan 11 12:05:14 asdfg kernel: asix 2-1.4:1.0 enp0s29u1u4: unregister 'asix' usb-0000:00:1d.0-1.4, ASIX AX88772 USB 2.0 Ethernet
    Jan 11 12:05:14 asdfg NetworkManager[1289]: <info>  [1578740714.6920] device (enp0s29u1u4): state change: ip-config -> unmanaged (reason 'removed', sys-iface-state: 'removed')
    Jan 11 12:05:14 asdfg NetworkManager[1289]: <info>  [1578740714.7115] dhcp4 (enp0s29u1u4): canceled DHCP transaction
    --
    Code:
    dmesg | grep -A7 ailed
    [    0.298319] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
    [    0.299071] PCI host bridge to bus 0000:00
    [    0.299074] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
    [    0.299075] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
    [    0.299076] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
    [    0.299078] pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
    [    0.299079] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
    [    0.299080] pci_bus 0000:00: root bus resource [bus 00-3e]
    --
    [   12.801840] systemd[1]: haveged.service: Failed with result 'exit-code'.
    [   12.802345] systemd[1]: initrd-switch-root.service: Succeeded.
    [   13.057808] EXT4-fs (sda7): re-mounted. Opts: acl,user_xattr
    [   13.380497] systemd-journald[446]: File /run/log/journal/3b2d469a8f60451893ad90f8553f1636/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [   13.390010] systemd[1]: Started Journal Service.
    [   13.567364] systemd-journald[446]: Received client request to flush runtime journal.
    [   14.354636] audit: type=1400 audit(1578740267.126:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ping" pid=482 comm="apparmor_parser"
    [   14.387334] SGI XFS with ACLs, security attributes, no debug enabled
    Rebooted several times in the last hours, see OP... ;-)
    Kind regards

    raspu

  4. #4

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Here more details from lspci

    Code:
    sudo lspci -vv
    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
            Subsystem: Dell Device 0494
            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-
            Latency: 0
            Capabilities: [e0] Vendor Specific Information: Len=0c <?>
    
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
            DeviceName:  Onboard IGD
            Subsystem: Dell Device 0494
            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-
            Latency: 0
            Interrupt: pin A routed to IRQ 29
            Region 0: Memory at e1400000 (64-bit, non-prefetchable) [size=4M]
            Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
            Region 4: I/O ports at 4000 [size=64]
            [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
            Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                    Address: fee01000  Data: 4025
            Capabilities: [d0] Power Management version 2
                    Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                    Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
            Capabilities: [a4] PCI Advanced Features
                    AFCap: TP+ FLR+
                    AFCtrl: FLR-
                    AFStatus: TP-
            Kernel driver in use: i915
            Kernel modules: i915
    
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
            Subsystem: Dell Device 0494
            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-
            Latency: 0
            Interrupt: pin A routed to IRQ 31
            Region 0: Memory at e2db0000 (64-bit, non-prefetchable) [size=16]
            Capabilities: [50] Power Management version 3
                    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                    Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
            Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
                    Address: 00000000fee00000  Data: 4024
            Kernel driver in use: mei_me
            Kernel modules: mei_me
    
    00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
            Subsystem: Dell Device 0494
            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-
            Latency: 0
            Interrupt: pin A routed to IRQ 30
            Region 0: Memory at e2d00000 (32-bit, non-prefetchable) [size=128K]
            Region 1: Memory at e2d80000 (32-bit, non-prefetchable) [size=4K]
            Region 2: I/O ports at 4080 [size=32]
            Capabilities: [c8] Power Management version 2
                    Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                    Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
            Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
                    Address: 00000000fee03000  Data: 4024
            Capabilities: [e0] PCI Advanced Features
                    AFCap: TP+ FLR+
                    AFCtrl: FLR-
                    AFStatus: TP-
            Kernel driver in use: e1000e
            Kernel modules: e1000e
            
    .....

    Kernel module e1000e, let's have a look in dmesg:

    Code:
    .....................................
    [10839.734868] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10846.590809] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10853.474951] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10860.286849] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10867.178792] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10874.014854] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10880.906916] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10887.814847] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10894.698793] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10901.526872] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10908.302852] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10915.110959] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10922.062936] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10928.822947] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10935.722954] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10942.538967] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10949.350977] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10956.194969] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10963.042939] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10969.898960] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10976.718979] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10983.622998] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10990.475054] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [10997.386975] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [11004.159034] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [11011.055075] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [11017.859022] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [11024.651017] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    OOOooooopppppssssss-----
    Kind regards

    raspu

  5. #5

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    ...after a fresh boot dmesg looks like:

    Code:
    dmesg | grep -e1000e
    [   18.019920] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
    [   18.019922] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [   18.020218] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [   18.127946] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
    [   18.229309] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d4:be:d9:54:1b:a3
    [   18.229313] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
    [   18.229373] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 4041FF-0FF
    [   18.898053] e1000e 0000:00:19.0 enp0s25: renamed from eth0
    [   37.901984] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   44.647682] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   51.537684] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   58.321760] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   65.173784] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   71.905792] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   78.741773] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   85.561998] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   92.409755] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [   99.189827] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  106.041844] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  112.921747] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  119.897767] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  126.737890] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  133.497842] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [  140.376549] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    Kind regards

    raspu

  6. #6

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Kind regards

    raspu

  7. #7

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Code:
    ethtool -K enp0s25 tso off
    ..didn't help.

    But apparently kernel 5.4 is broken for e1000e users... sigh...
    Kind regards

    raspu

  8. #8
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,791
    Blog Entries
    15

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Quote Originally Posted by suse_rasputin View Post
    Hi
    I doubt it, it looks more like a NetworkManager issue... I have the same interfaces here and all working fine, but I use wicked;

    Code:
     /sbin/lspci -nnk | grep -A3 Network
    00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
        DeviceName:  L1U1
        Subsystem: Intel Corporation Device [8086:2035]
        Kernel driver in use: e1000e
    --
    04:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
        DeviceName:  L2U1
        Subsystem: Intel Corporation Device [8086:2035]
        Kernel driver in use: e1000e
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #9

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    But in the bugzilla someone reported the same dmesg spam...

    I switched to Wicked, but it didn't buy me anything.
    Kind regards

    raspu

  10. #10

    Default Re: Update with kernel 5.4 - No Intel RJ45 network anymore

    Ooops, switching to Wicked and REBOOTING brings back the network... OK, then apparently NetworkManager is not playing nice.
    Kind regards

    raspu

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •