Hi, Stefan! Thanks for your explanation! On Tue, Nov 17, 2009 at 17:58, Stefan Lippers-Hollmann <s.L-H@xxxxxx <mailto:s.L-H@xxxxxx>> wrote: If you take a look at the vendor's windows driver for TP-LINK WN422G *v2*, how can I know I have v2 of the device? it becomes obvious that the device does not use the ZyDAS zd1211/ Atheros 5007UG cipset, but has switched to the new Atheros AR9271 chipset (which technically is a 150 MBit/s 802.11n "lite" chipset family) instead. %ATHER.DeviceDesc.9271% = ATHER_DEV_9271.ndi, USB\VID_0CF3&PID_9271 %ATHER.DeviceDesc.7010% = ATHER_DEV_7010.ndi, USB\VID_0CF3&PID_7010 %ATHER.DeviceDesc.1006% = ATHER_DEV_1006.ndi, USB\VID_0CF3&PID_1006 OK, I found this section on the CD with the drivers but my product id is 1006. How do you know it's AR9271 chipset and not, say, AR1006? I found /AR9271/i on the CD in driver files for Windows 2000, XP, XP64. Vista driver files don't have this substring anywhere (they have '9271' in netathur.inf 6 times, and '1006' is 6 times in analogus lines as well). At this moment a new driver called ath9k_htc is under (early) development: http://wireless.kernel.org/en/users/Drivers/ath9k_htc If i understand correctly 'Status' section, this driver is wireless and radioless at this moment, right? Maybe I should check this driver to see if it recognizes my card correctly? best regards, Piotr
Attachment:
signature.asc
Description: OpenPGP digital signature
