Nope, haven't solved it. I think I've patched the driver in 50 places
and it still goes up and down up and down in perfect cycles. Who needs
an atomic clock when you can just count the throughput cycles and know
exactly what time it is? :)
My current theory is that it's some sort of tx beamforming
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 ma
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 AR500
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
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
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]
Fla
