Comment # 5 on bug 1173449 from
I have a similar issue.  Mine actually involves two packages from PackMan: 
broadcom-wl-kmp-default- (the
actual wl.ko module) and broadcom-wl- (a module
blacklist file that goes under /etc/modprobe.d/).  Let me know if this is
really PackMan's issue.

I multiboot openSUSE Tumbleweed and Leaps 15.1 and 15.0 on the same PC as 15.2,
and these packages work fine on those distributions.  Two issues I see on 15.2
are that modules listed in the above blacklist file are still loaded upon boot
(ssb, b43, and bcma) (as well as b43legacy); and when I manually run
/sbin/modprobe wl, even after unloading the blaclisted modules, I get the
message, "modprobe: ERROR: could not insert 'wl': Operation not permitted." 
Indeed, wl is not loaded.  I wonder if the 15.2 issue is related to the active
issue of not allowing unsigned modules be be loaded when secure boot is active
on the PC, which appears to be enforced in 15.2 (see bugs - Changes needed in
Release Notes about unsigned kernel modules and Secureboot Mode on Leap 15.2;
and -
CONFIG_MODULE_SIG=y).  I do have secure boot activated on my PC.  Or, is the
problem that the PackMan module needs to be properly signed?  I am not sure. 
But I don't have a problem in the other three distributions.

My broadcom lspci line is:
05:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac
Wireless Network Adapter (rev 03)

I have attached the requested information.  Note that the very last line in the
file "bwayson-broadcom_issue-Leap_15.2-dmesg_with_packages" resulted from my
attempt to manually load wl.ko.

You are receiving this mail because: