bcmwl-kernel-source (not installed): bcmwl kernel module failed to build

[Priya Bansal]

I'm really not sure what the issue is. I'm a new Ubuntu user, and I was having troubles with my network driver (as well as, I'm assuming, some other drivers. I just don't think they installed correctly.) I ended up going to the advanced options menu in the boot loader and choosing what I think is an older version of Ubuntu and everything looks like it works fine. However, before I figured this out, I tried installing some network drivers from the same flash drive I installed Ubuntu with. Some errors got thrown, it looked like because some other firmware didn't get installed, and now even though it seems everything's working, this bcmwl-kernel-source (not installed) error keeps popping up and I don't know how to get rid of it.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
DKMSKernelVersion: 4.13.0-37-generic
Date: Mon Mar 26 12:32:20 2018
DuplicateSignature: dkms:bcmwl-kernel-source:(not installed):/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’
InstallationDate: Installed on 2018-03-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageVersion: (not installed)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: bcmwl
Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1724863, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.