On Tue November 16 2010 18:30:02 Stefan Nickl wrote:
The ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) line is the
one that counts.
Ok. I did the same (only one ath5k AP, though...).
Can you check if WPA1 (TKIP) works or not?
Uh, then complain to your vendor ;-)
Maybe there is something in the EEPROM which disables encryption, too. There
is a flag for this: ATH_CRYPT_CAP_CIPHER_AESCCM. Can you check if it is
enabled in your case?
It is (lspci -vn)
00:0f.0 0200: 168c:001b (rev 01)
Subsystem: 168c:2062
Flags: bus master, medium devsel, latency 168, IRQ 5
Memory at a0020000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath5k
Kernel modules: ath5k
But I don't think it makes a big difference. The SREV (MAC: 0xa5) is used in
the ath5k code, not the PCI IDs.
bruno
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.orghttps://lists.ath5k.org/mailman/listinfo/ath5k-devel