installation failed of Broadcoam STA Wireless proprietary drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcmwl (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu natty (development branch)
Release: 11.04
I have just started testing Ubuntu natty and got a wireless driver installation problem.
I tried to install the Broadcom STA wireless driver using additional driver option.During installation I got "SYSTEM error :InstallArchive
I had expected the driver to get installed instead I got failure in doing so.
I had similar problem in " Ubuntu 10.04.1 LTS" but got it solved using this link --"https:/
I am unable to follow the same steps in natty bcoz of the fact that bcml-kernel-
I also got bcml-kernel-source package crash report and have uploaded.I think the problem is with both jockey and bcml-kernel-source packages.
I am attaching some screen shots of the problem I faced.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.6-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.37-11-generic i686
Architecture: i386
Date: Sat Jan 1 14:22:48 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101229)
MachineType: Dell Inc. Inspiron 1545
PackageArchitec
ProcEnviron:
SHELL=/bin/bash
LC_MESSAGES=
LANG=en_US.UTF-8
LANGUAGE=
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: jockey
dmi.bios.date: 10/23/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0U315R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
Changed in bcmwl (Ubuntu): | |
status: | New → Confirmed |
I have been experiencing the same issue (on up-to-date 64bit Natty). It seems that the error is due to the use of init_MUTEX in one of the sources files (make.log will contain the full details) when the function was not in scope (sorry I do not still have the exact messages). I managed to get it working by commenting out this line and rebuilding the module.