Public bug reported:
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
** Affects: restricted-manager (Ubuntu)
Importance: Undecided
Status: New
--
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 member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
