[Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

[Steve Langasek]

Thanks for confirming.

> Should the shim-signed package have a dependency on a kernel that is
new enough?

For better or worse, there is no straightforward way to express such a
dependency.  But also, the fundamental problem here is not that shim-
signed has new requirements.  The fundamental problem is that you and
other users have been running a kernel that has had no security updates
for over 2 years and didn't know it.  While it was stated at the time
that these kernels would have security support for a limited time and
that users who had these kernels installed would not be automatically
rolled forward to the next series (as this might introduce regressions
in hardware support), evidently this information was not communicated in
a way that made it clear to users that they were out of security
support.

I will look into what can be done to improve the communication to users
in all the usual places that information about security updates are
communicated, to let users know they are running unsupported kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1818134

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions