* unsupported TL-WN422G (0cf3:1006) @ 2009-11-17 16:21 Piotr Findeisen 2009-11-17 16:58 ` Stefan Lippers-Hollmann 0 siblings, 1 reply; 5+ messages in thread From: Piotr Findeisen @ 2009-11-17 16:21 UTC (permalink / raw) To: linux-wireless [-- Attachment #1: Type: text/plain, Size: 1693 bytes --] Hi! I've bought TP-LINK WN422G USB wireless card with Zydas chipset (as stated by the seller) in the hope it will be supported by zd1211rw driver (listed here [1]), but it seems it's not. I've tried to find help on linuxforums.org <http://linuxforums.org> [2] — the only open option is to use ndiswrapper, which (a) is reported not to work earlier in the thread and (b) is the last option for me to consider. Search in linux-wireless's archives yielded only a result [3] with a patch included in my kernel (Ubuntu-2.6.31-14.48). My card's vendor:product id is 0cf3:1006 (different that the one listed [1] for WN422G). If i execute the following after plugging the card: echo "0cf3 1006 FFFFFFFF FFFFFFFF 0 0 1" | sudo tee -a /sys/bus/usb/drivers/zd1211rw/new_id dmesg reports (notice the 5s interval between first and second entry): -------------- [21745.628183] usb 2-1: reset high speed USB device using ehci_hcd and address 9 [21750.776294] usb 2-1: read over firmware interface failed: -110 [21750.888072] usb 2-1: reset high speed USB device using ehci_hcd and address 9 [21751.085403] zd1211rw: probe of 2-1:1.0 failed with error -110 -------------- lsusb reports the card as Bus 002 Device 009: ID 0cf3:1006 Atheros Communications, Inc What I can do to better diagnose the problem and possibly get the card working? best regards, Piotr Findeisen [1] http://linuxwireless.org/en/users/Devices/USB [2] http://www.linuxforums.org/forum/wireless-internet/154830-tl-wn422g-problem-2.html [3] 5 messages on 2009-02-04, http://marc.info/?l=linux-wireless&w=2&r=1&s=wn422g&q=b <http://marc.info/?l=linux-wireless&w=2&r=1&s=wn422g&q=b> [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 261 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: unsupported TL-WN422G (0cf3:1006) 2009-11-17 16:21 unsupported TL-WN422G (0cf3:1006) Piotr Findeisen @ 2009-11-17 16:58 ` Stefan Lippers-Hollmann 2009-11-17 22:12 ` Piotr Findeisen [not found] ` <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com> 0 siblings, 2 replies; 5+ messages in thread From: Stefan Lippers-Hollmann @ 2009-11-17 16:58 UTC (permalink / raw) To: Piotr Findeisen; +Cc: linux-wireless Hi On Tuesday 17 November 2009, Piotr Findeisen wrote: > Hi! > > I've bought TP-LINK WN422G USB wireless card with Zydas chipset (as > stated by the seller) in the hope it will be supported by zd1211rw > driver (listed here [1]), but it seems it's not. > I've tried to find help on linuxforums.org <http://linuxforums.org> [2] > — the only open option is to use ndiswrapper, which (a) is reported not > to work earlier in the thread and (b) is the last option for me to > consider. Search in linux-wireless's archives yielded only a result [3] > with a patch included in my kernel (Ubuntu-2.6.31-14.48). > > My card's vendor:product id is 0cf3:1006 (different that the one listed > [1] for WN422G). [...] If you take a look at the vendor's windows driver for TP-LINK WN422G *v2*, 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 At this moment a new driver called ath9k_htc is under (early) development: http://wireless.kernel.org/en/users/Drivers/ath9k_htc Regards Stefan Lippers-Hollmann ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: unsupported TL-WN422G (0cf3:1006) 2009-11-17 16:58 ` Stefan Lippers-Hollmann @ 2009-11-17 22:12 ` Piotr Findeisen [not found] ` <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com> 1 sibling, 0 replies; 5+ messages in thread From: Piotr Findeisen @ 2009-11-17 22:12 UTC (permalink / raw) To: Stefan Lippers-Hollmann; +Cc: linux-wireless [-- Attachment #1: Type: text/plain, Size: 1492 bytes --] Hi, Stefan! Thanks for your explanation! On Tue, Nov 17, 2009 at 17:58, Stefan Lippers-Hollmann <s.L-H@gmx.de <mailto:s.L-H@gmx.de>> 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 #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 261 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com>]
* Re: unsupported TL-WN422G (0cf3:1006) [not found] ` <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com> @ 2009-11-17 23:44 ` Stefan Lippers-Hollmann 2009-11-18 7:58 ` Piotr Findeisen 0 siblings, 1 reply; 5+ messages in thread From: Stefan Lippers-Hollmann @ 2009-11-17 23:44 UTC (permalink / raw) To: Piotr Findeisen; +Cc: linux-wireless Hi On Wednesday 18 November 2009, Piotr Findeisen wrote: > Hi, Stefan! > Thanks for your explanation! > > On Tue, Nov 17, 2009 at 17:58, Stefan Lippers-Hollmann <s.L-H@gmx.de> 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.1006% = ATHER_DEV_1006.ndi, USB\VID_0CF3&PID_1006 ^^^^ ^^^^ Which means your device is TP-LINK WN422G v2 - and therefore AR9271. > 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 > > What does 'early' mean in this context? Is it worth try or should i look for > replacement? Disclaimer, I neither have access to an AR9271 device, nor am familiar with its development state, therefore I base this on the afforementioned driver wiki page and the reference code. It's not merged in 2.6.32, wireless-next (~= 2.6.33) or wireless-testing yet and http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Status is pretty explicit about its state, namely that it doesn't actually transmit any data yet. Even though development seems to be pretty active and showing quite some potential, it will likely take several months before it becomes enduser compatible. Regards Stefan Lippers-Hollmann ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: unsupported TL-WN422G (0cf3:1006) 2009-11-17 23:44 ` Stefan Lippers-Hollmann @ 2009-11-18 7:58 ` Piotr Findeisen 0 siblings, 0 replies; 5+ messages in thread From: Piotr Findeisen @ 2009-11-18 7:58 UTC (permalink / raw) To: Stefan Lippers-Hollmann; +Cc: linux-wireless [-- Attachment #1: Type: text/plain, Size: 2733 bytes --] Hi, Stefan! Thank you for all the help! Unless i will be able to exchange my card with one based on zydas chipset and if i will have some free time, I'll contact ath9_htc developers (or the wiki) for any further reference and/or testing. Funny think about this USB card is that, when I plugged it into my laptop, it made my broken broadcom PCI-E card work again immediately, so money was not lost completely :) Best regards, Piotr On Wed, Nov 18, 2009 at 00:44, Stefan Lippers-Hollmann <s.L-H@gmx.de <mailto:s.L-H@gmx.de>> wrote: > Hi > > On Wednesday 18 November 2009, Piotr Findeisen wrote: > > Hi, Stefan! > > Thanks for your explanation! > > > > On Tue, Nov 17, 2009 at 17:58, Stefan Lippers-Hollmann <s.L-H@gmx.de > <mailto:s.L-H@gmx.de>> 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.1006% = ATHER_DEV_1006.ndi, > USB\VID_0CF3&PID_1006 > ^^^^ ^^^^ > Which means your device is TP-LINK WN422G v2 - and therefore AR9271. > > > 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 > > > > What does 'early' mean in this context? Is it worth try or should i > look for > > replacement? > > Disclaimer, I neither have access to an AR9271 device, nor am familiar > with > its development state, therefore I base this on the afforementioned driver > wiki page and the reference code. > > It's not merged in 2.6.32, wireless-next (~= 2.6.33) or wireless-testing > yet and http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Status is > pretty explicit about its state, namely that it doesn't actually transmit > any data yet. Even though development seems to be pretty active and > showing > quite some potential, it will likely take several months before it becomes > enduser compatible. > > Regards > Stefan Lippers-Hollmann [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 261 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-11-18 7:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-17 16:21 unsupported TL-WN422G (0cf3:1006) Piotr Findeisen
2009-11-17 16:58 ` Stefan Lippers-Hollmann
2009-11-17 22:12 ` Piotr Findeisen
[not found] ` <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com>
2009-11-17 23:44 ` Stefan Lippers-Hollmann
2009-11-18 7:58 ` Piotr Findeisen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).