Bug 1173449 - WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman.
WiFi Device not working for BCM-43142,even after the installation of boradcom...
Status: RESOLVED INVALID
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel
Leap 15.2
64bit Other
: P5 - None : Major (vote)
: ---
Assigned To: openSUSE Kernel Bugs
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-06-28 15:31 UTC by Aman Vaishya
Modified: 2020-11-19 14:35 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
bwayson's hwinfo output (1.11 MB, text/plain)
2020-07-18 22:22 UTC, Bill Wayson
Details
bwayson's dmesg output with PackMan packages (75.85 KB, text/plain)
2020-07-18 22:24 UTC, Bill Wayson
Details
bwayson's dmesg output without PackMan packages (75.82 KB, text/plain)
2020-07-18 22:24 UTC, Bill Wayson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aman Vaishya 2020-06-28 15:31:22 UTC
Not getting an option to turn wifi on in openSuse 15.2

Steps to reproduce :
1. Install opensuse leap 15.2.
2. add packman repo.
3. install broadcom-wl and reboot.

lspci output :

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1)
07:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)
08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Comment 1 Takashi Iwai 2020-07-08 10:28:21 UTC
Could you give the output of hwinfo, and the dmesg outputs with and without broadcom-wl package installation?  Please attach to Bugzilla (no paste).
Thanks.
Comment 2 Bill Wayson 2020-07-18 22:22:55 UTC
Created attachment 839829 [details]
bwayson's hwinfo output
Comment 3 Bill Wayson 2020-07-18 22:24:20 UTC
Created attachment 839830 [details]
bwayson's dmesg output with PackMan packages
Comment 4 Bill Wayson 2020-07-18 22:24:59 UTC
Created attachment 839831 [details]
bwayson's dmesg output without PackMan packages
Comment 5 Bill Wayson 2020-07-18 22:25:41 UTC
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.
Comment 6 Takashi Iwai 2020-07-27 07:38:24 UTC
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.
Comment 7 Aman Vaishya 2020-07-27 15:36:04 UTC
(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.
Comment 8 Miroslav Beneš 2020-11-19 14:35:50 UTC
Per Takashi's comment 6. See also comment 7.