Ralink rt2870 wifi support?

g_willikers said:
Greetings,
If the forums offered an "EDIT" button, I would have simply appended this to my last post,
but...

Anyway, here is the INF file from the Windows driver for the ENCORE ENUWI-N3 that uses the
RALINK rt2870 chipset.

SEE ATTACHED

--Chris

Please post here the output of the following command:

Code:
# usbconfig  dump_device_desc

I added new USB Ralink device. If you have Ralink RT2870 USB device 0x148F:0x2870 then it should work now. Check GIT repository again.
 
Greetings egorenar, and thank you for your response.
egorenar said:
Please post here the output of the following command:

Code:
# usbconfig  dump_device_desc
I already provided the output of that command, as well as some others in my post just before
the post you are replying to (this one) :)

egorenar said:
I added new USB Ralink device. If you have Ralink RT2870 USB device 0x148F:0x2870 then it should work now. Check GIT repository again.
I'll have a look. I'm not sure how to find the hex number - I'll see if it's in dmesg || messages.

Thank you for all your time and consideration.

--Chris
 
g_willikers said:
Greetings egorenar, and thank you for your response.

I already provided the output of that command, as well as some others in my post just before
the post you are replying to (this one) :)


I'll have a look. I'm not sure how to find the hex number - I'll see if it's in dmesg || messages.

Thank you for all your time and consideration.

--Chris

After running

Code:
usbconfig  dump_device_desc

you will see the hex numbers :)
 
Greetings egorenar,
Sorry I produced the output for the prior post. But forgot to paste it in - DO'H!

OK here it is:
Code:
[b]# usbconfig[/b]
[color="Teal"]## checkout of HEAD-2001-03-26[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.3: <JD FireFly Lexar> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

Code:
[b]# usbconfig[/b]
[color="Teal"]## checkout of HEAD-2001-04-06[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.3: <JD FireFly Lexar> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

I checked out your most recent version of HEAD,
I kldunloaded the prior version, deleted them from /boot/modules && /boot/kernel,
unpacked the new version, built it, copied rt2870.ko && rt2870.ko.symbols to:
/boot/modules && /boot/kernel, kldloaded it kldstat indicated it was loaded fine.
So I bounced the box with the rt2870_load="YES" in loader.conf && the necessary
entries in rc.conf. But no joy. Only a terse entry in /var/log/messages - no more.

Is there anything else I can do that may help to make this work?

Thank you very much egorenar, for all your time and consideration.

--Chris
 
I have unpacked the rt2870.sys file into it's individual components...

The tree consists of
Code:
.rsc   D   1,556
.text  F 614,514
.rdata F  34,752
.data  F  54,944
INT    F   2,500
.reloc F   9,678
------------------------
contents of .rsc
MOFDATA D 648
VERSION D 908
------------------------
contents of .rsc/MOFDATA
NDISMOFRESORCE F 648
------------------------
contents of .rsc/VERSION
1              F 908

I can upload the individual items within the rt2870.sys file, or I can pack the .sys file
and upload it. But because of the size limits imposed in these forums, I will need to
pack it into volums (segments) which will automatically find each other when unpacked.
Thereby returning into it's original form.
If this would be of any help. Please let me know, and I'll upload it/them into any form
that would be useful.

Thanks again.

--Chris
 
g_willikers said:
Greetings egorenar,
Sorry I produced the output for the prior post. But forgot to paste it in - DO'H!

OK here it is:
Code:
[b]# usbconfig[/b]
[color="Teal"]## checkout of HEAD-2001-03-26[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.3: <JD FireFly Lexar> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

Code:
[b]# usbconfig[/b]
[color="Teal"]## checkout of HEAD-2001-04-06[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.3: <JD FireFly Lexar> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

I checked out your most recent version of HEAD,
I kldunloaded the prior version, deleted them from /boot/modules && /boot/kernel,
unpacked the new version, built it, copied rt2870.ko && rt2870.ko.symbols to:
/boot/modules && /boot/kernel, kldloaded it kldstat indicated it was loaded fine.
So I bounced the box with the rt2870_load="YES" in loader.conf && the necessary
entries in rc.conf. But no joy. Only a terse entry in /var/log/messages - no more.

Is there anything else I can do that may help to make this work?

Thank you very much egorenar, for all your time and consideration.

--Chris

You should post the output of the command with parameter or else i cannot see vendor and product id.

Code:
# usbconfig  dump_device_desc
 
egorenar said:
You should post the output of the command with parameter or else i cannot see vendor and product id.

Code:
# usbconfig  dump_device_desc

Sorry, I didn't see the "dump_device_desc" in the man pages, and wasn't thinking. :r
Sorry for the bother.

Here is the information:
Code:
[b]usbconfig dump_device_desc[/b]
[color="Teal"]## AFTER checkout of HEAD-2001-04-06[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0000
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x203d
  idProduct = 0x1480
  bcdDevice = 0x0101
  iManufacturer = 0x0001  <Ralink>
  iProduct = 0x0002  <802.11 n WLAN>
  iSerialNumber = 0x0003  <1.0>
  bNumConfigurations = 0x0001

Again, sorry for the bother, and thank you very much for all your time and consideration.

--Chris
 
g_willikers said:
Sorry, I didn't see the "dump_device_desc" in the man pages, and wasn't thinking. :r
Sorry for the bother.

Here is the information:
Code:
[b]usbconfig dump_device_desc[/b]
[color="Teal"]## AFTER checkout of HEAD-2001-04-06[/color]
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0000
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x203d
  idProduct = 0x1480
  bcdDevice = 0x0101
  iManufacturer = 0x0001  <Ralink>
  iProduct = 0x0002  <802.11 n WLAN>
  iSerialNumber = 0x0003  <1.0>
  bNumConfigurations = 0x0001

Again, sorry for the bother, and thank you very much for all your time and consideration.

--Chris

Code:
idVendor = 0x203d
idProduct = 0x1480

I think it has rt3070 chip and not rt2870. Try "run" driver, i think it supports your device.
 
egorenar said:
Code:
idVendor = 0x203d
idProduct = 0x1480

I think it has rt3070 chip and not rt2870. Try "run" driver, i think it supports your device.

Thank you very much egorenar, for all your help.
I will give that a try. FWIW the Windows boxen that I'm using this on, installed
and is using the rt2870.sys driver that the CD for the dongle installed. I looked
at attempting to dis-assemble the dongle. But they've done a very good job of
sealing it (better than most). So I'm afraid that I might damage the antenna if I
try to dis-assemble it.

In any case, I'll try the "run" driver, and report back with my findings.

Thank you again egorenar, for all your time and consideration.

--Chris (g_willikers)
 
g_willikers said:
Thank you very much egorenar, for all your help.
I will give that a try. FWIW the Windows boxen that I'm using this on, installed
and is using the rt2870.sys driver that the CD for the dongle installed. I looked
at attempting to dis-assemble the dongle. But they've done a very good job of
sealing it (better than most). So I'm afraid that I might damage the antenna if I
try to dis-assemble it.

In any case, I'll try the "run" driver, and report back with my findings.

Thank you again egorenar, for all your time and consideration.

--Chris (g_willikers)

@egorenar
Thank you! :beer:beer:beer
It turns out that your suggestion was the "magic" - at least making/loading the driver
shows my dongle:
Code:
[b]# kldload runfw[/b]
firmware: 'runfw' version 1: 8192 bytes loaded at 0xc2c9054c
and
Code:
[b]# kldload if_run[/b]
run0: <1.0> on usbus0
run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address XX:XX:XX:XX:XX:XX
run0: firmware RT2870 loaded
run0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
run0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36M
bps 48Mbps 54Mbps
where XX:XX:... was the address (masked by XX)

Thank you again for all your time and consideration - I really appreciate it.

--Chris
 
Eee pc 901, FreeBSD 8.0-STABLE, last rt2860 driver

Dmesg
Code:
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
After that sometimes (when transfer much information), wlan0 down and, then, imidiatly, up. This leads to the fact that the network falls but routes (netstat -n -r) is ok (needs to dhclient wlan0 to network up).
 
nirnr00t said:
Eee pc 901, FreeBSD 8.0-STABLE, last rt2860 driver

Dmesg
Code:
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
rt28600: Tx watchdog timeout: resetting
After that sometimes (when transfer much information), wlan0 down and, then, imidiatly, up. This leads to the fact that the network falls but routes (netstat -n -r) is ok (needs to dhclient wlan0 to network up).

I need more information in order to fix this.
What were you doing before you got these messages ?
Did it happen often ?
 
I can do what you want to get information :)
After start I get from router (ifconfig_wlan0="DHCP WPA") ip. Than i start firefox and serf some pages (much trafic). Than i read it (0 trafic) and try to load another pages but fail.
Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
Ok, we retry (dhclient wlan0) and continue surf but at random (1-10 min) netfork fail again. In ifconfig network status stay "associated"
I try to repeat it by console login and ping -c 500 host, but no luck. Probably, it depends of hight load.
Kern without polling.
 
Discover some info:
Die to calcru problem, i was replaced default timecounter with TSC. Now i get back to standard and (get the calcru: went backward message :) )problem with driver appears less (in 8-10 min).
Now problem look that: same time after load, when net load is 0, network desapears. It follows by messages "rx watchdog timeout..." and "wlan down, wlan UP" Routes ok, ifconfig associated, but ping to default host fails. If start ping, nothing no conclusions on the screen. After aprox. 30 seconds network up, ping get 3-4 mess "no route to host" and get ok.
What command to compile driver with max debug options?
 
nirnr00t said:
Discover some info:
Die to calcru problem, i was replaced default timecounter with TSC. Now i get back to standard and (get the calcru: went backward message :) )problem with driver appears less (in 8-10 min).
Now problem look that: same time after load, when net load is 0, network desapears. It follows by messages "rx watchdog timeout..." and "wlan down, wlan UP" Routes ok, ifconfig associated, but ping to default host fails. If start ping, nothing no conclusions on the screen. After aprox. 30 seconds network up, ping get 3-4 mess "no route to host" and get ok.
What command to compile driver with max debug options?

By default debugging is deactivated.

How to activate debugging:

Code:
# sysctl dev.rt2860.0.debug=<DEBUG_FLAGS>

DEBUG_FLAGS:

RT2860_DEBUG_EEPROM = 0x00000001
RT2860_DEBUG_RX = 0x00000002
RT2860_DEBUG_TX = 0x00000004
RT2860_DEBUG_INTR = 0x00000008
RT2860_DEBUG_STATE = 0x00000010
RT2860_DEBUG_CHAN = 0x00000020
RT2860_DEBUG_NODE = 0x00000040
RT2860_DEBUG_KEY = 0x00000080
RT2860_DEBUG_PROT = 0x00000100
RT2860_DEBUG_WME = 0x00000200
RT2860_DEBUG_BEACON = 0x00000400
RT2860_DEBUG_BA = 0x00000800
RT2860_DEBUG_STATS = 0x00001000
RT2860_DEBUG_RATE = 0x00002000
RT2860_DEBUG_PERIODIC = 0x00004000
RT2860_DEBUG_WATCHDOG = 0x00008000
RT2860_DEBUG_ANY = 0xffffffff

Example: sysctl dev.rt2860.0.debug=0x00000006

0x00000006 = 0x00000002 | 0x00000004          - activates Rx and Tx debugging

You can combine debug flags with each other.

Wireshark logs would be also nice to have.
 
My system FreeBSD 8.0 release
I've bought DLink DWA-525 PCI WIFI card with chipset rt2860

I used Windows drivers from official dlink server
The card works with ndis driver, but HOSTAP mode is not supported

I've download the latest version of the driver rt2870_bsd8 from git, made rt2860.ko and loaded module into kernel, but my card still can't be detected by the system.
Code:
#pciconf -lv
none2@pci0:3:0:0:       class=0x028000 card=0x3c041186 chip=0x30601814 rev=0x00 hdr=0x00
    vendor     = 'Ralink Technology, Corp'
    class      = network

Thank you in advance!
 
qwerty2200 said:
My system FreeBSD 8.0 release
I've bought DLink DWA-525 PCI WIFI card with chipset rt2860

I used Windows drivers from official dlink server
The card works with ndis driver, but HOSTAP mode is not supported

I've download the latest version of the driver rt2870_bsd8 from git, made rt2860.ko and loaded module into kernel, but my card still can't be detected by the system.
Code:
#pciconf -lv
none2@pci0:3:0:0:       class=0x028000 card=0x3c041186 chip=0x30601814 rev=0x00 hdr=0x00
    vendor     = 'Ralink Technology, Corp'
    class      = network

Thank you in advance!

Sorry, but the card has not rt2860 but rt3060 chip. It is not supported by my driver now. Maybe later.
 
egorenar said:
By default debugging is deactivated.

How to activate debugging:

Code:
# sysctl dev.rt2860.0.debug=<DEBUG_FLAGS>

DEBUG_FLAGS:

RT2860_DEBUG_EEPROM = 0x00000001
RT2860_DEBUG_RX = 0x00000002
RT2860_DEBUG_TX = 0x00000004
RT2860_DEBUG_INTR = 0x00000008
RT2860_DEBUG_STATE = 0x00000010
RT2860_DEBUG_CHAN = 0x00000020
RT2860_DEBUG_NODE = 0x00000040
RT2860_DEBUG_KEY = 0x00000080
RT2860_DEBUG_PROT = 0x00000100
RT2860_DEBUG_WME = 0x00000200
RT2860_DEBUG_BEACON = 0x00000400
RT2860_DEBUG_BA = 0x00000800
RT2860_DEBUG_STATS = 0x00001000
RT2860_DEBUG_RATE = 0x00002000
RT2860_DEBUG_PERIODIC = 0x00004000
RT2860_DEBUG_WATCHDOG = 0x00008000
RT2860_DEBUG_ANY = 0xffffffff

Example: sysctl dev.rt2860.0.debug=0x00000006

0x00000006 = 0x00000002 | 0x00000004          - activates Rx and Tx debugging

You can combine debug flags with each other.

Wireshark logs would be also nice to have.

About a week of debugging get thats not driver problem. And some users report that they, too, is happening it with other wifi drivers (maybe it stack problem). Sorry for the inconvenience.
 
Hallo,

i tried your driver (rt2860) with pfsense (freebsd7.2) works perfectly :)
but there are problems on pfsense 2.0 (freebsd8) I always get kernel panic. So I tried to activate it manually in freebsd-shell:
ifconfig wlan0 create wlandev rt28600 wlanmode hostap
ifconfig wlan0 ssid CLUB channel 5 mode 11g up
the card is active and seems to work. But in this moment I try to connect by wlan-client a kernel-panic happens.
Fatal trap 12: page fault while in kernel mode
Fault code = supervisor read, page not present
And so on…
Can you help me please? :(
 
Anderstend said:
Hallo,

i tried your driver (rt2860) with pfsense (freebsd7.2) works perfectly :)
but there are problems on pfsense 2.0 (freebsd8) I always get kernel panic. So I tried to activate it manually in freebsd-shell:
ifconfig wlan0 create wlandev rt28600 wlanmode hostap
ifconfig wlan0 ssid CLUB channel 5 mode 11g up
the card is active and seems to work. But in this moment I try to connect by wlan-client a kernel-panic happens.
Fatal trap 12: page fault while in kernel mode
Fault code = supervisor read, page not present
And so on…
Can you help me please? :(

Hi, thanks for feedback.

In order to be able to help you, i need more information.
Would you install the kernel debugger on our system. Then you could produce a backtrace for me when a panic happens again and it would help me immensely.

Alex.
 
Back
Top