Testet 3.11 kernel on 13.04 but bcmwl failed to build:
DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.11.0-997-generic (x86_64)
tor 8 aug 2013 19:53:28 CEST
make: Entering directory `/usr/src/linux-headers-3.11.0-997-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
LD /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/built-in.o
CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_tkip_printstats’:
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2704:7: warning: passing argument 1 of ‘wl->tkipmodops->print_stats’ from incompatible pointer type [enabled by default]
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2704:7: note: expected ‘struct seq_file *’ but argument is of type ‘char *’
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2707:4: warning: passing argument 1 of ‘wl->tkipmodops->print_stats’ from incompatible pointer type [enabled by default]
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2707:4: note: expected ‘struct seq_file *’ but argument is of type ‘char *’
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2917:2: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2917:22: warning: assignment makes pointer from integer without a cast [enabled by default]
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2922:16: error: dereferencing pointer to incomplete type
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2923:16: error: dereferencing pointer to incomplete type
/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.c:2924:16: error: dereferencing pointer to incomplete type
cc1: some warnings being treated as errors
make[1]: *** [/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/src/wl/sys/wl_linux.o] Error 1
make: *** [_module_/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.11.0-997-generic'
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
NonfreeKernelModules: ksplice_l635i70h ksplice_mzwf73r4 ksplice_pqqiothc_bluetooth_new ksplice_pqqiothc ksplice_6m8jvkfb ksplice_9lrcrdgu_vmlinux_new ksplice_9lrcrdgu ksplice_hb6f9w1f ksplice_3181tj9j_vmlinux_new ksplice_3181tj9j ksplice_7fj628gy ksplice_ve96dlv6_vmlinux_new ksplice_ve96dlv6 ksplice_jhcz1xf2_reiserfs_new ksplice_jhcz1xf2 ksplice_l440xstc_reiserfs_new ksplice_l440xstc ksplice_rq91w70s_nfsd_new ksplice_rq91w70s ksplice_cvnprzpm ksplice_6cq0lwq6_vmlinux_new ksplice_6cq0lwq6 ksplice_hv75nix4_vmlinux_new ksplice_hv75nix4 ksplice_8gbhsdr6 ksplice_cj8kz0z4_bluetooth_new ksplice_cj8kz0z4 ksplice_1mxualsi ksplice_9ikyx4ra ksplice_nm328m24_vmlinux_new ksplice_nm328m24 ksplice_xwx0pvso ksplice_9xbk7fhh_drm_new ksplice_9xbk7fhh ksplice_hy7a1s9r ksplice_itsyghou_vmlinux_new ksplice_itsyghou ksplice_fhlgk6wq ksplice_c3f528hy_vmlinux_new ksplice_c3f528hy ksplice_mlih61wi_vmlinux_new ksplice_mlih61wi wl
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
DKMSKernelVersion: 3.11.0-997-generic
Date: Thu Aug 8 19:53:33 2013
InstallationDate: Installed on 2012-11-22 (259 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
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-30 (99 days ago)
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.