Comment 12 for bug 197819

Relevant output of lspci -vvnn :

03:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan
mini-PCI [14e4:4311] (rev 01)
        Subsystem: Hewlett-Packard Company Unknown device [103c:1363]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 23
        Region 0: Memory at b3200000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: b43-pci-bridge
        Kernel modules: ssb

On Fri, Mar 7, 2008 at 8:25 AM, Cory Flick <email address hidden> wrote:

> Manual removal of the firmware supplied by Hardy's fwcutter package, and
> then manual removal of Hardy's fwcutter package itself, followed by manual
> installation of the fwcutter package referenced on the site I have listed in
> my original post, followed by running that fwcutter package/program, DOES
> work.
>
> Again, not complaining or whining, just wondering if some of us with older
> Broadcom chips might have to go through these manual steps with anything
> beyond Gutsy, when Gutsy automated it all through its Restricted Drivers
> Manager. And of course, hoping the Ubuntu devs can include the proper
> fwcutter package for our troublesome Broadcom cards in Hardy, if possible.
>
>
>
> On Fri, Mar 7, 2008 at 3:49 AM, der_vegi <email address hidden> wrote:
>
> > And manually installing the firmware did not work either? Hm. What kind
> > of chip are you using? Looking at
> > http://linuxwireless.org/en/users/Drivers/b43/ shows, that not all
> > broadcom devices are supported. Could you please attach the output of
> > 'lspci -vvnn'?
> >
> > --
> > broadcom wireless not working fresh install of hardy
> > https://bugs.launchpad.net/bugs/197819
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in Source Package "b43-fwcutter" in Ubuntu: New
> > Status in Source Package "jockey" in Ubuntu: New
> >
> > Bug description:
> > flick@lil-spooky:~$ cat /etc/lsb-release
> > DISTRIB_ID=Ubuntu
> > DISTRIB_RELEASE=8.04
> > DISTRIB_CODENAME=hardy
> > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
> > flick@lil-spooky:~$ uname -a
> > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008
> > x86_64 GNU/Linux
> >
> > -------------------------------------------------------------------------------------------------
> > flick@lil-spooky:~$ apt-cache policy b43-fwcutter
> > b43-fwcutter:
> > Installed: 1:008-2
> > Candidate: 1:008-2
> > Version table:
> > *** 1:008-2 0
> > 500 http://us.archive.ubuntu.com hardy/universe Packages
> > 100 /var/lib/dpkg/status
> >
> > ----------------------------------------------------------------------------------------------------------------------------
> > what I expected to happen : after doing a fresh install of Hardy Alpha
> > 5, I started the Restricted Driver Manager to install the broadcom firmware
> > to get my wireless working, just like I did in Gutsy. I expected the
> > fwcutter package to download and install the correct firmware, which is what
> > happened under Gutsy. In Gutsy, the little orange light turned blue right
> > away ( my machine is an HP dv6000 series laptop ) indicating that wireless
> > is up and running.
> >
> > ------------------------------------------------------------------------------------------------------------------------------
> > what happened instead : started the Restricted Driver manager now called
> > "Hardware Drivers" under System-->Administration, clicked the checkbox for
> > the Broadcom firmware to be downloaded and installed. The Hardware Driver
> > manager told me it had downloaded and installed the firmware, however, the
> > orange light did not turn blue. I tried rebooting to see if that would make
> > a difference. It did not make a difference. No working wireless. This page :
> > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that
> > various kernel versions need not just different versions of the firmware,
> > but different versions of the fwcutter program/package itself, as well.
> > Would be great if that could be integrated into Hardy before final release.
> >
> > ----------------------------------------------------------------------------------------------------------------------------------
> >
>
>