We still don't know what kernel you're running. We do know that 2.6.37 did not include support for your wireless chipset. ath9k support specifically for AR9485 was added beginning with 2.6.39.
So if you're running the default kernel 2.6.37 from your 13.37 install, there are at least a couple of approaches to take. You can go to kernel.org, download source for one of the 2.6.39 series kernels, use an appropriate kernel .config file from Slackware 13.37 (for example the one for huge.smp ftp://ftp.slackware.com/pub/slackwar...els/hugesmp.s/
) and compile and install a kernel which is as close as possible to the one that you currently run that supports your chipset.
Or you can download and install (not upgrade) the Slackware-current packages for kernel 3.2.28 and kernel-modules. The only potential downside for this is the ath9k driver seems to operate very erratically in a lot of 3.x.x kernels. For me and my particular chipset, the ath9k in 3.2.27 would drop connections every 30 seconds or so, and I reverted to the more stable version in 2.6.37.
But if you're already running a kernel and ath9k version known to support your AR9485 chipset, you still haven't answered Alien Bob's question, which was: from a root console, what output does the command iwconfig give you? Does it recognize wireless extensions on any device node? The ath9k driver does not need to have put your card on wlan0; it could just as easily have put it on eth1 or elsewhere. If ath9k put the card on a different node than wlan0, that's the node you work with in your configuration, not wlan0.