It's absolutely not associated. It hunts around for the correct channel and does find the correct frequency, but it just doesn't go onward to stage 3 and finish the association, unless I time the ifdown/ifup just right.
There are no other clues in /var/log/syslog worth mentioning. It's the same stuff that's in the daemon.log. Thanks! Tom On 8/31/07, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Fri, Aug 31, 2007 at 10:39:10PM -0000, Tom Wood wrote: > > Same problem with gutsy tribe 5. > > > > I'll attach the relevant portion of the daemon.log that shows the entire > > process stalling after stage 2 (device configure) in NetworkManager. > > However, dhclient fires right after this and before stage 3 (IP > > configure start) even starts. Unless I'm mistaken, the interface is not > > up at this point, at least not the IP stack, but dhclient is still > > started. The ifdown/ifup trick works to bring the interface truly up, > > so stages 3-5 finish in short order thereafter. > > > > As always, I'll be glad to provide any more details you need. > > > > When you are at > > Aug 31 22:12:48 ubuntu NetworkManager: <info> Activation (ath0) Stage > 2 of 5 (Device Configure) complete. > Aug 31 22:12:50 ubuntu avahi-daemon[8042]: Registering new address > record for fe80::218:4dff:fe7a:59c0 on ath0.*. > > you should have about 10 seconds to capture output of iwconfig ath0 > > Can you do that please? Is it associated at that point? Do you see > more of relevance in /var/log/syslog at that point (or before/after)? > > - Alexander > > -- > NetworkManager fails to finish association to AP > https://bugs.launchpad.net/bugs/133966 > You received this bug notification because you are a direct subscriber > of the bug. > -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 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
