FS#77835 - [broadcom-wl] WPA2 connections not working on Kernel 6.2.5

Attached to Project: Community Packages
Opened by Bianca Arone (PancakeSharks) - Monday, 13 March 2023, 00:38 GMT
Last edited by Toolybird (Toolybird) - Monday, 13 March 2023, 06:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Updating to Kernel 6.2.5 causes some type of conflict with the package and it's impossible to connect to any encrypted network. It appears that someone found a patch for this issue on Kernel 6.3 that was also present on the Raspberry Pi.

At first I used broadcom-wl-dkms, but seeing that it wasn't working I removed the package and installed broadcom-wl, rebooting didn't do the trick.
It might be the same problem in Kernel 6.2.5.

Additional info:
https://gist.github.com/joanbm/fb90f4807b719a2e37a496936faabec9

Steps to reproduce:
1) Have broadcom-wl installed
2) Update to Kernel 6.2.5
3) Can't connect to Wi-Fi
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 13 March 2023, 06:56 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#77832 
Comment by Jon Whatmore (juanejot) - Monday, 13 March 2023, 03:17 GMT
Can confirm this behavior, adding that in addition to the lack of ability to connect to an encrypted (WPA2) network, I was also unable to connect to even an unencrypted network, using either BCM4322 or BCM4360 hardware. I too suspect a possible link to the 6.2.5 kernel, as I've also noticed the same inability to make a connection using a b43-firmware. Updates to supporting packages like networkmanager & libnm did not seem to be major (from 1.42.2-1 to 1.42.4-1). By contrast, see this diff between 6.2.2 and 6.2.5 (as Arch seems to have jumped publicly between 6.2.2.arch2-1 and 6.2.5.arch1-1), searching for "broadcom:"

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v6.2.5&id2=v6.2.2&dt=2

I can't make sense of all the kernel changes to how it works with Broadcom hardware, but they may be more than what incremental updates to either the driver or the Network Manager were able to keep up with. It sounds like maybe there are changes to how kernel 6.3 interfaces with Broadcom afoot, and changes between 6.2.2 and 6.2.5 may be laying some groundwork?
Comment by loqs (loqs) - Monday, 13 March 2023, 03:55 GMT
@juanejot see [1] and [2].

[1] https://bbs.archlinux.org/viewtopic.php?id=284254
[2] https://bbs.archlinux.org/viewtopic.php?id=284244
Comment by Toolybird (Toolybird) - Monday, 13 March 2023, 06:56 GMT
Seeing as "broadcom-wl" makedpends on "broadcom-wl-dkms", it's the same bug so closing this in favor of  FS#77832 

Loading...