jockey not recognizing broadcom bcm4306 wifi requires fwcutter - ibook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have installed Ubuntu 9.10 on my iBook G4 and jockey did not recognized the wiki adapter as one that needs external firmware.
Here is the output of lspci
0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
After manually installing fwcutter everything was fine.
Durring the fwcutter install, it ask me if I want to autoamticaly download the firmware. I said yes and the install process was smooth without any further user intervention.
This is a regresion, as in the past I used Ubuntu 8.04 and the wifi adapter was recognized as needing proprietary drivers.
ProblemType: Bug
.var.log.
Architecture: powerpc
Date: Sun Nov 15 16:57:14 2009
DistroRelease: Ubuntu 9.10
Lsusb:
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
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: jockey-gtk 0.5.5-0ubuntu3
PackageArchitec
ProcCmdLine: root=/dev/hda4 ro quiet splash
ProcEnviron:
LANG=ro_RO.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: jockey
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-powerpc ppc
XsessionErrors:
(gnome-
(gnome-
(nautilus:1574): Eel-CRITICAL **: eel_preferences
(polkit-
(gnome-
Changed in jockey (Ubuntu): | |
assignee: | nobody → rudi (rudi-pitoyo) |
description: | updated |
summary: |
- broadcom wifi not recognized as requireing fwcutter - ibook + jockey does not recognize broadcom bcm4306 requires fwcutter - ibook |
summary: |
- jockey does not recognize broadcom bcm4306 requires fwcutter - ibook + jockey not recognizing broadcom bcm4306 wifi requires fwcutter - ibook |
Thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
I've tried recreating this bug with Precise and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.
Please feel free to report any other bugs you may find.