Since upgrading from Fedora 39 to 40 I can no longer connect to Wi-Fi. My laptop has a Realtek WiFi adapter. Helpful tips/workarounds would be appreciated please. As a stopgap measure I’m using Ethernet connection to download updates. Thank you.
Hi, might be unrelated to your issue. But I also had a lot of issues with Wi-fi not working after messing with updates yesterday. It turned out that after shutting down and booting the laptop it did work, unlike when I Just ‘restarted’ the laptop. I’m not sure why this was the case but maybe it helps you!
At quick glance it sounds like UEFI, Fastboot, and/or firmware being retained through warm reboots.
I sometimes add as a kernel option reboot=pci or reboot=efi (pci works also on efi but one or the other might reboot harder depending on firmware) to make sure my reboots are hard. On my laptop reboot=pci causes my laptop’s power to shut off on reboot, and then it turns back on after a second like after a firmware update.
1 Like
Output of lspci -n -n -k as follows:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: pcieport
00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: pcieport
00:01.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:15db]
Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:0000]
Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc]
Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:0000]
Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
Subsystem: Hewlett-Packard Company Device [103c:84a2]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 [1022:15e8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 [1022:15e9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 [1022:15ea]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 [1022:15eb]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 [1022:15ec]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 [1022:15ed]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 [1022:15ee]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 [1022:15ef]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
Subsystem: Hewlett-Packard Company Device [103c:8319]
Kernel driver in use: rtw_8723de
Kernel modules: rtw88_8723de
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c5)
DeviceName: Onboard IGD
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
05:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller [1002:15de]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
05:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: ccp
Kernel modules: ccp
05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e0]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: xhci_hcd
05:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e1]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: xhci_hcd
05:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: snd_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63
05:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
06:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 61)
Subsystem: Hewlett-Packard Company Device [103c:84a2]
Kernel driver in use: ahci
Output of lsusb -v -v -t as follows:
Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/sys/bus/usb/devices/usb1 /dev/bus/usb/001/001
__ Port 004: Dev 002, If 0, Class=Video, Driver=uvcvideo, 480M
ID 04f2:b65d Chicony Electronics Co., Ltd
/sys/bus/usb/devices/1-4 /dev/bus/usb/001/002
__ Port 004: Dev 002, If 1, Class=Video, Driver=uvcvideo, 480M
ID 04f2:b65d Chicony Electronics Co., Ltd
/sys/bus/usb/devices/1-4 /dev/bus/usb/001/002
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/sys/bus/usb/devices/usb2 /dev/bus/usb/002/001
__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
ID 1058:0740 Western Digital Technologies, Inc. My Passport Essential (WDBACY)
/sys/bus/usb/devices/2-1 /dev/bus/usb/002/002
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/sys/bus/usb/devices/usb3 /dev/bus/usb/003/001
__ Port 001: Dev 002, If 0, Class=Wireless, Driver=btusb, 12M
ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
/sys/bus/usb/devices/3-1 /dev/bus/usb/003/002
__ Port 001: Dev 002, If 1, Class=Wireless, Driver=btusb, 12M
ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
/sys/bus/usb/devices/3-1 /dev/bus/usb/003/002
__ Port 002: Dev 003, If 0, Class=Mass Storage, Driver=ums-realtek, 480M
ID 0bda:0177 Realtek Semiconductor Corp.
/sys/bus/usb/devices/3-2 /dev/bus/usb/003/003
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/sys/bus/usb/devices/usb4 /dev/bus/usb/004/001
Output of uname -a as follows:
Linux fedora 6.8.7-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 17 19:21:08 UTC 2024 x86_64 GNU/Linux
Hello,
I have posted the output. What steps should I take next?
I removed and reinstalled the latest kernel via wired connection, but that has made no difference.
sudo rmmod rtw_8723de gives the response “rmmod: ERROR: Module rtw_8723de is not currently loaded”
sudo modprobe rtw88_8723de does not generate a response at the command line.
Never be afraid to trust an unknown future to a known God.
Corrie Ten Boom
I had the same problem. Turns out Fedora 40 introduced MAC address randomization: Changes/StableSSIDMACAddress - Fedora Project Wiki
If you need to register your MAC address on your router to be able to connect, you have to make it static.
Show connections:
nmcli connection show
Change MAC for your WIFI connection:
nmcli connection modify Your_WiFi_Connection_Name 802-11-wireless.cloned-mac-address XX:XX:XX:XX:XX:XX
Restart Network Manager:
sudo systemctl restart NetworkManager
Edit:
Just noticed the article reference the solution: Changes/StableSSIDMACAddress - Fedora Project Wiki
So this should be enough:
nmcli connection modify [$PROFILE] wifi.cloned-mac-address permanent
However, my initial answer still works.
2 Likes
Network hardware gets initialized at boot to support PXE. A “cold” boot is often needed to ensure that current firmware gets loaded, and for dual boot there have been cases where switching to linux fails if you don’t do shutdown then boot linux.
Try modprobe -n -v rtw88_8723de (after reading man modprobe so you understand the options`). Here:
% modprobe -n -v rtw88_8723de
insmod /lib/modules/6.8.7-300.fc40.x86_64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko.xz
insmod /lib/modules/6.8.7-300.fc40.x86_64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko.xz
insmod /lib/modules/6.8.7-300.fc40.x86_64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko.xz
insmod /lib/modules/6.8.7-300.fc40.x86_64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko.xz
This was definitely an issue for me.
My access point (Fritz Box) has an option to only allow known clients.
Toggling this (off) until connected successfully again and turning it on
afterwards seems to be sufficient for me.
1 Like
Issue now resolved. I disabled MAC address filtering on my router, so I now have connectivity back on my Fedora-running laptop, and have turned on private Wi-Fi addresses on my iOS devices. Thank you to all for your help.
Glad to hear you resolved it!
On my home network I never was a fan of MAC address filtering even before randomization. I figure I already know what’s on my network and have a secure AP (WPA2/3, AES, long key), and don’t want to be connecting a new or random device and have to keep that in-mind when it doesn’t exist on the allow list. Corporations can deal with that while providing a paycheck 
Some home wifi systems are more exposed to external connection attempts. I lived in the same house on a hill (strong signal for a long stretch of street) long enough for several waves of teenagers in nearby houses. WiFi routers started popping up followed by frequent attempts to connect.
Hi, I have same issue. At my office don’t have MAC address filetering, but it is not working. At home is fine. Any other idea?
Are you certain there is no MAC filtering or DHCP reserved addressing at the office?
If there is either of those then a changed MAC on your laptop could break the connection.
This doesn’t appear to be same issue. Please start a new thread and provide details of your system (output from running inxi -Fzxx in a terminal as preformatted text using the </> button from the top line of the text entry panel). You should be able to get some details by comparing journalctl output from the two locations. You will need to extract relevant records from the massive detail journalctl can provide. For starters, try journalctl -no-hostname -b <N> -g wifi |cat in a terminal (see man journalctl for explanations of the options, the |cat` wraps long lines).
You should make sure Fedora is fully updated including vendor firmware: a) so it is easier for others with similar hardware to replicate your issue, and b) so you aren’t chasing a problem that has been solved.
1 Like