[ath9k-devel] trouble with DWA-552 and ath9k

[Brian Walker <walkerbm@charter.net>]

My DWA-552 is in a P3 1ghz (very old) system with an AX63pro 
motherboard. I think the difference in subsystem id is perhaps the 
issue? Yours shows as AR5008 but mine shows as AR922X. Does anyone else 
have the exact same card as I do and it is working?

Brian

On 12/28/2009 03:49 PM, Pavel Roskin wrote:
> On Mon, 2009-12-28 at 14:22 -0500, Brian Walker wrote:
>    
>> Can anyone else confirm that this card works (or definitely does not
>> work) with the current (2009-12-11) ath9k driver?
>>
>> 00:0a.0 Network controller [0280]: Atheros Communications Inc. AR922X
>> Wireless Network Adapter [168c:0029] (rev 01)
>>       Subsystem: D-Link System Inc Device [1186:3a7a]
>>       Flags: 66MHz, medium devsel, IRQ 5
>>       [virtual] Memory at f8040000 (32-bit, non-prefetchable) [size=64K]
>>       Capabilities: [44] Power Management version 2
>>       Kernel driver in use: ath9k
>>       Kernel modules: ath9k
>>      
> I can definitely confirm that DWA-552 is working for me.  It didn't work
> on newer systems with Intel Quad Core CPU and Intel G35 chipset for
> reasons unrelated to ath9k.  Either it's not seen by lspci, or the PCI
> ID is corrupt.
>
> However, DWA-552 is working with ath9k on older systems, such as an AMD
> XP 2000 system with Asus V7B8X motherboard or PowerMac G3.  The access
> points are seen in the scan results and WPA connection is established
> quickly and reliably.
>
> The system and subsystem IDs is different, but the card is marked as
> D-Link DWA-552.
>
> 01:03.0 Network controller [0280]: Atheros Communications Inc. AR5008
> Wireless Network Adapter [168c:0023] (rev 01)
>          Subsystem: D-Link System Inc Device [1186:3a6d]
>          Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 24
>          Memory at 80890000 (32-bit, non-prefetchable) [size=64K]
>          Capabilities: [40] #80 [0000]
>          Kernel driver in use: ath9k
>          Kernel modules: ath9k
>
> wlan0     IEEE 802.11bgn  Mode:Managed  Frequency:2.437 GHz
>            Access Point: Not-Associated   Tx-Power=27 dBm
>            Retry  long limit:7   RTS thr:off   Fragment thr:off
>            Encryption key:off
>            Power Management:on
>
> # wpa_supplicant -c /etc/wpa_supplicant/mike1.conf -D wext -i wlan0
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
> Trying to associate with 00:19:5b:56:fc:73 (SSID='mike1' freq=2437 MHz)
> Associated with 00:19:5b:56:fc:73
> WPA: Key negotiation completed with 00:19:5b:56:fc:73 [PTK=TKIP
> GTK=TKIP]
> CTRL-EVENT-CONNECTED - Connection to 00:19:5b:56:fc:73 completed (auth)
> [id=0 id_str=]
>
>