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

From: Brian Walker <walkerbm@charter.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trouble with DWA-552 and ath9k
Date: Mon, 28 Dec 2009 17:54:49 -0500	[thread overview]
Message-ID: <4B393739.9000601@charter.net> (raw)
In-Reply-To: <1262035725.3002.23.camel@mj>

Ok? I'd be glad to provide a trace, etc. if I were given instructions on 
what was desired and how to do so. As I stated when I started this 
chain, I get the following when trying to use hostapd:

nl80211: Failed to set channel (freq=2412): -22 (Invalid argument)

When trying to use the card in managed mode, it does indeed fail on the 
first "ifconfig wlan0 up" command with
"SIOCSIFFLAGS: Input/output error". The second time I issue the ifconfig 
command it succeeds. Running "iwlist wlan0 scan" still returns no 
results although other wireless devices pickup several access points 
from neighbors.

Be glad to do or provide anything that might get this card working.

Brian

On 12/28/2009 04:28 PM, Pavel Roskin wrote:
> On Mon, 2009-12-28 at 16:06 -0500, Brian Walker wrote:
>    
>> 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?
>>      
> There is a difference in the system ID (23 vs 29), which is more
> important.
>
>    
>>   Yours shows as AR5008 but mine shows as AR922X. Does anyone else
>> have the exact same card as I do and it is working?
>>      
> I think you have an issue with the calibration.  I've seen it with
> Ubiquity SR71A.  That's indeed AR922X, so it's not supported by MadWifi
> at all.  With ath9k, the interface cannot be brought up the first time
> (debugging should a calibration timeout).  It can be brought up the
> second time (that is, the driver doesn't report an error), but there are
> no scan results.
>
> That card fails in FreeBSD 8.0 exactly in the same way, as if the code
> was written from the same specification.  But it does work under Windows
> XP with the Ubiquity driver (I had to patch the inf file, as it was
> missing the subsystem ID for the card).
>
> We could trace the calibration done by the Ubiquiti XP drivers under
> ndiswrapper and compare it with the calibration done by ath9k to see the
> difference.
>
>    