Howard Chu wrote: > Dan Williams wrote: >> On Fri, 2009-05-15 at 21:42 +0100, Dave wrote: >>> Before enabling wpa_supplicant, can you try scan for your AP (as root): >>> >>> iwlist ethX scan essid YYYYY > > That works fine. In fact, just "iwlist scan" returns the same result - only > the info for my AP is returned. (There are at least 6 APs visible from an > another laptop sitting nearby.) The fact we can parse the scan result from your AP is good. It indicates the AP doesn't transmit a large list of IEs which trip the card up. The fact we can't see the other APs... I'll assume that's your dodgy antenna :) >>> I'm interested in what it returns, and whether dmesg reports 'Ext scan >>> results too large' or something similar. > > No, it just continues with the stream of "frame lost" messages: > > eth2: Information frame lost. (10 times, followed by 1 > __ratelimit: 2 callbacks suppressed (then 10 more frame lost messages, and so on) I had thought you didn't get the frame lost messages until you tried to authenticate. If you always receive them, then it might just be due to an AP you're not interested in (and you might be able to ignore these warnings). A few questions: 1. How far is wpa_supplicant getting in authentication? Use -dd 2. If it authenticates, did you check whether you could dhcp on eth2? It would also be nice to identify the source of your frame lost messages. Any chance you could have a look at the wireless traffic with another card in monitor mode? Regards, Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
