Hi, posted that to ath5k-users, having no hit on the logs makes me think the users list isn't really that active :-)
dmesg says it is an AR5213 phy0: Selected rate control algorithm 'simple' ath5k_pci 0000:02:02.0: Atheros AR5213 chip found: MAC 0x56, PHY: 0x41 ath5k_pci 0000:02:02.0: RF5111 5GHz radio found (0x17) ath5k_pci 0000:02:02.0: RF2111 2GHz radio found (0x23) however PCI ID is 168c:0013 (rev 01) which is an AR5212 accordig to the page on linuxwireless.org. Regards, Bernhard ---- Hi everyone, first of all, are user-side experiences already appreciated or is it too early in the development stage to be usable? I have for ages now had more or less annoying issues with my Thinkpad and an Atheros AR5213 chip running Ubuntu Linux and Madwifi(-ng). Both at home (AP is a Linksys WRT54G running all releases of OpenWRT between WhiteRussion 1.0RC4 and Kamikaze 7.09 with WPA-PSK) and university (mostly running Colubris CN320/CN330 with WPA/EAP-TTLS) I had frequent to annoyingly disturbing disconnects where it took a long time to reconnect (up to 60seconds), sometimes it wasn't even possible to reconnect. Although I'm anything but a kernel hacker (more an experienced end-user) I decided to give ath5k a try. I loaded the ath5k branch of the wireless-2.6 git tree - latest commit in my local tree is commit 286c21f7d6b7a0315d717bdaf5efc320bbd19df6 Author: Luis R. Rodriguez <[EMAIL PROTECTED]> Date: Thu Nov 1 23:11:31 2007 -0400 and compiled that beast. The base system is Kubuntu Gutsy (7.10) with wpa_supplicant version 0.6.0+0.5.8-0ubuntu1. So far I've only tried to connect to my home network and first failed (network was running WPA(1)-PSK). wpa_supplicant log shows it repeating the group handshake phase forever and then disconnecting. The full log is here http://users.birkenwald.de/~berni/temp/ath5k_wpa.log I then changed the OpenWRT to psk2 (WPA2-PSK) and finally got a connect. http://users.birkenwald.de/~berni/temp/ath5k_wpa2.log at a first glance both unicast and multicast/broadcast AP->client work, the other direction however doesn't. I can't see any packets from the wireless station on the LAN, neither broadcast/multicast (DHCP and IPv6 router solicitation/neighbor discovery) nor unicast after manually setting neighbor cache entries. Any advise how I could debug further? Or is this a known issue? Thanks however already, I obviously can't tell anything about working experience so far but the WPA handshake feels so much better than it used to be with Madwifi. Regards, Bernhard _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
