Comment 66 for bug 42504

Sorry to the developers, but this problem seems to persist:

I'm experiences this problem with an atheros based card
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
        Subsystem: IBM Unknown device 057e
in a Thinkpad T43p. Dapper had no problems connecting to any kind of networks, but at some point through the edgy process (I was running edgy since mid July due to some problems with dapper) I was unable to connect to certain unencrypted networks.

Right now the situation is a bit weird. I can connect to any WEB/WPA encrypted WLAN, however, I can only rarely connect to an unencrypted network. The problem being here is, that the association with the access point fails, i.e. iwconfig shows simply
Access Point: not-associated

Weird is, that network-manager, kismet and so on show me the MAC-addresses of the APs, however, even trying to force the driver to associate with these, does not succeed.

Final comment, which might help: To my knowledge, I can only connect to unencrypted networks if the frequency of the AP is high (i.e. around 5 GHz), I think I have not connected to any unencrypted WLAN around 2.4 GHz.
iwconfig shows me IEEE 802.11a, but I don't recall if 5 GHZ belongs to a and 2.4 GHz to b and/or g... I necessary, I can look it up.

Any suggestions what might help? I tried going back to dapper's kernel, using wpasupplicant from curernt Debian unstable, going back to old wpasupplicant from dapper, but with any of these combinations I did not succeed in even getting connected to the network which works for edgy.

(sorry for the length)