On ONE of my computers, I systematically get “NO NETWORK” after kernel update 2021-3387, where kernel 5.3.18-59.24 is exchanged for 5.3.18-59.27 . Updating all the other packages - and NetworkManager - gives no problem, but updating the kernel always does, be it through the packagekit or through zypper-up. The “NO NETWORK” also stays if I switch from NetworkManager to wicked: apparently networking cannot be started up, somehow. I cannot imagine what is special with that one computer: maybe that it boots up with kernel parameter “i915.force_probe=4c8a”? Or that its ethernet cable is directly connected to the external router, whilst the other computers are connected through powerline? Since it is my wife’s computer, I told her NOT to install any updates anymore … which is of course no real solution. Who can point me to a real solution? Thanks already!
Please post:
/sbin/lspci -nnk | grep -iA3 net
uname -a
zypper se -si kernel r8168
Here are, FIRST, the three postings BEFORE kernel updating: network is OK After that I give the three postings after kernel updating, with NO network.
[LEFT] /sbin/lspci -nnk | grep -iA3 net
00:1f.6 Ether**net** controller [0200]: Intel Corporation Ether**net** Connection (10) I219-V [8086:0d4f] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d22]
Kernel driver in use: e1000e
Kernel modules: e1000e[/LEFT]
[LEFT] uname -a
Linux Sysa7PC 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) x86_64 x86_64 x86_64 GNU/Linux[/LEFT]
[LEFT] zypper se -si kernel r8168
Gegevens van opslagruimte laden...
Lezen van geïnstalleerde pakketten...
S | Name | Type | Version | Arch | Repository
---+-----------------------------+--------+----------------+--------+-------------------------------------------------------------
i+ | kernel-default | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i+ | kernel-default | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-devel | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-devel | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-extra | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-extra | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-optional | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-optional | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-devel | pakket | 5.3.18-59.24.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-devel | pakket | 5.3.18-59.19.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-firmware-all | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-amdgpu | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ath10k | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ath11k | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-atheros | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-bluetooth | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-bnx2 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-brcm | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-chelsio | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-dpaa2 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-i915 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-intel | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-iwlwifi | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-liquidio | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-marvell | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-media | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mediatek | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mellanox | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mwifiex | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-network | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-nfp | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-nvidia | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-platform | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-prestera | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-qlogic | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-radeon | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-realtek | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-serial | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-sound | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ti | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ueagle | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-usb-network | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-macros | pakket | 5.3.18-59.24.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-preempt-devel | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-preempt-devel | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-syms | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-syms | pakket | 5.3.18-59.19.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | purge-kernels-service | pakket | 0-8.3.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15[/LEFT]
In my NEXT post I give the three postings AFTER kernel updating, with NO NETWORK …
And HERE are the three postings AFTER kernel updating, with NO NETWORK …
[LEFT] /sbin/lspci -nnk | grep -iA3 net
00:1f.6 Ether**net** controller [0200]: Intel Corporation Ether**net** Connection (10) I219-V [8086:0d4f] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d22]
Kernel modules: e1000e
01:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:500e] (rev 01)
[/LEFT]
[LEFT] uname -a
Linux Sysa7PC 5.3.18-59.27-default #1 SMP Tue Oct 5 10:00:40 UTC 2021 (7df2404) x86_64 x86_64 x86_64 GNU/Linux[/LEFT]
[LEFT] zypper se -si kernel r8168
Gegevens van opslagruimte laden...
Lezen van geïnstalleerde pakketten...
S | Name | Type | Version | Arch | Repository
---+-----------------------------+--------+----------------+--------+-------------------------------------------------------------
i+ | kernel-default | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i+ | kernel-default | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-devel | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-devel | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-extra | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-extra | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-optional | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-default-optional | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-devel | pakket | 5.3.18-59.27.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-devel | pakket | 5.3.18-59.24.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-firmware-all | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-amdgpu | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ath10k | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ath11k | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-atheros | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-bluetooth | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-bnx2 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-brcm | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-chelsio | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-dpaa2 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-i915 | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-intel | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-iwlwifi | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-liquidio | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-marvell | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-media | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mediatek | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mellanox | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-mwifiex | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-network | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-nfp | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-nvidia | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-platform | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-prestera | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-qlogic | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-radeon | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-realtek | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-serial | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-sound | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ti | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-ueagle | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-firmware-usb-network | pakket | 20210208-2.4 | noarch | Hoofd-opslagruimte
i | kernel-macros | pakket | 5.3.18-59.27.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-preempt-devel | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-preempt-devel | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-syms | pakket | 5.3.18-59.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | kernel-syms | pakket | 5.3.18-59.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | purge-kernels-service | pakket | 0-8.3.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
[/LEFT]
You can see the diffrerence on the first posting: after kernel updating there is a line with non-volatile memory that was NOT there …
01:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:500e] (rev 01)
Also, I must add that after kernel updating, my /etc/resolv.conf file is zero bytes and does not exist. I tried the trick with “netconfig update -f” and then “systemctl restart network” but that gave no results: my resolv.conf file came up, but WITHOUT the three crucial lines:
search lan
nameserver fda2:e1c4:ffbd::1
nameserver 192.168.1.1
I thought about writing it in my resolv.conf file, but I know that will be overwritten on next boot … so what should I do now? Thanks for helping me out of this mess!
You can see the diffrerence on the first posting: after kernel updating there is a line with non-volatile memory that was NOT there …
Thats because of the grep -A3: 3 lines after…
And this one is missing:
Kernel driver in use: e1000e
So why it is missing?
Post as root:
journalctl -b | grep -Ei 'firmw|eth|network|wicked|e1000e'
grep -i 'e1000e' /etc/modprobe.d/*
cat /proc/cmdline
Text is TOO LONG, therefore I have to cut the first posting in two parts …
Hre goes the first part …
sudo journalctl -b | grep -Ei 'firmw|eth|network|wicked|e1000e'
[LEFT]okt 14 14:07:57 Sysa7PC kernel: drop_monitor: Initializing **network** drop monitor service
okt 14 14:07:57 Sysa7PC systemd-udevd[302]: **Network** interface NamePolicy= disabled by default.
okt 14 14:07:57 Sysa7PC systemd-udevd[356]: **eth**tool: autonegotiation is unset or enabled, the speed and duplex are not writable.
okt 14 14:07:58 Sysa7PC kernel: i915 0000:00:02.0: Direct **firmw**are load for i915/rkl_dmc_ver2_01.bin failed with error -2
okt 14 14:07:58 Sysa7PC kernel: i915 0000:00:02.0: [drm] Failed to load DMC **firmw**are i915/rkl_dmc_ver2_01.bin. Disabling runtime power management.
okt 14 14:07:58 Sysa7PC kernel: i915 0000:00:02.0: [drm] DMC **firmw**are homepage: https://git.kernel.org/pub/scm/linux/kernel/git/**firmw**are/linux-**firmw**are.git/tree/i915
okt 14 14:08:00 Sysa7PC systemd-udevd[541]: **Network** interface NamePolicy= disabled by default.
okt 14 14:08:00 Sysa7PC kernel: **e1000e**: Intel(R) PRO/1000 **Network** Driver - 3.2.6-k
okt 14 14:08:00 Sysa7PC kernel: **e1000e**: Copyright(c) 1999 - 2015 Intel Corporation.
okt 14 14:08:00 Sysa7PC kernel: **e1000e** 0000:00:1f.6: enabling device (0000 -> 0002)
okt 14 14:08:00 Sysa7PC kernel: **e1000e** 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
okt 14 14:08:00 Sysa7PC root[943]: udev hpmud.rules runs hp-**firmw**are to test if HP device with USB vendor ID 03f0 and USB product ID 0b2a at USB bus ID 001 and USB device ID 006 needs **firmw**are and if yes to upload it
okt 14 14:08:00 Sysa7PC kernel: **e1000e** 0000:00:1f.6: The NVM Checksum Is Not Valid
okt 14 14:08:01 Sysa7PC systemd[1]: Reached target Host and **Network** Name Lookups.
okt 14 14:08:01 Sysa7PC avahi-daemon[1056]: **Network** interface enumeration completed.
okt 14 14:08:01 Sysa7PC kernel: **e1000e**: probe of 0000:00:1f.6 failed with error -5
okt 14 14:08:01 Sysa7PC systemd[1]: Reached target **Network** (Pre).
okt 14 14:08:01 Sysa7PC systemd[1]: Starting **Network** Manager...
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.4174] **Network**Manager (version 1.22.10) is starting... (for the first time)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.4174] Read config: /etc/**Network**Manager/**Network**Manager.conf
okt 14 14:08:01 Sysa7PC systemd[1]: Started **Network** Manager.
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.4183] bus-manager: acquired D-Bus service "org.freedesktop.**Network**Manager"
okt 14 14:08:01 Sysa7PC systemd[1]: Reached target **Network**.
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.4190] manager[0x5619df880070]: monitoring kernel **firmw**are directory '/lib/**firmw**are'.
okt 14 14:08:01 Sysa7PC dbus-daemon[1058]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.8' (uid=0 pid=1261 comm="/usr/sbin/**Network**Manager --no-daemon ")
okt 14 14:08:01 Sysa7PC systemd-udevd[773]: **eth**tool: autonegotiation is unset or enabled, the speed and duplex are not writable.
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.5989] hostname: hostname: using hostnamed
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.5989] hostname: hostname changed from (none) to "Sysa7PC"
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.5991] dns-mgr[0x5619df869240]: init: dns=default,systemd-resolved rc-manager=netconfig
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6493] manager[0x5619df880070]: rfkill: Wi-Fi hardware radio set enabled
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6494] manager[0x5619df880070]: rfkill: WWAN hardware radio set enabled
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6507] Loaded device plugin: NMAtmManager (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-adsl.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6559] Loaded device plugin: NMBluezManager (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-bluetooth.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6566] Loaded device plugin: NMOvsFactory (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-ovs.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6583] Loaded device plugin: NMTeamFactory (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-team.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6596] Loaded device plugin: NMWifiFactory (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-wifi.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6601] Loaded device plugin: NMWwanFactory (/usr/lib64/**Network**Manager/1.22.10/libnm-device-plugin-wwan.so)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6603] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6604] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6604] manager: **Network**ing is enabled by state file
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6605] dhcp-init: Using DHCP client 'dhclient'
[/LEFT]
Here continues my first posting:
[LEFT] okt 14 14:08:01 Sysa7PC dbus-daemon[1058]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=1261 comm="/usr/sbin/**Network**Manager --no-daemon ")
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6607] settings: Loaded settings plugin: keyfile (internal)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6618] device (lo): carrier: link connected
okt 14 14:08:01 Sysa7PC systemd[1]: Starting **Network** Manager Script Dispatcher Service...
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6619] manager: (lo): new Generic device (/org/freedesktop/**Network**Manager/Devices/1)
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6629] ovsdb: Kon niet verbinden: Bestand of map bestaat niet
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6636] manager: startup complete
okt 14 14:08:01 Sysa7PC **Network**Manager[1261]: <info> [1634213281.6666] modem-manager: ModemManager available
okt 14 14:08:01 Sysa7PC systemd[1]: Started **Network** Manager Script Dispatcher Service.
okt 14 14:08:11 Sysa7PC systemd[1]: Startup finished in 6.637s (**firmw**are) + 2.324s (loader) + 1.676s (kernel) + 2.572s (initrd) + 11.732s (userspace) = 24.944s.
okt 14 14:08:11 Sysa7PC systemd[1]: **Network**Manager-dispatcher.service: Succeeded.
okt 14 14:08:17 Sysa7PC **Network**Manager[1261]: <info> [1634213297.2313] agent-manager: agent[f8487c2025e1cc61,:1.27/org.kde.plasma.[b]networkmanagement/1002]: agent registered
okt 14 14:08:17 Sysa7PC ksmserver[3860]: Qt: Session management error: **network**IdsList argument is NULL
okt 14 14:08:42 Sysa7PC kded5[3797]: kf.bluezqt: PendingCall Error: "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 **netw**
ork connection was broken."
okt 14 14:09:00 Sysa7PC systemd-udevd[756]: 1-9.1: Spawned process '/usr/bin/hp-**firmw**are -s 001:006' [952] is taking longer than 59s to complete
okt 14 14:09:01 Sysa7PC /hp-**firmw**are[952]: hp-**firmw**are[952]: error: Device hp:/usb/HP_LaserJet_CP1025?serial=00000GF0239GS does not support or require **firmw**are download.
okt 14 14:09:01 Sysa7PC systemd-udevd[756]: 1-9.1: Process '/usr/bin/hp-**firmw**are -s 001:006' failed with exit code 1.[/LEFT]
Second posting gives no result, not before and not after kernel updating: grep -i ‘e1000e’ /etc/modprobe.d/*
Third posting comes here:
[LEFT] sudo cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.27-default root=UUID=fbc6227b-c87b-462e-acbc-6d8855543210 i915.force_probe=4c8a splash=silent quiet mitigations=auto[/LEFT]
Something is clearly wrong. So how come ?
All as root!
modprobe -r e1000e
And now:
modprobe e1000e eeprom_bad_csum_allow=1
systemctl restart network.service
Does that work?
If yes, you should fill a bugreport.
No, that did not work out …
And the output of all commands?
Also as root after all commands:
lsmod | grep -i e1000
As I put the commands in, there is no output in the terminal. lsmod gives this, both BEFORE AND AFTER kernel updating (no change):
[LEFT] lsmod | grep -i e1000
**e1000**e 286720 0[/LEFT]
I would write a bugreport.
I did just that: Bug 1191663 on https://bugzilla.opensuse.org/show_bug.cgi?id=1191663 . Thanks for your good guidance!
This seems to be the culprit …
It’s actually a regression by the kernel patch
patches.suse/e1000e-Do-not-take-care-about-recovery-NVM-checksum.patch
This patch is documented here:
https://bugzilla.kernel.org/show_bug.cgi?id=213667
Because of this patch, my machine gives an NVM checksum error, and the driver corrected it in the past, while this isn’t done any longer and treated as a fatal error now.
Let’s hope it will get fixed soon!
BEFORE that patch was introduced into the kernel, this is what DMESG says about e1000e, when the network is there:
4.937015] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
4.937016] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
4.937045] e1000e 0000:00:1f.6: enabling device (0000 → 0002)
4.939897] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
…]
5.198207] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
5.267943] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) d8:bb:c1:11:df:da
5.267944] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
5.268049] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
And AFTER the patch was introduced in the new kernel, I have NO NETWORK and DMESG says this about e1000e:
4.734542] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
4.734543] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
4.734597] e1000e 0000:00:1f.6: enabling device (0000 → 0002)
4.734864] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
…]
4.996420] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
…]
5.061273] e1000e: probe of 0000:00:1f.6 failed with error -5
So THAT is the problem that has to be solved …
I repeat the message, this time with right encoding …
BEFORE that patch was introduced into the kernel, this is what DMESG says about e1000e, when the network is there:
4.937015] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
4.937016] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
4.937045] e1000e 0000:00:1f.6: enabling device (0000 -> 0002)
4.939897] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
...]
5.198207] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
5.267943] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) d8:bb:c1:11:df:da
5.267944] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
5.268049] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
And AFTER the patch was introduced in the new kernel, I have NO NETWORK and DMESG says this about e1000e:
4.734542] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
4.734543] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
4.734597] e1000e 0000:00:1f.6: enabling device (0000 -> 0002)
4.734864] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
...]
4.996420] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
...]
5.061273] e1000e: probe of 0000:00:1f.6 failed with error -5
So THAT is the problem that has to be solved …
My search engine gives: http://mynixworld.info/2012/12/05/e1000e-the-nvm-checksum-is-not-valid/
Maybe the new driver did become more strict on checking the NVM Checksum.
Indeed, since this new patch was introduced to mitigate the effects of a Dell computers failure where nvm checksum calculating slowed down the boot process, I suddenly get this message and NO NETWORK with this new kernel. It’s a brand new computer, no Dell at all, bought specially and only for use with Linux. It’s an Intel motherboard, while all my other computers are AMD.
So THAT is the problem that has to be solved …
- Can the patch be rewritten?
- Or can a kernel parameter be designed for booting?
- Must the EEPROM be corrected somehow?
- Must Intel’s e1000e driver be renewed?
- Or is there another method to avoid the network failure?
I suppose - or rather, I hope - that a solution is being researched “higher up”. But maybe there is a faster road? Because IF NOT, I am stuck for eternity without any kernel updates nor system version updates …
I read about a suggestion that I should enter UEFI-BIOS utility, enter ADVANCED MODE, and enable ADVANCED NETWORK STACK CONFIGURATION and then booting up; this should somehow clear the bad NVM checksum; and then I could go back to the BIOS and disable the network stack.
But I am hesitant: don’t I risk jeopardizing my whole network card that way? Is there somebody who can give me good advice in these matters? THANKS ALREADY!
Is the Ethernet integrated or is it a separate card?
If it is a separate card I would consider replacing it by another one.
If it is integrated, I would bite the bullet and follow the process in the link I posted to fix it.
Wait for the answers in your bugzilla.