For whatever it's worth :

I tried a different approach. I did a clean install of Gutsy, got wireless
working that way,  then upgraded to Hardy using update-manager -d.

Upon reboot, wireless does not work. Tried using "Hardware Drivers" under
System-->Administration, it offered to download the fwcutter package, I
accepted, and still no working wireless. Rebooted, still no working
wireless.


This is all 64bit, on an HP dv6000 laptop.




On Mon, Mar 3, 2008 at 9:04 PM, Cory Flick <email address hidden> wrote:

> Restricted Manager pops up the "has to install firmware" notice again. I
> click ok, it installs/runs fwcutter again, which again does not result in
> working wireless. On the web page I referenced in my original bug report,
> there's talk of different kernels requiring different fwcutter versions as
> well as different firmware versions. For what it's worth, I realize this
> issue is caused by Broadcom not opening up their drivers, and I'm willing to
> dig around and manually tweak things to get wireless up and running. Just
> posted the bug because Gutsy automated all this perfectly, which was
> fantastic.
>
>
>
> On Mon, Mar 3, 2008 at 4:51 PM, der_vegi <email address hidden> wrote:
>
> > So it seems to be a problem of b43-fwcutter's install routine or the
> > restricted-driver-manager jockey? Cory Flick, what happens, if you try
> > to uninstall b43-fwcutter and then try enabling your wireless card over
> > the restricted manager again?
> >
> >
> > ** Also affects: jockey (Ubuntu)
> >    Importance: Undecided
> >       Status: New
> >
> > --
> > 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.
> >
> > ----------------------------------------------------------------------------------------------------------------------------------
> >
>
>