Ubuntu
bcmwl package

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

Bug #1187206 reported by kelargo on 2013-06-04

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

installing low latency kernel for ubunustudio and this error occurred.

also, this laptop might have a hardware problem with the built in wireless.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-24.16-lowlatency 3.8.13
Uname: Linux 3.8.0-24-lowlatency x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
DKMSKernelVersion: 3.8.0-24-lowlatency
Date: Mon Jun 3 20:21:34 2013
InstallationDate: Installed on 2011-12-25 (526 days ago)
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
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 2013-06-02 (1 days ago)

Tags:

Revision history for this message

kelargo (kelong-2000) wrote on 2013-06-04:

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")

Apport retracing service (apport) on 2013-06-04

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-06-05:

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.