PROBLEM with rt73usb and rt2x00usb_vendor_request: Error...

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4852

laforge

14-06-2008 03:08:04

I try to use the module for a dlink dwl-g122 and a linksys wusb54gr-eu but with all the dongle the driver have a big problem with a simple download or sometimes after the dhcp negotiation.

Here the problem in the messages
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0dc0 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0e00 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0e40 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0e80 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0ec0 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0f00 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0f40 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0f80 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x0fc0 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x01 failed for offset 0x0000 with error -71.
Jun 14 043038 dubhe-thII kernel phy1 -> rt73usb_load_firmware Error - Failed to write Firmware to device.

After this messages the wifi dongle have no network connectivity.

My configuration is a Fedora 8 with a vanilla kernel
Hostdubhe-thII.mobile.int.ipv7.org - 0436-06/14/08 - Path~
[root30]$uname -a
Linux dubhe-thII.mobile.int.ipv7.org 2.6.25.4-UFP-DEVEL-ALPHA-1.0 #1 SMP PREEMPT Mon May 19 125254 CEST 2008 i686 i686 i386 GNU/Linux

Hostdubhe-thII.mobile.int.ipv7.org - 0436-06/14/08 - Path~
[root31]$modinfo rt2x00usb
filename /lib/modules/2.6.25.4-UFP-DEVEL-ALPHA-1.0/kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko
license GPL
description rt2x00 library
version 2.0.14
author http//rt2x00.serialmonkey.com
srcversion 548117493B80FE2FB5479D3
depends rt2x00lib,mac80211
vermagic 2.6.25.4-UFP-DEVEL-ALPHA-1.0 SMP preempt mod_unload CORE2


Hostdubhe-thII.mobile.int.ipv7.org - 0436-06/14/08 - Path~
[root32]$modinfo rt73usb
filename /lib/modules/2.6.25.4-UFP-DEVEL-ALPHA-1.0/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
license GPL
firmware rt73.bin
description Ralink RT73 USB Wireless LAN driver.
version 2.0.14
author http//rt2x00.serialmonkey.com
srcversion D0C0A3ECC1A9366F9904CB4

Hostdubhe-thII.mobile.int.ipv7.org - 0436-06/14/08 - Path~
[root33]$modinfo rt2x00lib
filename /lib/modules/2.6.25.4-UFP-DEVEL-ALPHA-1.0/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko
license GPL
description rt2x00 library
version 2.0.14
author http//rt2x00.serialmonkey.com
srcversion 7B7D406DD1192570B2AD6B7
depends mac80211,input-polldev,crc-itu-t,rfkill
vermagic 2.6.25.4-UFP-DEVEL-ALPHA-1.0 SMP preempt mod_unload CORE2

This module actualy for me is unusable.

laforge

21-06-2008 11:54:34

Someone can help me ? Please...

IvD

21-06-2008 12:32:13

What is the output of 'lsusb' ?

Have you tried blacklisting rt73usb and using rt2500usb?

laforge

21-06-2008 13:47:09

What is the output of 'lsusb' ?

Have you tried blacklisting rt73usb and using rt2500usb?[/quote3o9tryw4]


[root23]$lsusb
[code3o9tryw4]Bus 002 Device 013: ID 07d1:3c03 D-Link System DWL-G122 802.11g Adapter [ralink rt73][/code3o9tryw4]

Uhmmmm i try the rt2500usb but not recognize the device.
My dongle have a rt73 chipset...

I try the vanilla kernel from 2.6.25.1 to .7...the problem is in all version.

I try this driver and the legacy driver. No one work, this rt73usb some time go down, the legacy generate a kernel oops...
This is a not lucky chipset...i think is better to change it with other dongle with another chipset...
Have you any idea?

IvD

21-06-2008 13:50:05

Ok, this is indeed a rt73usb device.

If Legacy fails as well, does it even work in windows? Perhaps the dongle is broke, since this sounds a lot like a hardware error.

laforge

21-06-2008 19:48:34

Ok, this is indeed a rt73usb device.

If Legacy fails as well, does it even work in windows? Perhaps the dongle is broke, since this sounds a lot like a hardware error.[/quote1s0dof3d]

Same problem with a Dlink DWL-G122 and a and a Linksys WUSB54GR, both with rt73 chip...
Under a windows xp in virtual environment the dongle work fine...

You have an idea why the driver after some time start to generate this message

Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt73usb_bbp_read Error - PHY_CSR3 register busy. Read failed.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181349 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
Jun 21 181350 dubhe-thII kernel phy8 -> rt73usb_bbp_read Error - PHY_CSR3 register busy. Read failed.

and stop working?
The only way i have to resolve this problem, is to unload the module and unplug the dongle, then plug the dongle (the module is loaded automaticaly). After this for five or ten minutes the link is stable. I think depends on the quantity of the traffic (download or upload) on wifi link.

laforge

24-06-2008 12:03:52

I think that the problem is the same that i found with the legacy driver.
Is the cable length the problem, with this dongle up to 3mt is the right configuration without any problem.
I try the dongle for a day without any problem under linux.

[urlp99zgapj]http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=8&t=4851[/urlp99zgapj]

inffu

29-07-2008 07:21:15

Hi,

I can confirm the problem using multiple dongles. We use three devices per host and after about 12h one of them does die and rt73usb produces these kind of error messages. Surprisingly it is not always the same NIC. Two of the Logilink WL0025 are connected via 30cm long cables to a powered hub and the last one of them is directly connected.
We had the same problem with the legacy driver.

inffu

darkxer0x

29-07-2008 22:18:58

Have you tried this[/url2g2ej3ia]?
It worked form me