Ubuntu
bcmwl package

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

Bug #1667884 reported by sai satyam on 2017-02-25

This bug report is a duplicate of: Bug #1595765: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bcmwl (Ubuntu)	New	Undecided	Unassigned

Bug Description

wifi is not enabled

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
DKMSKernelVersion: 4.8.0-36-generic
Date: Sat Feb 25 10:13:22 2017
DuplicateSignature: dkms:bcmwl-kernel-source:(not installed):/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageVersion: (not installed)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: bcmwl
Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

sai satyam (saisatyam) wrote on 2017-02-25:

DKMSBuildLog.txt Edit (111.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (21.9 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2017-02-25

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2017-02-27:

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 1595765, 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.