On 28/10/10 21:54, Gertjan van Wingerde wrote:
On 10/28/10 21:06, Lee wrote:
On 28/10/10 10:23, Helmut Schaa wrote:
Am Donnerstag 28 Oktober 2010 schrieb Lee:
On 26/10/10 07:40, Helmut Schaa wrote:
# tcpdump -i mon0 "ether src XX:XX:XX:XX:XX:XX"
Do you see any frames from your specific client?
Yes. I can see this:
# tcpdump -i mon0 "ether host 00:1F:3B:79:41:6F"
[...]
10:10:03.013402 5.5 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 14 Pad 20 KeyID 0
However, on wlan0 I don't see anything beyond the EAPOL packets.
Temporarily turning off WPA encryption let me successfully connect to my AP.
Aha, could you please try if loading rt73usb with nohwcrypt=1 helps?
Helmut
(argh, brown paper bag)
I went through the compiled kernels again, and I've screwed up at the last
commit while bisecting (Sorry, Helmut!). The first bad kernel is a commit
later:
# bad: [f1aa4c541e98afa8b770a75ccaa8504d0bff44a7] rt2x00: Write the BSSID to register when interface is added
On the good side, I tested 2.6.36 with nohwcrypt=1, and it works. Yay!
Hmm, the patch itself that seems to cause the badness doesn't look bad.
However, closer inspection shows that the intf->bssid field may be initialized incorrectly.
I may be a long shot, but can you check if the attached patch helps?
---
Gertjan.
I tried the patch. Old behaviour: nohwcrypt=0 doesn't work, nohwcrypt=1 does.
I'm compiling the kernel with the revert of 'bisect bad' right now.
-Lee
--
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
