My Asus 1000HA netbook came with a pretty good Atheros internal wireless adaptor, but it isn't capturing well enough the local wi-fi signals I'm piggy-backing onto. A few years ago I bought an external USB wireless adaptor (TP-LINK TL-WN422G), which I've used when needed while running WindowsXP on the hard drive. Now I'd like to use it with my pendrive CorePlus-5.1 installation, and I need your help to set it up.
Factoid: The driver for TP-LINK in WindowsXP is Atheros athuw.sys. Whether this driver came from the Windows driver store or was generic, I no longer remember. No CD came with the device.
I'll describe what I've done and what happened, and I'll give you all the information I was able to gather (be it related or not, as the case may be).
I disabled the internal wireless adaptor while in Windows XP, shut down, booted Core, and plugged the TP-LINK into a USB port.
The LED on the TP-LINK didn't go on.
I ran the TCL Wifi app and got the following message:
Found wifi device wlan0
Standby for scan of available networks...
wlano Interface doesn't support scanning: Network is down
Set to try a few times to obtain a lease.
Failed to connect.
In the terminal, I ran iw, ifconfig, and iwconfig and got the folowing results:
tc@box:~$ iw dev
tc@box:~$ iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
tc@box:~$ ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:25:86:E4:07:53
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
In Control Panel>System Stats>dmesg, I found the following entries near the bottom:
usb 1-2: new high-speed USB device number 6 using ehci-pci
usb 1-2: ath9k_htc: Firmware htc_9271.fw requested
usb 1-2: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-2:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-2:1.0: ath9k_htc: FW Version: 1.3
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
ieee80211 phy1: Atheros AR9271 Rev:1
(Like I said, I have no idea if these dmesg stats, or indeed any of the above data, are related to the TP-LINK, they just look like they might be)
There was no entry for wlan0 in Control Panel>System Stats>net.
I don't know what other data to collect.
If you can help me get this TP-LINK wireless adaptor up and running, I will appreciate it a lot.