3071 chip support is broken?!

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

MarkP

19-04-2011 09:06:19

It appears RaLink 3071 chip support is broken.

It looks like support either was once in the driver and has broken, or is in the process of adding.

Any idea how I can get it to work? Or what I can do to help?

I am using a D-Link DWA-140 Usb Wireless REV B2

It is important to note that the REV B1 h/w uses a different chip and works very well, unfortunately I can't buy one of those-(

The Rev B2 h/w appears to use a RaLink 3071 chip. The manufacturer's driver 2011_0107_RT3070_RT3370_Linux_STA_v2.5.0.1_DPO sort of works (drops a lot of packets when monitoring, so is no use to me-(), so I know the D-Link is ok.




[mp13@mp13fedora rt2x00]$ lsusb
Bus 002 Device 006 ID 07d13c0a D-Link System DWA-140 RangeBooster N Adapter(rev.B2) [Ralink RT2870]


rt2870usb driver -

Tested using

ad381c32aa2a4152dc99fd92769f57d2e2cb4cfd rt2x00 Implement get_antenna and set_antenna callback functions
but with some extra INFO lines added to rt2800lib.c-


Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) driver supports SSID scans (scan_capa 0x01).
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) new 802.11 WiFi device (driver 'rt2800usb' ifindex 4)
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) exported as /org/freedesktop/NetworkManager/Devices/2
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) now managed
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) device state change 1 -> 2 (reason 2)
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) bringing up device.
Apr 19 094352 mp13fedora kernel [ 141.555598] phy1 -> rt2x00lib_request_firmware Info - Loading firmware file 'rt2870.bin'.
Apr 19 094352 mp13fedora NetworkManager[1033] <warn> (wlan0) firmware may be missing.
Apr 19 094352 mp13fedora NetworkManager[1033] <info> (wlan0) deactivating device (reason 2).
Apr 19 094352 mp13fedora kernel [ 141.559173] phy1 -> rt2x00lib_request_firmware Info - Firmware detected - version 0.12.
Apr 19 094352 mp13fedora kernel [ 141.559179] phy1 -> rt2800_check_firmware Info - len 4096 fw_len 4096
Apr 19 094352 mp13fedora kernel [ 141.559181] phy1 -> rt2800_check_firmware Info - len ok
Apr 19 094352 mp13fedora kernel [ 141.559183] phy1 -> rt2800_check_firmware Info - rt2x00dev->chip.rt = 0x3071
Apr 19 094352 mp13fedora kernel [ 141.559185] phy1 -> rt2x00lib_request_firmware Error - Current firmware does not support detected chipset.
Apr 19 094352 mp13fedora NetworkManager[1033] <info> found WiFi radio killswitch rfkill1 (at /sys/devices/pci000000/0000001d.0/usb2/2-1/2-1.7/2-1.71.0/ieee80211/phy1/rfkill1


Note that
a) It loaded the wrong firmware - rt2870.bin
b) Ignore the line from NetworkManager about firmware missing, it did load, you get a different error if it is missing
c) Tricking it into loading the correct firmware (presumably rt3071.bin), using symlinks, doesn't help much.

Any ideas?

Cheers
Mark

IvD

19-04-2011 19:32:58


Apr 19 094352 mp13fedora kernel [ 141.559185] phy1 -> rt2x00lib_request_firmware Error - Current firmware does not support detected chipset.
[/quote1v6o1s0o]

This basically is the main problem. You are using the wrong firmware version. You should upgrade your firmware based on the latest version from the Ralink website.


a) It loaded the wrong firmware - rt2870.bin
[/quote1v6o1s0o]

Nope, the file is correct. The version isn't.


c) Tricking it into loading the correct firmware (presumably rt3071.bin), using symlinks, doesn't help much.
[/quote1v6o1s0o]

That doesn't make sense as the rt2800usb explicitely loads rt2870.bin (which contains support for rt3071).

MarkP

03-05-2011 16:25:31

OK, I have downloaded all the recent drivers from Ralink and searched for the newest rt2870.bin I can find (based on file timestamp).

The best I can find is the one from 2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO dated April 27th 2011.

Is that a good version to use?

I am getting further but still failing with Fedora 14 2.6.35.12-90.fc14.x86_64

I am currently rebuilding the latest serial monkey kernel and driver git tree and will see if that works better tomorrow.

The driver appears to start ok and can scan. I can't get it to connect. Also (most importantly to me) it dies when I do an "ifconfig wlan0 down" so I can do a "iwconfig wlan0 mode monitor"-

May 3 161128 mp13fedora NetworkManager[1087] <info> (wlan0) taking down device.
May 3 161128 mp13fedora kernel [26782.555692] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x1204 with error -71.
May 3 161128 mp13fedora kernel [26782.576262] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x06 failed for offset 0x1328 with error -71.
May 3 161128 mp13fedora kernel [26782.596836] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x0208 with error -71.
May 3 161128 mp13fedora kernel [26782.617381] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x0c failed for offset 0x0000 with error -71.
May 3 161128 mp13fedora kernel [26782.638621] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x7010 with error -71.
May 3 161128 mp13fedora kernel [26782.659186] phy1 -> rt2x00usb_vendor_request Error - Vendor Request 0x07 failed for offset 0x7010 with error -71.


I'll post again tomorrow and let everyone know how I get on with the latest serialmonkey tree.

Cheers
Mark

MarkP

04-05-2011 17:34:18

I've updated to the serialmonkey tree as of 150719d0aff7460894651808d6a951a87d096c4e "rt2x00 Initial support for RT5370 USB devices." and I think it is now working.

I am using the rt2870.bin from 2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO.

Actually I ran into problems with the graphics driver in the serialmonkey kernel - the monitor probe was failing, and hence the resolution was being limited to 1024x768 and was all blury....

I am currently running/testing using the latest 2.6 development kernel as of 609cfda586c7fe3e5d1a02c51edb587506294167 "Merge branch 'stable/bug-fixes-for-rc5' of git//git.kernel.org/pub/scm/linux/kern ... konrad/xen" but with all the serialmonkey changes (up to the one mentioned earlier) merged in (and a couple of Fedora 14 graphics card hacks).

This appears to be working well, though feels rather "bleeding edge".

Many thanks everyone for your help.
Cheers
Mark