Some updates. I tried it with a properly installed 7.10 tribe 5, still the same errors there, so reinstalled 7.04 to be able to safely use it as my desktop computer.
<copy/paste from my forum thread> I've made "some" progress. First off, I scrapped network-manager and knetworkmanager in favor of wicd, and I've never since looked back. Secondly, while I still only have one shot at connecting, but *now* I can reset it without having to restart the machine. Now, off the top of my head, the ritual to restore after it's broken down (with likely some irrelevant, unneeded and redundant steps): 1) Open wicd 2) Disconnect the network to be safe (with the button) 3) Close wicd 3) Do 'sudo modprobe -r ipw3945 && sudo modprobe ipw3945' in a terminal (mayhaps just one modprobe ipw3945 call does the trick, I'm not knowledgeable enough to know) 4) Open wicd again, hit refresh 5) At this point, it discovers my essids again 90% of the time, if not I return to step 2, rinse and repeat 6) Hit connect and pray. That'd be the discovery part. I've had shaky luck of being able to reconnect, with a success rate of ~20% or less. Sometimes, if I do it the DHCP way, it just freezes at Obtaining IP address. Other times, both with DHCP and with a static ip, it connects and reports a 0% signal. Further other times, it connects and reports a valid signal, but only one ping request goes through before the connection dies. (I usually run a 'ping 192.168.0.1' in another terminal so I know if I succeeded.) Wicd doesn't seem to want to connect successfully (or at least, not give the UI feedback that it is trying) if you haven't hit disconnect since your last attempt, and often if you haven't restarted the program itself. So a lot of opening/closing involved. Better than nothing, I guess. This way I can keep at it and eventually get it back in shape without the constant reboots. But it's still about as broken; what if the connection breaks down when I'm not there to give an effort to beat it back into shape? --- So there seems to be *something* awry, perhaps with the ipw3945 module, in the way it "releases" the interface, forcing me to reload the module to be able to once again discover essids and establish connections. Likely the iffy connecting is also a result of this? -- Intel PRO/Wireless 3945ABG can connect once, after that reboot is needed to reconnect https://bugs.launchpad.net/bugs/134515 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
