Ubuntu
restricted-manager package

BCM43XX Doesn't associate after restricted-manager installs its driver

Bug #138362 reported by Jamie Jackson
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Invalid
Medium
Unassigned
restricted-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: restricted-manager

Dell D620; Gutsy Tribe 5; Dell 1390 Wireless (=BCM4311); x86

I'm Live Booting Gutsy Tribe 5. It detected my BCM4311 in the restricted drivers manager. I installed what it wanted me to ("Firmware for Broadcom 43xx Chipset Family").

Using NetworkManager, I can see my AP, but can't associate. I was able to connect with Fiesty via fwcutter and ndiswrapper (respectively).

Attached is output from:
"sudo tail -f /var/log/syslog | grep NetworkManager > syslog.txt:
...it shows before, during, and after I try to associate.

I'm seeing a lot of
Sep 9 03:34:27 ubuntu NetworkManager: <info> Activation (eth1): waiting for device to cancel activation.
Sep 9 03:34:27 ubuntu NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported

...which seems like a problem, but don't know how to interpret.

Apologies if this bug report is misguide or misplaced, as maybe it belongs upstream? I don't know, I'm just hoping to get it fixed for the Gutsy release, since this device causes so many headaches when it has to be configured manually.

Note to self: I used latest bzr version of restricted-manager as suggested by Matteo in https://bugs.launchpad.net/restricted-manager/+bug/135000

Revision history for this message
Jamie Jackson (jamiejackson) wrote :

One more thing: This is not a support request (I could set it up with ndiswrapper, if I wanted), I'd just like to see this device work out of the box in Gutsy.

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

Marking as invalid since r-m only takes care of cutting firmware

BTW I'm glad my fix on r-m works, thanks for reporting.

Changed in restricted-manager:
status: New → Incomplete
Revision history for this message
Matteo Z (matteozandi) wrote :

filed against linux-source-2.6.22 since bcm43xx is a kernel module, should be forwarded upstream I guess

Matteo Z (matteozandi)
Changed in restricted-manager:
status: Incomplete → Invalid
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Jamie, thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out,
we were wondering if you can still reproduce this issue? Could you please download and try the new version of Ubuntu from
http://www.ubuntu.com/getubuntu/download and report back your results? I'm not 100% positive if this is a bug with the driver or with Network Manager. But please get back to us regarding the new release and we'll go from there. Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jamie Jackson (jamiejackson) wrote : Re: [Bug 138362] Re: BCM43XX Doesn't associate after restricted-manager installs its driver

I let my Feisty upgrade to Gutsy after the release, and it *did* seem
to work afterwards. Thanks for checking.

Jamie

On 10/27/07, Leann Ogasawara <email address hidden> wrote:
> Jamie, thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out,
> we were wondering if you can still reproduce this issue? Could you please download and try the new version of Ubuntu from
> http://www.ubuntu.com/getubuntu/download and report back your results? I'm not 100% positive if this is a bug with the driver or with Network Manager. But please get back to us regarding the new release and we'll go from there. Thanks again and we appreciate your help and feedback.
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
> --
> BCM43XX Doesn't associate after restricted-manager installs its driver
> https://bugs.launchpad.net/bugs/138362
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Jamie,

Thanks for your reponse. This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at [WWW] https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.