Ubuntu
bcmwl package

bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build

Bug #1272761 reported by rogerglewis13@gmail.com on 2014-01-25

This bug report is a duplicate of: Bug #1156138: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']. Edit Remove

This bug affects 1 person

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

Bug Description

just upgraded? no idea what is amiss.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: i386
DKMSKernelVersion: 3.8.0-35-lowlatency
Date: Sat Jan 25 22:06:21 2014
InstallationDate: Installed on 2013-03-31 (300 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
PackageVersion: 6.20.155.1+bdcom-0ubuntu6
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build
UpgradeStatus: Upgraded to raring on 2014-01-25 (0 days ago)

Tags:

Revision history for this message

rogerglewis13@gmail.com (rogerglewis13) wrote on 2014-01-25:

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

Revision history for this message

rogerglewis13@gmail.com (rogerglewis13) wrote on 2014-01-25:

No ideas I am afraid.

Apport retracing service (apport) on 2014-01-25

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-01-29:

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