package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build

[hamish darby]

Acer d260 with mainline kernel 2.6.36-999-generic_2.6.36-999.201009240945_i386 crash report auto generated when inserting or removing SD card per testing for bug #633852 by total newb ( Ithink, maybe)

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3
Uname: Linux 2.6.36-999-generic i686
Architecture: i386
Date: Fri Sep 24 22:02:22 2010
ErrorMessage: bcmwl kernel module failed to build
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
PackageVersion: 5.60.48.36+bdcom-0ubuntu3
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build

[hamish darby (hjdarby-deactivatedaccount)]

The ENE technology card reader was not detected

a@geraldton:~$ uname -a
Linux geraldton 2.6.36-999-generic #201009240945 SMP Fri Sep 24 10:56:08 UTC 2010 i686 GNU/Linux

a@geraldton:~$ dmesg
[ 0.000000] #43 [0001a00000 - 0001a0e000] BOOTMEM
[ 0.000000] #44 [0001b00000 - 0001b0e000] BOOTMEM
[ 0.000000] #45 [00017f7040 - 00017f7044] BOOTMEM
[ 0.000000] #46 [00017f7080 - 00017f7084] BOOTMEM
[ 0.000000] #47 [00017f70c0 - 00017f70d0] BOOTMEM
[ 0.000000] #48 [00017f7100 - 00017f7110] BOOTMEM
[ 0.000000] #49 [00017f7140 - 00017f71e0] BOOTMEM
[ 0.000000] #50 [00017f7200 - 00017f7248] BOOTMEM
[ 0.000000] #51 [00017f7280 - 00017fb280] BOOTMEM
[ 0.000000] #52 [000180e000 - 000188e000] BOOTMEM
[ 0.000000] #53 [000188e000 - 00018ce000] BOOTMEM
[ 0.000000] #54 [0001b0e000 - 00020017ec] BOOTMEM
[ 0.000000] Initializing HighMem for node 0 (000377fe:0003f600)
[ 0.000000] Memory: 1005596k/1038336k available (4993k kernel code, 31764k reserved, 2405k data, 740k init, 128504k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfff16000 - 0xfffff000 ( 932 kB)
[ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 0.000000] vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
[ 0.000000] .init : 0xc083a000 - 0xc08f3000 ( 740 kB)
[ 0.000000] .data : 0xc05e05df - 0xc0839c68 (2405 kB)
[ 0.000000] .text : 0xc0100000 - 0xc05e05df (4993 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:2304 nr_irqs:712
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 1662.576 MHz processor.
[ 0.004009] Calibrating delay loop (skipped), value calculated using timer frequency.. 3325.15 BogoMIPS (lpj=6650304)
[ 0.004020] pid_max: default: 32768 minimum: 301
[ 0.004067] Security Framework initialized
[ 0.004113] AppArmor: AppArmor initialized
[ 0.004226] Mount-cache hash table entries: 512
[ 0.008259] Initializing cgroup subsys ns
[ 0.008269] Initializing cgroup subsys cpuacct
[ 0.008281] Initializing cgroup subsys memory
[ 0.008301] Initializing cgroup subsys devices
[ 0.008307] Initializing cgroup subsys freezer
[ 0.008312] Initializing cgroup subsys net_cls
[ 0.008378] CPU: Physical Processor ID: 0
[ 0.008383] CPU: Processor Core ID: 0
[ 0.008389] mce: CPU supports 5 MCE banks
[ 0.008401] CPU0: Thermal monitoring handled by SMI
[ 0.008409] using mwait in idle threads.
[ 0.008424] Performance Ev...

[Brian Murray (brian-murray)]

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 607617, 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. Please continue to report any other bugs you may find.