unresponsive at broadcom firmware installation

Bug #135000 reported by Nanley Chery
48
Affects Status Importance Assigned to Milestone
Restricted Manager
Invalid
Undecided
Unassigned
restricted-manager (Ubuntu)
Fix Released
Medium
Matteo Z

Bug Description

Summary:
I'm running Ubuntu 7.10 (Tribe 5) on an Acer Aspire 3000 notebook. My wireless card is a bcm4318. bcm43xx firmware cannot be installed due to restricted drivers manager's unresponsiveness.

Details:
After installing Gutsy, I clicked on the restricted drivers manager and noticed that my broadcom 43xx firmware wasn't enabled. I clicked the broadcom firmware checkbox, a dialog box came up and I chose "Enable Firmware." A dialog box asking me whether I want to specify a file or a website for the firmware. When clicking browse (for the file), I get no response; when typing in the file's destination and clicking "OK," nothing happens. However, when I chose the url option and click ok, the file downloads. But, after it downloads, the dialog box closes and I'm just left with the Restricted Manager window.If I try to repeat this process again (2 or 3 times), the url option stops working and I must click the "X" button on the dialog box. After I click that button, Restricted Manager is still left and greyed out (only the close and x button works).
Oh, and sometime after installing and before enabling the firmware, a box came up saying i didn't have a needed repository enabled to install the firmware. So I enabled the universe and multiverse repositories.

Pictures:
Here's some pictures of what this looks like of what it looks like:
http://flickr.com/photos/52895259@N00/

Revision history for this message
Matteo Z (matteozandi) wrote :

I believe we have three issues:
- browse doesn't open a file picker (reproduced)
- message dialog "needed source not enabled" is probably hidden behind r-m main window
- fw_location is not updated with tmp location (reproduced, results in "Cannot open input file http://xeve.de/down/wl_apsta.o")

> nothing happens
If everything went well, bcm43xx should be in enabled status and in use. Still we could pop out a warning if enabling goes wrong.. and hopefully not place it behind any window :)

Matteo

Revision history for this message
Matteo Z (matteozandi) wrote :

one is enough

Changed in restricted-manager:
status: New → Confirmed
status: New → Invalid
Revision history for this message
Nanley Chery (nanoman) wrote :

If I understand correctly, for the second issue you listed, I should mention that the dialog box was not hidden for me. It popped up either after I clicked the broadcom checkbox or "Enable Firmware" for the first time.

Revision history for this message
junk123 (junk123-deactivatedaccount-deactivatedaccount) wrote :

I am also having the same problem on my Dell E1705 laptop using the BCM drive and trying to use the firmware cutter. I used ndiswrapper in Feisty but would be nice to see the integrated cutter working.

Revision history for this message
Matteo Z (matteozandi) wrote :

I see, so the dialog

"The software source for package
   bcm43xx-fwcutter
is not enabled."

actually helped and drove you to enable software repositories and there is nothing wrong about it, right?

Revision history for this message
zeddock (zeddock) wrote :

Same problem here on a fresh Tribe 5 install.

I want to mention that my 4309 worked out of the box before the Aug 3rd updates hit.
See: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/130511

Thanx!
zeddock

Revision history for this message
Nanley Chery (nanoman) wrote :

Yup, nothing wrong. I guess I shouldn't have mentioned it...

Revision history for this message
Matteo Z (matteozandi) wrote :

Nice, marking as 'fix in progress' since I already commited changes to my branch (waiting for Martin's review) and point 2 of my first comment is not an issue.

Changed in restricted-manager:
status: Confirmed → In Progress
Revision history for this message
zeddock (zeddock) wrote : Re: [Bug 135000] Re: unresponsive at broadcom firmware installation

If you are being sarcastic, again, I am sorry. Still learning the ways.

zeddock

On 8/29/07, Matteo Zandi <email address hidden> wrote:
>
> Nice, marking as 'fix in progress' since I already commited changes to
> my branch (waiting for Martin's review) and point 2 of my first comment
> is not an issue.
>
> ** Changed in: restricted-manager (Ubuntu)
> Status: Confirmed => In Progress
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Matteo Z (matteozandi)
Changed in restricted-manager:
assignee: nobody → matteozandi
importance: Undecided → Medium
Revision history for this message
David Cottrell (davidc-cfc) wrote :

I had the same experience with my Belkin PCMCIA card on Toshiba laptop. I did a fresh install of Gutsy Tribe 5, Restricted Drivers Manager found the Broadcom 43xx family. I ticked the enable option. Downloading of the wl_apsta.o started & finished. Then nothing happened. Closed & opened Restricted Drivers Manager and ticked the enable option again but it wanted to download the file again. The browse button did nothing (no dialog box) so I typed the downloaded location of wl_apsta.o again. Again nothing happened.

In the end I got it working with the same downloaded file (from the same source with wget) and sudo bcm43xx-fwcutter -w wl_apsta.o The lights came on after ejecting & inserting the card and started working in Network Manager straight away.

Revision history for this message
zeddock (zeddock) wrote :

Hard to remove my 4309 from this Dell Laptop, but I might try to getting
working anyway.
zeddock

On 8/31/07, David Cottrell <email address hidden> wrote:
>
> I had the same experience with my Belkin PCMCIA card on Toshiba laptop.
> I did a fresh install of Gutsy Tribe 5, Restricted Drivers Manager found
> the Broadcom 43xx family. I ticked the enable option. Downloading of
> the wl_apsta.o started & finished. Then nothing happened. Closed &
> opened Restricted Drivers Manager and ticked the enable option again but
> it wanted to download the file again. The browse button did nothing (no
> dialog box) so I typed the downloaded location of wl_apsta.o again.
> Again nothing happened.
>
> In the end I got it working with the same downloaded file (from the same
> source with wget) and sudo bcm43xx-fwcutter -w wl_apsta.o The lights
> came on after ejecting & inserting the card and started working in
> Network Manager straight away.
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
David Cottrell (davidc-cfc) wrote :

Hi zeddock. Sorry, my comments weren't specifically addressed to your postings. I was looking for somewhere to report my experience & rather than starting a new thread this seemed to be the best place.

I'd doubt that removing & re-connecting your wlan card will make much difference, but it might be worth taking the cover flap off & checking the connections. I only did it with my PCMCIA card to save a reboot.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi zeddock, before you extract the firmware unload the bcm43xx module, then extract the firmware to /lib/firmware/`uname -r`/, and then load the bcm43xx module, and should work just fine.

Revision history for this message
zeddock (zeddock) wrote :

OK. Will try that. And will skip the disconnec of the wlan via a reboot.

Nevertheless, I would like to see this issue addressed before Gusty goes
gold.

zeddock

On 9/2/07, Basilio Kublik <email address hidden> wrote:
>
> Hi zeddock, before you extract the firmware unload the bcm43xx module,
> then extract the firmware to /lib/firmware/`uname -r`/, and then load
> the bcm43xx module, and should work just fine.
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
zeddock (zeddock) wrote :

PS. I've always known I can get the silly thing to work. The desire is to
see a stable Ubuntu in Gusty, that handles these things like the OS it
should be. Only then will it be capable of replacing all of my users' MS
boxes. <grin>

zeddock

On 9/2/07, Basilio Kublik <email address hidden> wrote:
>
> Hi zeddock, before you extract the firmware unload the bcm43xx module,
> then extract the firmware to /lib/firmware/`uname -r`/, and then load
> the bcm43xx module, and should work just fine.
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
ubuntu4fun (k2osuchowski) wrote :

I have the same problem on my HP nx6110 notebook.

After installation of Ubuntu Gusty Gibbon Tribe 5 I used Restricted Drivers Manager for my wireless card (Broadcom 43xx). It asked me if I want to enable the restricted firmware. I agreed and downloaded the firmware from given server. But after downlaoding nothing has happened.

I don't even know where the downloaded firmware is in my system.

Restricted Drivers Manager is very useful application, but in fact it hasn't worked with Broadcom 43xx wireless chipsets so far.

Is there any chance to fix it?

Revision history for this message
Nanley Chery (nanoman) wrote :

You could have wireless working by following this:
http://ubuntuforums.org/showthread.php?p=1071920&mode=linear

Matteo Zandi recently added fixes to his branch of the Restricted Manager. Correct me if I'm wrong, but I think his changes will be added once the official maintainer, Martin Bohm, reviews his changes. Once this happens, the fixed r-m will be part of the next Gutsy Alpha, or Beta.

Revision history for this message
zeddock (zeddock) wrote :

Basilio,
Can you be so kind as to step me through? How do I:
Unload the bcm43xx module
Extract the firmware
Load the bcm43xx module

zeddock

On 9/2/07, Basilio Kublik <email address hidden> wrote:
>
> Hi zeddock, before you extract the firmware unload the bcm43xx module,
> then extract the firmware to /lib/firmware/`uname -r`/, and then load
> the bcm43xx module, and should work just fine.
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Basilio Kublik (sourcercito) wrote :

zeddock
do as follows:

user@machine:~$ cd /tmp
user@machine:/tmp$ sudo rmmod bcm43xx
user@machine:/tmp$ wget -c http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
user@machine:/tmp$ sudo bcm43xx-fwcutter -w /lib/firmware/`uname -r`/ wl_apsta-3.130.20.0.o
user@machine:/tmp$ modprobe bcm43xx

Revision history for this message
Arthur Smith (arthurmsmith) wrote :

That very last command ("modprobe bcm43xx") fails on my pc with "FATAL: Error inserting bcm43xx (/lib/modules/2.6.22-10-generic/kernel/drivers/net/wireless/bcm43xx/bcm43xx.ko): Operation not permitted"

Revision history for this message
Matteo Z (matteozandi) wrote :

Nanley Chery: you are right, except that the maintainer is Martin Pitt.

@all:

please don't use launchpad as a support tool, follow links to forums/wiki to get support.

Still if you want to try my fix, do:

$ sudo apt-get install bzr
$ cd ~
$ bzr get http://bazaar.launchpad.net/~matteozandi/restricted-manager/mzandi2 restricted-manager
$ cd restricted-manager
$ gksudo ./restricted-manager

or wait for r-m next update.

Revision history for this message
zeddock (zeddock) wrote :

Since it began here and others will read here... I want to correct the simple instructions to deal with this problem.

Basilio was kind enough to post this:
user@machine:~$ cd /tmp
user@machine:/tmp$ sudo rmmod bcm43xx
user@machine:/tmp$ wget -c http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
user@machine:/tmp$ sudo bcm43xx-fwcutter -w /lib/firmware/`uname -r`/ wl_apsta-3.130.20.0.o
user@machine:/tmp$ sudo modprobe bcm43xx

I added a sudo to the last line.

No reboot needed. Go check your icon and find that wireless networks now show up.
I am using a Dell Latitude D800 with a bcm4309 in it.

Thanx Basilio. Hopefully this little piece of info will help others to squash this BUG.

zeddock

Revision history for this message
zeddock (zeddock) wrote :

An update...
Even though I thought it was working, because I could "see" wireless networks listed in network manager, I had to do a few things before it seemed to fully work for me.
1. sudo gedit /etc/network/interfaces
2. sudo gedit /etc/udev/rules.d/70-persistent-net.rules

These 2 commands had to be used to change the wireless from eth1 to wlan0. I am unsure if both changes must be done or not. But once I did this and rebooted, all is seeming to work correctly.

zeddock

Revision history for this message
CeesSluis (testcees) wrote :

The instructions from zeddock and Basilio fixed my broadcom bcm4306 in a new Ubuntu Gusty Gibbon Tribe 5 installation on HP zx5022ea notebook too.

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks, Matteo. Merged.

Changed in restricted-manager:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

restricted-manager (0.31) gutsy; urgency=low

  [ Martin Pitt ]
  * RestrictedManager/{RestrictedManagerGtk.py,manager.glade}: Show the
    rationale for a driver as a tooltip. (LP: #134019)
  * RestrictedManager/core.py: Add DefaultHandler.is_hw_available(): This can
    be implemented if a handler has an additional way of detecting the
    presence of hardware and modalias matching is not sufficient. Add proper
    support for it to connected_hardware().
  * Add RestrictedManager/handlers/sl_modem.py: Handler for software modems
    supported by sl-modem-daemon. (LP: #125015)
  * Replaced icons by the excellently looking ones from Lapo Calamandrei.
    These are now GPLed and available as SVG (whereas the previous ones were
    CC-BY-SA, stolen from another project, and only available as bitmap).
    (LP: #140557)

  [ Matteo Zandi ]
  * RestrictedManager/RestrictedManagerGtk.py: Fix function name for firmware
    check. (LP: #130789)
  * RestrictedManager/RestrictedManagerGtk.py: Make "Browse" button of
    firmware dialog work instead of causing the app to hang. (LP: #135000)

 -- Martin Pitt <email address hidden> Tue, 18 Sep 2007 13:24:02 +0200

Changed in restricted-manager:
status: Fix Committed → Fix Released
Revision history for this message
zeddock (zeddock) wrote :

I have not done this update of R-M yet, bt even though I have wireless
working through the above process, it does seem like a low thoughput speed.

zeddock

On 9/18/07, Martin Pitt <email address hidden> wrote:
>
> restricted-manager (0.31) gutsy; urgency=low
>
> [ Martin Pitt ]
> * RestrictedManager/{RestrictedManagerGtk.py,manager.glade}: Show the
> rationale for a driver as a tooltip. (LP: #134019)
> * RestrictedManager/core.py: Add DefaultHandler.is_hw_available(): This
> can
> be implemented if a handler has an additional way of detecting the
> presence of hardware and modalias matching is not sufficient. Add
> proper
> support for it to connected_hardware().
> * Add RestrictedManager/handlers/sl_modem.py: Handler for software
> modems
> supported by sl-modem-daemon. (LP: #125015)
> * Replaced icons by the excellently looking ones from Lapo Calamandrei.
> These are now GPLed and available as SVG (whereas the previous ones
> were
> CC-BY-SA, stolen from another project, and only available as bitmap).
> (LP: #140557)
>
> [ Matteo Zandi ]
> * RestrictedManager/RestrictedManagerGtk.py: Fix function name for
> firmware
> check. (LP: #130789)
> * RestrictedManager/RestrictedManagerGtk.py: Make "Browse" button of
> firmware dialog work instead of causing the app to hang. (LP: #135000)
>
> -- Martin Pitt <email address hidden> Tue, 18 Sep 2007 13:24:02
> +0200
>
> ** Changed in: restricted-manager (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
zeddock (zeddock) wrote :

I am happy to report that upon a new CD install, with format... from the Sept 22 Nightly ISO, The Restricted Drivers Manager moves through the process of installing the 43xx firmware driver from the internet much more smoothly.

However, on my 4309 this command:
sudo gedit /etc/udev/rules.d/70-persistent-net.rules

shows that the wireless is set to eth1, not wlan0. I am not sure this SHOULD be wlan0, but I can tell you that the wireless is not working out of the box.

I am still playing with ways to get it working.

zeddock

Revision history for this message
zeddock (zeddock) wrote :

It is possible that this bug should be closed as the Restricted Manager may be completing its work correctly and some other package is responsible for correctly configuring 70-persistent-net.rules for wlan and other configurations.

zeddock

Revision history for this message
Nanley Chery (nanoman) wrote :

Did you post your comment in the wrong package?

On 9/23/07, zeddock <email address hidden> wrote:
>
> It is possible that this bug should be closed as the Restricted Manager
> may be completing its work correctly and some other package is
> responsible for correctly configuring 70-persistent-net.rules for wlan
> and other configurations.
>
> zeddock
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
zeddock (zeddock) wrote :

I actually posted that in 2 different bugs.
My latest CD-formatted Install, with updates, has the 4309 in my Dell D800
working.

I just had turned off the wireless via a key combination and didn't want
anyone else to make same mistake.

zeddock

On 9/23/07, Nanley Chery <email address hidden> wrote:
>
> Did you post your comment in the wrong package?
>
> On 9/23/07, zeddock <email address hidden> wrote:
> >
> > It is possible that this bug should be closed as the Restricted Manager
> > may be completing its work correctly and some other package is
> > responsible for correctly configuring 70-persistent-net.rules for wlan
> > and other configurations.
> >
> > zeddock
> >
> > --
> > unresponsive at broadcom firmware installation
> > https://bugs.launchpad.net/bugs/135000
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> unresponsive at broadcom firmware installation
> https://bugs.launchpad.net/bugs/135000
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Joe Baker (joebaker) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes! The restricted driver installation for my wifi bcm_43xx card
works now using the Restricted drivers manager (had to install
ubuntu-restricted-extras first manually).

I downloaded the daily ISO image of 9/25/2007 of edubuntu i386 desktop
live cd.
Performed the install of the OS.
Then I tried the restricted driver for the wifi card which was
properly identified.
An error indicated something to the effect that I didn't have
restricted support enabled.

I installed the ubuntu-restricted-extras package which then allowed me
to successfully use the Restricted Driver Manager successfully.

It would be good if the Restricted Driver Manager could make this
suggestion or start the process of downloading this tool.

- -Joe Baker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG+/Yf7J1dPd3sAmARAgaNAJ4zos7NQfEFSzF5bqK7g789YEgosgCfdQsM
laWNwYwtgL/NkknOiwdHwMg=
=89v7
-----END PGP SIGNATURE-----

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.