Ubuntu
bcmwl package

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

Bug #1216588 reported by Jackow on 2013-08-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

Dieser Kernel scheint irgendwie buggy zu sein, da ich nichts gemacht habe.
UbuntuStudio 13.04 auf einem hp Compaq 6710b Laptop.
Externes Audiointerface M-Audio Fast-Track Pro.
XFCE Desktop.
Keine Anwendung offen.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
DKMSKernelVersion: 3.8.0-29-lowlatency
Date: Sat Aug 24 09:59:44 2013
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-04-27 (119 days ago)

Tags:

Revision history for this message

Jackow (jack-mellonet) wrote on 2013-08-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")

Apport retracing service (apport) on 2013-08-25

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-08-26:

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.