For about a week, every single Fedora 40 system update installation causes a WiFi driver load failure, which then requires a second reboot in order to get the WiFi driver to load.
I don’t know if whether or not this particular bug is a Fedora-related issue or is KDE’ Plasma’s.
This is likely related to a specific package.
Please use fpaste, lspci and other tools to get the needed infos for debugging
Will do the next time this happens. I saved the two commands you mentioned in a SHell script (.sh) since I’m still learning Linux commands and Linux diagnostics, which is way different from Windows.
Go ahead and provide some hardware details in case someone else with similar hardware already has a fix. I suggest posting the output from inxi -Fzxx (as pre-formatted text, using the </> button from the top line of the text entry panel).
journalctl has copious information from previous boots, so you don’t have to wait until the issue occurs again. It does take some work to find relevant entries because journalctl has access to massive amounts of data. For starters, look at man journalct to learn how to select the number (N, counting back) of the boot of interest. Also read about “priority” (-p P) and “grep” (-g <string>). Two useful “incantations” are:
journalctl --no-hostname -b -p 4|cat. This gives messages with priorities from 0 (emergency) through 4 (notice). The |cat wraps lines – without that you get lines ending with > when pasting as text.
journalctl --no-hostname -b -g wifi |cat. Here, I get:
% journalctl --no-hostname -b -g wifi |cat
May 31 10:18:47 kernel: Intel(R) Wireless WiFi driver for Linux
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: enabling device (0100 -> 0102)
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x2816, cnv-id 0x1000100 wfpm id 0x80000000
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: PCI dev a370/4030, rev=0x312, rfid=0x105110
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 0
[...]
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 28
May 31 10:18:47 kernel: iwlwifi 0000:00:14.3: loaded firmware version 46.7e3e4b69.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
May 31 10:18:48 kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x312
May 31 10:18:48 kernel: iwlwifi 0000:00:14.3: base HW address: 04:ed:33:d9:16:d3, OTP minor version: 0x4
May 31 10:18:48 kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
May 31 10:18:49 NetworkManager[1234]: <info> [1717161529.3736] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf, 22-wifi-mac-addr.conf)
May 31 10:18:49 NetworkManager[1234]: <info> [1717161529.3814] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill1) (driver iwlwifi)
May 31 10:18:49 NetworkManager[1234]: <info> [1717161529.3886] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.46.0-2.fc40/libnm-device-plugin-wifi.so)
May 31 10:18:49 kernel: iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0
May 31 10:18:53 NetworkManager[1234]: <info> [1717161533.3271] device (wlo1): Activation: (wifi) access point 'Infinity' has security, but secrets are required.
May 31 10:18:53 NetworkManager[1234]: <info> [1717161533.3282] device (wlo1): Activation: (wifi) connection 'Infinity' has security, and secrets exist. No new secrets needed.
May 31 10:18:53 NetworkManager[1234]: <info> [1717161533.5053] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "#####"
When reporting problems, a good strategy is to starrt by presenting enough detail to allow others with access to similar hardware to reproduce the problem. Unless you have unique hardware there is a good chance someone already knows a solution or at least a workaround.Yes both commands should be ran now.
I think fpaste generates a link, lspci gives us your wifi card model. Copy the result here and add
```
Text
```
So it is formatted as code
Here is contents from lspci | fpaste:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter
Very easy to see which adapter is the wifi.
Now running lspci -s 02:00.0 -nnk should provide the details needed.
The man page for lspci is very helpful.
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
DeviceName: WLAN
Subsystem: Hewlett-Packard Company Device [103c:8319]
Kernel driver in use: rtw_8723de
Kernel modules: rtw88_8723de
Should I run the command lspci -s 02:00.0 -nnk again the next time the WiFi fails to load?
This command just shows us the hardware and driver, so you only need to run it again if you try one of the other drivers. The “Subsystem:” line is important information, as vendors often configure WiFi differently so you
need it to get the LHDB records. These include another report of problems similar to your issue. The LHDB lists 3 alternatives to the kernel.org driver used by Fedora.
Your model does not support 5Ghz. Many 2.4 Ghz networks are congested, so some users upgrade to dual band adapters, but newer adapters have two antenna connections and you would need find an adapter designed to use a single antenna. There are situations where 2.4 Ghz outperforms 5Ghz.
@krisrh21 They were asking you to provide the code you copied in preformatted text </> , it’s easier to read and diagnose. Here is an image of what you need to do.
System:
Kernel: 6.8.11-300.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 40 (KDE Plasma)
Machine:
Type: Laptop System: HP product: HP Laptop 15-bs0xx v: Type1ProductConfigId
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: HP model: 832A v: 23.77 serial: <superuser required>
part-nu: 1WJ89UA#ABA UEFI: Insyde v: F.74 date: 12/15/2023
CPU:
Info: dual core model: Intel Core i3-7100U bits: 64 type: MT MCP
arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
L3: 3 MiB
Speed (MHz): avg: 700 min/max: 400/2400 cores: 1: 700 2: 700 3: 700 4: 700
bogomips: 19200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5916
Device-2: Cheng Uei Precision Industry (Foxlink) HP TrueVision HD Camera
driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-5:5
chip-ID: 05c8:03ac
Display: wayland server: Xwayland v: 24.1.0 compositor: kwin_wayland
driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
display-ID: 0
Monitor-1: eDP-1 res: 1366x768 size: N/A
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast
surfaceless: drv: iris wayland: drv: iris x11: drv: iris inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.8 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
device-ID: 8086:5916 display-ID: :0.0
API: Vulkan v: 1.3.283 surfaces: xcb,xlib,wayland device: 0
type: integrated-gpu driver: N/A device-ID: 8086:5916 device: 1 type: cpu
driver: N/A device-ID: 10005:0000
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
API: ALSA v: k6.8.11-300.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter
vendor: Hewlett-Packard driver: rtw_8723de v: N/A pcie: speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:d723
IF: wlo1 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 0bda:b009
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
lmp-v: 8
Drives:
Local Storage: total: 931.51 GiB used: 683.51 GiB (73.4%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-60JC3T1
size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 97.87 GiB used: 19.76 GiB (20.2%) fs: ext4 dev: /dev/sda4
ID-2: /boot/efi size: 49.9 MiB used: 19 MiB (38.1%) fs: vfat
dev: /dev/sda3
ID-3: /home size: 736.63 GiB used: 653.18 GiB (88.7%) fs: ext4
dev: /dev/sda6
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 3.88 GiB (48.5%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda5
Sensors:
System Temperatures: cpu: 50.0 C pch: 44.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.4 GiB used: 14.04 GiB (91.2%)
Processes: 348 Power: uptime: 5h 50m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 32 Compilers: N/A Shell: Bash v: 5.2.26
running-in: konsole inxi: 3.3.34