No WiFi after initial setup

Hi guys,

I have a problem in bazzite after installing it on a newly built PC which I can‘t find a solution for.

While setting up bazzite everything worked fine but after the initial update, my WiFi adapter doesn’t show up under networks anymore, neither do any WiFi networks to connect to.

Interestingly enough, when looking at the settings I can still see the WiFi-Network I used for the setup process, but there’s no way to change any properties or connect to any network (in Gaming or Desktop mode).

I am using the integrated WiFi of my Board MSI B850M Mortar WiFi, which seems to be a Qualcomm NCM865 - lspci found the adapter as Qualcomm WCN785x.

I have tried any and all solutions I found online:

• ⁠Fastboot is deactivated
• ⁠Re-installed both, Windows and Bazzite
• ⁠De-activated and reactivated WiFi adapter in BIOS • ⁠Rebooted many, many times
• ⁠Unplugged PC and pressed power button before rebooting
• ⁠Booting into Bazzite by rebooting from Windows
• ⁠Changing boot order between Windows and Bazzite

None of the above resolved the issue. I really don’t have any clue how to get it fixed.

Is there anything else I could try?

If initial setup is working… then there is maybe so fault in last update.

When you power on computer, there should be list of available images displayed just for a second. You need to be quick and select second image from boot menu, this should be working image (if I understend you correctly).

Additionally, dual boot is not officially supported by Bazzite (or any other Universal Blue projects).

If you have Windows and wifi works fine, there is probably NOT BIOS issue.

Also try to unplug from eletricity your home wifi router, wait at least 10 seconds and plug it on again.

Did you checked in terminal: journal -xe -e
If there is some error displayed there, usually in red coluor.

Thanks for your reply!

I think you’re referring to the grub screen? If so, I don’t get the grub screen during startup.

I don’t know if it makes any difference but I don’t think that it was necessarily a Bazzite update that has been performed. It looked like it would on steam deck and happened before I even had the chance to complete the setup process.

I am aware that Bazzite doesn’t officially support dual boot, but I had the same issue before installing Windows on the second drive.

When entering „journal -xe -e“ into the terminal I get „command not found“ as output.

Probably autocorrected, the command is:
journalctl -xe -e

2 Likes

That worked - thanks!
However, there’s no red text to be seen.
This is what I get:

A start job for unit rpm-ostreed.service has begun execution.
░░ 
░░ The job identifier is 9528.
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: Reading config file '/etc/rpm-ostreed.conf'
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: In idle state; will auto-exit in 61 seconds
Mai 25 16:47:47 Sebastian systemd[1]: Started rpm-ostreed.service - rpm-ostree System Management Daemon.
░░ Subject: A start job for unit rpm-ostreed.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit rpm-ostreed.service has finished successfully.
░░ 
░░ The job identifier is 9528.
Mai 25 16:47:47 Sebastian audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: Allowing active client :1.212 (uid 1000)
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: client(id:cli dbus:1.212 unit:ptyxis-spawn-32dc891c-9ff5-4f39-9ae2-0b81e9d319b6.scope uid:1000) added; new total=1
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: client(id:cli dbus:1.212 unit:ptyxis-spawn-32dc891c-9ff5-4f39-9ae2-0b81e9d319b6.scope uid:1000) vanished; remaining=0
Mai 25 16:47:47 Sebastian rpm-ostree[7353]: In idle state; will auto-exit in 64 seconds
Mai 25 16:47:47 Sebastian polkitd[1376]: Unregistered Authentication Agent for unix-process:7342:645096 (system bus name :1.211, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (>
Mai 25 16:47:49 Sebastian steam[5088]: ERROR: ld.so: object '/usr/lib/extest/libextest.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Mai 25 16:47:49 Sebastian steam[5088]: ERROR: ld.so: object '/usr/lib/extest/libextest.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Mai 25 16:47:53 Sebastian kernel: x86/split lock detection: #DB: CHTTPClientThre/5353 took a bus_lock trap at address: 0xf3781c74
Mai 25 16:47:53 Sebastian kernel: x86/split lock detection: #DB: CHTTPClientThre/5353 took a bus_lock trap at address: 0xf3781c74

Is there anything in there that could hint to the underlying problem?

since the initial install worked, this is probably a regression of some sorts. Bazzite moves at quite the brisk pace with updates. You may have better luck if you reinstall in a few days, maybe the issue is fixed by then. Alternatively, you could try installing bluefin/aurora (depending on your DE), see if that works and then rebase to bazzite.

Thanks!

So there‘s hope that a (near) future update may fix the issue? Or would you suggest I re-download and clean install it to have better chance?

I also did a rollback via terminal in a previous installation. That has fixed the issue for a bit, but eventually led to me being able to boot into grub, but none of the available os versions could be booted. So I might just try that before going for a full reset since I‘d ideally like to avoid having to format the drive again.

I am pretty sure this is a wifi regression in the qualcomm driver that we fixed in aurora and bluefin this week. Are you able to update the system to the latest build somehow?

I have just updated everything (SteamOS & Bazzite). I do however not see any change, still don’t see any WiFi under WiFi & Networks (besides the Network I used for the initial setup).

Did I maybe miss a step to activate WiFi?

Can you please post output of “rpm-ostree status” command.

There shouldn’t be anything like to manual enable wifi. Maybe you did something to disable it.

Don’t know if Bazzite also got new live installer, if yes then you can download latest ISO and boot it then check if wifi is working and then do not install anything from live ISO.

That is the way you can know if you maybe somehow broke/disable wifi setting.

The output of this command might be helpful too:

lspci | grep -i net

Absolutely, this is the output of “rpm-ostree status”:

State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:b07fe8d109b15e6d6bd87db658daa55f751e5756827fd14aec0b71c70514d2af
                  Version: 42.20250522.1 (2025-05-22T07:12:55Z)

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1b4f8022abbf006a8f25618db1be65f5b4be2028f46f6532b1481150ddee4506
                  Version: 42.20250522.1 (2025-05-22T07:09:39Z)

and of “lspci | grep -i net”:

0d:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8126 5GbE Controller (rev 01)
0e:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)

I will be trying live boot, once I had the chance to download the current .iso. and report back.

Another thing I noticed while updating everything: The initial update I mentioned in my intial post seems to have been a SteamOS update rather than a bazzite update. Before that, WiFi worked, afterwards it didn’t. Don’t know if that information helps in troubleshooting, but it’s not going to harm either.

UPDATE: I have not been able to live boot bazzite from the bootable USB drive I created with ventoy. All I could have done was install it. I tried normal and grub mode.

I have tried rebasing from Bazzite to Aurora and back. Unfortunately WiFi has not been working in either of them.

Hi. I have the same problem with wifi after bazzite update (no wifi network showing up)
My motherboard: MSI X870 GAMING PLUS WIFI

lspci | grep -i wi-fi

0a:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)

uname -r

6.14.6-105.bazzite.fc42.x86_64

rpm-ostree status

 Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1b4f8022abbf006a8f25618db1be65f5b4be2028f46f6532b1481150ddee4506
                  Version: 42.20250522.1 (2025-05-22T07:09:39Z)
          LayeredPackages: coolercontrol liquidctl openrazer-daemon

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
          LayeredPackages: coolercontrol liquidctl openrazer-daemon

I’ve rolled back to 42.20250417 which is using older kernel 6.13.9-103.bazzite. No problems with wifi on older image.

2 Likes

That seems like a great starting point!

I tried to rollback to that version using the following command:

bazzite-rollback-helper rebase bazzite-deck:42-stable-20250417

but got this as output:

bazzite-rollback-helper rebase bazzite-deck:42-stable-20250417  
Rebasing to ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:42-stable-20250417. Continue? [Y/n]: y
Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:42-stable-20250417
error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: reading manifest 42-stable-20250417 in ghcr.io/ublue-os/bazzite-deck: manifest unknown

Did I maybe mess up the command or is this due to the fact I had never installed that version of bazzite?

The version I am using is this Release 42.20250417: Stable (F42.20250417) · ublue-os/bazzite · GitHub
that is bazzite not bazzite-deck
Command from github page

bazzite-rollback-helper rebase 42.20250417

Don’t know if it helps

1 Like

I have been able to piece together the command for the proper bazzite-deck version and lo and behold, WiFi works. Thanks a lot for the suggestion!

The only thing I’m wondering if that means we have to stick to that version until there’s yet another new kernel..

2 Likes

Yes, it’s a bug/regression.

3 Likes

Thanks for pointing that out. So essentially, whenever there’s an update for bazzite I just check if it comes with a new kernel version? Sorry for the beginner questions, but I’m new to linux.

I’ve switched to testing branch.
In testing-42.20250528 changelog there is possible fix to our issue

9775c6b 	fix: Downgrade linux firmware for atheros bug

Wifi is working for me so far

rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:testing
                   Digest: sha256:3001ee18e4778d22743c9b2fccd8858b46b5a1f8e4f0e29cc09bdd37d56c3fb8
                  Version: testing-42.20250529 (2025-05-29T11:12:25Z)
          LayeredPackages: coolercontrol liquidctl openrazer-daemon

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
          LayeredPackages: coolercontrol liquidctl openrazer-daemon
                   Pinned: yes