Linksys USB Network Adapter WUSB600N does not work

Bug #433019 reported by Ben
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This usb adapter did work in 9.04. Currently it is able to list some wireless networks but no signal strength. Also it is unable to connect to --ANY-- network, WEP/WPA/WPA2 and open networks.

This spam is from dmesg and hopefully helpful to you.

--------------------------------------------------------------------------

[ 1383.080680] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1004 with error -19.
[ 1383.080686] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1004 with error -19.
[ 1383.080690] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[ 1383.080694] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x0208 with error -19.
[ 1383.080697] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1004 with error -19.
[ 1383.080701] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1204 with error -19.
[ 1383.080704] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1328 with error -19.
[ 1383.080708] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[ 1383.080711] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
[ 1383.080717] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.080820] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.080923] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081026] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081130] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081233] phy0 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf70b3d84
[ 1383.081237] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081340] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081443] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081545] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081648] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081750] phy0 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf70b3d8c
[ 1383.081820] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.081923] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082026] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082128] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082231] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082333] phy0 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf70b3d94
[ 1383.082355] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082458] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082560] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082663] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082766] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082868] phy0 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf70b3d94
[ 1383.082889] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.082992] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.083094] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.083197] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.083300] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 1383.083402] phy0 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf70b3d94

Revision history for this message
Ben (b3nw) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ben (b3nw) wrote :

this persists in the 9.10 beta release.

Revision history for this message
Webbie (james-h-cracknell) wrote :

I just installed Karmic (x64) and had a different issue with my WUSB600N (at least as described above), however the error messages above seem to indicate the same root cause.

I found that while my WUSB600N would appear to be working, and could connect to wireless G access points, it would not list or connect to wireless N access points.

Running lsmod, I noticed that while there were rt (ralink) modules loaded, of the six of them, none of them were dependencies of rt2780sta, which is specific to the chipset of the WUSB600N. In fact, every module other than rt2780 was a direct or indirect dependency of rt2800usb. Blacklisting rt2800usb fixed my problem. Given that rt2x00 was disabled as a consequence of blacklisting rt2800usb, I believe this may resolve the above issue as well.

Temporary fix for people with similar problems:

echo "blacklist rt2800usb" | sudo tee -a /etc/modprobe.d/blacklist

then restart.

Revision history for this message
Webbie (james-h-cracknell) wrote :

Correction: for rt2870 above, read rt2870sta.

Revision history for this message
glutinous (steven-epicfinalboss) wrote :

I have a Linksys WUSB600N USB wifi adapter as well. It was connecting to my WPA2 Personal network fine in 9.04, but broke once I upgraded to 9.10. It could scan it (most of the time...), but could not connect.

Webbie's temporary fix (adding rt2800usb to the blacklist) worked for me. Not really sure what the root cause of this problem is.

Revision history for this message
madbiologist (me-again) wrote :

Could each of you please attach the output of lsusb with the adaptor plugged in?

Revision history for this message
Lucio Crusca (lucrus) wrote :

Same problem here.

lsusb output:

# lsusb
Bus 002 Device 005: ID 148f:3070 Ralink Technology, Corp.

Revision history for this message
Lucio Crusca (lucrus) wrote :

BTW, blacklisting rt2800usb didn't work for me (moreover the kernel keeps loading rt2800usb even after it's been blacklisted).

Revision history for this message
glutinous (steven-epicfinalboss) wrote :

$ lsusb
Bus 001 Device 007: ID 1737:0071 Linksys
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 014: ID 050d:016a Belkin Components
Bus 003 Device 013: ID 0a5c:4503 Broadcom Corp.
Bus 003 Device 012: ID 0a5c:4502 Broadcom Corp.
Bus 003 Device 011: ID 0a5c:4500 Broadcom Corp.
Bus 003 Device 002: ID 046d:c025 Logitech, Inc. MX500 Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
spod (samoverton) wrote :

I had exactly the same problem described by Webbie, and his solution worked for me too. I'm using a different device with the same chipset:

$ lsusb
Bus 001 Device 002: ID 07d1:3c09 D-Link System DWA-140 802.11n Adapter [ralink rt2870]

Perhaps update the bug description so it is relevant to the chipset/drivers and not just the WUSB600N device?

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Benjamin,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 433019

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
glutinous (steven-epicfinalboss) wrote :

Actually, I don't have any issues lately. I think the latest kernel & Ubuntu updates have resolved the issue (I am running Ubuntu 9.10). I will re-raise it if it still happens...

Revision history for this message
Patrick M (prmillius) wrote :

sounds like my issue with another brand of usb
#111961

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Changed in linux (Ubuntu):
status: Expired → New
Revision history for this message
glutinous (steven-epicfinalboss) wrote :

Ran into this issue again recently. My Linksys WUSB600N (v1) USB wi-fi adapter was working fine with Ubuntu 10.04.1 and the 2.6.32-21-generic kernel image, IF I blacklisted rt2800usb.

Any kernel update afterwards has since broken it. Here is what I did to 'fix' it.

1. Continued blacklisting rt2800usb.

2. Basically followed the instructions in this post (but carried out the steps manually, rather than use the shell script): http://ubuntuforums.org/showpost.php?p=9534492&postcount=34

 This seems to work. My Linksys WUSB600N (v1 - NOT the v2) is connecting to my D-Link wireless router properly, and seems reasonably stable. Not sure what the proper fix would be or what changed to break it. :(

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 433019

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.