Great news! I glad you’ve succeeded too!
1 Like
So I was waiting in vain for an update to fix this problem… Goodbye. Last time I tried Fedora, because BCM43142 worked in any other Gnu/Linux on this machinr!
Hi, @peterjmb! We are all free to do what we want to, and you’re free to use Fedora or any other distro you like.
I don’t have BCM43142, so I know next to nothing about it. But as the information about this problem posted in known bugs article for Fedora 30 (not 29 or 28, not for earlier ones) I assume it used to work for previous Fedora releases without any problem too.
If the problem is with some new features of newer versions of wpa_supplicant, then you can face exactly the same issue on other distribution. Right now for the ones which use the same version as Fedora, later on distributions with slower update cycle.
Then again, maybe it’s Fedora-specific (which it doesn’t look like with the info I’ve seen), or if it would be resolved in wpa_supplicant by the time other GNU/Linux distribution updates wpa_supplicant, or if Broadcom decides to update their proprietary driver to help it’s users (like you) – then there’s a chance you wouldn’t see this on another distro.
So please do what your heart desires ) And, as they say, stay free, stay open source! 
What problem though? Were you experiencing the exact same issues as the poster did here?
Sorry for the late reply, now I’m using Fedora on another machine, but on this laptop with Broadcom wireless the issue remains in other Linux distros too. Just enabled secure boot for another reason: no more WiFi. Disable secureboot and the WiFi works again!
This behavior usually has a very simple explanation.
-
Custom/addon driver – for your WiFi in your case, but it can also be Nvidia’s GPU or some other device, also VirtulaBox kernel modules – usually need additional kernel modules, and quite often they are recompiled on your machine for each new kernel (with the use of dkms or akmods).
This system works perfectly with secure boot disabled.
-
But secure boot essentially want every kernel module to be signed with a valid certificate/signatu, if module isn’t signed, secure boot won’t allow to load it. Again, it work ok with modules provided by Fedora, as they are all validly signed.
-
The modules dynamically recompiled for each kernel on your machine aren’t signed as you or your computer don’t possess valid Fedora private key to do such a signing. Thus they are rejected by secure boot.
This is true not only for the Fedora, but for any Linux distribution.
Note. Actually, you can sign new modules with your own private key manually or even automatically on each rebuild. But the setup process is quite complicated, and basically no one bothers. I’ve heard Ubuntu does setup this signing, at least for Nvidia’s drivers, but I don’t use Ubuntu myself.
2 Likes