Numerous USB cordless tools?

I have a broadcom cordless card in my laptop computer and also regarding I recognize, it works as an USB tool. I additionally have one USB stick cordless tool (TL-WN422G - makes use of ath9k_htc vehicle driver) which I intend to make use of at the very same time as the first (Broadcom) tool.

The trouble is, after I load ath9k_htc - iwconfig does disappoint the new USB tool (the TL-WN422G - wlan1/ ath0/ whatever), yet just the old one (wlan0 - Broadcom, examined by MAC).

I attempted this USB tool (TL-WN422G) on my various other computer system that has PCI cordless card in it, and also they both functioned simply great with each other after I pluged it in ... I get wlan0 (Ralink) and also wlan1 (TL-WN422G). Is it some sort of a trouble for the laptop computer that both tools are identified as USB? Just how do I make wlan1 show up on my laptop computer?

additionally, my system is totally approximately day 2.6.35 kernel (Arch)

modify: I've currently downloaded and install the required ar9271.fw from linuxwireless.org and also I place it right into/ lib/firmware - glitch because?

dmesg offers me this on laptop computer:

usb 1-5: new high speed USB device using ehci_hcd and address 9
usb 1-5: ath9k_htc: Firmware - ar9271.fw not found
ath9k_hif_usb: probe of 1-5:1.0 failed with error -22

and also this on the computer system that does function:

usb 1-5: new high speed USB device using ehci_hcd and address 4
usb 1-5: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
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
cfg80211: Calling CRDA for country: CN
Registered led device: ath9k-phy1::radio
Registered led device: ath9k-phy1::assoc
Registered led device: ath9k-phy1::tx
Registered led device: ath9k-phy1::rx
usb 1-5: ath9k_htc: USB layer initialized
usbcore: registered new interface driver ath9k_hif_usb
0
2019-05-06 01:27:41
Source Share
Answers: 1

for one reason or another the ar9721.fw documents was vacant ... downloaded and install the documents once more-- place it right into/ lib/firmware and also currently it functions ...

0
2019-05-08 16:41:44
Source