Broadcom wireless driver can't be installed in Karmic Koala

Bug #404685 reported by Ismail Gjevori
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Karmic by Ismail Gjevori

Bug Description

My laptop use Broadcom wireless card. When i'm logged in with Live User Session (using a live CD) it shows me that i'm using proprietary hardware (and ask me if i want to install the wireless driver). If i install Ubuntu 9.10 to my laptop and log in with a normal user account i can't install the wireless driver. The "Restricted drivers" shows me that i am not using proprietary hardware. So i'm not able to be connected to the internet because my Ethernet card is broken.

Revision history for this message
Ismail Gjevori (isgjevori) wrote :

Now i'm using wireless network by installing these packages from the USB startup disk:
1- fakeroot
2-patch
3-dkms
4-bcmwl
But it will be more comfortable to install the driver from "Restricted drivers".

Philip Muškovac (yofel)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jonathan Jesse (jjesse) wrote :

@ ismail have you copied the .debs for those packages over to a usb drive and then install them? or how else do you install? for me it is not detecting my wireless card on my Dell Mini 9. tried this with today's daily

Revision history for this message
Ismail Gjevori (isgjevori) wrote :

no, the .deb files can be found in the cd of Ubuntu (or USB in my case). But these packages aren't installed by default so go to System-->Administration-->Software Source and in the Software for Ubuntu tab chose the option that the packages can be installed from CD-ROM with Ubuntu. Than Install the packages from Synaptic Package Manager.

Revision history for this message
SabreWolfy (sabrewolfy) wrote :

Same for me using Karmic Beta. Installed onto Acer Aspire 4710 laptop on two occasions. Restricted drivers shows that none are available. I installed the "b43-fwcutter" package from the repositories. On the first installation of the Beta though, I was offered the restricted drivers, but only at a later time (not immediately). On the second installation, I even tried restarting the machine, but I was still told there are no restricted drivers.

Philip Muškovac (yofel)
summary: - Broadcom wireless driver can't be installed in Karmic Koala alpha
+ Broadcom wireless driver can't be installed in Karmic Koala
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Ismail,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 404685

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Ismail Gjevori (isgjevori) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ismail 1603 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0340000 irq 22'
   Mixer name : 'Conexant CX20549 (Venice)'
   Components : 'HDA:14f15045,103c30a5,00100100'
   Controls : 18
   Simple ctrls : 8
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=6d61bc7e-4e6b-4ad1-80c7-963d527b26f9
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario C500 (RY510EA#ABZ)
NonfreeKernelModules: wl
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=UUID=c9e83583-4ecc-4ba5-b53b-ed756e722425 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/20/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.12
dmi.board.name: 30C6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.12:bd12/20/2006:svnHewlett-Packard:pnPresarioC500(RY510EA#ABZ):pvrF.12:rvnHewlett-Packard:rn30C6:rvr78.10:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario C500 (RY510EA#ABZ)
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ismail Gjevori (isgjevori) wrote : AlsaDevices.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : AplayDevices.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : BootDmesg.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : Card0.Amixer.values.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : CurrentDmesg.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : IwConfig.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : Lspci.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : PciMultimedia.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : ProcCpuinfo.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : ProcInterrupts.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : ProcModules.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : UdevDb.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : UdevLog.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : WifiSyslog.txt
Revision history for this message
Ismail Gjevori (isgjevori) wrote : XsessionErrors.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Brad Figg (brad-figg)
tags: added: acpi
tags: added: acpi-apic
tags: added: acpi-event
tags: added: bios
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: b73a1py79
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.