The package broadcom-wl from RPM Fusion is the right package for your card. Is your system up-to-date? When installing the driver, as well as with every new kernel, one has to wait a couple of minutes until the kernel modules get rebuilt. Is it possible that you restarted the system right after install?
What is the output of lspci | grep wireless and lsmod | grep wl?
In addition to the suggestions from @tqcharm, there have been some issues a while ago with Broadcom wifi in relation to an update to wpa_supplicant, this specifically crippled older Macbooks.
Since F40 is about to be replaced with F41, one other suggestion could be to install that instead, since it will likely carry the fixes needed. As an alternative you can search the forums for “macbook broadcom wifi” and you will find a number of threads with suggestions to mitigate the issue.
Good point. However, after a few weeks of issues the wl-kmod source package got fixed by the RPM Fusion team (I know that from personal experience, as I also have an old MacBook at home with F40), hence my question regarding the system being up to date.
@tfpppp , please also post the output from dnf list installed *kmod-wl*.
lspci | grep wireless and lsmod | grep wl gave no output. I entered them in terminal as you had written. Is this correct way to do it or i missed something?
I suspect that the driver modules didn’t get built. The output of dnf list installed *kmod-wl* should have also listed at least one package in format:
You could try uninstalling and reinstalling the broadcom-wl package. After reinstalling the package, give it at least a couple of minutes before rebooting:
Right after reinstalling, you could check if the modules are being built, with the command ps -ax | grep wl (you can run it several times). If there is more than one line, than the module is being built. Don’t restart yet.
Once the command ps -ax | grep wl outputs only one line (ending with grep --color=auto wl) you can restart.
Hopefully the Wireless option is showing up in the Settings.
In many, if not most, cases where a kernel module may not have been properly built due to an early reboot there is a quick and seemingly positive fix.
The command sudo akmods --rebuild --force will remove the existing kmod package and build and install a newer completed version of that package.
If this problem is caused by a defective version of the kmod-wl kernel module then the akmods command should repair it.
I noticed also that though the rollback to an earlier version of wpa-supplicant was mentioned there seems no indication that there was an attempt to try that as a solution.
The OP is missing the packages kernel-modules and kernel-modules-extra for the latest kernel, but has kernel-modules-core installed. I thought those two missing packages are being installed at the time of a new kernel version install, and not necessarily when a new module is being built. Am I wrong maybe?
This is not necessary anymore, since both wpa_supplicant and broadcom-wl got a fix in August.