Ubuntu
bcmwl package

bcmwl-kernel-source 5.100.82.112+bdcom-0ubuntu3: bcmwl kernel module failed to build

Bug #1427656 reported by Glendon Gross on 2015-03-03

This bug report is a duplicate of: Bug #1197586: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6 Error! Bad return status for module build [error: implicit declaration of function ‘create_proc_entry’]. Edit Remove

This bug affects 1 person

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

Bug Description

Apparently this bug has also been reported for other versions of the kernel source. I think it may have to do with incomplete module builds, since I am running a low-latency kernel.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-46.76-lowlatency 3.13.11-ckt15
Uname: Linux 3.13.0-46-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
DKMSKernelVersion: 3.13.0-46-generic
Date: Mon Mar 2 08:10:32 2015
InstallationDate: Installed on 2015-03-01 (2 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageVersion: 5.100.82.112+bdcom-0ubuntu3
SourcePackage: bcmwl
Title: bcmwl-kernel-source 5.100.82.112+bdcom-0ubuntu3: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Glendon Gross (gross-clones) wrote on 2015-03-03:

DKMSBuildLog.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2015-03-03

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2015-03-04:

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