If that device is actually a 0cf3:3000 that was changed to 0cf3:3002 by firmware loading in the Windows driver, I think this problem is solved in Debian by using linux kernel 2.6.38 and firmware-atheros package (>=0.28).
However, if it's a 0cf3:3002 like the one in a Dell Vostro V130, the problem remains unsolved: https://bugzilla.kernel.org/show_bug.cgi?id=27402 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720949 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/714862
