rt2800usb not working with Ralink 3072

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

itxaka

08-06-2011 06:44:33

Hello guys!

First, let me say congrats for the good work on the rt2xxx drivers.

Second, lets see if we can find what is wrong with one of them wich affect a Ralink 3072.

Hardware info
Bus 001 Device 005 ID 148f3072 Ralink Technology, Corp.

Distro used Backtrack 5 Gnome 32b
Linux bt 2.6.38 #1 SMP Thu Mar 17 205218 EDT 2011 i686 GNU/Linux


Linux wireless drivers page suggest that this exact model works
Ralink RT3072 RT3072 0x148f 0x3072

Compat wireless Updated to latest bleeding edge 2.6
Linux drivers Updated to latest git

lsmod
root@bt~# lsmod|grep rt
rt2800usb 10028 0
rt2800lib 33048 1 rt2800usb
crc_ccitt 1281 1 rt2800lib
rt2x00usb 9319 1 rt2800usb
rt2x00lib 33002 3 rt2800usb,rt2800lib,rt2x00usb
mac80211 248838 4 rt2800lib,rt2x00usb,rt2x00lib,ath9k
cfg80211 152934 3 rt2x00lib,ath9k,mac80211

dmesg when conecting the device
[quoteawlzgbti]
[ 140.158382] Registered led device rt2800usb-phy1radio
[ 140.158574] Registered led device rt2800usb-phy1assoc
[ 140.158764] Registered led device rt2800usb-phy1quality
[ 140.159236] usbcore registered new interface driver rt2800usb
[/quoteawlzgbti]
So it seems to work.

Now here comes the problems. It seems to be really unstable at scanning, sometimes working sometimes not. But that is not the main issue, the problem is when trying to connect to a wep/wpa/wpa2 network (Haven't tried with an open one) the device stops responding and this appears on dmesg
[quoteawlzgbti]
[ 825.410603] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x1328 with error -71.
[ 825.823305] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x0c failed for offset 0x0000 with error -71.
[ 826.243819] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x7010 with error -71.
[/quoteawlzgbti]
As you can see, the first 2 errors refer to different offsets, then the third one keeps referring to the same offset. The last error keeps repeating ad infinium.

If you don't do anything, wiicd will hang up and die until you disconnect the usb wireless by unplugging it.

But not it comes the fun part, if you disconnect it and reconnect it shortly, it works. Don't ask me why
[quoteawlzgbti]
[ 834.638568] usb 1-5 USB disconnect, address 3
[ 834.639767] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[ 834.647661] phy1 -> rt2x00usb_regbusy_read Error - Indirect register access failed offset=0x00007010, value=0xf0d01d28
[ 837.924173] usb 1-5 new high speed USB device using ehci_hcd and address 5
[ 838.091332] cfg80211 Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule
[ 838.091344] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091353] cfg80211 Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule
[ 838.091362] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091370] cfg80211 Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule
[ 838.091379] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091387] cfg80211 Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule
[ 838.091397] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091404] cfg80211 Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule
[ 838.091414] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091422] cfg80211 Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule
[ 838.091431] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091438] cfg80211 Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule
[ 838.091448] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091456] cfg80211 Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule
[ 838.091465] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091473] cfg80211 Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule
[ 838.091481] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091487] cfg80211 Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule
[ 838.091494] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091500] cfg80211 Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule
[ 838.091507] cfg80211 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091513] cfg80211 Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule
[ 838.091520] cfg80211 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091526] cfg80211 Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule
[ 838.091533] cfg80211 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091539] cfg80211 Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule
[ 838.091546] cfg80211 2474000 KHz - 2494000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 838.091794] ieee80211 phy2 Selected rate control algorithm 'minstrel_ht'
[ 838.093968] Registered led device rt2800usb-phy2radio
[ 838.094049] Registered led device rt2800usb-phy2assoc
[ 838.094137] Registered led device rt2800usb-phy2quality
[ 847.055875] ADDRCONF(NETDEV_UP) wlan1 link is not ready
[ 852.690786] wlan1 authenticate with xxxxxx (try 1)
[ 852.692307] wlan1 authenticated
[ 852.692406] wlan1 associate with xxxxxx (try 1)
[ 852.694391] wlan1 RX AssocResp from xxxxxxx (capab=0x471 status=0 aid=9)
[ 852.694409] wlan1 associated
[ 852.704983] ADDRCONF(NETDEV_CHANGE) wlan1 link becomes ready
[ 862.792092] wlan1 no IPv6 routers present
[/quoteawlzgbti]

The connection seems stable, but the link power is much lower than it should be and the speed is...really poor. Also, the disconnect/connect trick does not always work. Sometimes it will just hang with the offset 0x7010 error forever.

BTW, the card works with the rt2870sta module, but as fas as I understand, this module is not recommended.


Just for the hell of it, I shoot up a usb with ubuntu live 11.04, and the dmesg error is different. The error claims that rtx200 does not support this chipset. But I guess that is due to Ubuntu having an older linux-firmware/compat wireless?


So any guesses? Im open to test anything be it new drivers, strange hacks, or whatever you can think of D

Thanks!

itxaka

08-06-2011 10:33:48

Well, fuck me sideways.

I just updated compat-wireless to the latest one again (01/06/2011 I think) and it seems to work now. I guess somebody must had reported this to them or rt2x00 devs and you fixed it.

Plz close! and sorry for the inconvenience D