On 5/23/07, dragoran <drago01@xxxxxxxxx> wrote:
Jeff Spaleta wrote: > On 5/22/07, John Poelstra <poelstra@xxxxxxxxxx> wrote: >> * iwl3945 wireless >> * linville committed some fixes for it and is looking at it more >> today >> * doesn't blowup machines any more, but needs more testing >> * jeremy plans to look into it a little more > > Is there anything specific i could be testing I could be doing and > reporting back on? > just use your card ;) connect/disconnect to networks download data / upload data scan for networks etc. if you notice any oops or other bugs, report them...
Still fails on first attempt a re-associating, same as before..... Here is the beginning of the borkage. I'm actually connected to AP 00:14:6a:5b:3a:80 (WAP) when this happens. There are 2 APs for the same network; perhaps the driver is dueling with both of them? [There is also another WEP network present.] May 23 12:37:46 localhost kernel: wlan0: authenticate with AP 00:14:69:3b:af:60 May 23 12:37:46 localhost kernel: wlan0: Initial auth_alg=0 May 23 12:37:46 localhost kernel: wlan0: authenticate with AP 00:14:6a:5b:3a:80 May 23 12:37:46 localhost kernel: wlan0: RX authentication from 00:14:6a:5b:3a:80 (alg=0 transaction=2 status=0) May 23 12:37:46 localhost kernel: wlan0: authenticated May 23 12:37:46 localhost kernel: wlan0: associate with AP 00:14:6a:5b:3a:80 May 23 12:37:46 localhost kernel: wlan0: RX deauthentication from 00:14:6a:5b:3a:80 (reason=2) May 23 12:37:46 localhost kernel: wlan0: deauthenticated May 23 12:37:46 localhost kernel: wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=00:14:6a:5b:3a:80 A3=00:16:41:e2:48:c7) May 23 12:37:46 localhost kernel: wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=00:14:6a:5b:3a:80 A3=00:12:da:c3:84:c9) Believe this is the same I've BZ'ed before..... tom -- Tom London -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
