WiFi glitch on 2026 XPS 13 (Wildcat Lake) installation

Ask Fedora
1

On an installation of the most recent Fedora Workstation ISO, all hardware components are recognized and working == yay! – except WiFi. Note that I immediately installed Fedora to disk, partitioning and deleting the preinstalled Windows 11 without booting the latter. I also installed the comprehensive supplemental driver package when no WiFi was active immediately after initial FW installation, but no joy.

I see this in the system log:

Screenshot From 2026-06-26 07-20-56
Screenshot From 2026-06-26 07-20-562500×1300 381 KB

First time I’ve encountered errors like these on an install, so happy for any suggestions. I’ve seen some earlier discussions that Windows Fast Boot can bork detection of the wireless adapter, but the Intel BE213 is clearly being seen during bootup. What steps should I take to resolve this?

Thanks!!!

2

what do you get from fwupdmgr refresh --force && fwupdmgr update -v?

3

Hey, Steve, I get this:

(fwupdmgr:13353): GLib-GIO-DEBUG: 08:56:52.952: \_g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for 'gsettings-backend'
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.953: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.953: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.953: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.953: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.953: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
(fwupdmgr:13353): GLib-GIO-DEBUG: 08:56:52.953: \_g_io_module_get_default: Found default implementation gnome (GProxyResolverGnome) for 'gio-proxy-resolver'
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.957: watch_established: "/system/proxy/" (establishing: 1)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.957: watch_established: "/system/proxy/http/" (establishing: 1)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.957: watch_established: "/system/proxy/https/" (establishing: 1)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.957: watch_established: "/system/proxy/ftp/" (establishing: 1)
(fwupdmgr:13353): dconf-DEBUG: 08:56:52.958: watch_established: "/system/proxy/socks/" (establishing: 1)
(fwupdmgr:13353): Fwupd-DEBUG: 08:56:52.958: emitting ::status-changed() \[idle\]
(fwupdmgr:13353): FuMain-DEBUG: 08:56:52.975: current version is 76012103: 76012103=same, 76012102=older
(fwupdmgr:13353): FuMain-DEBUG: 08:56:52.982: current version is 2023: 2023=same
(fwupdmgr:13353): FuMain-DEBUG: 08:56:52.990: No releases found
(fwupdmgr:13353): FuMain-DEBUG: 08:56:52.998: current version is 2023: 2023=same
Devices with the latest available firmware version:
• PC SN7100S SanDisk 512GB
• UEFI CA
• UEFI dbx
• Windows UEFI CA
Devices with no available firmware updates:
• Internal SPI Controller (BIOS)
• LuxSharePC
• System Firmware
• TPM
• UEFI Device Firmware
• UEFI Device Firmware
• Touch Controller Sensor
• Bios DB Key
• Bios FW Aux Authority
• Integrated Webcam FHD
• KEK CA
• Key Exchange Key
• Option ROM UEFI CA
• Touch (SW42101)
(fwupdmgr:13353): FuMain-DEBUG: 08:56:52.998: skipping reboot check

I (@computersavvy) edited your post and converted the preformatted text from your screen input using the format you had set

image

to markdown
image
Notice the major difference in structure and how it now appears exactly as initially seen on your screen. The button on the far left of the toolbar shown makes that difference.

When posting as preformatted text please always ensure you are in markdown mode before clicking the </> button

4

Shame. I was hoping you were going to get a firmware update for it over but it’s not even mentioned as a specific device.

5

I also found this by poking around the forum:

While I really would rather not have to install Windows just to fix this issue, I’ll do it if there’s no other way to resolve the problem.

6

Intel seems to have lost interest in Linux after dropping their linux distro.https://www.intel.com/content/www/us/en/products/sku/240284/intel-wifi-7-r2-be213/downloads.html only has Windows packages. Having used Linux for decades, I’ve learned to have USB dongles with in kernel support for network and sound while waiting for drivers to support newer hardware and kernels.

Edit: Linux was added to the list of drivers, dated June 25. It has support for 7.1 kernels.

7

Good advice, thanks!

Maybe I should try Omarchy, which fully supports the other 2026 XPS models with Panther Lake chipsets. Although the WiFi 7 device in those is the Intel BE211, not the BE213 in my XPS 13.

But I’ll order a dongle as well. Cheers!

8

If I’m reading this Ubuntu bug ticket right, support is expected in kernel 7.2 - but in the interim, Ubuntu has backported it.

Maybe it’s worth giving Ubuntu a try?

9

Worth a try, thanks!

10

Well, I gave Ubuntu a try, but the most up-to-date desktop build failed to use the BE213. Further research seems to indicate that at this point in time support would require using an unstable kernel in addition to the Intel driver, and I just didn’t want to go there, since Ubuntu is not my preferred distro.

So using a little WiFi USB dongle, I’ve installed Fedora Cosmic Atomic and am trying that out since I really like the Cosmic DE, even if it still feels a little unfinished and rough around the edges. I figure it’s just a not-very-long matter of time before the 7.1 kernel gets added to Atomic, and I can get by in the meantime. Gotta say I really like the XPS 13; it’s a superb machine if you’re looking for a very lightweight,nicely-constructed laptop with good battery life, screen, and keyboard, and intended for mainstream productivity, non-gaming entertainment, browsing, etc.