Comment 23 for bug 1899678

To clarify - the modprobe was not a live-session - this was after a
full disk install.

So - I MOK enrolled after the ubiquity install - no wifi on first
logon. Modprobe wl gave the not permitted error.

I then manually connected and force a reinstall of bcmwl-kernel-source
and subsequently on boot another MOK enroll was requested. It was
only then that Wifi was available.

On Wed, 21 Oct 2020 at 22:30, Steve Langasek <email address hidden> wrote:
>
> If you are trying to do the modprobe during the live session, it is
> expected that this will not succeed. It's only after MOK enrollment
> that these locally-signed modules will be allowed to be loaded by the
> kernel under SecureBoot.
>
> If the modprobe works post-reboot and post-MOK-enrollment, then this is
> working as required and I believe we can close the bug report.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1899678
>
> Title:
> No wifi after installation - does not work with secure boot enabled
>
> Status in bcmwl package in Ubuntu:
> New
> Status in dkms package in Ubuntu:
> New
> Status in shim-signed package in Ubuntu:
> New
> Status in ubiquity package in Ubuntu:
> New
>
> Bug description:
> After installation I noted that my broadcom wifi was not available.
> This is a regression from 20.04 where installation automatically
> installed the broadcom driver.
>
> So I tried to force the installation again - see trace below.
>
> The dialog message to enter the secure password appeared - however on
> reboot a confirmation to change the MOK state was not seen - the
> distro booted straight in.
>
> sudo apt install --reinstall bcmwl-kernel-source
> [sudo] password for dad:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade.
> Need to get 1,546 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB]
> Fetched 1,546 kB in 0s (5,232 kB/s)
> (Reading database ... 202371 files and directories currently installed.)
> Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ...
> Removing all DKMS Modules
> Done.
> Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ...
> Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
> Loading new bcmwl-6.30.223.271+bdcom DKMS files...
> Building for 5.8.0-22-generic
> Building for architecture x86_64
> Building initial module for 5.8.0-22-generic
> Done.
>
> wl.ko:
> Running module version sanity check.
> - Original module
> - No original module exists within this kernel
> - Installation
> - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/
>
> depmod....
>
> DKMS: install completed.
> modprobe: ERROR: could not insert 'wl': Operation not permitted
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.137ubuntu12) ...
> update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.10
> Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
> ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
> Uname: Linux 5.8.0-22-generic x86_64
> ApportVersion: 2.20.11-0ubuntu49
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: Budgie:GNOME
> Date: Tue Oct 13 18:32:47 2020
> InstallationDate: Installed on 2020-10-13 (0 days ago)
> InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013)
> SourcePackage: bcmwl
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+subscriptions