just updated from 5.19.6-200 to 6.0.5-200 and there’s no wifi connection (not detecting any networks). booting back on 5.19 everything’s fine again.
i’m running f36 on late 2011 mbp/broadcom-wl.
Can you please post us the output of inxi -Nas pre-formated </>text.
1 Like
Got same issue on F36. Neither wifi nor rj45 are detecting any network.
basically it goes from driver: wl on 5.19 to
Device-2: Broadcom BCM4331 802.11a/b/g/n driver: N/A
ethernet works fine though.
ps: idk if it is obvious or not, but broadcom-wl is still installed.
so, if there’s no reasonable course of action on fixing this what do i do now? atm i try different newer kernel versions with no luck - wifi didn’t work with 6.0.5, 6.0.7 and now with 6.0.8 too. after each one i roll back to 5.19.
with f37 release will i be able to choose kernel version? what i’m afraid of is i’ll upgrade to f37 and pre-6 kernel versions shall disappear from boot menu while being replaced with three latest post-6 versions and them it’s asta la vista for me.
i’ve got myself into a serious pickle here.
i decided to try to remove broadcom-wl and reinstall it on 6.0.10. when i did that it removed “5.19 dependencies”. so, when wifi driver still didn’t work on 6.0.10 i went back to 5.19 and it wasn’t installed there and when i install it (broadcom driver that is) it also installs 6.0.10 kernel-core (but skips kernel, kernel-modules and kernel-modules-extra) and dependecies to it. and when i reboot it tries to boot into a 6.0.10, but fails, and when i get back to 5.19 it shows no driver. so how do i get back to somewhat older version of broadcom-wl driver to work with 5.19 kernel and not contaminated with kernel 6+ code?
so i uninstall everything, keep a clear 5.19 install. how do i install broadcom-wl then without getting any kernel updates?
so, idk if this is a miracle or a curse, but when i removed broadcom driver again and rolled back to 5.19 it turned out that there is some other wifi driver available:
inxi -n
Network:
Device-1: Broadcom NetXtreme BCM57765 Gigabit Ethernet PCIe driver: tg3
IF: enp2s0f0 state: down mac: 3c:07:54:3e:8f:5f
Device-2: Broadcom BCM4331 802.11a/b/g/n driver: bcma-pci-bridge
IF-ID-1: wlp3s0b1 state: up mac: b8:8d:12:28:37:7a
the issue now is with this generic (?) driver i can only connect to 2.4ghz network with much lower speed (i even updated to 6.0.10). and if i install the bdroabcom driver i get back to square one - inxi returns no driver again and get no wifi connection at all.
so for now i can hang on this bcma-pci-bridge driver, but i’d really like to find a way to run broadcom driver properly. so the question of how to go back to 5.19 is still stands.
5.19 is EOL but htere is an LTS Kernel you could try to use as long 6.x not works well … you just have to check always to see if the proprietary drivers got upgraded.
5.15lts doesn’t solve the issue because it isn’t with the 5.19. i pretty much don’t care if the kernel version is eol, i’m fine with not getting updates or whatever as long as i can get the wifi driver working properly.
the issue is, as far as i can understand, that the freshly installed broadcom-wl forces some 6.0.5 and 6.0.10 dependencies and it doesn’t work because of this, no matter the actual kernel running. in this respect the situation is identical on 5.15, 5.19 and 6.0.10. and i know it kept working with 5.19 dependecies to this day.
so what i need now is a way to install the driver on 5.19 (or 5.15lts - doesn’t matter as long as i can do it) without adding some 6.0+ components. for example, i tried to download the rpm package and install it with no active internet connection, but the installation fails this way.
Any module installed using an akmod has dependencies on the kernel running (and on the versions being installed). Some of those dependencies may not be compatible between version levels, so the matching versions are installed.
I think your issue is that you removed something and allowed it to remove dependencies of other packages. That other package(s) saw those dependencies were already installed so did not re-install them.
Lesson here is that one should be very careful about removing a package and allowing it to also remove a lot of dependencies. The --noautoremove option is designed for this case.
You can get a complete list of the packages removed as dependencies with dnf history to identify the transaction that was used to remove the package, then dnf history info <Transaction ID> for detailed info on what was done in that transaction
just to reiterate, the original issue occurred long before removal of the package and its dependencies. any kernel update from 5.19 with working broadcom-wl past 6.0 lead to “no driver” issue. the only difference now is that just by updating the kernel i could keep working version on 5.19 and with reinstalling the driver i now get faulty “later” version on any kernel.
so is there a chance that if i try older akmod-wl (which afaiu is requiring 6.0+ kernel stuff) and broadcom-wl versions i may find some of them do not require post 6 kernel?
so, here’s the transaction:
Command Line : remove broadcom-wl
Comment :
Packages Altered:
Removed broadcom-wl-6.30.223.271-19.fc36.noarch @@System
Removed kmod-wl-5.19.15-201.fc36.x86_64-6.30.223.271-42.fc36.x86_64 @@System
Removed kmod-wl-5.19.16-200.fc36.x86_64-6.30.223.271-42.fc36.x86_64 @@System
Scriptlet output:
1 depmod: WARNING: /lib/modules/5.19.16-200.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol kunit_do_failed_assertion
2 depmod: WARNING: /lib/modules/5.19.16-200.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol __kunit_test_suites_exit
3 depmod: WARNING: /lib/modules/5.19.16-200.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol __kunit_test_suites_init
4 depmod: WARNING: /lib/modules/5.19.16-200.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol kunit_binary_assert_format
5 depmod: WARNING: /lib/modules/5.19.15-201.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol kunit_do_failed_assertion
6 depmod: WARNING: /lib/modules/5.19.15-201.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol __kunit_test_suites_exit
7 depmod: WARNING: /lib/modules/5.19.15-201.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol __kunit_test_suites_init
8 depmod: WARNING: /lib/modules/5.19.15-201.fc36.x86_64/kernel/sound/soc/soc-utils-test.ko.xz needs unknown symbol kunit_binary_assert_format
how do i revert it? should i look for these versions of kmod-wl and broadcom-wl on the internet specifically?
Those kmod-wl packages were built locally for the specific kernel by broadcom-wl and the code that it contained at that time (as well as the code contained in the kernel-devel package for those kernels).
I do not know all the details, but I know older fedora packages are available from koji and you probably with a little effort could get the matching and needed packages from there. I do not know how to identify exactly what would be required though. It may be a trial and error process for you .
It also might require that you remove all the newer kernels so you are only working with the 5.19.XX kernel. Older kernels are available on koji.
https://koji.fedoraproject.org/koji/packages
It seems the akmod-wl and broadcom-wl packages are hosted on rpmfusion so the archives are not on koji as I initially supposed.
Different process to locate and download them, but still seems prudent to remove all the 6.X kernels and then download and install the appropriate broadcom packages to build the drivers for the 5.19.XX kernel.
While not entirely relevant this may give you some pointers.
https://discussion.fedoraproject.org/t/fedora-34-broadcom-wl/77103/4