http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 http://bugzilla.opensuse.org/show_bug.cgi?id=1173449#c3 --- Comment #3 from Bill Wayson --- Created attachment 839830 --> http://bugzilla.opensuse.org/attachment.cgi?id=839830&action=edit bwayson's dmesg output with PackMan packages -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 http://bugzilla.opensuse.org/show_bug.cgi?id=1173449#c5 --- Comment #5 from Bill Wayson --- I have a similar issue. Mine actually involves two packages from PackMan: broadcom-wl-kmp-default-6.30.223.271_k5.3.18_lp152.20.7-pm152.12.45.x86_64 (the actual wl.ko module) and broadcom-wl-6.30.223.271-pm152.12.45.x86_64 (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 https://bugzilla.opensuse.org/show_bug.cgi?id=1173682 - Changes needed in Release Notes about unsigned kernel modules and Secureboot Mode on Leap 15.2; and https://bugzilla.opensuse.org/show_bug.cgi?id=1173158 - 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: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 http://bugzilla.opensuse.org/show_bug.cgi?id=1173449#c7 --- Comment #7 from Aman Vaishya --- (In reply to Takashi Iwai from comment #6)

Both of you seem to have enabled Secure Boot, and that's the known side-effect of the Leap 15.2 kernel. Now it takes more strict Secure Boot lockdown to refuse the unsigned kernels. You'd need to sign the modules by yourself and enable the key via MOK enrollment, or at easiest, just disable Secure Boot in the BIOS.

Optionally, Packman sign the modules by its build server with its own key and enroll that public key onto your system. Or, change the package to do a one-time key generation and implement the MOK enrollment. In anyway, it's the Packman's packaging problem. Please report and discuss with Packman people.

Yes, after disabling the secure boot, the WiFi driver seems to work. -- You are receiving this mail because: You are the assignee for the bug.