Broadcom WLAN kernel module not loaded when secure boot is enabled

Bug #2073303 reported by Sebastian
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
broadcom-sta (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

With a fresh install of Ubuntu 24.04 LTS on an older notebook with a Broadcom BCM4352 WLAN chip and secure boot enabled, I tried to get WiFi running by installing the bcmwl-kernel-source package. Unfortunately, the module does not load:

> sudo modprobe wl
modprobe: ERROR: could not insert 'wl': Key was rejected by service

I was then following the procedure described here, to sign the wl kernel module manually:

https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/

This resulted in this warning - but the module wl module did not load either.
>dkms status
broadcom-sta/6.30.223.271, 6.8.0-38-generic, x86_64: installed (WARNING! Diff between built and installed module!)

Can you advise how to get the wl kernel module running? Thank you in advance.

-------------------------------------------------------------------------------------------------

Description: Ubuntu 24.04 LTS
Release: 24.04

bcmwl-kernel-source:
  Installed: 6.30.223.271+bdcom-23ubuntu1
  Candidate: 6.30.223.271+bdcom-23ubuntu1
  Version table:
 *** 6.30.223.271+bdcom-23ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu noble/restricted amd64 Packages
        100 /var/lib/dpkg/status

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Dual Band Wireless Network Adapter [14e4:43b1] (rev 03)
 Subsystem: Lenovo BCM4352 802.11ac Dual Band Wireless Network Adapter [17aa:0623]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 255
 IOMMU group: 10
 Region 0: Memory at c1200000 (64-bit, non-prefetchable) [size=32K]
 Region 2: Memory at c1000000 (64-bit, non-prefetchable) [size=2M]
 Capabilities: <access denied>
 Kernel modules: bcma, wl

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-23ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 22:38:08 2024
InstallationDate: Installed on 2024-07-14 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sebastian (pythaios) wrote :
Revision history for this message
Sebastian (pythaios) wrote :

I would like to add a few more details on how to reproduce (and how I fixed it eventually). I installed Ubuntu 24.04 alongside to an existing Ubuntu 20.04 installation with UEFI boot enabled, but on the same physical devices (just on a new/different partition). Grub detected the existing 20.04 installation but it appears the UEFI image does not get updated: I could list the available boot options but the boot loader did not appear on machine start-up after running grub-update.

After some time, I decided to back the entire disk up and erase it. It seems erasing the existing UEFI boot partition and followed by a fresh install did the trick: when installing the bcmwl-kernel-source package, I was asked to enter a password for enrolling a new MOK, after reboot I prompted the password and the wl module loads just fine.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in broadcom-sta (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.