bcm43xx not showing

[KillerKiwi]

I used to bcm43xx to install the wireless firmware worked perfectly but dosnt show in restricted drivers as I would expect?

Means I have to know about bcm43xx :)

[Martin Pitt (pitti)]

Simply because the driver is free, no need to configure it manually. The firmware needs to be installed manually anyway, since we cannot distribute it (and it is not a kernel module either).

[KillerKiwi (killerkiwi2005)]

The firmware (which is not "free") was installed automaticlly..... by the bcm43xx cutter package.

This is probably not the right place but should not drivers requiring non free firmware also be listed in restricted drivers?

[Martin Pitt (pitti)]

We could add some nasty hack to make it appear as restricted driver, but even then, it wouldn't make sense to disable the bcm43xx driver.

[KillerKiwi (killerkiwi2005)]

I don't think it needs to be disabled just visible in restricted drivers when installed... ie restricted drivers is like "the wall of shame", the hardware needs some software/binary/firmware to run properly and this is obviously not as we want it to be.

Also I think many people will start to think that if a driver/firmware combination is not in restricted drivers than it must be all "free".

Restricted driver could be a great an educational tool.

[Martin Pitt (pitti)]

Alright, let's reopen this again and think about it. Looking at /lib/firmware and checking the package contents of the kernel tells us which bits are definitively free, but we cannot know which additional files there are free and which are not. Any idea?

[KillerKiwi (killerkiwi2005)]

Here's a list from debian of drivers that require firmware and there
status....
http://doolittle.icarus.com/~larry/fwinventory/2.6.17.html October 2006

On 4/16/07, Martin Pitt <email address hidden> wrote:
>
> Alright, let's reopen this again and think about it. Looking at
> /lib/firmware and checking the package contents of the kernel tells us
> which bits are definitively free, but we cannot know which additional
> files there are free and which are not. Any idea?
>
> ** Changed in: restricted-manager (upstream)
> Importance: Undecided => Wishlist
> Status: Rejected => Needs Info
>
> --
> bcm43xx not showing
> https://bugs.launchpad.net/bugs/103200
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Martin Pitt (pitti)]

restricted-manager (0.21) gutsy; urgency=low

  * Merged Matteo Zandi's branch for supporting firmware modules, with an
    implementation for bcm43xx. Thanks a lot for this great contribution! I
    i18n'ed all those changes, dropped a few irrelevant ones (such as
    renaming is_handler to is_special), and fixed some errors in the
    DriverHandler/FWHandler split.
  * RestrictedManager/bcm43xx.py:
    - enable(): Wait for bcm43xx-fwcutter to finish.
    - is_enabled(): Test for any bcm43xx_* firmware file, not just for
      bcm43xx_microcode11.fw (since that does not exist with every firmware
      version). Also, do not require bcm43xx-fwcutter to be installed, since
      the user might have unpacked it manually.
    - disable(): Simplify code using glob().
  * RestrictedManager/core.py, install_package(): Set debconf priority to
    critical to avoid debconf questions (in particular the one from
    bcm43xx-fwcutter).
  * RestrictedManager/bcm43xx.py: Some string simplification.
  * po/POTFILES.in: Add bcm43xx.py.
  * po/de.po: Update to complete translation again.
  * restricted-manager: Update the title text, and change it dynamically
    depending on whether any driver is enabled.
  * Drop RestrictedManager/xorgconfig.py and its mentioning in
    debian/copyright. Add a dependency to guidance-backends, which is now the
    official source for that file.

 -- Martin Pitt <email address hidden> Tue, 19 Jun 2007 19:00:42 +0200

[KillerKiwi (killerkiwi2005)]

Legendary :)

On 6/20/07, Martin Pitt <email address hidden> wrote:
>
> restricted-manager (0.21) gutsy; urgency=low
>
> * Merged Matteo Zandi's branch for supporting firmware modules, with an
> implementation for bcm43xx. Thanks a lot for this great contribution!
> I
> i18n'ed all those changes, dropped a few irrelevant ones (such as
> renaming is_handler to is_special), and fixed some errors in the
> DriverHandler/FWHandler split.
> * RestrictedManager/bcm43xx.py:
> - enable(): Wait for bcm43xx-fwcutter to finish.
> - is_enabled(): Test for any bcm43xx_* firmware file, not just for
> bcm43xx_microcode11.fw (since that does not exist with every
> firmware
> version). Also, do not require bcm43xx-fwcutter to be installed,
> since
> the user might have unpacked it manually.
> - disable(): Simplify code using glob().
> * RestrictedManager/core.py, install_package(): Set debconf priority to
> critical to avoid debconf questions (in particular the one from
> bcm43xx-fwcutter).
> * RestrictedManager/bcm43xx.py: Some string simplification.
> * po/POTFILES.in: Add bcm43xx.py.
> * po/de.po: Update to complete translation again.
> * restricted-manager: Update the title text, and change it dynamically
> depending on whether any driver is enabled.
> * Drop RestrictedManager/xorgconfig.py and its mentioning in
> debian/copyright. Add a dependency to guidance-backends, which is now
> the
> official source for that file.
>
> -- Martin Pitt <email address hidden> Tue, 19 Jun 2007 19:00:42
> +0200
>
>
> ** Changed in: restricted-manager (upstream)
> Status: Needs Info => Fix Released
>
> --
> bcm43xx not showing
> https://bugs.launchpad.net/bugs/103200
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[zeddock (zeddock)]

The firmware update shows in the Restricted Drivers Manager for me, but to get the firmware by pre-populated URL, the download finishes but it is unclear where it went or if that concludes with success. If you choose local the Browse button gives no file-picker and typing it in also gives no indication of success/failure.

zeddock

[zeddock (zeddock)]

It now shows in RDM, but the selection of it in RDM fails without indicating. Also, the local "Browse" button does not give a file-picker.
zeddock

[zeddock (zeddock)]

Wish list?

[Matteo Z (matteozandi)]

zeddock: please refer to

https://bugs.launchpad.net/ubuntu/+source/restricted-manager/+bug/135000

as it seems to be exactly your problem (as you also confirmed).

This particular bug was about bcm43xx not present in r-m (irst reported on 2007-04-05).

[MohamadReza Mirdamadi (mohi)]

It appears for me in restricted driver manager after installing via adept in Kubuntu. but not before installing this package!

I think it should be showed in Driver Manager. :)

[MohamadReza Mirdamadi (mohi)]

sorry.. I installed "b43-fwcutter" in that case and it worked perfect!