Try now:
sudo modprobe -r wl
sudo modprobe -v wl.
Results in:
Errors during downloading metadata for repository fedora:
Curl error (6) Couldn't resolve host name for https://mirrors.fedoraproject.org/..
Error: fedora meta data could not be downloaded (my translation)
If I could do these steps from the earlier kernel, there I can connect to the internet with usb and bluetooth, but not with the latest kernel.
1 Like
sudo modprobe -v wl results in:
insmod /lib/modules/6.10.3-200.fc40.x86_64/extra/wl/wl.ko.xz
modprobe: ERROR: could not insert 'wl': Unknown symbol in module, or unknown parameter (see dmesg)
Performed a fresh install of F40. To get working used:
sudo dnf downgrade broadcom-wl --releasever=37 -y
Maybe rebuilding the kernel module dependencies, with sudo depmod, then reloading the wl modules might help.
If still not working, someone with fresh ideas might join the conversation (see also J Mullerâs workarounds above).
Journalctl should have the dmesg output. I imagine it will provide useful details. Iâve been using linux on Apple systems for over 20 years, so have found it necessary to have USB dongles for ethernet, WiFi, Bluetooth, and audio to avoid work interruptions with kernel upgrades and security-related updates. I currently have a late 2012 iMac with the same BCM4360 and using wl:
% inxi -Nxx
Network:
Device-1: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter vendor: Apple driver: wl
v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:43a0
I do, however, also have a wired network. Maybe you could take your laptop to a place that has a wired network. Failing that, you could add a USB wired network dongle. I have in the distant past struggled with building and installing updates to network drivers by downloading source packages with older kernels or even macOS.
At the time, I often needed to build patched versions of packages, so was quite familiar with the process, but even so multiple iterations were often needed to get all the required packages. It is much simpler to plug in a WiFi dongle.
I tried this. When I installed broadcom-wl and rebooted, again fedora could not connect to internet, not even with bluetooth or usb tethering. And therefore I could not downgrade broadcom-wl as it gives curl error (no internet)
OMG, this is the best advice ever, not sure why this had never occurred to me. I have a 2014 MBP and a 2015 iMac, and both have struggled for years with Broadcom issues across multiple distros, and of course fell victim to this latest issue. It would be so great to leave all that behind.
I have an old, slow WiFi dongle I bought for a Raspberry Pi. Plugged that in to my MBP, worked immediately, bye-bye Broadcom.
Any recommendations on brands or chipsets of WiFi dongles that are well-supported by mainline Linux/Fedora? (Feel free to ignore if thatâs too off-topic for this thread.)
1 Like
Not off topic since that is often suggested as a workaround for the broadcom issue.
Almost any wifi dongle with an intel chipset works. Several others do as well but I do not have a variety of devices to recommend. The chipset is the important part since it must be supported by fedora.
1 Like
Glad to see my experience from years of fighting with Apple Broadcom wifi is helpful to others.
External dongles come in many form factors from a small dongle like the Edimax to ones with large antennae on a cable. Apple seems to use pretty good antennae, so the small ones may not work in places where builtin WiFi does work in macOS.
You should be able to determine the chip used by your existing dongle by running inxi -Nzxx. The Raspberry Pi community should be a good source of information about linux compatible USB WiFi hardware.
2 Likes
I have the same issues, my broadcom BCM4331 was working fine, until the upgrade. Using
ip link show
...
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000
link/ether ac:29:3a:e6:87:ac brd ff:ff:ff:ff:ff:ff
I see that the interface is up, but I had no available connections, and turning off/on wifi in network manager did nothing. However, I ran
iw dev wlp2s0 scan
which was successful, showing all the available wireless networks, and network manager picked up on them and automatically connected to my regular wireless network. If youâre unable to downgrade wpa_supplicant, this may be an option
1 Like
BCM4360 working perfect until last week.
Looking forward to solve
Please check that the BCM4360 is detected by the kernel with inxi -Nzxx, then look for âDISABLEDâ for the wifi device (usually starts with âwlâ) in ip link show. Then try iw <wifi_device> scan.
I wanted to retry installing from scratch and then trying to downgrade wpa_supplicant and then installing broadcom-wl directly from release 37, but alas my laptop also has issues with its hdd and I cannot reinstall from scratch. I think the usb dongle or possibly using a LAN (my laptop doesnât have etherner input but I am sure there is a converter I can buy to use the LAN) should fix the issue for good, rather than dealing with broadcom-wl every time there is an update.
Probably not wise with using f40.
The dongle seems best to me. They are available both for wifi and ethernet.
1 Like
woks for me:
sudo dnf reinstall wpa_supplicant
Hi,
but am I the only one still having this problem?
MacBook Pro early 2011
Andrea
This thread mentions a number of workarounds/upgrades. My late 2012 still needs a manual step to enable WiFi after rebooting. If the workarounds donât help, then please start a new thread. If you havenât been able to use WiFI (maybe with an older kernel) because you system doesnât have alternate internet access, e.g., a USB WiFi dongle or wired ethernet) you may need access to another system.
We canât help without more details than you have provided. It is best if those details are provided as text so they can be found with a web search. You may need to save details to text file and transfer to another system using a USB memory âkeyâ. You can also download the current wpa_supplicant RPM package to a USB key on another system and install it from the USB key.
Please proivde the output from running inxi -Fzxx in a terminal (as pre-formatted test using the </> button from the top line of the text entry panel) so we can see your hardware details, the drivers being used, and the kernel version.
Have you run sudo dnf reinstall wpa_supplicant? Here I have:
% sudo dnf list installed | grep wpa_supplicant
wpa_supplicant.x86_64 1:2.11-3.fc40 @updates
Seams to be solved with newest update:
Hello everyone,
Since today everything is working fine again.
I donât understand what has changed, not the kernel and not the version of wpa_supplicantâŚ
Andrea