bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcmwl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Trying to install linux-lowlatency package on a MacBookPro with ubuntu 13.04, synaptic reports:
run-parts: executing /etc/kernel/
Error! Bad return status for module build on kernel: 3.8.0-30-lowlatency (x86_64)
Consult /var/lib/
Looking at make.log says:
DKMS make.log for bcmwl-6.
Sun Sep 15 18:30:16 CEST 2013
make: Entering directory `/usr/src/
CFG80211 API is prefered for this kernel version
Using CFG80211 API
LD /var/lib/
CC [M] /var/lib/
CC [M] /var/lib/
CC [M] /var/lib/
CC [M] /var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
LD [M] /var/lib/
Building modules, stage 2.
CFG80211 API is prefered for this kernel version
Using CFG80211 API
MODPOST 1 modules
FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
make: Leaving directory `/usr/src/
So apparently this is the culprit on the lowlatency kernel:
FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'
best,
-mario
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.
ProcVersionSign
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
DKMSKernelVersion: 3.8.0-30-lowlatency
Date: Sun Sep 15 18:29:36 2013
InstallationDate: Installed on 2012-04-23 (510 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120421)
MarkForUpload: True
PackageVersion: 6.20.155.
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.20.155.
UpgradeStatus: Upgraded to raring on 2013-04-30 (138 days ago)
tags: | removed: need-duplicate-check |
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.