Linksys By Cisco WUSB600N v2 Doesn't Work

Bug #408165 reported by Sean McNamara on 2009-08-03
232
This bug affects 35 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

I have a "Linksys By Cisco" brand WUSB600N v2. Its USB ID is
1737:0079 Rev. 0101

When the USB adapter is hotplugged (or even coldplugged) the USB bus recognizes that "something" has been plugged in, but no additional modules are loaded at all. The output of `lsmod' before and after hot insertion is identical. So no modules claim they support this card.

The original of this model, WUSB600N, is supposedly an rt2870-compatible chip. I am not sure whether "v2" is an entirely different chipset, or whether it's just rt2870 with a quirk. I tried manually adding the USB ID to the rt2870sta source code and rebuilding the driver, but doing so gave me a kernel oops within that module. So apparently the fix to get it supported isn't as simple as adding that one line. But at least rt2870 seems to be partially aware of the chip -- right after the oops I ran `ifconfig' and the interface was up and I could get its MAC address (and it was correct). But since the module oopsed, I was unable to send any commands to the wireless interface via NetworkManager, iwconfig, etc.

I'm not sure how fervently upstream tries to support manufacturers who buy the rt2870 chipset and put it in their own product. If Ralink is nice enough to patch their drivers for the quirks of other vendors' products (such as Linksys) then it's just a matter of waiting. But if the action is in Linksys' court, I'm not sure they would help us at all. I think we will need a volunteer kernel hacker to take a look at it and see if the fix is reasonably easy.

Since these wireless USB adapters are relatively inexpensive, I am willing to donate one to a single competent individual who believes he/she can get this working well. All I ask in return is that you get it working, and return it to me when you are done with it (shipping at my expense)... unless of course you break it, which is understandable. Fragile little device.

NB: I've tested this thoroughly on both Jaunty and Karmic. In Karmic, we have the rt2800usb driver as part of the open source rt2x00 project (now entering mainline); but the new set of rt2* drivers still fail to automatically probe this card. I applied my patch to the rt2870sta driver downloaded from Ralink's website and built that on Jaunty, but did not test my naive patch against the Karmic kernel sources, as I expected the same result.

UPDATE: I think the future of Ralink chipsets on Linux is the rt2x00 project, as they are moving at a faster pace than rt2870sta and they are integrated into mainline. Their wifi drivers are first class citizens, with a behavior just like you'd expect from, say, iwlwifi: NetworkManager can use them; WPA2 works without a custom supplicant; no proprietary daemons; etc. Not sure how much code rt2x00 shares with rt2870sta (if any), but hopefully this project will pick up support for 1737:0079 soon.

zwaardmeester (zwaardmeester) wrote :

I can confirm the problems with this WUSB600N v2 stick. The Ralink driver does not work (even after adding the usb-id) and neither does ndiswrapper. Please help.

cOS (alantring) wrote :

IMHO it seems WUSB600N v2 used a new Ralink rt35x2 chipset (http://www.ralinktech.com/ralink/Home/News/PressReleases/01_08_2009.html)

Unfortunately, it seems that Ralink has not been released yet the linux module. The Windoze driver has been publicly released last august 24.

mandros (jherrerob) wrote :

WUSB600N v2 still uses rt2870 chipset.

Windows controller details, once installed, shows it is using this file:
c:\Windows\System32\DRIVERS\rt2870.sys

Product:
Linksys WUSB600N ver.2
USB ID is 1737:0079

Steve Sinclair (radarsat1) wrote :

Just to confirm, I have the same problem. (After adding usb-id)

The driver loads and detects the stick, but no matter what I do, "iwlist" gives "No scan results". After configuring RT2870STA.dat, my SSID changes accordingly in "iwconfig" but I cannot connect to it.

arvidgibas (arvidgibas) wrote :

I can also confirm the problems with the LinkSys WUSB600Nv2 stick.

Sean McNamara (smcnam) wrote :

Any word from the vendors on this bug? AFAICT Ralink are the ones who hired the staff engineers to work on Linux drivers, so maybe they should work on this.

What is the general process for getting new hardware supported? Unless Ralink/Linksys release open documentation on their chipsets, it is not realistic to expect that the community at large will implement a driver for this. We need the support of the companies peddling these chips.

Is there any way to get Canonical to engage Linksys or Ralink asking them to help us?

Also, the rt2x00 project seems to support rt2870 chips now with the rt2800usb driver. I'm not sure of the extent of modification to that driver that would be needed to support this card, if it's even a true rt2870; but it seems like any company or individual who possesses the hardware documentation and a kernel hacker would be able to get this going. That could be Canonical if they pulled the right strings.

description: updated

I have the same problem with a new WUSB600N v2. Any idea if/when support to this device will be added?

B-ZaR (teemu-erkkola) wrote :

Same here, I read that WUSB600N works in karmic with 270Mbps, but I guess that was just the "v1" (1737:0071) version. Any news on this?

Daan Kets (daankets) wrote :

I have just tried it, with my WUSB600N V2, and found that it works perfectly well on the 64bit version of Karmic Koala, on my Dell Latitude D830, if I use the NDISWRAPPER utility. Install the 'Windows Wireless Drivers' utility using apt or the new 'Ubuntu Software Center'. Then, download and extract the Windows XP driver (file called WUSB600Nv2_XP_1.4.4.0.zip) from the Linksys site.

Unplug your USB stick.

Using the Windows Wireless Drivers utility, install the driver by selecting the .inf file from the extracted WinXPX64 folder. Keep the dialog open, and insert your USB stick. Then close the dialog, and just use the Network Manager applet. It should now work.

Warning: DO NOT UNPLUG THE USB STICK WHILE THE SYSTEM IS RUNNING. This will lead to the stick no longer being recognized, and NDISWRAPPER will hang. I'll try to attach a screenshot later.

1 comments hidden view all 139 comments
Daan Kets (daankets) wrote :

Another screenshot, from within the 'Wireless Network Drivers' window.

Booting with the stick plugged seems to resolve the hang problem described in commont #9.

I tried the ndiswrapper steps on a 32bit machine (Thinkpad z60t) and still doesn't work. Seems it detected the device but could not load the driver:
$ ndiswrapper -l
rt2870 : driver installed
 device (1737:0079) present

dmesg show:
[ 497.791979] ndiswrapper (import:242): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
[ 497.792453] ndiswrapper (load_sys_files:206): couldn't prepare driver 'rt2870'
[ 497.794223] ndiswrapper (load_wrap_driver:108): couldn't load driver rt2870; check system log for messages from 'loadndisdriver'

and /var/log/messages:
Oct 31 09:15:11 ibm-laptop loadndisdriver: loadndisdriver: load_driver(358): couldn't load driver rt2870

David Oftedal (rounin) wrote :

Not only can I confirm that this device doesn't work in Linux; it doesn't work in 64-bit Windows 7 either!

If this device ever starts being useful for anything, it'll be when they release new drivers for it.

David Oftedal (rounin) wrote :

Great news, though! I was able to obtain the same results as Daan Kets by using the same distro (64-bit Karmic) and the same driver (64-bit XP version) and following the steps outlined above. Thank you so much for this invaluable piece of information! Let's hope other buyers of this device will find their way to this page as well.

I guess this also means that I owe the producers of this little gizmo an apology: It will indeed work in Windows 7; all it takes is downloading the newest Windows XP driver, installing that through the NDIS-wrapper in the newest release of Ubuntu, then installing Xen or VMWare on top of that, and finally running Windows 7 and Internet Explorer to one's heart's content using the virtualized network device. Easy as pie!

David Oftedal (rounin) wrote :

Not so great news, though: After working for a short while initially, it now quickly fails each time it starts connecting to a network, causing the network-manager utilities to hang until the OS is rebooted. It could conceivably start to work again temporarily if the machine were completely powered off, but it may also have been a mere coincidence that it ever worked in the first place.

Incidentally, the device was sold to me as "WUSB-600N-EU", which is reported to work with Linux, and not as "WUSB600N ver.2", which is what is actually printed on the device. Linux users should probably be wary of buying either of these until the driver issue is resolved.

deadite66 (deadite.66) wrote :

i tried ndiswrapper it worked but was limited to 802.11g speeds (54Mbps) not the 270Mbps i get in windows.

On Ralink website, there are the driver for the chipset RT3572. Lastly my WUSB600Nv2 (= WUSB600N-EU) works !!!

Steve Sinclair (radarsat1) wrote :

Which one? I just downloaded the Linux driver labeled RT3572, version 2.3.0.0, released 12/14/09. It compiled and loaded fine, but didn't seem to do much when I plugged in my WUSB200Nv2. No network device appeared. Do I need to manually associate the driver with the device somehow?

Steve Sinclair (radarsat1) wrote :

I just tried the latest Windows XP driver with ndiswrapper as well, but ndisgtk just says "Hardware present: No".

lsusb says:

    Bus 001 Device 004: ID 1737:0079 Linksys

But no network device appears when I plug it in.

Steve Sinclair (radarsat1) wrote :

Should have said, running Jaunty i686.

Sorry, yes, the lastest release (date 12/14/09, version 2.3.0.0). I have to add the device and vendor id in "common/rtusb_dev_id.c" file (between the "ifdef RT35xx ... #endif // RT35xx //") else it doesn't work.

In the "os/linux/config.mk", I enable "HAS_WPA_SUPPLICANT", "HAS_NATIVE_WPA_SUPPLICANT_SUPPORT", "HAS_QOS_DLS_SUPPORT", "HAS_DOT11N_DRAFT3_SUPPORT", "HAS_DOT11_N_SUPPORT" and "HAS_STATS_COUNT". I tried to enable "HAS_CFG80211_SUPPORT" but I have build errors. for the moment, I dont try others options.

lsusb says:
      Bus 001 Device 004: ID 1737:0079 Linksys

ifconfig ra0 says:
      ra0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
                  inet adr:192.168.2.102 Bcast:192.168.2.255 Masque:255.255.255.0
                  adr inet6: xxxx::xxxx:xxxx:xxxx:xxxx/64 Scope:Lien
                  UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                  Packets reçus:432694 erreurs:0 :0 overruns:0 frame:0
                  TX packets:24952 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 lg file transmission:1000
                  Octets reçus:104196211 (104.1 MB) Octets transmis:3136614 (3.1 MB)

iwconfig ra0 says:
      ra0 Ralink STA ESSID:"xxxxxxx" Nickname:"RT3572STA"
                  Mode:Managed Frequency=2.462 GHz Access Point: xx:xx:xx:xx:xx:xx
                  Bit Rate=130 Mb/s
                  RTS thr:off Fragment thr:off
                  Link Quality=100/100 Signal level:-57 dBm Noise level:-63 dBm
                  Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
                  Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Steve Sinclair > Can you tell me your bit rate when it will work for you ? I think it's too low.

Greg Haugrud (greg-tekai) wrote :

I just tried with the same changes made by Yohann and I'm up and running albeit a little slower than expected. My bit rate according to iwconfig only seems to hit 54 Mb/s, although my G wireless card only gets 24. I'll play around with some settings and see if I can work that out. I'm running on 32-bit Karmic if anyone's interested with latest updates.

Either way, it's working and that's a pretty good holiday present.

Thanks Yohann!

rori (rori) wrote :

Hi, just here to confirm problems with (1737:0071) Linksys as well on Karmic

Hi guys!

I agree with Greg Haugrud and Yohann Chastre.
This device works in Linux and Ubuntu (Karmic 64 bits).

The NetworkManager gives it the following long name :
"Linksys Linksys WUSB600N Wireless-N USB Network Adapter with Dual-Band ver. 2".

You must use the "RT3572" driver from Ralink to enable the device, by editing the "rtusb_dev_id.c".
An interesting side effect: I also use a D-Link System DWA-140 802.11n Adapter (USB id: 07d1:3c09). The id of this card is listed inside the file "common/rtusb_dev_id.c". The driver works for this adapter too, in fact they both share the same chipset: RT2870. So I had to unload an other driver (RT3070sta) to make the cards work.

I hope this will help someone.

[I'm a French Ubuntu user, please forgive my language mistakes if I have made some, I'm not used to write in English.]

Greg Haugrud (greg-tekai) wrote :

Hi,

Well, it looks like while my device is finally working, I can only connect at 802.11G right now. I haven't played much over the holidays, but one thing I did do is set my router to allow only N connections and then I couldn't connect.

I see that Yohann's connection is connecting using 802.11N, so it must be something on my end. I'm sure I have the right flags (ie, both HAS_DOT11_N... have "Y"), but maybe I'll run through recompiling everything again and post my results.

It's also strange that my internal G card only connects at 24 while the WUSB600N connects at the full 54 MBps, but that's another problem for another day. At least I can watch my HD recordings from my MythTV without it stuttering from most of our house :-)

Redger, good to hear you've had success too!

rori, isn't the 1737:0071 the V1 of the WUSB600N? It should work with the older rt2870 driver - there's lots on google for getting that to work. In fact, I bought this device thinking it would work then found out it was a V2 with a different chipset.

Steve Sinclair (radarsat1) wrote :

Hi, finally got a chance to try again.. when I added the correct vender and product id to "common/rtusb_dev_id.c", then it worked. Thanks!

Halaliel (halaliel) wrote :

I also have this Linksys WUSB600N stick.
Just got a WRT160N router plugged in, router & stick works.
Yet the mode is wireless G 54Mbps & N 300Mps is not shown.
Has read above concerning lack of proper driver, so is asking for an update that gets this working for us all.

Thank you !

Sean McNamara (smcnam) wrote :

I tried using RT3572USB driver, dated 12/22/2009, version 2.3.0.0, with stock Ubuntu 9.10 and couldn't get it to authenticate.

I have a 1737:0079 device (as stated in my original bug) and a dual-band router that can associate with 802.11g, 802.11n and 802.11a devices. I use WPA2 PSK with AES encryption, but have also tried WPA PSK with TKIP for completeness.

I added the PCI ID like everyone else did, and played around with various options in config.mk. I tried setting config with iwpriv, with cfg80211, with NetworkManager, and with the .dat file -- all to no avail.

The furthest I could get is using NetworkManager with cfg80211 support enabled. The attached dmesg is what happens when I try to authenticate with the 802.11n band using NetworkManager.

The revealing line(s):

[ 2961.072742] --> Control Thread !! ERROR !! Unknown(cmdqelmt->command=0xd79010c) !!

This is likely what's holding it up. iwconfig indicates an encryption key is set, 100/100 signal strength, essid is correct, bit rate is correct... by all indications it should be associating, but it's just not. :(

madbiologist (me-again) wrote :

Linux kernel 2.6.33-rc3 has just been released. The release notes at http://lkml.org/lkml/2010/1/5/512 include the following comment:

rt2x00: Add USB ID for Linksys WUSB 600N rev 2.

Based on past kernel releases I would expect between 3 and 5 more RC's (at approximately 1-week intervals) until 2.6.33 final. Then we just need someone to make a PPA for Karmic, followed later by a PPA for Lucid when it is released.

Sean McNamara (smcnam) wrote :

madbiologist: I tested 2.6.33-rc3, and indeed it appears that the USB ID has been added.

However, the RF chipset for this card is still not implemented in rt2x00. So this is basically the driver lying about what it supports.

When I try to load rt2800usb, I get

[ 23.229048] phy0 -> rt2800_init_eeprom: Error - Invalid RT chipset detected.
[ 23.229053] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

I tried modifying rt2800lib.c to treat a RT3572 as a RT3070 (which is dangerous in itself) like this:

//line 1854, rt2800lib.c
} else if (rt2x00_check_rev(chip, 0xffff0000, 0x35720000)) {
                        rt2x00_set_chip_rt(rt2x00dev, RT3070);
                }

This got me a working pointer to the rt2x00dev, but none of the RF chip tests succeed:

if (!rt2x00_rf(&rt2x00dev->chip, RF2820) &&
            !rt2x00_rf(&rt2x00dev->chip, RF2850) &&
            !rt2x00_rf(&rt2x00dev->chip, RF2720) &&
            !rt2x00_rf(&rt2x00dev->chip, RF2750) &&
            !rt2x00_rf(&rt2x00dev->chip, RF3020) &&
            !rt2x00_rf(&rt2x00dev->chip, RF2020) &&
            !rt2x00_rf(&rt2x00dev->chip, RF3021) &&
            !rt2x00_rf(&rt2x00dev->chip, RF3022)) {
                ERROR(rt2x00dev, "Invalid RF chipset detected.\n");
                return -ENODEV;
        }

From my tests, it appears that:

1) Certainly, this driver is not ready to support 1737:0079, even though it now claims to.
2) It doesn't appear a trivial task to just bypass checks inside the driver to get it to work. Neither the RT (Ralink-Tech wireless core) nor RF (radio receiver) chipsets in the 1737:0079 are supported at all by this driver.

Interestingly though, the call

rt2x00_check_rev(chip, 0xffff0000, 0x35720000)

succeeds, so the existing driver infrastructure is able to positively determine that the RT chip is a 3572. The real question is, what else needs to be done to add support for the 3572?

Since I am no expert on this hardware, I am not going to proceed further. But the chance is pretty slim that the 3572 is so similar to the 3070 that the same driver code can simply be plugged in and expected to work by treating the 3572 as a 3070. They are distinct chipset models for a reason :)

IMHO this kernel patch that adds the USB ID is actually a bug. The driver doesn't support this chipset at all, so claiming that it does is just going to deceive users, and possibly interfere with legitimate drivers that might actually work with a 3572 chipset, such as the Ralink rt3572sta drivers on their website. It doesn't make sense to claim support for something until support for it is there, at least in an alpha state.

madbiologist (me-again) wrote :

Sean: Interesting. Unfortunately I am not a kernel developer, nor a programmer. I couldn't have even modified rt2800lib.c like you did.

Hopefully, the phrase "this is only a release candidate" applies here, and full support will be available in 2.6.33 final.

For me it does not work either. I have added the1737:0079 id and it almost works. Scanning works perfectly but I cannot connect to any encrypted networks with network manager. I can connect to an open network, but the connection is very (and I mean *very*) slow, I suspect a very large amount of package dropping (which I suspect is also the reason why it doesn't connect with encrypted networks), though iwconfig shows 48Mb/s.

I've tested it with various configuration options to no avail.

Sean McNamara: I had the same problem with the unknown command errors. This apparently has something todo with DOT11_N or DOT11N_DRAFT because when I switch these off I don't get the errors anymore but there is also no change in behavior.

(Switching DOT11N off entails hacking the driver a bit, because it still tries to set bAdhocN to TRUE in sta/sta_cfg.c. In Set_AdhocN_Proc() I put "#ifdef DOT11_N_SUPPORT // function code #else return FALSE; #endif" around it and it compiled okay again)

I really hope that this driver will work soon for the 1737:0079 because my ndiswrapper setup seems to have gotten unstable with the latest karmic kernel.

Download full text (4.3 KiB)

Sean McNamara and Marten van de Sanden: humm ... strange problems. since Christmas, I connect to my Linksys WRT610N Dual Band router with WPA2/AES encryption. I have no problem of connection. I'm under Ubuntu 9.04 i386 with a 2.6.32 linux kernel.

The "iwconfig" command says with "2.4 GHz" band:
$ iwconfig ra0
ra0 Ralink STA ESSID:"****_1" Nickname:"RT3572STA"
          Mode:Managed Frequency=2.462 GHz Access Point: **:**:**:**:**:40
          Bit Rate=130 Mb/s
          RTS thr:off Fragment thr:off
          Link Quality=100/100 Signal level:-45 dBm Noise level:-63 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The "iwconfig" command says with "5 GHz" band:
$ iwconfig ra0
ra0 Ralink STA ESSID:"****_2" Nickname:"RT3572STA"
          Mode:Managed Frequency=5.18 GHz Access Point: **:**:**:**:**:41
          Bit Rate=270 Mb/s
          RTS thr:off Fragment thr:off
          Link Quality=100/100 Signal level:-65 dBm Noise level:-56 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The "iwpriv" commands say:
$ iwpriv ra0 show AuthMode
ra0 show: WPA2PSK

$ iwpriv ra0 show EncrypType
ra0 show: AES

$ iwpriv ra0 show NetworkType
ra0 show: Infra

$ iwpriv ra0 get_site_survey
ra0 get_site_survey:
Ch SSID BSSID Security Siganl(%) W-Mode ExtCH NT
36 ****_2 **:**:**:**:**:41 WPA2PSK/AES 68 11a/n ABOVE In
11 ****_1 **:**:**:**:**:40 WPA2PSK/AES 100 11b/g/n NONE In

Do you build the RT3572 driver (version 2.3.0.0 / 12/22/2009) with the following options in "os/linux/config.mk" ?
# Support ATE function
HAS_ATE=n

# Support QA ATE function
HAS_QA_SUPPORT=n

# Support XLINK mode
HAS_XLINK=n

# Support Wpa_Supplicant
HAS_WPA_SUPPLICANT=y

# Support Native WpaSupplicant for Network Maganger
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

#Support Net interface block while Tx-Sw queue full
HAS_BLOCK_NET_IF=n

#Support DFS function
HAS_DFS_SUPPORT=n

#Support Carrier-Sense function
HAS_CS_SUPPORT=n

# Support for Multiple Cards
HAS_MC_SUPPORT=n

#Support for IEEE802.11e DLS
HAS_QOS_DLS_SUPPORT=y

#Support for EXT_CHANNEL
HAS_EXT_BUILD_CHANNEL_LIST=n

#Support for Net-SNMP
HAS_SNMP_SUPPORT=n

#Support features of 802.11n Draft3
HAS_DOT11N_DRAFT3_SUPPORT=y

#Support features of Single SKU.
HAS_SINGLE_SKU_SUPPORT=n

#Support features of 802.11n
HAS_DOT11_N_SUPPORT=y

HAS_KTHREAD_SUPPORT=y

#Support statistics count
HAS_STATS_COUNT=y

#Client support WDS function
HAS_CLIENT_WDS_SUPPORT=n

#Support for Bridge Fast Path & Bridge Fast Path function open to other module
HAS_BGFP_SUPPORT=n
HAS_BGFP_OPEN_SUPPORT=n

#Support MAC80211 LINUX-only function
HAS_CFG80211_SUPPORT=n

Notice : I cannot enable "HAS_CFG80211_SUPPORT" because the build failed.
CC [M] [...]/2009_1222_RT3572_LinuxSTA_V2.3.0.0/os/linux/../../os/linux/cfg80211.o
[...]/2009_1222_RT3572_L...

Read more...

bbear (kminney) wrote :
Download full text (3.3 KiB)

Hi,
I have been battling to get my WUSB600N V2 to work reliably for a few weeks and I think that my experiences are relevant to this thread even though it is not strictly speaking a pure Ubuntu install which I am using.

Before I go too far, and before I violate some rule about acceptable usage of launchpad, I would like to mention that I am actually using Linux Mint 7 32bit, which as I understand is built on Ubuntu 9.04 (Jaunty).

Following the excellent advice from this tread I am able to get a *solid* connection using 5Ghz band and network-manager says that I am connected at 270Mbps.

By *solid* I mean that for regular surfing the net, everything works great and I can leave my Linux box on for hours and it never looses the connection. However, I experience audio glitches when streaming AAC audio to my Linux media center. I am wondering if others who think they have a fully working WUSB600N V2 might also have the same problem but are not aware of it yet. NOTE, if I stream MP3 instead, I do not see these audio glitch problems. I am guessing that it has to do with packet size difference maybe.

I wonder if there are still some issues with the ralink driver that need to be investigated??

I am using the latest ralink rt3572 driver [2.3.0.0] from the ralink website, I ran make and make install to install it as per instructions which I gathered from this thread.

Essentially I get the same results from iwlist/iwpriv as Yohann reported above. The only thing to note is that my makefile is NOT identical, I have one difference - in mine I have 'HAS_KTHREAD_SUPPORT n'

The symptoms:
when streaming AAC audio files from my Windows (samba) share to my Linux box I get frequent 2 second glitches in the audio (about three times in a 4 minute song) . I used Gnome Mplayer, VLC and also Boxee for my testing.

The audio glitches do not happen if I use wired 1Gbps Ethernet connection

Testing/observations:
When I experience the audio glitches, Wireshark reports "TCP: Retransmission" (interestingly, no retransmission events occur when using wired connection)

If I move the WUSB600N V2 to a Windows XP home box and stream the same AAC from the first Windows box (the one which I used for the windows share for my Linux tests) I experience zero audio glitches, this is even though the windows box reports low signal (two bars) and a 40.5Mbps connection! On the windows box I also connect using 5Ghz band.

I have am using the 5Ghz band. I have no microwave oven or other interference source nearby.

network-tools reports zero transmit errors, zero receive errors, zero collisions

I will upload the Wireshark results so you can see the TCP Retransmission events. I will also include the same capture, but for the wired connection, here you will see that there are no TCP retransmissions. The attachment is a zip file containing two CSV files which can be viewed in open office or Excel. One file is for the wireless result, the other is for the wired (1Gbps) result

The other possible issue I am seeing is with the data transfer rate. If I copy a 3+Gb file from my windows box to my Linux box it takes 908 seconds, this works out to be:

  3,171,522,212/908 = 3.49 Mbytes per secon...

Read more...

bbear (kminney) wrote :

Sorry, I forgot to include the results from iwlist and ivpriv:

$ iwconfig ra0
ra0 Ralink STA ESSID:"ssid-xxxxx-xxxxx-5g" Nickname:"RT3572STA"
          Mode:Managed Frequency=5.2 GHz Access Point: xx:xx:xx:xx:xx:xx
          Bit Rate=270 Mb/s
          RTS thr:off Fragment thr:off
          Link Quality=100/100 Signal level:-51 dBm Noise level:-56 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

$ iwpriv ra0 show AuthMode
ra0 show: WPA2PSK
$ iwpriv ra0 show EncrypType
ra0 show: AES
$ iwpriv ra0 show NetworkType
ra0 show: Infra
$ iwpriv ra0 get_site_survey
ra0 get_site_survey:
Ch SSID BSSID Security Siganl(%)W-Mode ExtCH NT
40 ssid-xxxxx-xxxxx-5g xx:xx:xx:xx:xx:xx WPA2PSK/AES 99 11a/n BELOW In
3 ssid-xxxxx-xxxxx-24g xx:xx:xx:xx:xx:xx WPA2PSK/AES 37 11b/g/n ABOVE I

bbear (kminney) wrote :

Some additional information on my setup ..

I am using Linux kernel 2.6.28-11-generic on 32bit AMD platform (Asus M2NPV-VM)

I modified my "os/linux/config.mk" to change the 'HAS_KTHREAD_SUPPORT' to 'y', so everything matches Yohann's config. I ran 'make clean', 'make', then 'make install'

My wireless-n link is back up but I am still seeing the same issues when streaming AAC from my Windows share.

Does anyone have any ideas/suggestions?

BoboKrull (jesper-ferm) wrote :

Hi, I have tried to do the above as Yohann described.
But I get no response when plugging in my adapter.
I'm quite knew with linux but I have tried to apply this guide http://ubuntuforums.org/showthread.php?p=8665204#post8665204
but with the modifications for this chip RT3572 instead!

Can I use this guide or am I missing something?
I'm using version 9.10 and I can see the adapter if I list it, so I know that I have entered correct id in rtusb_dev_id.c.

Thanks, Bobo

BoboKrull : I think this guide is quite too old. I built the RT3572 module like this:
1) download the RT3572 module source from RalinkTech website (filename: 2009_1222_RT3572_LinuxSTA_V2.3.0.0.tar.bz2)
2) execute the command "bunzip2 2009_1222_RT3572_LinuxSTA_V2.3.0.0.tar.bz2"
3) execute the command "tar -xvf 2009_1222_RT3572_LinuxSTA_V2.3.0.0.tar"
4) add the device and vendor id "{USB_DEVICE(0x1737,0x0079)}" between the "#ifdef RT35xx" and "#endif // RT35xx //" in the file "common/rtusb_dev_id.c"
5) modify the "os/linux/config.mk" like I described in my previous message
6) execute the command "sudo make"
7) execute the command "sudo make install"
8) execute the command "sudo modprobe rt3572sta" => a blue light will turn on and the network interface "ra0" will create (commands "ifconfig" and "iwconfig")

Notice: sometimes, my Ubuntu doesn't detect correctly my stick so I have to unplug and re-plug.

bbear (kminney) wrote :

Yohann,
thanks for helping BoboKrull, I was going to respond but am at work and struggling to remember all the steps which I did.

After I reinstalled the ralink driver (with the change to the config.mk to match yours) the adapter would not come back up, and I remember that doing the "sudo modprobe rt3572sta" was the step which I was missing. I also had to power up/down my system at one point to get it to be recognized but maybe your solution of pulling the adapter out/in would have fixed it just as well.

BTW does anyone have any feedback on my observations about slow transfer rate and 'TCP Retransmission' causing audio played over the wireless network to glitch? Maybe I am the only one out there having this problem, or perhaps not many people are using this h/w version of the adapter yet?

I have run out of ideas myself, and are about to give up altogether on using wireless with Linux. My last ditch attempt to fix this will be to do a complete, clean install of Karmic. I will also leave pulseaudio enabled initially to see if that helps (in my Jaunty installation at the moment I have pulse disabled as it does not play well with the Boxee app I am running)

BBear,
Like I have just one PC at home, I don't test the best bit rate I can have. I think the "Bit Rate" information given by the "iwconfig" command is not the real bit rate. I think the bit rate change over time. Perhaps, with the linux version of RT3572 module, the real bit rate is very low, 4~5 Mbps (Yes, it is very low for 802.11n), whereas, with the windows version, the bit rate is 40 Mbps. What is the bit rate of your AAC audio files ?

I will try to understand, with the source files, how the bit rate given by the "iwconfig" command is computed and try to know the real bit rate.

Yohann

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Sean McNamara (smcnam) on 2010-04-23
tags: removed: needs-upstream-testing
ramon (chinoclaus123) on 2010-06-09
Changed in linux (Ubuntu):
assignee: nobody → ramon (chinoclaus123)
status: Incomplete → Fix Released
Changed in linux (Ubuntu):
assignee: ramon (chinoclaus123) → nobody
status: Fix Released → Triaged
importance: Undecided → Medium
tags: added: kernel-needs-review kernel-net
tags: added: kernel-reviewed
removed: kernel-needs-review
59 comments hidden view all 139 comments
Andy Whitcroft (apw) wrote :

As the attached patch is not for the ubuntu packages I have removed the patch designation from it.

This issue is fixed for Ubuntu 11.04? Or wifi still not working?

DJ Roberts (arudis4x) wrote :

THAT WORKED!!!

I sat here and racked my brain trying to get this to work and after combing through tons of info on the subject, i managed to get it to work.

Using the tarball that emory provided (RT3572-WUSB600Nv2-2.4.0.1-kernel-2.6.35.tgz (2.3 MiB, application/x-tar))
extracted it.... then

   make clean
   make
   sudo make install

followed by blacklisting all the ones that kitt had mentioned....

   I blacklisted:
       blacklist rt2800usb
       blacklist rt2800lib
       blacklist rt2x00usb
       blacklist rt2x00lib
       blacklist rt2800pci
       blacklist rt2x00pci

then....

sudo modprobe -r rt3572sta
sudo modprobe rt3572sta

followed by a reboot. and whamo. worked instantly. I would just like to say a big huge gargantuan monstrous THANX!!! to all of the patient people in this community. This is the reason i wanted to even try running ubuntu. You guys are hands down the best tech support iv ever had the privilege of taking advice from and well... thanks. =P

Broc Giddens (giddensdb) wrote :

Same user from #98....

I wiped my computer and installed Ubuntu 9.10 amd64. Driver dated 2009_1214 compiled and worked. Did the distribution upgrade to 10.04 and recompiled and it worked. Upgraded to 10.10 and tried to recompiled but it did not work. Connected directly and upgraded to 11.04 and still the driver failed to compile.

I have read that the drivers won't compile on a 64 bit system but i've compiled up to the last two upgrades. Also compiled in Mint 10 x64 and worked.

I have also noticed that it will work with one kernel version, then an kernel upgrade will break it, then another kernel upgrade will fix it.

It would be great to get this added out of the box. Any input is appreciated.

Marco Improda (dmarck90) wrote :

It don't work also on Ubuntu 11.04, please patch it.

Download full text (3.4 KiB)

it is not kiding?

2011/5/1 Marco Improda <email address hidden>

> It don't work also on Ubuntu 11.04, please patch it.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/408165
>
> Title:
> Linksys By Cisco WUSB600N v2 Doesn't Work
>
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> I have a "Linksys By Cisco" brand WUSB600N v2. Its USB ID is
> 1737:0079 Rev. 0101
>
> When the USB adapter is hotplugged (or even coldplugged) the USB bus
> recognizes that "something" has been plugged in, but no additional
> modules are loaded at all. The output of `lsmod' before and after hot
> insertion is identical. So no modules claim they support this card.
>
> The original of this model, WUSB600N, is supposedly an
> rt2870-compatible chip. I am not sure whether "v2" is an entirely
> different chipset, or whether it's just rt2870 with a quirk. I tried
> manually adding the USB ID to the rt2870sta source code and rebuilding
> the driver, but doing so gave me a kernel oops within that module. So
> apparently the fix to get it supported isn't as simple as adding that
> one line. But at least rt2870 seems to be partially aware of the chip
> -- right after the oops I ran `ifconfig' and the interface was up and
> I could get its MAC address (and it was correct). But since the module
> oopsed, I was unable to send any commands to the wireless interface
> via NetworkManager, iwconfig, etc.
>
> I'm not sure how fervently upstream tries to support manufacturers who
> buy the rt2870 chipset and put it in their own product. If Ralink is
> nice enough to patch their drivers for the quirks of other vendors'
> products (such as Linksys) then it's just a matter of waiting. But if
> the action is in Linksys' court, I'm not sure they would help us at
> all. I think we will need a volunteer kernel hacker to take a look at
> it and see if the fix is reasonably easy.
>
> Since these wireless USB adapters are relatively inexpensive, I am
> willing to donate one to a single competent individual who believes
> he/she can get this working well. All I ask in return is that you get
> it working, and return it to me when you are done with it (shipping at
> my expense)... unless of course you break it, which is understandable.
> Fragile little device.
>
> NB: I've tested this thoroughly on both Jaunty and Karmic. In Karmic,
> we have the rt2800usb driver as part of the open source rt2x00 project
> (now entering mainline); but the new set of rt2* drivers still fail to
> automatically probe this card. I applied my patch to the rt2870sta
> driver downloaded from Ralink's website and built that on Jaunty, but
> did not test my naive patch against the Karmic kernel sources, as I
> expected the same result.
>
> UPDATE: I think the future of Ralink chipsets on Linux is the rt2x00
> project, as they are moving at a faster pace than rt2870sta and they
> are integrated into mainline. Their wifi drivers are first class
> citizens, with a behavior just like you'd expect from, say, iwlwifi:
> NetworkManager can use them; WPA2 works without a custo...

Read more...

Robin Sheat (eythian) wrote :

A very quick test on Natty indicates that if I use the drivers attached here by emory (version 2.4.0.1) rather than the current ones (2.5.0.0 from the ralink website) it works. The 2.5 drivers cause kernel oopses. The 2.4 seems to connect OK. I've only tried it with a g network, and haven't really moved data yet, so I don't know if it'll keep working.

Robin Sheat (eythian) wrote :

The method on #85 works fine on Natty, now I've given it more testing and connected to an 'n' network.

kitt (kittkatt0) wrote :

Confirmed, I've got it working on 11.04 64bit using the tarball in #85.

1.) Follow the instructions as he laid out.

2.) After you've "make install" cd into os/linux

3.)type in "sudo /sbin/insmod rt3572sta.ko"

Your wifi stick will now activate and start working. Unfortunately you need to do step #3 every time you reboot. They explan in the readme how to get it to autoload on boot if you want to take the time to learn how.

Robin Sheat (eythian) wrote :

To make it autoload, do 'sudo make install', blacklist all the build-in modules, and plug the adaptor in. It should keep working from now on.

Whenever the kernel is upgraded, you'll need to so 'make ; sudo make install' again, but that should be it.

Unless someone turns it into a DKMS module...

Robin Sheat (eythian) wrote :

(oh, if the non-working modules have already loaded you'll need to manually rmmod them before this will work I think.)

Robin Sheat (eythian) wrote :

OK, after using it for a while it turns out to not be terribly stable. It often slows right down to a crawl. Ping still works, but doing anything real gets terrible speeds, and unplugging/replugging the USB fixes this, until the next time it happens. Sometimes it'll go all day without this problem, sometimes it happens every 5 minutes.

Sometimes it disconnects, but nm reconnects it quickly again.

Robin Sheat (eythian) wrote :

A bit of experimentation suggests that it's a whole lot more stable when network manager is replaced with wicd. I've had it running for about 10 hours with wicd managing the wifi and it hasn't dropped out once. I guess the repeated scanning that n-m does upsets it or something. Haven't checked with the 2.5.0 drivers to see if they cause issues with wicd.

Arik (arik.b) wrote :

Just a confirmation really.

Linux chikara 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

After a few days of using it, 2.5.0.0 (from ralink site) is flaky and exhibits the following:

* disconnect after leaving overnight producing the attached oops
* inability to connect after cold-plugging
* occasional disconnects
* occasional 802.11n authentication failure - NetManager would claim a failure to authenticate but would auth with a 802.11g network. Usually accompanied by an Oops but I don't have a sample

I have compiled 2.4.0.1 a.k.a. "the empry driver" as per emory's instructions and I am currently using it. It allows cold-plugging at least. We'll see in a few days.

-- Arik

Robin Sheat (eythian) wrote :

The driver from #85 on wicd is still the best I've found, however it is prone to dropping out, sometimes regularly, sometimes not at all. Usually replugging fixes this (and I think that it will tend to reconnect itself after a while), sometimes a reboot is required.

Arik (arik.b) wrote :

Update: last 4 days the network has been up non-stop. No oops, no drops, ping-flooded to my local gateway for 24 hours, packet loss 0.01% (nil).

I'm happy.

Using the 2.4.0.1 package from #85 with network manager. Didn't try wicd but I doubt it will change the stability.

-- Arik

sixgeek (sixgeek) wrote :

@ Arik
I can confirm that. It works very well with network-manager and 2.4.0.1.

Arik (arik.b) wrote :

Okay it finally gave up the ghost about 12 hours ago. Attached is the Oops it created. Replugging didn't help.

Reboot hung on something (the graphical screen obstructed the view) and I had to use the old Alt-Shift-SysRq to sync-unmount-boot the box.

All in all having 6 days of continuous connectivity on a desktop is... doable... but I cannot call this a stable setup.

-- Arik

Robin Sheat (eythian) wrote :

Yeah, in my case, it worked for about that long. Then started dropping out sometimes. Then occasionally crashing. I then spent a bit of time messing about with the drivers, and now it crashes every time the driver is loaded and the wifi stick plugged in. I'm wondering if there's something in some of the drivers that upsets the hardware (or my one is faulty.)

I've seen both the oopses that are in your attachment many times :)

Jose Luis Carballo (jlcb03) wrote :

I think the main problem is that WUSB600N v2 is recognized by Ubuntu as WUSB600N v1. I suppose tweaking the hardware detection so that it parses correctly the device string ID could resolve the problem. It's really a pity this device can't be properly detected "out of the box".

Broc Giddens (giddensdb) wrote :

I've done a fresh install of Xubuntu daily that has kernel 3.0-1. The kernel identified the device as V2 and model RT3572 but did not "just work" "out of the box". I built Emery's driver and got the hardware working with little resistance but still encounter the same kernel oops as with the previous kernels. Just adding my two cents. Maybe its progress that the kernel differentiates between v1 and v2 but something is still not adding up with the driver module and kernel.

Broc Giddens (giddensdb) wrote :

I've downloaded the latest driver from Ralink dated 4-27-2011. I'm gonna try my hand at modifying it like emory did and see if it is any more stable on this kernel. Anyone who wants to help let me know! I'm new at this myself but definately willing to learn.

emory (emoryl) wrote :

I wound up using a wireless bridge instead due to the instability of the
adapter.

I still have the hardware though and if you hit a wall I may be able to
assist from the sidelines, I don't remember it being difficult.

Robin Sheat (eythian) wrote :

Broc, I've tried the latest driver, and for me it was the worst of the lot. I gave up on the wusb600n for now, going to go with a wireless bridge when I get around to getting one.

Dror Cohen (drorcohen) wrote :

I hope this will help someone - used the instructions in #85 and once I defined the wireless with a static IP the only problem I still face is the fact I need to disconnect and reconnect the usb dongle after a return from Sleep.

daefen (daefen) wrote :

I am using the driver modified by emory and, instead of using network-manager (drops every 5 minutes or less ) or wicd (not working at all), I configured a static IP in the interfaces file plus wpa_supplicant support and now the dongle has been working flawlessly since then.

Ben Roob (benjaminroob) wrote :

Well, after going through the mentioned steps, i got a blue LED. Reboot. Stick was not active, no wireless connection. Plugged in and out, blacklisted 2800 mods still in "lsmod", so obviously did some errors... Going through steps again (clean, make, install... blacklisting, modprob), works fine. Reboot, everything is hopefully ok for now... after 2 reboots.

So, because this is the first helping post/article, a big thanks to all who helped getting this device to work.

Getting the wireless connection works fine was the first step, after installing a "clean" ubuntu 11.04 64bit. Anyone has problems after running update, kernel update or the "automatic" system update?

specialk (geigerkr) wrote :

Hi, Ben. I just finally completed an update to 11.04 with a triple whammy - no grub, no video, no connection. After getting through the first two, I can also confirm that solution provided in #85 allows me again to connect. I think a re-do will be necessary with any kernel or release upgrade. I was thinking to upgrade to 11.10 now, since I'm a glutton for punishment and check if for some odd reason she's now working out of the box. Worst case scenario, the same steps for 11.10 would be OK, but I hope there are enough people following this one now to get some traction for the post 11.10...

Robin Sheat (eythian) wrote :

It doesn't work out of the box in 11.10. It doesn't identify it at all.

Ferry Toth (ftoth) wrote :

I've just tried with the 3.2rc4 mainline kernel for oneric. Same, driver does not load. And if loaded manually (modprobe rt2800usb) they don't work.

However, building and installing linux-next compat-wireless from http://linuxwireless.org/en/users/Download solves the problem. Note: currently linux-next IS linux 3.2.

To me it looks like mainline is not configured to build the new driver.

Reportedly the driver is supported from linux 3.1 onward.

Ferry

Julian Wiedmann (jwiedmann) wrote :

The kernel is missing CONFIG_RT2800USB_RT35XX (which is disabled by default as it depends on EXPERIMENTAL). compat-wireless probably has that option enabled.

Keith Patton (fubofo) wrote :

I know I'm probably gonna get told this is nothing to do with Ubuntu, but...

I can confirm this adapter works flawlessly out-of-the-box with Fedora 16, blue LED and everything.
I really don't understand why I haven't been able to get this adapter working in Ubuntu since 10.04

Keith Patton (fubofo) wrote :
Download full text (5.6 KiB)

OK now I'm confused.
I seem to have the latest 2.5.0.0 driver compiled with no errors and installed successfully (Ubuntu 11.10 64bit)
lsmod shows the rt3572sta module loaded but not linked to any thing ??
iwconfig reports that I now have ra0 (previously had only eth0, lo and usb0 [my android])
rt28xx does not seem to be getting loaded at all (which is good I believe ??)
synaptic shows that I have wpasupplicant installed (not wpasupplicant:i386)

now here's the strange part....
gnome-network-manager on 2 occassions displayed the WUSB600Nv2 correctly and actually scanned networks perfectly. However upon attempting to connect to my network (WPA2) the entire PC froze, causing me to power the machine off twice :S
So I make uninstall, manually remove /etc/Wireless/RT2870STA/ folder , make, sudo make install again - now gnome-network-manager doesn't recognise it ??!

another strange part...
with gnome-network-manager removed and using wicd: even after make uninstall (RT3572STA driver), wicd seems to be able to scan and attempt to connect to networks?? However, again it fails on connecting to WPA2 networks (bad password) though it will connect to unsecure networks........???

-------------------------------------------------------------------------------------------------------
 Building modules, stage 2.
  MODPOST 1 modules
  LD [M] /home/kaipee/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/rt3572sta.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-16-generic'
kaipee@zoostorm-ubuntu:~/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO$ sudo make install
make -C /home/kaipee/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux -f Makefile.6 install
make[1]: Entering directory `/home/kaipee/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux'
rm -rf /etc/Wireless/RT2870STA
mkdir /etc/Wireless/RT2870STA
cp /home/kaipee/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/RT2870STA.dat /etc/Wireless/RT2870STA/.
install -d /lib/modules/3.0.0-16-generic/kernel/drivers/net/wireless/
install -m 644 -c rt3572sta.ko /lib/modules/3.0.0-16-generic/kernel/drivers/net/wireless/
/sbin/depmod -a 3.0.0-16-generic
make[1]: Leaving directory `/home/kaipee/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux'
kaipee@zoostorm-ubuntu:~/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO$
-------------------------------------------------------------------------------------------------------

...lsmod shows...

-------------------------------------------------------------------------------------------------------
kaipee@zoostorm-ubuntu:~/Downloads/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO$ lsmod
Module Size Used by
rndis_host 13855 0
cdc_ether 13494 1 rndis_host
usbnet 26168 2 rndis_host,cdc_ether
rt3572sta 679247 1
cfg80211 209711 0
rfcomm 46622 0
bnep 18139 2
bluetooth 185637 10 rfcomm,bnep
pci_stub 12622 1
vboxpci 23200 0
vboxnetadp 13382 0
vboxnetflt 23441 0
vboxdrv 282548 3 vboxpci,vboxnetadp,vboxnetflt
binfmt_misc ...

Read more...

Keith Patton (fubofo) wrote :

I have been able to successfully connect to my own network (unsecured) using wicd - however am unable to browse internet
gnome-network-manager still does not recognise the device
Network Tools displays all link information correctly
iwconfig displays ra0 with correct information

screenshot here:
http://www.kaipee.co.uk/fileman/backend/r.php/public/58C58C90436F4828A780DA5BD0ADF79E

I would be extremely grateful if someone could get back to me to figure out the 2 remaining issues:
* gnome-network-manager identifying the device
* connecting using WPA-PSK

Keith Patton (fubofo) wrote :

I have now successfully got the RaLink 2.5.0.0 driver (rt3572sta) to load using /sbin/insmod rt3572sta.ko from my build directory
the device is now listing in lsmod (rt3572sta)
the blue LED turns on and blinks while sending packets
device is now also recognised in gnome-network-manager
Bit Rate displays at 300 Mb/s

I just cannot seem to get the adapter to connect using WPA2PSK - any assistance would be much appreciated
Step 3 in README mentions building for wpa_supplicant but I do not understand what needs to be done here, or at what point

3> In os/linux/config.mk
 define the GCC and LD of the target machine
 define the compiler flags CFLAGS
 modify to meet your need.
 ** Build for being controlled by NetworkManager or wpa_supplicant wext functions
    Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.
    => #>cd wpa_supplicant-x.x
    => #>./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

scrnsht: http://www.kaipee.co.uk/fileman/backend/r.php/public/AF36A9AAE287496586942AC3B0F2E7BE

marble (marblepebble) wrote :

In Precise, to get this device to work, install linux-backports-modules-cw-3.3-precise-generic and reboot. (Works just fine for me now, with WPA2, but didn't work at all until I installed the extra wireless modules.)

Keith Patton (fubofo) wrote :

Works flawlessly everytime on anything I tested:

http://ubuntuforums.org/showpost.php?p=11711811&postcount=6

WUSB600N V2 is working for me on Ubuntu 12.04LTS natively.

Sometimes connection hangs though and cannot recover from suspension. To fix, simply unplug/replug adapter and turn off its power management feature: "sudo iwconfig wlan0 power off"

Sean McNamara, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Displaying first 40 and last 40 comments. View all 139 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers