I recently installed Kubuntu, and that connects (using network manager) without difficulty. In light of this, I'd say it's the gnome network manager client that is causing the difficulty, and if you can deal with the jarring difference in UI, you can:
Install kde network manager client: apt-get install network-manager-kde then in the gnome 'sessions' config tool, disable the original network-manager, and add an entry for network manager (KDE Client). The command is 'knetworkmanager' or '/usr/bin/knetworkmanager' Log out, and log back in to give it a go. ..this might work for you until the ubuntu/gnome side catches up. I'm not sure, but I think that for whatever reason, the gnome client isn't recognizing when wpasupplicant has successfully connected, and is therefore not starting the dhcp client. I'm really not sure on the details, and this is a guess based on little knowledge of how network-manager actually works. Anywho, let's keep it all rolling and take over the world! :-) On Tuesday 03 April 2007 03:26:49 Przemysław Kulczycki wrote: > Network manager also failed to connect to my wifi on my laptop (HP > Compaq nx6325) with Broadcom BCM4310 using ndiswrapper driver. I could > only connect manually each restart thru wifi-radar. I uninstalled > network-manager because I was so mad at it. -- network-manager kills ndiswrapper networking https://bugs.launchpad.net/bugs/93183 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
