From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Mon, 28 Dec 2009 16:28:45 -0500 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <4B391DCB.6010500@charter.net> References: <4B2A5FA8.8060905@charter.net> <19242.62265.487757.695747@gargle.gargle.HOWL> <4B2AFC5D.1060001@charter.net> <19243.2224.974537.876295@gargle.gargle.HOWL> <4B39058A.6080108@charter.net> <1262033354.3002.11.camel@mj> <4B391DCB.6010500@charter.net> Message-ID: <1262035725.3002.23.camel@mj> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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. -- Regards, Pavel Roskin