I am using feisty and have been experiencing the same bug since some month ago (may be an upgrade). I can't even associate using iwconfig, however I found the following workaround: when I use iwconfig to associate to the AP, I also specify the channel as follows
iwconfig eth1 ESSID <MY_ESSID> mode Managed channel <MY_CHANNEL> Channels can be listed by issuing the command "iwlist scan". This suffices to associate to the AP, and makes the subsequent "dhclient eth1" work and obtain an address. -- Wireless (ipw3945) doesn't work after suspend/hibernation https://bugs.launchpad.net/bugs/114490 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
