TP-Link TL-WN321G usb wireless device not work, xubuntu 9.10

[kissson]

[ 13.754089] udev: starting version 147
[ 14.294336] parport_pc 00:04: reported by Plug and Play ACPI
[ 14.430705] ppdev: user-space parallel port driver
[ 14.521862] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.716097] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[ 14.716102] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[ 14.716138] usbcore: registered new interface driver rt2500usb
[ 15.088017] phy1: Selected rate control algorithm 'minstrel'
[ 15.088017] Registered led device: rt73usb-phy1::radio
[ 15.088017] Registered led device: rt73usb-phy1::assoc
[ 15.088017] Registered led device: rt73usb-phy1::quality
[ 15.118810] usbcore: registered new interface driver rt73usb
[ 15.884171] rt73usb 1-1:1.0: firmware: requesting rt73.bin
[ 18.363413] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 105.551899] wlan0: direct probe to AP 00:13:49:3d:20:9d try 1
[ 105.561517] wlan0 direct probe responded
[ 105.561573] wlan0: authenticate with AP 00:13:49:3d:20:9d
[ 105.572722] wlan0: authenticated
[ 105.572746] wlan0: associate with AP 00:13:49:3d:20:9d
[ 105.578555] wlan0: RX AssocResp from 00:13:49:3d:20:9d (capab=0x431 status=0 aid=2)
[ 105.578558] wlan0: associated
[ 105.777966] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 105.959650] wlan0: disassociating by local choice (reason=3)
[ 116.068017] wlan0: no IPv6 routers present

Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

  *-network
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 00:1d:0f:df:43:e2
       capabilities: ethernet physical wireless
       configuration: broadcast=yes multicast=yes wireless=IEEE 802.11bg

rt73usb 26336 0
crc_itu_t 1852 1 rt73usb
rt2500usb 21152 0
rt2x00usb 11548 2 rt73usb,rt2500usb
rt2x00lib 29756 3 rt73usb,rt2500usb,rt2x00usb
led_class 4096 1 rt2x00lib
input_polldev 3716 1 rt2x00lib
mac80211 181236 2 rt2x00usb,rt2x00lib
parport_pc 31940 0
cfg80211 93052 2 rt2x00lib,mac80211
parport 35340 3 lp,ppdev,parport_pc

if needed, send me command-line and I gave the report

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

apport-collect 543298
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` 543298
if you are using Jaunty Jackalope (9.04)

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

[Charlie Kravetz (cjkgeek)]

Thanks for the additional supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

Thanks for taking the time to make Ubuntu better!

[Roderick Charles Drew (rod-uksurfers)]

This is also the case in Lucid 10.4, both in my i386 and amd64 machines, 2.6.32-23-generic kernel and at least its two predecessors. I can sometimes achieve success after plugging in the device after having booted up, but often TAIL -F /VAR/LOG/MESSAGES reveals the device as being "usb 2-3: new high speed USB device using ehci_hcd and address XXX" i.e. it is not being recognised properly when plugged in. Worth noting here that I have a TP-Link wireless PCI card installed (also an Atheros chip), that also fails to function. LSPCI reveals: "Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)", so it should be fine. Neither of the two other TP Link PCI wireless cards that I have tried work either. It would seem to me that the underlying problem is to do with the rt73usb module. In all the versions of Ubuntu that I have run, I have never had any problems with atheros-based wireless devices, whether PCI cards or USB, so this is somewhat of a surprise.

[kissson (bird1110)]

mentioned device worked in lubuntu 10.10
need
ifconfig inf down / up
and
iwconfig params
several time then it will be okay
I think it should work on G K X also

[Roderick Charles Drew (rcd)]

I can confirm that this device works fine in Kubuntu 10.10 and Xubuntu 10.10.

[Charlie Kravetz (cjkgeek)]

@kisson: This issue occurs in Ubuntu 9.10, but not in Ubuntu, Kubuntu, Xubuntu, Lubuntu 10.04 and 10.10?

[marky_mark (decapitated-sfr)]

hasardous issue with the same TP-LINK wifi dongle in Ubuntu 10.10 x86 and 10.1O amd64.

rt73usb module

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.