Hi,
On Wed, 16 Jan 2008, Larry Finger wrote:
> Please check that modules rfkill and rfkill-input are configured and loaded
> on your system. In your dmesg output, you are missing lines that look like
>
> Registered led device: b43-phy0:tx
> Registered led device: b43-phy0:rx
> Registered led device: b43-phy0:radio
I'll check this properly when I'm at the access point in question, though
when I plug in the card here (different location), rfkill was already
loaded (I have b43 in /etc/modules), rfkill-input loaded automatically and
I got straight on.
dmesg | grep " led "
produces no output whatsoever.
> Are you running the panel applet? On my KDE system, I can right click on
> that icon in the lower-right hand corner, and select from any of the AP's
> in my vicinity.
I'm using gnome, but I am using the gnome-network-manager panel applet,
yes. I also get a list of ESSIDs and pick from them. However, if NM has
knowledge of a network it has previously been on it seems to try and join
that one on its own initiative.
When the failure happens (eg if I login and let it jump automatically to
the AP in question), the NM applet swirls for a few seconds and then gives
up, dropping to the little red exclamation mark symbol saying it has no
network. If I then click to pick an ESSID, that ESSID is already selected,
but trying again produces the same brief swirl before it gives up.
Gavin
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
