Ubuntu 16.4LTS version does not have modprobe 'wl' package in kernel

Asked by HB

I have recently tried to run :
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.1_amd64.deb

The answer was:

(Adatbázis olvasása ... 359448 files and directories currently installed.)
Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.1_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) over (6.30.223.271+bdcom-0ubuntu1~1.1) ...
Beállítás: bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building only for 4.8.0-41-generic
Building for architecture x86_64
Building initial module for 4.8.0-41-generic
Done.

wl:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.8.0-41-generic/updates/dkms/

depmod....

DKMS: install completed.
modprobe: ERROR: could not insert 'wl': Required key not available
update-initramfs: deferring update (trigger activated)
Processing triggers for shim-signed (1.19~16.04.1+0.8-0ubuntu2) ...
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-41-generic

What is the main thing that
modprobe: ERROR: could not insert 'wl': Required key not available

The kernel version is Linux 4.8.0-41-generic.

What should I do now?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
HB
Solved:
Last query:
Last reply:
Revision history for this message
HB (hbalint1) said :
#1

Have installed my Broadcom wifi card and than the problem disappeared.

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#2

It's probably, because you were trying to install an unsigned kernel module (wl module) while having SecureBoot enabled in the UEFI firmware

Either disable SecureBoot in UEFI or sign the kernel module using this procedure (replacing vboxdrv with wl) :

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

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#3