broadcom-wl missing from 6.19.14 ogc kernel

[lsjobom]

Describe the bug

A fresh install of 44 on a mid-2014 macbook pro gives no wifi at all. It looks like the wl driver is not loaded properly.

What did not work

ujust iwd
ujust configure-broadcom-wl
Updating via Bazzite portal -> System Management -> Update Bazzite and apps.
rebasing to testing
All of course including the appropriate reboots

What did work

Rebasing to 43. Here wifi was working immediately, possibly as a result of the above ujust stuff. Wifi was not working on the live session in 43.

This is in a way the opposite of #4793 which was solved by a fresh install. The symptoms are similar to #4787.

What did you expect to happen?

Being able to fix wifi with ujust iwd and/or ujust configure-broadcom-wl.
On 43 I can see that the correct driver is in use:
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)
Subsystem: Apple Inc. Device 0112
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at b0600000 (64-bit, non-prefetchable) [size=32K]
Memory at b0400000 (64-bit, non-prefetchable) [size=2M]
Capabilities:
Kernel driver in use: wl
Kernel modules: wl, bcma

These are not the kernel driver nor modules I see on 44. The same on 44 after ujust iwd and configure-broadcom-wl is

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)
Subsystem: Apple Inc. Device 0112
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at b0600000 (64-bit, non-prefetchable) [size=32K]
Memory at b0400000 (64-bit, non-prefetchable) [size=2M]
Capabilities:
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcmass

Session Logs

dmesgs from 43 and 44:

dmesg43.txt
dmesg44.txt

Warning: your paste size is very large etc etc.

Hardware

MacbookPro 11,1 mid 2014

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)
Subsystem: Apple Inc. Device 0112
Flags: bus master, fast devsel, latency 0, IRQ 18

Operating System: Bazzite 43
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
Qt Version: 6.10.3
Kernel Version: 6.17.7-ba29.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4278U CPU @ 2.60GHz
Memory: 8 Gibyte of RAM (7.7 Gibyte usable)
Graphics Processor: Intel® Iris® Graphics 5100
Manufacturer: Apple Inc.
Product Name: MacBookPro11,1
System Version: 1.0

Extra information or context

rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable-43
Digest: sha256:3c96c8062c2319e72213b638eafd5228ba29567ff1c8ceb9e2f6341c76029891
Version: 43.20260420 (2026-04-20T05:51:15Z)
Pinned: yes

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
Digest: sha256:d2f131cb9e5cd3c633bc19bf8bb82c156f47f70f6776cab6ae9a3c3bee2e4172
Version: 44.20260501.1 (2026-05-01T23:50:23Z)

[lsjobom]

Is this the same as #3381 ?
sudo modprobe wl
modprobe: FATAL: Module wl not found in directory /lib/modules/6.19.14-ogc1.1.fc44.x86_64

rpm-ostree install broadcom-wl
error: Packages not found: broadcom-wl

rpm-ostree search akmod-wl
No matches found.

[ShaggyMummy]

Hit this issue today,

Rolling back to 43 got me back up and running

heres my device info
https://paste.centos.org/view/64d08a7e

[TheMDev]

It seems the wl akmods package which adds support for some legacy broadcom wifi devices including the BCM4360 was likely accidentally dropped in the switchover to the OGC Kernel.
e54b455#diff-55ff6682381e23108ec5b29f56197cfd0293376de2e26e02062da7f0d7feaa28L35
6a41984#diff-55ff6682381e23108ec5b29f56197cfd0293376de2e26e02062da7f0d7feaa28R35

I do not have a wifi card to test this with so I'm going to post a possible workaround here if someone is willing to try this out at their own risk.

WARNING

The following instructions are only for OGC Linux Kernel Version 6.19.14-ogc5.1.fc44.x86_64 part of Bazzite F44.20260515. Before continuing make sure the version listed by rpm-ostree status matches 44.20260515
Layering these packages will likely break updates but they can always be removed by rpm-ostree reset if you run into any issues.

# We need crane to download the required packages from ublue akmods.
brew install crane

# Use crane to download and extract the packages we need.
crane export ghcr.io/ublue-os/akmods:ogc-44-6.19.14-ogc5.1.fc44 | tar -xf - \
rpms/common/broadcom-wl-6.30.223.271-28.fc44.noarch.rpm \
rpms/kmods/kmod-wl-6.19.14-ogc5.1.fc44.x86_64-6.30.223.271-61.fc44.x86_64.rpm

# Install the downloaded packages 
rpm-ostree install rpms/common/broadcom-wl-6.30.223.271-28.fc44.noarch.rpm
rpm-ostree install rpms/kmods/kmod-wl-6.19.14-ogc5.1.fc44.x86_64-6.30.223.271-61.fc44.x86_64.rpm

#Reboot

[lsjobom]

@TheMDev TL;DR yes, this is a fix.

I had to make sure to install both packages simultaneously, and disable iwd to get things working.

What I did:

rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:ddb61d1ca94a2c7a0fc3b2ef45194a8d058df6fd7f1a26fa2612fb99aee6b9a4
                  Version: 44.20260515 (2026-05-15T07:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable-43
                   Digest: sha256:3c96c8062c2319e72213b638eafd5228ba29567ff1c8ceb9e2f6341c76029891
                  Version: 43.20260420 (2026-04-20T05:51:15Z)
                   Pinned: yes

Crane export [...] gives no feedback at all, but at least no error.

I had some problems installing the packages since I tried to do it one at a time. Solved by installing them at the same time.

rpm-ostree install \
  rpms/common/*.rpm \
  rpms/kmods/*.rpm
Checking out tree f56b154... done
Enabled rpm-md repositories: updates fedora updates-archive
Importing rpm-md... done
rpm-md repo 'updates' (cached); generated: 2026-05-28T01:04:44Z solvables: 18188
rpm-md repo 'fedora' (cached); generated: 2026-04-22T13:34:32Z solvables: 76354
rpm-md repo 'updates-archive' (cached); generated: 2026-05-28T06:08:25Z solvables: 13915
Resolving dependencies... done
Relabeling... done
Checking out packages... done
Running systemd-sysusers... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Pruned images: 0 (layers: 66)
Freed: 2,7 GB (pkgcache branches: 0)
Added:
  broadcom-wl-6.30.223.271-28.fc44.noarch
  kmod-wl-6.30.223.271-61.fc44.x86_64
Changes queued for next boot. Run "systemctl reboot" to start a reboot

Reboot

rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:ddb61d1ca94a2c7a0fc3b2ef45194a8d058df6fd7f1a26fa2612fb99aee6b9a4
                  Version: 44.20260515 (2026-05-15T07:01:06Z)
            LocalPackages: broadcom-wl-6.30.223.271-28.fc44.noarch
                           kmod-wl-6.30.223.271-61.fc44.x86_64

After some finagling with ujust iwd and ujust configure-broadcom-wl, I have wifi again.
I had to disable iwd and enable broadcom-wl to get it working.

[lsjobom]

No, wait, wifi is working even with iwd. I checked with NetworkManager --print-config | grep wifi.backend as well as systemctl is-active iwd when I finally got it working. Iwd was inactive then, is active now.
I think that the order that solved it for me was

• ujust iwd, choose disable, reboot
• ujust configure-broadcom-wl, choose disable, reboot
• ujust configure-broadcom-wl, choose, enable, reboot. After this wifi started working at d: 121.14Mbit/s u: 51.36Mbit/s
• ujust iwd, choose enable, reboot. This gives slightly faster speeds, at d: 191.44Mbit/s u: 59.69Mbit/s

Sample size of one for the speeds, but it matches the other anecdata about iwd giving slightly better performance

[TheMDev]

Awesome, thanks for the testing. I will get a PR opened here shortly.

[TheMDev]

The fix is now available in testing using: bazzite-rollback-helper rebase testing-44.20260528
https://github.com/ublue-os/bazzite/releases/tag/testing-44.20260528

[lsjobom]

Confirmed working in testing-44.20260528. Thanks a lot! Should I write a test report somewhere to have that box ticked as well?

Footnote for anyone reading along: The layered packages did, in fact, stop me from rebasing from any of my deployments. 44 with the packages, 44 without the packages, 43. This was solved with rpm-ostree reset. Upon rebasing and rebooting I had no wifi, since iwd was inactive.

$ NetworkManager --print-config | grep wifi.backend
wifi.backend=iwd
$ systemctl is-active iwd
inactive
$ lspci -k | grep -A 3 Broadcom
02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera
        Subsystem: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)
        Subsystem: Apple Inc. Device 0112
        Kernel driver in use: wl
        Kernel modules: bcma, wl
$ lsmod | grep wl
wl                   6529024  0
cfg80211             1601536  1 wl

this was fixed with ujust iwd and a reboot.

[mddunner]

Thank you for reporting this and the fix! I rebased with testing-44.20260530 and this resolved the issue for me as well.

Additional data points:

• in bazzite 43, I never had 5ghz connectivity and was limited to ~50mbps
• in testing-44.20260530 with iwd disabled, 5ghz functions and I'm getting ~350mbps (my AP's are wifi5)
• in testing-44.20260530 with iwd enabled, 5ghz fails and I am limited to ~50mbps

Thanks again!!

[lsjobom]

I believe that this will be a problem once more. The above commit 5043719 removes /tmp/rpms/{common,kmods}/wl.rpm from build_files/install-kernel-akmods. This seems to mean that testing-44.20260303.1 and later are missing the driver.

Perhaps @KyleGospo can shed some light on the situation, since that's who merged pr #4997 and also made the commit reverting it?

Is broadcom-wl dropped on purpose? Are we meant to layer broadcom-wl and kmod-wl as per above instead?