This has come up a few times: http://mail.gnome.org/archives/networkmanager-list/2006-May/msg00095.html http://mail.gnome.org/archives/networkmanager-list/2006-May/msg00233.html
I think the consensus is that this is a bug in the BCM43xx driver since it is not properly reporting it's capabilities to NM. I wish I could point you towards a solid solution but I have not seen one mentioned yet. There does seem to be a bug filed on it though... On 6/9/06, Trochalakis Christos <[EMAIL PROTECTED]> wrote:
Hello there, I have the following problem with the nm-applet. Some time ago i disabled the option "Enable Wireless", from that moment i wasn't able to reenable it and networkmanager started to act weird, it recognizes my wifi adapter as a wired adapter: NetworkManager: <information> starting... NetworkManager: <information> eth1: Device is fully-supported using driver 'bcm43xx'. NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth1'. NetworkManager: <information> Deactivating device is there anything i can do to get it back working? thanks in advance, Chris ps: I m using fedora core 5 ppc and NetworkManager version 0.6.2 _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
_______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
