rt2x00 802.11n devices

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

dch24

23-08-2007 07:10:14

I'm trying to pick up a Ralink 802.11n USB to see what it takes to get it working. Other World Computing is doing a special on Ralink 802.11n PCI/PCMCIA/USB for $59[/url3olwtdvu], so I'm considering buying one.

I'm compiling a list of Ralink 802.11n devices below, linked to the source of the info, with as much detail as I can get. [b3olwtdvu]Note that these are probably not supported by the rt2x00 linux driver yet![/b3olwtdvu] But that support is coming soon.

Some abbreviations from the [url=http://www.ralinktech.com/ralink/data/RT2800.pdf3olwtdvu]Ralink datasheet[/url3olwtdvu]

1T3R = 1 transmitter, 3 receivers
2T3R = 2 transmitters, 3 receivers

RT2800P = PCI / Cardbus, single band (802.11b/g/n), with RT2860 + RT2820
RT2800PD = PCI / Cardbus, dual band (802.11a/b/g/n), with RT2860 + RT2850
RT2800U = USB 1.1/2.0, 802.11b/g/n, with RT2870 + RT2820
RT2800UD = USB 1.1/2.0, 802.11a/b/g/n, with RT2870 + RT2850
RT2800E = PCIe, 802.11b/g/n, with RT2890 + RT2820
RT2800ED = PCIe, 802.11/a/b/g/n, with RT2890 + RT2850

Hardware list[list3olwtdvu][*3olwtdvu][url=http://www.xlr8yourmac.com/feedback/802_11N_Mac_reports.html3olwtdvu]Edimax EW-7708PN[/url3olwtdvu] - Cardbus (PCMCIA)
RT2800P
[/*m3olwtdvu]
[*3olwtdvu][url=http://www.xlr8yourmac.com/feedback/802_11N_Mac_reports.html3olwtdvu]Edimax EW-7728In PCI, or Planex PCI-GW-DS300N, or Quickertek nQuicky PCI[/url3olwtdvu]
RT2800P (lots of rebranding cards that are basically identical) The [url=http://www.edimax.com/images/Image/manual/Wireless/EW-7728In/EW-7728In-v1UserManual.pdf3olwtdvu]user manual for the EW-7728[/url3olwtdvu] says it's Ralink.
[/*m3olwtdvu]
[*3olwtdvu][url=http://www.xlr8yourmac.com/feedback/802_11N_Mac_reports.html3olwtdvu]Edimax EW-7718Un[/url3olwtdvu] - USB
RT2800U
[/*m3olwtdvu]
[*3olwtdvu][url=http://www.asus.com/products.aspx?l1=12&l2=42&l3=137&l4=0&model=1711&modelmenu=23olwtdvu]Asus WL-130N 802.11n PCI[/url3olwtdvu] (specs say Ralink)
RT2800P? (not dual band)
[/*m3olwtdvu]
[*3olwtdvu][url=http://www.xlr8yourmac.com/archives/aug07/082007.html#S231973olwtdvu]Belkin N1 Expresscard[/url3olwtdvu]
Careful - this may be mislabeled as a Ralink chipset, but it's probably Atheros.[/*m3olwtdvu][/listu3olwtdvu]
I looked for a while but didn't find any products that used the dual-band Ralink chips. Maybe some will become available in a while.

IvD

23-08-2007 08:06:39

At the moment there is indeed no rt2800pci or rt2800usb support in rt2x00.

The rt2800pci drivers have just been released under the GPL so work will soon begin to add rt2800pci to the rt2x00 tree. Luis is already working on porting the register definitions.

The rt2800usb drivers have not been released under the GPL yet, but as soon as those are as well work can begin to port it to rt2x00 as well.

Priority at this moment is preparing rt2x00 for the 2.0.8 and 2.1.0 release,
the significance of those 2 release is bringing rt2x00 into the vanilla kernel tree, so that means that I am not adding experimental code in either release. ;)

dch24

23-08-2007 08:17:48

Priority at this moment is preparing rt2x00 for the 2.0.8 and 2.1.0 release, the significance of those 2 release is bringing rt2x00 into the vanilla kernel tree, so that means that I am not adding experimental code in either release.[/quotetnu06fbq]That's what I'd like to work on the most at the moment, also. So, I suppose, this can wait.

It's interesting to look at and think about, though. -) I'm glad Luis is doing it.

zephyr

01-11-2007 14:18:19

I just got an EDIMAX EW-7728In. Haven't tried any drivers for it yet. Please let me know if there is any progress in the 802.11n area. I am more than willing to help test the drivers out. Let me know. BTW... Thank You for these drivers.

Neville

05-11-2007 01:56:43

FYI the NDIS driver that comes with this, presumably the vanilla Ralink driver, works fine with Gutsy/ndiswrapper, but not at 802.11n speeds, at least not with my setup. My guess is other rt2870 devices will behave identically.

Anyway, unlike a lot of the devices this forum is most concerned with, ndiswrapper represents a real option for people wanting to use it.

thorstenhirsch

09-12-2007 01:04:57

Now that rt2x00 has made it into the next kernel, what exactly will be supported? Does 2.6.24 already include support for 802.11n devices (rt2860/70)?

thorstenhirsch

09-12-2007 20:41:07

Today I had some time to check it myself

- kernel 2.6.24-rc4 does not have support for RT2860
- neither does the "hourly tarball" of rt2x00-cvs

But even worse, I cannot compile the original driver from RaLink (version 1.0.4.0)
[code12ciz998][...]
gcc -Wp,-MD,/home/torti/tmp/rt2860/os/linux/../../common/.rtmp_init.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DAGGREGATION_SUPPORT -DPIGGYBACK_SUPPORT -DWMM_SUPPORT -DLINUX -Wall -Wstrict-prototypes -Wno-trigraphs -DCONFIG_STA_SUPPORT -DDBG -I/home/torti/tmp/rt2860/include -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(rtmp_init)" -D"KBUILD_MODNAME=KBUILD_STR(rt2860sta)" -c -o /home/torti/tmp/rt2860/os/linux/../../common/rtmp_init.o /home/torti/tmp/rt2860/os/linux/../../common/rtmp_init.c
gcc -Wp,-MD,/home/torti/tmp/rt2860/os/linux/../../sta/.rtmp_data.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DAGGREGATION_SUPPORT -DPIGGYBACK_SUPPORT -DWMM_SUPPORT -DLINUX -Wall -Wstrict-prototypes -Wno-trigraphs -DCONFIG_STA_SUPPORT -DDBG -I/home/torti/tmp/rt2860/include -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(rtmp_data)" -D"KBUILD_MODNAME=KBUILD_STR(rt2860sta)" -c -o /home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.o /home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.c
/home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.c: In function 'RTMPHardTransmit':
/home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.c:1736: error: 'MAC_TABLE_ENTRY' has no member named 'NonQosDataSeq'
/home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.c:1737: error: 'MAC_TABLE_ENTRY' has no member named 'NonQosDataSeq'
/home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.c:1737: error: 'MAC_TABLE_ENTRY' has no member named 'NonQosDataSeq'
make[2]: *** [/home/torti/tmp/rt2860/os/linux/../../sta/rtmp_data.o] Error 1
make[1]: *** [_module_/home/torti/tmp/rt2860/os/linux] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.23-ARCH'
make: *** [LINUX] Error 2[/code12ciz998]
This is what happens on an up-to-date installation of archlinux/kernel 2.6.23 and also with the previously mentioned self-compiled 2.6.24-rc4. (

Spy84464

10-12-2007 18:58:03

Yes, rt2x00 doesn't support rt2580 yet. You'll have to ask Ralink to fix their driver in the meantime.

thorstenhirsch

11-12-2007 01:42:11

I got response from RaLink. They fixed the driver - or they fixed the link to the driver. Anyway, I can compile the following driver successfully http//www.ralink.com.tw/data/drivers/2 ... .4.0.0.tgz

IvD

01-01-2008 22:03:28

I can now announce that I have started working on rt2860 and rt2870 for rt2x00, they will be named rt2800pci and rt2800usb respectively.

ticjac

20-01-2008 21:57:27

Nice work IvD ;)

I have a D-Link DWA-140 USB Dongle.
DONGLE SPECS
http//www.dlink.com/products/?sec=0&pid=652

The D-Link DWA-140 USB Dongle has a Ralink RT2870 Chipset from Ralink here
http//www.ralinktech.com/ralink/Home/S ... Linux.html

I'm going to install SUSE Linux as a dual operating system om my PC when and if your Passive mode(monitor mode) is ready !?

I'm new to Linux so please guide me when it's finished.

Cheers ;)Ticjac

bonekracker

26-01-2008 04:58:47

Greetings.

I just got a "Belkin N Wireless USB Adapter" (F5D8053).

I have not found any useful documentation for the device.
http//www.belkin.com/support/product/? ... id=F5D8053

Based on the Windows drivers provided with the product, though, it is based on the RT2870.

Looking forward to helping test, etc.

Linkin

15-02-2008 15:17:43

I've got some trouble installing the driver for my D-Link DWA-140 USB Dongle.

I'm trying to build the latest beta but it doesn't compile. I did it with 2800usb=y and rt2x00=y and everything else to n but it fails.

Is there something I should take care of?

Thanks

IvD

15-02-2008 15:21:35

First off it is usually a good idea to post compilation errors instead of saying "it is broken". But in this case

There isn't much to see or test for the rt2800 drivers. They are still under development and most of the driver isn't implemented yet.

Linkin

15-02-2008 17:28:52

First off it is usually a good idea to post compilation errors instead of saying "it is broken". But in this case

There isn't much to see or test for the rt2800 drivers. They are still under development and most of the driver isn't implemented yet.[/quote1ozpjrgr]

Sorry I was in a hurry so I didn't post the exact error messages and It didn't seem to be relevant either.

I just hoped I forgot to trigger something in the config ). How is the progress on the driver so far?

IvD

15-02-2008 18:19:34

Well recent problems with rt2x00 prohibited me from working on rt2800 drivers.
Today I have spend a good amount of time on it, and I think it goes reasonably well although I haven't worked on the more tricky parts yet (register initialization).

Linkin

16-02-2008 12:32:04

That's great! I would love to help you in some way. Maybe you need someone for testing? Just let me know )

underplay

17-02-2008 09:55:16

IvD, Im glad you are working on this chipset, currently it is the only thing holding me back from moving back to the Linux kernel, just like Linkin I would be glad to help you test this out when you need me too. I know you are a busy guy but I have some questions im hoping you can answer.

1) Will there be injection support?

2) Will there be x64 support or is that just up to a compiler flag that will automatically convert the definitions on compile?

3) Im an amateur C++ coder, can you point me to some learning material about developing drivers for hardware under Linux, I would use google but im hoping someone like you can point me to some more specific information. I would like to experiment a bit and see if I can help speed up the development process.

Thanks.

IvD

17-02-2008 10:37:00


1) Will there be injection support?
[/quote28pbhttr]

This feature depends on mac80211. When mac82011 starts supporting injection mode, then rt2x00 supports it as well.


2) Will there be x64 support or is that just up to a compiler flag that will automatically convert the definitions on compile?
[/quote28pbhttr]

All rt2x00 drivers support 64bit


3) Im an amateur C++ coder, can you point me to some learning material about developing drivers for hardware under Linux, I would use google but im hoping someone like you can point me to some more specific information. I would like to experiment a bit and see if I can help speed up the development process.
[/quote28pbhttr]

http//kernelnewbies.org/KernelHacking

Linkin

17-02-2008 12:06:33


1) Will there be injection support?
[/quote3nkds1dp]

This feature depends on mac80211. When mac82011 starts supporting injection mode, then rt2x00 supports it as well.


2) Will there be x64 support or is that just up to a compiler flag that will automatically convert the definitions on compile?
[/quote3nkds1dp][/quote3nkds1dp]

I thought that there is injection support in mac80211 http//www.mjmwired.net/kernel/Document ... ection.txt

IvD

17-02-2008 12:31:25

Well in that case rt2x00 supports injection mode ;)

underplay

17-02-2008 19:46:08

Awesome, thanks IvD.

ticjac

25-02-2008 21:46:07

Hi,

As I stated before I have a D-link DWA-140 USB dongle(RT2870 chipset), and I like to know whats the best linux OS and kernel for me when I beginn testing your driver.

For a few weeks ago I installed the latest Backtrack on VMware-workstation in winxp and it worke fine. The latest BackTrack 3 Beta actually found my USB network card, but I also tested the Ralink driver
I found here
http//www.ralinktech.com/ralink/Home/S ... Linux.html
I dont know much linux so I found out how to install the Ralink linux driver and it also seems to work fine. But of course it did not work in any monitor mode as far as I tested a few commands
Then I had some other problem with my Winxp pro so I just formatet the disk.


I now beginn a new clean install and like to know whats the best working environment for your driver. I also need to know if I have to have the linux Kernel 2.6.24 to do this ? Is Backtrack 3 beta having this Kernel ?
I have also installed Suze linux a couple for times before, so if anyone can
help or guide me please do. Thanks in advance.

IvD

25-02-2008 22:07:06

Let me say this again
rt2800pci and rt2800usb driver inside the rt2x00 package are still under development. At the moment they are not fully developed yet, and they can't be tested at the moment.
They are currently in the cvs repository for backup purposes only, and in no way meant for compilation or testing.
When those 2 drivers have been completed and they are ready for testing I will announce that on this forum and on the website.
Until that moment, using the drivers from the Ralink website is the only option (which also means that getting support for those drivers are to be requested on the Ralink website).

ticjac

25-02-2008 23:28:19

Thanks IvD. I have understood this, but I'm only try to get ready with the(a) OS before the driver is finished on whatever time. I also have to learn me some more linux in the meantime I guess.!

PS If you "Linkin" se this, maby you could help me. You also got the same USB dongle that I have (D-link DWA-140 (RT2870)) ?

kurt2

29-04-2008 16:21:27

I have been using Debian Lenny Kernel 2.6.24-1-686 and I compiled and installed the ralink 2860 module and iwconfig shows ra0, however just above the ra0 interface in the iwconfig output it shows the following

[quote2d27ipxt]Driver for device ra0 has been compiled with an ancient version of Wireless Extension, while this program support version 11 and later. Some things may be broken...[/quote2d27ipxt]

do you guys get this same message when you compile your ralink drivers from the ralink website? and if not do you know of a fix, because my wireless extensions are the latest version, not ancient at all, its as if the ralink drivers refuse to use them though.

IvD

29-04-2008 16:50:52

We don't provide support for drivers that are not released as part of this project.

bonekracker

13-06-2008 01:49:32

Ivo,

What is your best guess on when 2800-series will be supported in 2X00?
(If it matters, specifically 2870).

Thank you.

Linkin

03-07-2008 12:33:48

I'm very curious about it too.

I know that you said we all will know that its ready when you announce it but I just want to ask you about the progress.

Its because of the official drivers from Ralink are actually not that easy to set up. I still have not succeeded yet to get them working right.

Please give us a hint about the status of your rt2870 implementation so that I know if its worth the hassle with the official driver.

IvD

03-07-2008 15:46:38

I have just send this email to the rt2400-devel and linux-wireless mailinglists.

[quoteqjc6jlyo]
Hi,

I have promised time and time again work for rt2860/rt2870 is underway,
and although rt2x00.git contained a base for this work for quite some time
already, development of those drivers have been halted during the past
months.

I can now announce that as of next week the real development on rt2800
will begin. The current base will be refactored for the past changes in rt2x00
(like the recent DMA changes), and will be extended afterwards.

This also means rt2x00lib will be updated for 802.11n support, and the
current HW crypto implementation must be tested to see if at least the
rt2x00lib part of that code is correct so it can be used for rt2800 safely.

The goal will be to have a testable driver before the end of this month,
and hopefully a stable driver early September. Plans for kernel integration
can be made when the driver is under testing, so I won't make any
speculations about that right now.

Ivo
[/quoteqjc6jlyo]

Linkin

04-07-2008 10:16:28

That is great news! Thanks! D

kurt2

04-07-2008 19:45:10

awesome! D

falcoman

22-08-2008 23:27:08

hello
sorry for my bad english. I want to buy a dlink DWA140 dongle usb ( rt2870).

Is there a driver will be available soon for linux ubuntu or backtrack distribution?

Injection Mode and monitor mode will be available ?

is it a good chose to buy this dongle for linux? i want a n device.

Thanks you

Spy84464

25-08-2008 18:09:10

Hello,
work is still is progress, and yes monitor and injection will be supported. Do not expect the driver to be shipped by any distribution soon though, as it will only happen with the release of kernel 2.6.28, at least (if I am not mistaken).
Ralink provides driver in the meantime, but we don't support them, and I don't know how well they perform. The decision is really up to you, and how hurry you are.

Regards,
Romain

eth0

25-08-2008 19:40:34

I'm currently using the rt2860sta (pci device) and its working fine...
connection single isn't as strong in the exact same location as under windows though.

I did have problems with WPA but I forget to set the flags before compiling.

There is no injection atm though (

So i'm looking forward to the rt2x00 drivers if they are ever released )

billgzzz

29-08-2008 18:00:39

Hello,
work is still is progress, and yes monitor and injection will be supported. Do not expect the driver to be shipped by any distribution soon though, as it will only happen with the release of kernel 2.6.28, at least (if I am not mistaken).
Ralink provides driver in the meantime, but we don't support them, and I don't know how well they perform. The decision is really up to you, and how hurry you are.

Regards,
Romain[/quote1bzcdupy]
[b1bzcdupy]
Any news on the beta version and the progress?[/b1bzcdupy] [i1bzcdupy]lots of people with the newest eee pc's 901/1000 are waiting for this driver (rt2860 patched)
[/i1bzcdupy]

[b1bzcdupy]Keep Up.
Thank you guys wink [/b1bzcdupy]

Spy84464

30-08-2008 17:57:01

Here is the latest message Ivo posted on the list
[quote1f6vcmcb]Hi,

Several weeks after the deadline for the initial rt2800 version,
I regret to inform everybody that I still do not have a working driver.

rt2800pci is still incomplete since I have put a lot of focus on the rt2800usb
driver to get at least a single working driver out. Unfortunately rt2800usb
remains very stubborn and refuses. The only success I have had so far is
when I first load the legacy driver and switch to rt2800usb afterwards.
This means I am missing a register initialization or there is a problem with
the register initialization ordering.

The result is that it looks like I will cancel all previously announced deadlines,
and at this time can't give a indication when the first version can be released.
What I can promise is that rt2800usb will be released first, since that driver is most
complete, and I am putting all focus on that driver first.

Ivo[/quote1f6vcmcb]
I suggest you subscribe to the list if you want to be kept informed about the latest status of that driver.

billgzzz

31-08-2008 01:21:24

too bad cry

Any link of the latest status would be helpful.I cant find the link ?

Spy84464

06-09-2008 21:02:37

Which link? To the lists? Here it is [url33rvdl56]http://sourceforge.net/mail/?group_id=107832[/url33rvdl56].

Vuslat

07-09-2008 23:03:52

Hello,
work is still is progress, and yes monitor and injection will be supported. Do not expect the driver to be shipped by any distribution soon though, as it will only happen with the release of kernel 2.6.28, at least (if I am not mistaken).
Ralink provides driver in the meantime, but we don't support them, and I don't know how well they perform. The decision is really up to you, and how hurry you are.

Regards,
Romain[/quote2yr3zy0g]
[b2yr3zy0g]
Any news on the beta version and the progress?[/b2yr3zy0g] [i2yr3zy0g]lots of people with the newest eee pc's 901/1000 are waiting for this driver (rt2860 patched)[/color2yr3zy0g]
[/i2yr3zy0g]

[b2yr3zy0g]Keep Up.
Thank you guys wink [/b2yr3zy0g][/quote2yr3zy0g]

Yes thats right there's a large eee community which r waiting for the rt2860 injection mode..great project guys!!

Linkin

09-09-2008 14:33:00

[quotew39o3ep9]
What I can promise is that rt2800usb will be released first, since that driver is most
complete, and I am putting all focus on that driver first.[/quotew39o3ep9]

Awesome! Cant wait to try my D-Link rt2800usb device D

Flam9

12-09-2008 16:19:16


Yes thats right there's a large eee community which r waiting for the rt2860 injection mode..great project guys!![/quote21426rkd]


+1 waiting on a driver update to fix injection on my Eee PC 1000h /
I'll even donate 20$ if it makes the process faster...

summy73

25-09-2008 14:03:00

about rt2860 me too... my brand new 901 is so sad about this!!!!! please help him feel happier )))

DasWiesel

26-09-2008 11:26:38

about rt2860 me too... my brand new 901 is so sad about this!!!!! please help him feel happier )))[/quote1a6npetd]

me too.
looking every day for news...

summy73

01-10-2008 08:26:11

Any news?? how is the work in progress of the rt2860 pathed drivers?

thnks

Summy

DasWiesel

03-10-2008 11:55:06

I found nothing.
IvD can you give us some news?

AdamBaker

03-10-2008 20:27:38

You picked the right day to ask - Mattias Nissler has just posted a series of patches that get rt2800usb closer to a working state. Scan now works but there are still unexplained error messages on Rx and problems on Tx.

summy73

03-10-2008 21:14:22

where can i found? thnks

AdamBaker

04-10-2008 22:58:31

The progress statement is at
http//sourceforge.net/mailarchive/foru ... 2400-devel

If you go back from there to the mailing list you'll see the 5 required patches but it looks like Ivo has already pulled them into the experimental branch in git which is what you need to be using if you want to hack on this code (and if you don't feel up to hacking on the code then it won't be much use to you yet).

summy73

10-10-2008 07:46:20

will the new patched 2860 driver be included in ubuntu 8.10 at the end of the month?

Andy

IvD

10-10-2008 13:54:02

will the new patched 2860 driver be included in ubuntu 8.10 at the end of the month?

Andy[/quote2v03bp2q]

You need to ask Ubuntu if they are going to ship it.
But this project [b2v03bp2q]HAS NOT RELEASED ANY RT2860/RT2870 DRIVER YET[/b2v03bp2q]

summy73

10-10-2008 14:16:46

yes i know is not released yet, but hope it will be released soon.. so many eeepc901 users like me r waitin )

m4rtin

14-10-2008 10:14:22

am I right, that all EEE PC 1000H netbooks have rt2860 chipset? And did the older EEE PC's have Atheros chipsets?

corpcd

17-10-2008 07:38:07

am I right, that all EEE PC 1000H netbooks have rt2860 chipset? And did the older EEE PC's have Atheros chipsets?[/quotevuo5myh1]

As far as I know, eeepc 901 and 1000 uses the Ralink rt2860 chipset wifi with 'n' support, but the old series 701 uses an Atheros based chipset, which is supported by the madwifi drivers.

I am another guy waiting for the release, but let the experts take his time.
corp

ajes

01-11-2008 19:35:01

Hi
MSI WIND U100 users with RT2700E chipset also waiting for support )

Best regards

lornz

02-11-2008 22:02:44

It would be awesome, if packet injection would work with the eeePC 1000h -/

dmoerner

04-11-2008 06:21:03

Very nice work on the rt2800pci driver in the experimental branch of your git repository. It's nice to see it pick up the wlan0/wmaster0 and be able to minimally associate with iwconfig. Of course, it reliably panics with modprobe -r rt2800pci && modprobe rt2800pci or with wpasupplicant, but that's to be expected at this stage.

IvD

04-11-2008 18:42:43

It's nice to see it pick up the wlan0/wmaster0 and be able to minimally associate with iwconfig. [/quote207k3wuk]

Ehm rt2800pci isn't capable of scanning or associate at this point...


Of course, it reliably panics with modprobe -r rt2800pci && modprobe rt2800pci or with wpasupplicant, but that's to be expected at this stage.[/quote207k3wuk]

Could you post the stacktrace of the panic?

dmoerner

04-11-2008 23:12:35

It's nice to see it pick up the wlan0/wmaster0 and be able to minimally associate with iwconfig. [/quote28c53jtb]

Ehm rt2800pci isn't capable of scanning or associate at this point...
[/quote28c53jtb]

I just mean that it didn't panic on iwconfig wlan0 essid network, and subsequent iwconfigs showed wlan0 as associated with the network.



Of course, it reliably panics with modprobe -r rt2800pci && modprobe rt2800pci or with wpasupplicant, but that's to be expected at this stage.[/quote28c53jtb]

Could you post the stacktrace of the panic?[/quote28c53jtb]

The system is experiencing hard lockups, with no possible input received. This is reproducible by restarting network and bringing wlan0 up (/etc/init.d/networking force-reload && ifup wlan0) on Debian Sid. The watchdog timer, when I turn it on, definitely picks it up and restarts, but how can I get a stack trace from this? Sorry to be ignorant, but are there any links that would explain how to extract that data?

IvD

04-11-2008 23:15:49

Ok, never mind. I have received help for the rt2800pci driver, and he is finishing the last pieces of missing code hopefully with those pieces filled in the crash will disappear as well.

ticjac

20-11-2008 15:51:57

Hi,

I finally managed to find a RT2870 Chipset modified(support Monitoring an Injection mode ) driver here

http//hirte.aircrack-ng.org/rt2870-2.6 ... te.tar.bz2

It seems to support Monitoring an Injection mode they say.

Taken from this forum post
http//tinyshell.be/aircrackng/forum/in ... 0#msg24840


As stated before I have a D-link DWA-140 (USB Dongle)

THE USB DONGLE SPECS
http//www.dlink.com/products/?sec=0&pid=652

The D-link DWA - 140 has a Ralink RT2870 Chipset

The original driver is located here(have not used(tryed) it for this installasion)
http//www.ralinktech.com/ralink/Home/S ... Linux.html

I want to install this driver
http//hirte.aircrack-ng.org/rt2870-2.6 ... te.tar.bz2

but it does not want to install correct ?

Now I have been sitting here trying to install the driver fore several days. I have tried several solutions on the Internet but nothing seems to work. Would you please help ?
I am using the latest Ubuntu 8.10 version with default install. Have installed it successfully in winxp with VMware 6. The network connection also works but I'am not sure which driver it uses.
Anyway after unpaking the driver and running make && make install I got this

fred@fred-desktop/media/disk/rt2870-2.6.25-hirte/rt2870$ make && make install
make -C tools
make[1] Entering directory `/media/disk/rt2870-2.6.25-hirte/rt2870/tools'
gcc -g bin2h.c -o bin2h
make[1] Leaving directory `/media/disk/rt2870-2.6.25-hirte/rt2870/tools'
/media/disk/rt2870-2.6.25-hirte/rt2870/tools/bin2h
cp -f os/linux/Makefile.6 /media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/Makefile
make -C /lib/modules/2.6.27-7-generic/build SUBDIRS=/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux modules
make[1] Entering directory `/usr/src/linux-headers-2.6.27-7-generic'
CC [M] /media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.o
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c In function 'rt_ioctl_giwscan'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1413 warning passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1413 warning passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1413 warning passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1413 error too few arguments to function 'iwe_stream_add_event'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1425 warning passing argument 1 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1425 warning passing argument 3 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1425 warning passing argument 4 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1425 error too few arguments to function 'iwe_stream_add_point'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1448 warning passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1448 warning passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1448 warning passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1448 error too few arguments to function 'iwe_stream_add_event'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1464 warning passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1464 warning passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1464 warning passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1464 error too few arguments to function 'iwe_stream_add_event'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1475 warning passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1475 warning passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1475 warning passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1475 error too few arguments to function 'iwe_stream_add_event'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1489 warning passing argument 1 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1489 warning passing argument 3 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1489 warning passing argument 4 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1489 error too few arguments to function 'iwe_stream_add_point'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1515 warning passing argument 1 of 'iwe_stream_add_value' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1515 warning passing argument 4 of 'iwe_stream_add_value' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1515 warning passing argument 5 of 'iwe_stream_add_value' makes pointer from integer without a cast
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1515 error too few arguments to function 'iwe_stream_add_value'
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1543 warning passing argument 1 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1543 warning passing argument 3 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1543 warning passing argument 4 of 'iwe_stream_add_point' from incompatible pointer type
/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.c1543 error too few arguments to function 'iwe_stream_add_point'
make[2] *** [/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux/../../os/linux/sta_ioctl.o] Error 1
make[1] *** [_module_/media/disk/rt2870-2.6.25-hirte/rt2870/os/linux] Error 2
make[1] Leaving directory `/usr/src/linux-headers-2.6.27-7-generic'
make *** [LINUX] Error 2
fred@fred-desktop/media/disk/rt2870-2.6.25-hirte/rt2870$

As you see there are many Warnings and some errors. After this I have also tried to change some settings I found on the internet in the installation folders files and installed ndiswrapper
but without any luck ?

If Any clue at all ,please I am almost a newbie at linux so please any solution in newbie terms language ?

Thanks in advance

IvD

20-11-2008 19:16:34


but it does not want to install correct ?

Now I have been sitting here trying to install the driver fore several days. I have tried several solutions on the Internet but nothing seems to work. Would you please help ?
[/quote38pemowm]

Would it not be more logical to request support on the website where you DOWNLOADED the driver instead of on the project website which has NOT YET released the driver?

ticjac

20-11-2008 19:53:18





Would it not be more logical to request support on the website where you DOWNLOADED the driver instead of on the project website which has NOT YET released the driver?[/quote1pg8j5jm]

I have requested it on other forum, but the point is that as more people who see this, as more are the chances that someone know a solution to the problem. Thank you !?

IvD

20-11-2008 19:58:51

Well as long as you are not going to complain that none of the project developers will provide support...

cubi

21-11-2008 15:01:02

hello IvD,
do you have any kind of information related to an alpha/beta release, or even a roadmap? ;)
greetings,
cubi

IvD

21-11-2008 19:10:42

hello IvD,
do you have any kind of information related to an alpha/beta release, or even a roadmap? ;)
greetings,
cubi[/quote2tzjahtg]

As mentioned several times already, but apparently for most users unacceptable There is no schedule for the rt2800 release. It is work in progress and all previously existing release schedules have been dropped.

manuel700000

24-11-2008 14:25:18

Hi.

I have a Ralink 2860.
Is it possible to use your 2870 driver modified?

How Can I use it? oops

Regards.

IvD

24-11-2008 14:35:26


I have a Ralink 2860.
Is it possible to use your 2870 driver modified?
.[/quotecgfufvai]

No a USB driver won't work for PCI hardware.

manuel700000

24-11-2008 16:48:04

I have 2860 to pci
2870 driver is for usb? roll

Regards

IvD

24-11-2008 18:03:25

I have 2860 to pci
2870 driver is for usb? roll
[/quotel7qxrgic]

yes

oget

01-12-2008 22:23:40


As mentioned several times already, but apparently for most users unacceptable There is no schedule for the rt2800 release. It is work in progress and all previously existing release schedules have been dropped.[/quote29h7tgyg][/quote29h7tgyg]
Hi,
I think if you periodically report on how much progress is made and how much work is to be done, people wouldn't ask so many questions.
This thread was opened more than 14 months ago.
July 3rd 2008, a developer says the development of the driver will begin in a week.
On the mailing list I see that the last post on this subject was about 2 months ago.
This is an open source project. Please don't be ashamed to say "No we didn't have time to do any progress in the last X weeks. We were busy/ we didn't have the motivation, send us some beer."
People are wondering if this project will ever make a release, if it is going to merge the mainstream kernel etc.
In my opinion, there is no need to hide this information. Even if you'd say "Don't expect any release in the next 3 years", it is still better than not saying anything.

Regards

IvD

03-12-2008 19:41:34

The problem with that is, that I would spend more time posting messages about "no progress with bug X", "no progress with Feature Y", etc etc then I would spend on developing. There is only 1 person working on rt2x00 and more then enough features and bugs where people are complaining that is taking too much time before it is released.

And saying "this feature will come after x weeks" is the same as having an actual schedule, which I already stated multiple times now, that I do not have.

This discussion is in my eyes quite pointless, since I am constantly repeating myself. So count me out of the rest of the discussion, that way I can focus on more important things then reassuring users.

IvD

14-12-2008 20:59:19

[quote29tkgnvo]
Hi,

It has been a while since the last official rt2800 update, but here it finally is.

I have a new release schedule for rt2800, it is quite short but I think people
do want to know this

        December 20 Move rt2800pci/rt2800usb into rt2x00.git master branch

The drivers are not ready for usage yet, in fact at the moment rt2800pci will
print lots of error messages into your logfile, while rt2800usb simply breaks
down when you bring the interface up.

But the important thing is that the code itself is completed, the only 2 features
which are missing are Powersaving and Aggregation support. But for the initial
release I don't think those features will be critical.

For the people interested in the regular release cycle
        On December 20th I will also release rt2x00 2.3.0
        This release will include the following new features
                power saving support
                Mesh support
                WDS support
                rfkill support for rt2500usb/rt73usb

Ivo
[/quote29tkgnvo]

bonekracker

15-12-2008 15:37:51

Excellent!

Thank you for your work on this, Ivo.

IvD

20-12-2008 10:06:27

[quote1dip8afi]rt2800pci and rt2800usb have been promoted to the rt2x00.git master branch.
With a lot of help from Luis both rt2800pci and rt2800usb have made a lot of
progress this week. Overall the drivers are not very usable, but neither caused
any crashes or system hangs when the interface was brought up.

Ivo[/quote1dip8afi]

corpcd

22-12-2008 12:11:39

Thanks for your work.

corp

Timmes

02-01-2009 23:53:47

Great work! Just testing it out with a Sweex LW302[/url3ox0if5i] card. Doesn't work though, the EEPROM isn't read correctly

[code3ox0if5i][ 10.125205] rt2800pci 0000:00:0b.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 10.131357] phy0 -> rt2800pci_validate_eeprom: EEPROM recovery - MAC: 52:74:72:ed:2e:c3
[ 10.131361] phy0 -> rt2800pci_validate_eeprom: EEPROM recovery - Antenna: 0xf112
[ 10.131363] phy0 -> rt2800pci_validate_eeprom: EEPROM recovery - NIC: 0x0000
[ 10.131367] phy0 -> rt2800pci_validate_eeprom: EEPROM recovery - Freq: 0x8100
[ 10.131372] phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0601, rf: 0001, rev: 00000101.
[ 10.135191] phy0: Selected rate control algorithm 'minstrel'
[ 10.135705] Registered led device: rt2800pci-phy0:radio
[ 10.135723] Registered led device: rt2800pci-phy0:assoc
[ 10.135741] Registered led device: rt2800pci-phy0:quality

[...]

[ 151.335605] phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
[ 151.335613] rt2800pci 0000:00:0b.0: firmware: requesting rt2860.bin
[ 151.382092] phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
[ 151.388522] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 151.390973] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 151.396784] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 151.397286] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 151.397786] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 151.404032] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 151.404040] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 151.404047] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 151.404054] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.[/code3ox0if5i]

Sweex MAC addresses should start with 00160A, the Ralink driver gives the correct MAC, the rt2800pci driver gives a different MAC each time.

lspci -vvv output
[code3ox0if5i]00:0b.0 Network controller: RaLink Device 0601
Subsystem: Z-Com, Inc. Device 0063
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at dffe0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
[/code3ox0if5i]

It'd be real sweet if i could get this to work. Does anyone have a suggestion perhaps?

IvD

03-01-2009 09:52:23

incorrect eeprom reading? hmm that might be interesting. Anybody else with invalid MAC addresses?

IvD

04-01-2009 15:11:04

Managed to reproduce it myself. Fixed in rt2x00.git

Timmes

05-01-2009 22:11:20

( It still refuses to work. The MAC address is read correctly though.

dmesg output
[code6mtbivnx][ 9.582109] rt2800pci 0000:00:0b.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 9.588266] phy0 -> rt2800pci_validate_eeprom: EEPROM recovery - NIC: 0x0000
[ 9.588272] phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0601, rf: 0001, rev: 00000101.
[ 9.591983] phy0: Selected rate control algorithm 'minstrel'
[ 9.592525] Registered led device: rt2800pci-phy0:radio
[ 9.592543] Registered led device: rt2800pci-phy0:assoc
[ 9.592560] Registered led device: rt2800pci-phy0:quality

[...]

[ 10.075668] udev: renamed network interface wlan0 to wlan1

[...]

[ 55.179223] phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
[ 55.179231] rt2800pci 0000:00:0b.0: firmware: requesting rt2860.bin
[ 55.210770] phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
[ 55.217259] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 55.238763] input: rt2800pci as /class/input/input4
[ 55.273623] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 55.300787] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 55.322078] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 55.344065] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x26b7d269
[ 55.372032] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 55.372040] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 55.372047] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[ 55.372054] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
[/code6mtbivnx]

ifconfig output
[code6mtbivnx]wlan1 Link encap:Ethernet HWaddr 00:16:0a:00:ab:6b
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
[/code6mtbivnx]

iwconfig output
[code6mtbivnx]wlan1 IEEE 802.11bgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=6 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0[/code6mtbivnx]

"iwconfig wlan1 mode ...." always fails and "iwlist wlan0 scan" just returns an empty list.

IvD

05-01-2009 22:16:40

iwconfig wlan0 mode.. fails because it _must_ be called while the interface is down.
I am aware of the other issues, and I will look into them.

prahal

06-01-2009 08:12:31

Same issues as above though I add another problem . Kernel crash heppened before latest git when doing modprobe -r rt2800pci; modprobe rt2800pci (without anything in dmesg). I tracked it down to loading the firmware a second time. I don't know if this was supposed to work though I worked around it by adding
[code1thrrr8d]
diff --git a/drivers/net/wireless/rt2x00/rt2800pci.c b/drivers/net/wireless/rt2x00/rt2800pci.c
index 3beb494..39c50f0 100644
--- a/drivers/net/wireless/rt2x00/rt2800pci.c
+++ b/drivers/net/wireless/rt2x00/rt2800pci.c
@@ -1000,6 +1000,9 @@ static int rt2800pci_load_firmware(struct rt2x00_dev *rt2x00dev,
unsigned int i;
u32 reg;

+ if (rt2x00dev->fw != NULL)
+ return 0;
+
/*
* Wait for stable hardware.
*/
[/code1thrrr8d]

I ll post it to the ML properly (with signoff and such) as soon as the two remainings issues are fixed.
That is the ML seems to be broken no access to archive since November and messages I send I do not receive. Maybe an antispam issue though I cannot check as the archive access is broken.

The last issue is that after last git I get this when mdoprobe -r rt2800pci ; modprobe rt2800pci
[code1thrrr8d]
Jan 6 08:31:59 jason kernel: [ 259.236461] ------------[ cut here ]------------
Jan 6 08:31:59 jason kernel: [ 259.236470] WARNING: at fs/sysfs/dir.c:462 sysfs_add_one+0x4a/0x50()
Jan 6 08:31:59 jason kernel: [ 259.236477] sysfs: duplicate filename 'ieee80211' can not be created
Jan 6 08:31:59 jason kernel: [ 259.236483] Modules linked in: cfg80211(+) crc_ccitt eeprom_93cx6 binfmt_misc af_packet i915 drm rfcomm l2cap
parport_pc ppdev parport ipv6 i2c_i801 i2c_core container sbs sbshc pci_slot acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_stats
cpufreq_ondemand cpufreq_userspace iptable_filter ip_tables x_tables speedstep_lib freq_table pciehp joydev arc4 ecb uvcvideo hci_usb compat_io
ctl32 videodev v4l1_compat psmouse bluetooth serio_raw snd_hda_intel rng_core snd_pcm_oss snd_mixer_oss iTCO_wdt iTCO_vendor_support pcspkr snd
_pcm atl1e video output battery snd_seq_oss snd_seq_midi ac snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device eeepc_laptop rfkill
button snd shpchp pci_hotplug soundcore snd_page_alloc intel_agp agpgart evdev ext3 jbd mbcache sg sd_mod pata_acpi ata_generic ata_piix libat
a scsi_mod ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys fuse [last unloaded: eeprom_93cx6]
Jan 6 08:31:59 jason kernel: [ 259.236647] Pid: 6294, comm: modprobe Not tainted 2.6.28-rc9-wl-eeepc-rt2x00-2 #4
Jan 6 08:31:59 jason kernel: [ 259.236654] Call Trace:
Jan 6 08:31:59 jason kernel: [ 259.236666] [<c012ce46>] warn_slowpath+0x76/0x90
Jan 6 08:31:59 jason kernel: [ 259.236677] [<c0226263>] string+0x23/0xa0
Jan 6 08:31:59 jason kernel: [ 259.236686] [<c0220f52>] idr_get_empty_slot+0xf2/0x290
Jan 6 08:31:59 jason kernel: [ 259.236696] [<c022116b>] ida_get_new_above+0x7b/0x190
Jan 6 08:31:59 jason kernel: [ 259.236705] [<c01a7ba1>] find_inode+0x31/0x60
Jan 6 08:31:59 jason kernel: [ 259.236714] [<c01df550>] sysfs_ilookup_test+0x0/0x10
Jan 6 08:31:59 jason kernel: [ 259.236722] [<c01df8a1>] sysfs_find_dirent+0x21/0x30
Jan 6 08:31:59 jason kernel: [ 259.236731] [<c01df8cc>] __sysfs_add_one+0x1c/0x80
Jan 6 08:31:59 jason kernel: [ 259.236740] [<c01df97a>] sysfs_add_one+0x4a/0x50
Jan 6 08:31:59 jason kernel: [ 259.236748] [<c01dfea8>] create_dir+0x48/0x90
Jan 6 08:31:59 jason kernel: [ 259.236757] [<c01dff19>] sysfs_create_dir+0x29/0x50
Jan 6 08:31:59 jason kernel: [ 259.236765] [<c0221c9f>] kobject_get+0xf/0x20
Jan 6 08:31:59 jason kernel: [ 259.236774] [<c0221d7e>] kobject_add_internal+0xce/0x1a0
Jan 6 08:31:59 jason kernel: [ 259.236782] [<c0228a6b>] kvasprintf+0x4b/0x70
Jan 6 08:31:59 jason kernel: [ 259.236790] [<c0221e74>] kset_register+0x24/0x50
Jan 6 08:31:59 jason kernel: [ 259.236818] [<c028bb13>] __class_register+0xc3/0x190
Jan 6 08:31:59 jason kernel: [ 259.236881] [<f84b9150>] cfg80211_init+0x0/0x70 [cfg80211]
Jan 6 08:31:59 jason kernel: [ 259.236895] [<f84b9156>] cfg80211_init+0x6/0x70 [cfg80211]
Jan 6 08:31:59 jason kernel: [ 259.236922] [<c0101126>] do_one_initcall+0x36/0x1b0
Jan 6 08:31:59 jason kernel: [ 259.236950] [<c0187073>] __vunmap+0xa3/0xd0
Jan 6 08:31:59 jason kernel: [ 259.236978] [<c0152d63>] load_module+0x1733/0x1830
Jan 6 08:31:59 jason kernel: [ 259.237078] [<c0182c90>] vma_link+0x80/0xa0
Jan 6 08:31:59 jason kernel: [ 259.237087] [<c01833dd>] mmap_region+0x24d/0x4a0
Jan 6 08:31:59 jason kernel: [ 259.237133] [<c0152ee7>] sys_init_module+0x87/0x1b0
Jan 6 08:31:59 jason kernel: [ 259.237143] [<c0103e9f>] sysenter_do_call+0x12/0x2f
Jan 6 08:31:59 jason kernel: [ 259.237150] ---[ end trace 1d3bb0de00ebe9e9 ]---
Jan 6 08:31:59 jason kernel: [ 259.237161] kobject_add_internal failed for ieee80211 with -EEXIST, don't try to register things with the same
name in the same directory.
Jan 6 08:31:59 jason kernel: [ 259.237176] Pid: 6294, comm: modprobe Tainted: G W 2.6.28-rc9-wl-eeepc-rt2x00-2 #4
Jan 6 08:31:59 jason kernel: [ 259.237182] Call Trace:
Jan 6 08:31:59 jason kernel: [ 259.237191] [<c0221e00>] kobject_add_internal+0x150/0x1a0
Jan 6 08:31:59 jason kernel: [ 259.237200] [<c0221e74>] kset_register+0x24/0x50
Jan 6 08:31:59 jason kernel: [ 259.237224] [<c028bb13>] __class_register+0xc3/0x190
Jan 6 08:31:59 jason kernel: [ 259.237274] [<f84b9150>] cfg80211_init+0x0/0x70 [cfg80211]
Jan 6 08:31:59 jason kernel: [ 259.237287] [<f84b9156>] cfg80211_init+0x6/0x70 [cfg80211]
Jan 6 08:31:59 jason kernel: [ 259.237311] [<c0101126>] do_one_initcall+0x36/0x1b0
Jan 6 08:31:59 jason kernel: [ 259.237334] [<c0187073>] __vunmap+0xa3/0xd0
Jan 6 08:31:59 jason kernel: [ 259.237358] [<c0152d63>] load_module+0x1733/0x1830
Jan 6 08:31:59 jason kernel: [ 259.237406] [<c0182c90>] vma_link+0x80/0xa0
Jan 6 08:31:59 jason kernel: [ 259.237414] [<c01833dd>] mmap_region+0x24d/0x4a0
Jan 6 08:31:59 jason kernel: [ 259.237460] [<c0152ee7>] sys_init_module+0x87/0x1b0
Jan 6 08:31:59 jason kernel: [ 259.237469] [<c0103e9f>] sysenter_do_call+0x12/0x2f
Jan 6 08:31:59 jason kernel: [ 259.255093] mac80211: Unknown symbol regulatory_hint_11d
Jan 6 08:31:59 jason kernel: [ 259.255847] mac80211: Unknown symbol cfg80211_wext_giwname
Jan 6 08:31:59 jason kernel: [ 259.256575] mac80211: Unknown symbol cfg80211_wext_giwmode
Jan 6 08:31:59 jason kernel: [ 259.257722] mac80211: Unknown symbol wiphy_register
Jan 6 08:31:59 jason kernel: [ 259.257997] mac80211: Unknown symbol wiphy_new
Jan 6 08:31:59 jason kernel: [ 259.261321] mac80211: Unknown symbol wiphy_unregister
Jan 6 08:31:59 jason kernel: [ 259.261916] mac80211: Unknown symbol ieee80211_radiotap_iterator_init
Jan 6 08:31:59 jason kernel: [ 259.262346] mac80211: Unknown symbol __ieee80211_get_channel
Jan 6 08:31:59 jason kernel: [ 259.263462] mac80211: Unknown symbol cfg80211_wext_siwmode
Jan 6 08:31:59 jason kernel: [ 259.264180] mac80211: Unknown symbol ieee80211_radiotap_iterator_next
Jan 6 08:31:59 jason kernel: [ 259.264507] mac80211: Unknown symbol ieee80211_channel_to_frequency
Jan 6 08:31:59 jason kernel: [ 259.266319] mac80211: Unknown symbol ieee80211_frequency_to_channel
Jan 6 08:31:59 jason kernel: [ 259.267638] mac80211: Unknown symbol wiphy_free
Jan 6 08:31:59 jason kernel: [ 259.282417] rt2x00lib: Unknown symbol ieee80211_register_hw
Jan 6 08:31:59 jason kernel: [ 259.282765] rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
Jan 6 08:31:59 jason kernel: [ 259.282993] rt2x00lib: Unknown symbol ieee80211_wake_queue
Jan 6 08:31:59 jason kernel: [ 259.283345] rt2x00lib: Unknown symbol ieee80211_find_sta
Jan 6 08:31:59 jason kernel: [ 259.283622] rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
Jan 6 08:31:59 jason kernel: [ 259.284340] rt2x00lib: Unknown symbol ieee80211_ctstoself_get
Jan 6 08:31:59 jason kernel: [ 259.284876] rt2x00lib: Unknown symbol ieee80211_wake_queues
Jan 6 08:31:59 jason kernel: [ 259.285149] rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
Jan 6 08:31:59 jason kernel: [ 259.285972] rt2x00lib: Unknown symbol ieee80211_stop_queue
Jan 6 08:31:59 jason kernel: [ 259.286252] rt2x00lib: Unknown symbol ieee80211_stop_queues
Jan 6 08:31:59 jason kernel: [ 259.286911] rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
Jan 6 08:31:59 jason kernel: [ 259.287404] rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
Jan 6 08:31:59 jason kernel: [ 259.287684] rt2x00lib: Unknown symbol ieee80211_unregister_hw
Jan 6 08:31:59 jason kernel: [ 259.288431] rt2x00lib: Unknown symbol ieee80211_rts_get
Jan 6 08:31:59 jason kernel: [ 259.288712] rt2x00lib: Unknown symbol ieee80211_beacon_get
Jan 6 08:31:59 jason kernel: [ 259.289759] rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
Jan 6 08:31:59 jason kernel: [ 259.291471] rt2x00pci: Unknown symbol rt2x00lib_suspend
Jan 6 08:31:59 jason kernel: [ 259.291664] rt2x00pci: Unknown symbol rt2x00lib_probe_dev
Jan 6 08:31:59 jason kernel: [ 259.291978] rt2x00pci: Unknown symbol ieee80211_free_hw
Jan 6 08:31:59 jason kernel: [ 259.292193] rt2x00pci: Unknown symbol ieee80211_alloc_hw
Jan 6 08:31:59 jason kernel: [ 259.292543] rt2x00pci: Unknown symbol rt2x00lib_rxdone
Jan 6 08:31:59 jason kernel: [ 259.292750] rt2x00pci: Unknown symbol rt2x00queue_get_entry
Jan 6 08:31:59 jason kernel: [ 259.293084] rt2x00pci: Unknown symbol rt2x00lib_remove_dev
Jan 6 08:31:59 jason kernel: [ 259.293853] rt2x00pci: Unknown symbol rt2x00lib_resume
Jan 6 08:31:59 jason kernel: [ 259.295853] rt2800pci: Unknown symbol rt2x00mac_add_interface
Jan 6 08:31:59 jason kernel: [ 259.296134] rt2800pci: Unknown symbol rt2x00mac_get_stats
Jan 6 08:31:59 jason kernel: [ 259.296520] rt2800pci: Unknown symbol rt2x00pci_initialize
Jan 6 08:31:59 jason kernel: [ 259.296795] rt2800pci: Unknown symbol rt2x00mac_set_key
Jan 6 08:31:59 jason kernel: [ 259.297441] rt2800pci: Unknown symbol rt2x00pci_uninitialize
Jan 6 08:31:59 jason kernel: [ 259.297718] rt2800pci: Unknown symbol rt2x00queue_get_entry
Jan 6 08:31:59 jason kernel: [ 259.298086] rt2800pci: Unknown symbol rt2x00pci_suspend
Jan 6 08:31:59 jason kernel: [ 259.298363] rt2800pci: Unknown symbol rt2x00mac_config_interface
Jan 6 08:31:59 jason kernel: [ 259.298758] rt2800pci: Unknown symbol rt2x00pci_remove
Jan 6 08:31:59 jason kernel: [ 259.299032] rt2800pci: Unknown symbol rt2x00mac_remove_interface
Jan 6 08:31:59 jason kernel: [ 259.299311] rt2800pci: Unknown symbol rt2x00lib_txdone
Jan 6 08:31:59 jason kernel: [ 259.299842] rt2800pci: Unknown symbol rt2x00mac_config
Jan 6 08:31:59 jason kernel: [ 259.300141] rt2800pci: Unknown symbol rt2x00queue_get_queue
Jan 6 08:31:59 jason kernel: [ 259.300417] rt2800pci: Unknown symbol rt2x00mac_conf_tx
Jan 6 08:31:59 jason kernel: [ 259.300917] rt2800pci: Unknown symbol rt2x00mac_start
Jan 6 08:31:59 jason kernel: [ 259.301223] rt2800pci: Unknown symbol rt2x00mac_stop
Jan 6 08:31:59 jason kernel: [ 259.301509] rt2800pci: Unknown symbol rt2x00pci_regbusy_read
Jan 6 08:31:59 jason kernel: [ 259.301784] rt2800pci: Unknown symbol rt2x00mac_configure_filter
Jan 6 08:31:59 jason kernel: [ 259.302181] rt2800pci: Unknown symbol rt2x00mac_tx
Jan 6 08:31:59 jason kernel: [ 259.302480] rt2800pci: Unknown symbol rt2x00pci_resume
Jan 6 08:31:59 jason kernel: [ 259.302830] rt2800pci: Unknown symbol rt2x00pci_probe
Jan 6 08:31:59 jason kernel: [ 259.303104] rt2800pci: Unknown symbol rt2x00mac_get_tx_stats
Jan 6 08:31:59 jason kernel: [ 259.303478] rt2800pci: Unknown symbol rt2x00pci_rxdone
Jan 6 08:31:59 jason kernel: [ 259.303811] rt2800pci: Unknown symbol rt2x00mac_bss_info_changed
Jan 6 08:31:59 jason kernel: [ 259.304090] rt2800pci: Unknown symbol rt2x00pci_write_tx_data
[/code1thrrr8d]


PS the wiki instruction are out of date as cogito is no more and also the only way to update that I found it to git reset --hard before git rebase as the history is not kept upstream between each update ... it seems that the tree is changed as a whole from time to time so I have to restart from master, destroy and rebuild my branches and so forth.

IvD

06-01-2009 17:46:05

Same issues as above though I add another problem . Kernel crash heppened before latest git when doing modprobe -r rt2800pci; modprobe rt2800pci (without anything in dmesg). I tracked it down to loading the firmware a second time. I don't know if this was supposed to work though I worked around it by adding
[code3rvm17cw]
diff --git a/drivers/net/wireless/rt2x00/rt2800pci.c b/drivers/net/wireless/rt2x00/rt2800pci.c
index 3beb494..39c50f0 100644
--- a/drivers/net/wireless/rt2x00/rt2800pci.c
+++ b/drivers/net/wireless/rt2x00/rt2800pci.c
@@ -1000,6 +1000,9 @@ static int rt2800pci_load_firmware(struct rt2x00_dev *rt2x00dev,
unsigned int i;
u32 reg;

+ if (rt2x00dev->fw != NULL)
+ return 0;
+
/*
* Wait for stable hardware.
*/
[/code3rvm17cw]

I ll post it to the ML properly (with signoff and such) as soon as the two remainings issues are fixed.
[/quote3rvm17cw]

Well the patch is incorrect. This would prevent the firmware to be loaded and thus makes the hardware useless.
Furthermore, rt2800pci doesn't access rt2x00dev->fw directly, so it should never check for it.
If you look in rt2x00firmware.c you will see that load_firmware is only called when rt2x00dev->fw is set, it will even crash before it ever hits rt2800pci_load_firmware() when it is NULL.


That is the ML seems to be broken no access to archive since November
[/quote3rvm17cw]

SourceForge issue.


and messages I send I do not receive. Maybe an antispam issue though I cannot check as the archive access is broken.
[/quote3rvm17cw]

Well I am working daily with it, and I am not experiencing any problems

Timmes

07-01-2009 21:55:47

D'oh. )

Anyway, i get a hard lockup whenever i bring the interface up more than once. No scan results in ad-hoc mode either.

Timmes

17-01-2009 19:38:09

Just tried with the latest git, hard lockups are gone now (thanks!), but still not working.

Dmesg output
[code7hn04bil][ 586.452515] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 586.468864] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x08008048
[ 761.791801] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xa7c80000
[ 761.808243] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xa7c80000
[ 1009.092522] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xa7c80000
[ 1009.115610] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xa7c80000[/code7hn04bil]

ticjac

04-02-2009 20:55:04

Any with a D-Link DWA-140 USB Dongle with a Ralink RT2870 Chipset got it up and running in monitor and injection mode ?

IvD

04-02-2009 21:44:57

rt2800usb is working in monitor mode and is able to transmit frames. Provided that you disable hardware encryption by using the nohwcrypt=1 module argument.

ticjac

05-02-2009 20:44:31

rt2800usb is working in monitor mode and is able to transmit frames. Provided that you disable hardware encryption by using the nohwcrypt=1 module argument.[/quote3l39eepq]

Tanks IvD, but does "able to transmit frames" means that it is ready for injection mode ?. I have a minimum of knowledge aboot linux
and are using backtrack 3.

IvD

05-02-2009 21:00:45

"able to transmit frames" means just that, I have tested it to be able to associate to an AP. I did no further testing. If you want to know if it can handle injection, you will have to try it yourself.

Timmes

07-02-2009 12:22:24

Just tested the latest git. Despite all the changes in the source no change whatsoever in the behaviour of my RT2860 card. (
Ivo, just how far is the source from being usable? I'd help if i could but i'm not a programmer. Also do you check your PM's?

IvD

07-02-2009 13:20:35

Just tested the latest git. Despite all the changes in the source no change whatsoever in the behaviour of my RT2860 card. (
[/quote202m6jq9]

Thats because all changes were for rt2800usb and not rt2800pci.


Ivo, just how far is the source from being usable?
[/quote202m6jq9]

rt2800usb is working reasonably well, considering that it supports no HW crypto or aggregation. Off course there are still a few bugs needed to be sorted out before I can merge it upstream.

Note that the development rate is slow because rarely anybody bothers to help with the developmentof the drivers, and I also have to maintain all previous drivers. With hardly anybody even interesting in helping the development of the rt2x00 drivers, you can expect things to go slowely. Especially since I also have things like study and a paid job.

pezboytom

07-02-2009 15:10:59

I appreciate that you're doing most of the work on this project but is there any way, short of actually writing code, to help out? Have been following the progress of this driver since I got my eee, as I presume have many other people. Interested in helping out if possible but if I started learning to write modules now I think I'd be doing more harm than good!

I see there is a module in staging now (rt2860sta), is it worth debugging this or is it already a relatively old release? Also, how comes it has the same name as the ralink driver?

IvD

07-02-2009 15:12:56


I see there is a module in staging now (rt2860sta), is it worth debugging this or is it already a relatively old release? Also, how comes it has the same name as the ralink driver?[/quote239anygm]

Because it _is_ the driver as released by Ralink. The maintainer of the staging driver didn't want to wait for rt2800pci/rt2800usb and has added the drivers from Ralink to that tree.

MostAwesomeDude

08-02-2009 07:12:44

I've never hacked on wireless cards before, but I'm not exactly a newbie. Is there anything I should read besides the current work in git and the Ralink official sources to get familiar with the code and HW?

~ C.

IvD

08-02-2009 09:14:38

I've never hacked on wireless cards before, but I'm not exactly a newbie. Is there anything I should read besides the current work in git and the Ralink official sources to get familiar with the code and HW?
[/quote2jy126ef]

Not really, you might find the mac80211 API docs on linuxwireless.org interesting though.

Also Ralink released a very think mac80211 driver for rt2860 which might be useful for some basic functionality, http//kernel.org/pub/linux/kernel/peop ... .0-GPL.tgz the driver does only contain the basic requirements (1 TX queue, STA mode, SW encryption) so it lacks a lot rt2800pci has, but it is interesting to get to know the basics.

Timmes

09-02-2009 22:35:29

Ralink also offers more complete driver code under NDA.

IvD

10-02-2009 09:54:13

Define "more complete"? The Open Source driver they posted on the website?

leetree

10-02-2009 21:06:57

Ralink Technology, Corp. is a Taiwanese Wi-Fi chipset manufacturer which claims to have 10% of the WLAN chipset market worldwide. [quote3e22ygsn][b3e22ygsn]They are one of the few Wi-Fi chipset manufacturers that provide documentation without a non-disclosure agreement, and the unrestricted right to redistribute and use the firmwares for their products[/b3e22ygsn][/quote3e22ygsn]. Because of this their devices are well supported by open source drivers, making them a favourable choice for Linux and BSD users.

IvD

10-02-2009 21:45:35

Well leetrees point regarding the "unrestricted right" to firmware and "documentation without a non-disclosure agreement" are both incorrect in the case of Ralink. So I suggest ignoring that post.

leetree

12-02-2009 03:06:30

Ivd

it was just a quote from internet jezzz.

http//www.nationmaster.com/encyclopedi ... Technology

IvD

12-02-2009 11:52:18

But what was the intent of the post then? Posting a random quote regarding Ralink? Was there anything you wanted to point out with the quote regarding 802.11n devices?

Timmes

13-02-2009 18:16:57

Ralink offers STA-only linux code on their website. You can't run an AP. An AP driver exists, it is used in several linux / ralink based wireless routers.

My memory didn't serve me right though, the AP driver is not under NDA but you have to sign a SLA with Ralink Sales.

leetree

13-02-2009 23:31:24

Thanks,Timmes

pezboytom

02-03-2009 16:20:16

Would it be any use at this point to provide error messages, or is it understood that the code isn't yet mature enough for this to be worthwhile?
Tom

IvD

02-03-2009 16:35:24

Reporting error messages is fine, it might give hints on why it isn't tranfering frames yet.

pezboytom

02-03-2009 17:04:53

When I try and bring the interface up the first time I get this
[codelfbkzu5x]root@darkstar:ifconfig wlan0 up
root@darkstar:dmesg
phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
rt2800pci 0000:01:00.0: firmware: requesting rt2860.bin
phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
input: rt2800pci as /devices/pci0000:00/0000:00:1c.3/0000:01:00.0/input/input9
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2800pci_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
phy0 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
usb 5-1: USB disconnect, address 2
usb 5-1: new full speed USB device using uhci_hcd and address 3
usb 5-1: configuration #1 chosen from 1 choice
[/codelfbkzu5x]
This is with no usb devices plugged in so I'm not entirely sure where those messages are coming from! If I try bringing the interface down and then up again I get
[codelfbkzu5x]phy0 -> rt2800pci_load_firmware: Error - Unstable hardware.
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
[/codelfbkzu5x]
This is on my eee with ralink rt2860 and the latest git snapshot, rt2800pci module loaded. If you want anything more specific do let me know.
Tom

pezboytom

04-03-2009 13:06:07

The interface now comes up and down without error. However, "iwlist scan wlan0" shows no results, nor does the card associate with an AP. Dmesg is showing more or less the same
[code23kvpph1]phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
rt2800pci 0000:01:00.0: firmware: requesting rt2860.bin
phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
input: rt2800pci as /devices/pci0000:00/0000:00:1c.3/0000:01:00.0/input/input9
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2800pci_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
phy0 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
rt2800pci 0000:01:00.0: PCI INT A disabled
usb 5-1: USB disconnect, address 2
pci 0000:01:00.0: reg 10 32bit mmio: [0x000000-0x00ffff]
pci 0000:01:00.0: PME# supported from D0 D3hot
pci 0000:01:00.0: PME# disabled
rt2800pci 0000:01:00.0: enabling device (0000 -> 0002)
rt2800pci 0000:01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
rt2800pci 0000:01:00.0: setting latency timer to 64
phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 0781, rf: 0003, rev: 28720200.
phy1: Selected rate control algorithm 'minstrel'
Registered led device: rt2800pci-phy1::radio
Registered led device: rt2800pci-phy1::assoc
Registered led device: rt2800pci-phy1::quality
phy1 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
rt2800pci 0000:01:00.0: firmware: requesting rt2860.bin
phy1 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
input: rt2800pci as /devices/pci0000:00/0000:00:1c.3/0000:01:00.0/input/input10
phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.[/code23kvpph1]
Then when bringing up the card with ifconfig the bottom four lines are repeated.

Nothing is getting received or transmitted according to ifconfig.

pezboytom

13-03-2009 15:34:54

A new error has emerged! On bringing up the interface now, I get this message in dmesg
[code2v0ydp9y]phy7 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware[/code2v0ydp9y]
As far as I can tell the card is still not transmitting or receiving.
Appreciate your work!
Tom

hbrucky

20-03-2009 22:08:58

Hi,

I just starting trying to get the RT2860 in my Eee Box B202 running (goal work as access point) some days ago. I read through all information that looked like being potentially useful and finally got to the same issue as pezboytom just described here. Although not being a kernel developer, but having seen (and created) a bit of C code years ago (actually I'm a Java developer), I looked at parts of the code as far as I could, just using common sense, to see whether I could at least narrow the region where something goes wrong. Added some more debugging statements to parts of the code, actually related to the "startup" of the device and loading of the firmware (which I had to configure correctly first), but didn't really succeed.

Just for the case that something of this still might be interesting, here are some of details I got from my "tests"
- rt2x00lib_request_firmware was finally OK, i.e. it returns 0
- The firmware loaded (it has been put into the kernel, so it's not loaded from the file system by now) has 8192 bytes, which matches the size of the original firmware file, so seems to be OK.
- rt2x00dev->ops->lib->load_firmwarert2x00dev, rt2x00dev->fw->data, rt2x00dev->fw->size) returns 0 = OK, too.
- Same for rt2x00lib_start(...), rt2x00lib_initialize(...) and rt2x00lib_start(...)

[quoteksa90y6n][ 419.475301] phy0 -> rt2x00lib_request_firmware Info - Loading firmware file 'rt2860.bin'.
[ 419.475312] rt2800pci 00000300.0 firmware using built-in firmware rt2860.bin
[ 419.475318] phy0 -> rt2x00lib_request_firmware Info - Firmware detected - version 0.11.
[ 419.475372] rt2800pci 00000300.0 Heiko rt2x00lib_request_firmware OK (retval = 0)<6>phy0 -> rt2x00lib_load_firmware Info - Heiko Sending firmware to device (8192 bytes)...<6>phy0 -> rt2x00lib_load_firmware Info - Heiko Result of load_firmware(...) 0<6>phy0 -> rt2x00lib_start Info - Heiko rt2x00lib_load_firmware(...) returned 0<7>device 'input5' device_add
[ 419.478903] PM Adding info for No Businput5
[ 419.480774] input rt2800pci as /devices/pci000000/0000001c.1/00000300.0/input/input5
[ 419.484321] device 'event5' device_add
[ 419.484422] PM Adding info for No Busevent5
[ 419.484484] phy0 -> rt2x00lib_start Info - Heiko rt2x00lib_initialize(...) returned 0<6>phy0 -> rt2x00lib_start Info - Heiko rt2x00lib_start(...) completed.<3>phy0 -> rt2800pci_mcu_status Error - MCU request failed, no response from hardware
[ 419.517970] phy0 -> rt2x00mac_conf_tx Info - Configured TX queue 0 - CWmin 5, CWmax 10, Aifs 2, TXop 0.
[ 419.517987] phy0 -> rt2x00mac_conf_tx Info - Configured TX queue 1 - CWmin 5, CWmax 10, Aifs 2, TXop 0.
[ 419.518004] phy0 -> rt2x00mac_conf_tx Info - Configured TX queue 2 - CWmin 5, CWmax 10, Aifs 2, TXop 0.
[ 419.518027] phy0 -> rt2x00mac_conf_tx Info - Configured TX queue 3 - CWmin 5, CWmax 10, Aifs 2, TXop 0.[/quoteksa90y6n]

The only thing I'm not really sure about is that some of my "traces" were not written, i.e. the respective code was not run. Looking closer at the code around, which is _request_firmware(...) in drivers/base/firmware_class.c, I found that that function "quickly" returns with 0 if it finds the requested firmware in the kernel itself ("built-in"), so there is some code which is not executed then, and it doesn't look absolutely obvious to me that all of it is really only relevant if the firmware is read from the user space (I don't know exactly how that works, that's why I chose the built-in firmware by now - please enlighten me here ;-) ).

@Ivo Can you tell whether
1) there might be any relation at all (maybe it's a completely wrong location where to look) and whether
2) some of that code should actually be called - in that case, please give me some hint how I can test with "external" firmware, i.e. which component is responsible for providing it at runtime. Just some basic hint so I can continue to collect the required information.

If I can help in any way to solve this, please let me know. As I mentioned, I don't have experience with kernel programming, but I can do some easy modifications like adding tracing code or slightly modifying existing behavior, if that helps.

Thanks and best regards
Heiko

IvD

20-03-2009 23:03:56


1) there might be any relation at all (maybe it's a completely wrong location where to look) and whether
2) some of that code should actually be called - in that case, please give me some hint how I can test with "external" firmware, i.e. which component is responsible for providing it at runtime. Just some basic hint so I can continue to collect the required information.
[/quoteo1h0kik2]

rt2x00 doesn't work with built-in firmware, it will always need the external firmware file to operate.
Other then that there is no point in following the error codes from the rt2x00 functions, they will all return 0. The problem is the hardware register initialization and either there are some missing initialization calls or they are not in the correct order. THe best thing is comparing the initialization with the original Ralink drivers to see if there are critical differences.

pezboytom

14-05-2009 21:05:48

The behaviour of the card has changed with the latest snapshot from git. Trying to bring the interface up I now get this output
[code2b05x522]phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
rt2800pci 0000:01:00.0: firmware: requesting rt2860.bin
phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11.
input: rt2800pci as /devices/pci0000:00/0000:00:1c.3/0000:01:00.0/input/input9
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
phy0 -> rt2800pci_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
phy0 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
rt2800pci 0000:01:00.0: PCI INT A disabled
[/code2b05x522]The led on my eeepc goes out at this point and it becomes impossible to switch back on without restarting. Upon trying to remove the module rt2800pci, the system crashes completely.

Mony

17-06-2009 15:32:53

Any progress with "master mode"? Managed to start the card with hostapd (it is in master mode, and there is mon.wlan0) but i can't see the network from my laptop or connect to "hidden ssid". All this with WPA2 enc, but the problem is also there without any enc. Any suggestions? PS using 2860 pci card.

solar

17-06-2009 18:36:30

Managed to start the card with hostapd.[/quote2r978sok]


How did you manage that? With standart Ralink RT2860_Linux_STA drivers?

Mony

17-06-2009 20:12:35

No with the driver from git[/urldkb8ai2c]. With original(ralink) driver it works perfect as client, but from what i know master mode is not supported ( Unfortunately i need it to work as Access point (

pezboytom

18-06-2009 14:18:04

Shock horror, does this mean that the changes get made to git without them coming up on the web interface? I was under the impression that there had been no update since 23rd may and that snapshot crashes my card completely!

Does anyone know if this driver is now working in managed mode?

Spooler

23-06-2009 17:55:46

From the git web[/url1mmpkl7i]
[quote1mmpkl7i]
description rt2x00 drivers (mac80211)
owner Ivo van Doorn
last change Sat, 20 Jun 2009 161918 +0000
URL
git//git.kernel.org/pub/scm/linux/kern ... rt2x00.git
http//www.kernel.org/pub/scm/linux/ker ... rt2x00.git
[b1mmpkl7i]2 days ago Ivo van Doorn rt2x00 Implement support for rt2800pci [/b1mmpkl7i]
...[/quote1mmpkl7i]

I tried them with my SparkLAN WPIR-501. Just to be precise it's in fact a RT2800pci, RT2860 MAC/BBP and RT2820 RF.
Before the new release, when modprobing rt2800pci (staging) I used to get lots of this (and the card wouldn't work).
[code1mmpkl7i]rt2800pci 0000:01:06.0: firmware: requesting rt2860.bin
phy1 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware[/code1mmpkl7i]
Now, when modprobing the drivers
[code1mmpkl7i][ 3273.151293] rt2800pci 0000:01:06.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
[ 3273.158567] phy2: Selected rate control algorithm 'minstrel'
[ 3273.159539] Registered led device: rt2800pci-phy2::radio
[ 3273.159561] Registered led device: rt2800pci-phy2::assoc
[ 3273.159582] Registered led device: rt2800pci-phy2::quality[/code1mmpkl7i]
Which seems alright to me, but I'm no expert.
Then when I try to put it in master mode with iwconfig, this happens. (Is that normal? )
[code1mmpkl7i]>iwconfig wlan0 mode Master
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.[/code1mmpkl7i]
With that being said, hostapd *seems* to start just fine and ends up saying
[code1mmpkl7i]wlan0: Setup of interface done.[/code1mmpkl7i]
I've yet to test if it really works since I'm remote right now, but iwconfig doesn't show anything wrong (maybe except the levels, but I didn't connect any antennas for the time being).
[code1mmpkl7i]>iwconfig wlan0
wlan0 IEEE 802.11bgn Mode:Master Frequency:2.412 GHz Tx-Power=12 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:C9B0-34CF-522C-DF93-E585-0864-2714-C63C [2]
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0[/code1mmpkl7i]
Oh, and also, dmesg still throws
[code1mmpkl7i][ 4050.151084] phy2 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 4050.178143] phy2 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware[/code1mmpkl7i]

Btw, many thanks to IvD for all the work on the drivers. Also thanks to Mattias, Mark, Felix and Xose for the latest patch work. Sweet piece of code guys.

Mony

02-07-2009 20:56:47

I'll give it a try tomorrow. The thing with iwconfing wlanx mode master + err is normal. Only way to get it in master mode is hostapd.

jjfromd

14-07-2009 14:55:12

For what its worth, I just tried the rt2800pci drivers. It appears that I cannot send wireless packets, either in managed mode or AP mode.

AP mode with hostapd, when I tcpdump the monitor interface, I see iwlist scans from my test client, and see SSID responses. However, tcpdump and monitor from the client never sees the response.

Managed mode, I can do iwlist $dev scan sometimes and see SSIDS. However, I can't connect to even an open AP.

FWIW, both work much better with a rt2800usb-based adapter I had kicking around.

Anything I can do to help get this going?

MatejB

14-07-2009 23:31:20

Is there any way to compile the rt2800pci driver without recompiling the entire kernel from your git?
BTW compat-wireless does not include it in its latest "bleeding edge" version (2009-07-14).

IvD

15-07-2009 00:36:36

Is there any way to compile the rt2800pci driver without recompiling the entire kernel from your git?[/quote1l7v8s94]

No.

BTW compat-wireless does not include it in its latest "bleeding edge" version (2009-07-14).[/quote1l7v8s94]

That is because compat-wireless is based on the upstream wireless-testing.git and not rt2x00.git.

MatejB

20-07-2009 22:13:05

I just compiled and tested the rt2800pci driver. 'iwlist wlan0 scan' says the network is down. When I bring it up with 'ifconfig wlan0 up' it works for a short time (it can scan the near stations) but after a while it stops. It seems like the device was brought down somehow. dmesg shows
phy0 -> rt2800pci_mcu_status Error - MCU request failed, no response from hardware
ADDRCONF(NETDEV_UP) wlan0 link is not ready
Is this supposed to be normal? Am I missing something? Or the driver is not working properly?
BTW 'lspci -n' shows 18140781 (I have an EEEbox B202).

cortez8591

21-07-2009 08:40:14

Is there any way to compile the rt2800pci driver without recompiling the entire kernel from your git?[/quote3vzfp5x2]

No.[/quote3vzfp5x2]

Does it mean there is no chance to run e.g. 2.6.31 kernel and at the same time using rt70usb in master mode? weird..

IvD

21-07-2009 09:20:31

Is there any way to compile the rt2800pci driver without recompiling the entire kernel from your git?[/quote1xgg7zvr]

No.[/quote1xgg7zvr]

Does it mean there is no chance to run e.g. 2.6.31 kernel and at the same time using rt70usb in master mode? weird..[/quote1xgg7zvr]

Well that is complete rubbish. rt73usb is persent in 2.6.31 so why shouldn't you be able to use that driver?
Please note that you are replying to a topic which is about [b1xgg7zvr]RT2800[/b1xgg7zvr] and not [b1xgg7zvr]RT73[/b1xgg7zvr]

cortez8591

21-07-2009 09:55:53

Well that is complete rubbish. rt73usb is persent in 2.6.31 so why shouldn't you be able to use that driver?
Please note that you are replying to a topic which is about [b3hjb1zl6]RT2800[/b3hjb1zl6] and not [b3hjb1zl6]RT73[/b3hjb1zl6][/quote3hjb1zl6]

Oh, I've read somewhere that drivers can be obtained only from Your kernel branch.. my bad

MatejB

24-07-2009 23:32:00

I managed somehow to patch the compat-wireless source with the rt2800pci driver and compile it successfully
1. added rt2800pci.* and rt2x00soc.* (drivers/net/wireless/rt2x00)
2. updated Makefile and rt2x00.h (same dir as above)
3. modified config.mk (main dir) (I added just CONFIG_RT2800PCI_PCI=m, CONFIG_RT2800PCI=m is already included)
4. (optionally) uncommented CONFIG_RT2X00_DEBUG

I agree that this procedure isn't clean as the mac80211 libraries (or some other) may be different in the rt2x00 git and in compat-wireless. But I still wonder whether this produces the same driver (in my case both of them were unusable).

Hobard

27-07-2009 04:07:31

Hi,

Does the rt2800usb driver work on ARM?

I tried using it with a Ralink USB dongle (USB Id 148f3070) but it wouldn't return any scan results.

MrIch

12-08-2009 06:32:21

Hi,

Does the rt2800usb driver work on ARM?

I tried using it with a Ralink USB dongle (USB Id 148f3070) but it wouldn't return any scan results.[/quote1hosc1wt]

that does not work on amd64 either... (

IvD

12-08-2009 07:32:24

that does not work on amd64 either... ([/quotekvhyhfty]

It doesn't work correctly regardless of chipset revision, architecture, etc etc.

Hobard

13-08-2009 10:55:20

[quote1of1f97s]It doesn't work correctly regardless of chipset revision, architecture, etc etc[/quote1of1f97s]
Is it possible to check out an earlier revision from GIT to get a working rt2800usb driver?
From earlier posts it seems to have been working at some point.

IvD

14-08-2009 04:16:08

yes, you have to use git checkout <commit>, where <commit> should be replaced with the commit you want to try.

pezboytom

17-08-2009 08:06:37

I just checked out the latest git snapshot and things are looking a lot better! Using wicd I got a full set of scan results and it looked like it was going to connect to my home network (WPA-TKIP) but failed at the last minute. The error given was "unable to obtain IP" but I'm not sure how accurate that was. The signal strength isn't being reported correctly - all of the networks showed 100% strength. I haven't had a chance to try connecting to other networks with different types of encryption. The card also runs in monitor mode, although injection fails. One weird thing I noticed is that X seems to be under quite a lot of strain while the card is up. The touchpad locked up when I brought up wlan1 in X but I got round this by bringing it up beforehand. dmesg still shows these errors though
[code32grda5g]psmouse.c: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away.
psmouse.c: resync failed, issuing reconnect request[/code32grda5g]
The MCU error still shows up when the card is first brought up too.

Some real noticeable progress this time, looking like the end is in sight. Great work, thanks a lot guys!

Timmes

06-09-2009 20:32:30

With the latest git my rt2860 card is transmitting beacon frames and responding to probe requests, i'm using a rt2500 card to capture what's going through the air.

Unfortunately the frames are malformed. They're almost right, wireshark can decypher them correctly (basic rates, rates, country info, rsn info, etc) but says it's a malformed 802.11 packet. The FCS is reported as 0x00000000 for the beacons as well as the probe responses.

Almost there.....

Botanix

18-09-2009 05:56:57

What is the current status of the driver for USB devices? Is it usable?

IvD

18-09-2009 06:33:47

What is the current status of the driver for USB devices? Is it usable?[/quote1747o33z]

Well just try the latest rt2x00.git version and see for yourself.

Botanix

18-09-2009 07:55:53

What is the current status of the driver for USB devices? Is it usable?[/quotem7vvwpo0]

Well just try the latest rt2x00.git version and see for yourself.[/quotem7vvwpo0]
I don't have a card to test it with yet. I am trying to decide which one to go with.
But thanks for the answer.

wRAR

19-09-2009 17:09:46

I tried rt2800pci with my rt2860 on eee PC 901. I used 2.6.31 merged with latest ivd/rt2x00.git. ifconfig wlan0 up works, but iwlist scan doesn't show anything. I also experience slowing of keyboard and touchpad while wlan0 is up.
UPD kismet shows my network, but its SSID is shown only in the log ("Detected new managed network"), main window shows "<Hidden SSID>".

dmesg shows lots of ACPI AE_TIME errors and one soft lockup.

mgc8

12-10-2009 02:08:12

Hello,

I am tryingo to configure a RT2860 device as an access point, it is embedded in an Asus EeeBox.

I used the latest git combined with compat-wireless to test the rt2800pci driver on a 2.6.30 kernel (Debian Squeeze). After supplying the rt2860.bin firmware, hostapd is able to start the interface correctly. I can see the SSID on the right channel from another computer via kismet, but the signal seems extremely weak and I was unable to associate. Is this the expected level of functionality for the driver or should I attempt to tweak it and establish a connection? Is there anything I can do to aid in development/testing?
It's great to see some support for this chip at last!

Thank you and best regards,
Mihnea

MatejB

10-11-2009 12:08:31

I noticed that rt2800pci is included in compat-wireless (2009-11-10).

However it doesn't compile. The reason lib2800lib.c. It is missing some usb related
macros and structs. After I added an "#include <linux/usb.h>" line it compiled fine.

I know that the rt2x00 has newer code than those in compat-wireless, but in the latest
git the usb.h header was still not included (at least not directly, maybe implicitly through other
headers).

BTW, I compiled it on a 2.6.30 kernel (from debian-backports).

Could someone check this out.

IvD

10-11-2009 17:48:53

Patch to fix it has been send upstream.

n0PxN0p

19-11-2009 11:15:18

Yesterday i blacklisted rt2860sta, downloaded and installed daily compat-wireless on my eee 901 debian box

[code3252tv9l]root@deadbox:~# uname -a
Linux deadbox 2.6.30-2-686 #1 SMP Sat Sep 26 02:09:22 UTC 2009 i686 GNU/Linux
root@deadbox:~# lspci|grep 01:00.0
01:00.0 Network controller: RaLink RT2860
root@deadbox:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1f:c6:df:34:fe
inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::21f:c6ff:fedf:34fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1225 errors:0 dropped:0 overruns:0 frame:0
TX packets:829 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:109863 (107.2 KiB) TX bytes:107437 (104.9 KiB)
Memory:fbfc0000-fc000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

root@deadbox:~# lsmod | grep rt
rt2800pci 10808 0
rt2800lib 22656 1 rt2800pci
rt2x00usb 10300 1 rt2800lib
rt2x00pci 7260 1 rt2800pci
crc_ccitt 1816 1 rt2800pci
rt2x00lib 26092 4 rt2800pci,rt2800lib,rt2x00usb,rt2x00pci
led_class 3852 1 rt2x00lib
mac80211 141208 3 rt2x00usb,rt2x00pci,rt2x00lib
cfg80211 109436 2 rt2x00lib,mac80211
rfkill_backport 17036 1 cfg80211
eeprom_93cx6 1920 1 rt2800pci
usbcore 126052 6 btusb,usb_storage,rt2x00usb,uhci_hcd,ehci_hcd
agpgart 30836 1 intel_agp
root@deadbox:~# dmesg | grep rt2800pci
[ 3.248659] rt2800pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 3.248671] rt2800pci 0000:01:00.0: setting latency timer to 64
[ 3.257737] rt2800pci 0000:01:00.0: PCI INT A disabled
[ 3.257747] rt2800pci: probe of 0000:01:00.0 failed with error -17[/code3252tv9l]

i unloaded all the modules, may be arc4 and ecb should be unloaded too

[code3252tv9l]root@deadbox:~# rmmod rt2800pci
root@deadbox:~# rmmod rt2800lib
root@deadbox:~# rmmod rt2x00pci
root@deadbox:~# rmmod rt2x00usb
root@deadbox:~# rmmod rt2x00lib
root@deadbox:~# rmmod mac80211
root@deadbox:~# rmmod cfg80211
[/code3252tv9l]

And again... always make sure you load ecb and arc4 modules after mac80211

[code3252tv9l]root@deadbox:~# modprobe mac80211
root@deadbox:~# modprobe cfg80211
root@deadbox:~# modprobe ecb
root@deadbox:~# modprobe arc4
root@deadbox:~# modprobe rt800pci
root@deadbox:~# dmesg | tail
[ 1642.951824] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 1642.951830] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 1642.951851] cfg80211: Calling CRDA for country: US
[ 1719.863467] rt2800pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1719.863481] rt2800pci 0000:01:00.0: setting latency timer to 64
[ 1719.879852] phy0: Selected rate control algorithm 'minstrel'
[ 1719.881176] Registered led device: rt2800pci-phy0::radio
[ 1719.881210] Registered led device: rt2800pci-phy0::assoc
[ 1719.881246] Registered led device: rt2800pci-phy0::quality
[ 1719.906585] udev: renamed network interface wlan0 to wlan1
root@deadbox:~# ifconfig wlan1
wlan1 Link encap:Ethernet HWaddr 00:15:af:ed:a9:6c
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)[/code3252tv9l]

Thank You for your work, guys.

ari

10-12-2009 01:26:01

I tried rt2800pci with my rt2860 on eee PC 901. I used 2.6.31 merged with latest ivd/rt2x00.git. ifconfig wlan0 up works, but iwlist scan doesn't show anything. I also experience slowing of keyboard and touchpad while wlan0 is up.
UPD kismet shows my network, but its SSID is shown only in the log ("Detected new managed network"), main window shows "<Hidden SSID>".

dmesg shows lots of ACPI AE_TIME errors and one soft lockup.[/quote13nix95k]


On ubuntu karmic/64-bits - I have a linksys WMP600N dual band card based on 2860. The ubuntu 9.10 stock driver (1.8.x.x from ralink) performs pretty badly on karmic, fills up dmesg with error messages, does not work in N mode with network-manager (out of dozens of reboots, it only connected once), to to make it work more or less reliably on G mode I had to remove network-manager and use WEP - and still the connection is dropped every 24 / 36 hours or so.

Anyhow, last week I gave the latest wireless-compat a shot. Now rt2800pci detects my card (ubuntu 9.10 stock rt2800pci did not even detect the card), and I could bring up the interface and do scans, that part worked fine. The problem is that associations failed most of the time, and even when they seemed to work (as shown by iwconfig), DHCP didn't get an IP, and static IP configuration didn't help either. All this with WEP.

I was wondering if anyone could actually get rt2800pci to work on ubuntu 9.10 / 64bits, at least in open mode or with WEP in wireless G.
What I ultimately want is to get the card to work in Wireless N on 5GHz with WPA2... but it seems I am kind of far from getting there.

tudstudent

05-03-2010 07:50:29

This is may be a simple question, but I was wondering or the rt2860 can work in "Master mode".

I have read this complete topic and others, but at the moment couldn't find an answer.

So can the rt2860 do a stabel function as AP?

It is this chip

RT2800P = PCI / Cardbus, single band (802.11b/g/n), with RT2860 + RT2820

MatejB

09-07-2010 11:01:00

This is may be a simple question, but I was wondering or the rt2860 can work in "Master mode".

I have read this complete topic and others, but at the moment couldn't find an answer.

So can the rt2860 do a stabel function as AP?

It is this chip

RT2800P = PCI / Cardbus, single band (802.11b/g/n), with RT2860 + RT2820[/quotecop6v242]

Yesterday I gave rt2800pci a try after a long time on my EEE Box. [bcop6v242]It works in AP mode![/bcop6v242]
I used Debian Lenny with backported 2.6.32 kernel, hostapd 0.6.9 and the latest compat-wireless
(dating 10/6/27).

You guys did a very good job, although some responsiveness in this forum would be appreciated.

bluesman

02-08-2010 17:41:51

Hi,
also working (finally!!) RaLink RT2860 with rt2800pci in AP mode on Asus b202 eeebox debian squeeze 2.6.35-rc6-wl )

I'm using it without problems for now, thank you guys!!

phusg

09-08-2010 19:35:49

Thanks for the heads-up guys, I've been waiting for this.

I just replaced my RT2561 PCI card with a RT2860 card on Debian Lenny with latest backports 2.6.32 kernel, latest 0.24 firmware-ralink and hostapd 0.6.9.

lspci, iwconfig and ipconfig output look fine, except iwconfig doesn't show the SSID I have set in hostapd.conf and my laptop can't see the AP as it did with the previous RT2561.

Did you guys upgrade from something similar and have to change anything in hostapd for example? I've left hw_mode=g and driver=nl80211 there.

Is compat-wireless necessary? I can't find it in the debian repository and haven't needed it previously.

Any help appreciated!

Mony

11-08-2010 13:15:12

phusg get the last compat wireless. goto http//wireless.kernel.org/en/users/Download , extract the archive, get in the folder, type ./scripts/driver-select rt2x00 , make , make install. You can always latter uninstall it by `make uninstall`.

Ok now my problem. I have rt2860pci trying to run in master mode. The system is ubuntu 10 32bit. I have installed latest stable compat wireless (also tried the git one), tried hostapd v 0.6.9 , 0.6.10 , git.. and i cannot get the card working in 11N. My setup is channel=2, essid=xx, wpa2(tried without enc at all), mode=g etc and its working perfect. But if i enable 11n (ieee80211n=1, ht_capab=[HT40+][SHORT-GI-40]) hostapd don't want to start and tells me it cannot change channel + unsupported by driver and in 2-3 tries to start crashes my system. I've also tried with ht20, short-gi20, even with commented ht_capab line and still no go. Any ideas?

Mony

12-08-2010 16:49:31

It seems N support isnt ready yet. http//wireless.kernel.org/en/users/Drivers/rt2800pci
According to this
not working yet
* 11n support (mainly aggregation)

Well i guess i will wait for that ) Keep up the good work guys, in g mode with hostapd its working perfect )
EDIT
After > 1 day using the card in master mode i found zero problems(except the lack of N support). No ping losses, no disconnects, stable transfer of 2.7MB/s, using wpa2 ccmp. )

nan

23-08-2010 12:23:30

Hello, i have problems with setting Master mode for rt2860pci.

PC asus eee box b202, debian lenny, 2.6.32-5-686

What i did
1) blacklist and unload rt2860sta, "make unload" to be sure
2) compile and install latest compat-wireless-2010-08-22 (tried stable compat-wireless-2.6.36-rc1-2 too)
3) modinfo seems to be correct
[codez0vz8n17]$ modinfo rt2800pci
filename: /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/rt2x00/rt2800pci.ko
license: GPL
firmware: rt2860.bin
description: Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 7E9587E51E23587D536C5E4[/codez0vz8n17]
4) /lib/firmware/rt2860.bin is from ralink site (tried firmware-ralink package too)
5) load driver
[codez0vz8n17]$ sudo modprobe -v rt2800pci
insmod /lib/modules/2.6.32-5-686/updates/drivers/misc/eeprom/eeprom_93cx6.ko
insmod /lib/modules/2.6.32-5-686/updates/net/wireless/cfg80211.ko
insmod /lib/modules/2.6.32-5-686/updates/net/mac80211/mac80211.ko
insmod /lib/modules/2.6.32-5-686/updates/compat/compat_firmware_class.ko
insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
insmod /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/rt2x00/rt2x00lib.ko
insmod /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/rt2x00/rt2x00pci.ko
insmod /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/rt2x00/rt2800lib.ko
insmod /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/rt2x00/rt2800pci.ko[/codez0vz8n17]
[codez0vz8n17][ 1797.724889] cfg80211: Calling CRDA to update world regulatory domain
[ 1797.891743] rt2800pci 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1797.891767] rt2800pci 0000:03:00.0: setting latency timer to 64
[ 1797.906024] phy0: Selected rate control algorithm 'minstrel'
[ 1797.909185] Registered led device: rt2800pci-phy0::radio
[ 1797.909238] Registered led device: rt2800pci-phy0::assoc
[ 1797.909290] Registered led device: rt2800pci-phy0::quality[/codez0vz8n17]
6) interface shows up
[codez0vz8n17]$ iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off[/codez0vz8n17]
7) setting ad-hoc or monitor works, but not master
[codez0vz8n17]$ sudo iwconfig wlan0 mode master
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.[/codez0vz8n17]
8) after reboot driver is loaded automatically with same results.

i'm confused. what should i check? orz
Thanks.

IvD

23-08-2010 13:52:34

Hello, i have problems with setting Master mode for rt2860pci.
[codeh7cuuoo4]$ sudo iwconfig wlan0 mode master
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.[/codeh7cuuoo4]
8) after reboot driver is loaded automatically with same results.

i'm confused. what should i check?[/quoteh7cuuoo4]

Well first of there is a huge sign at the top of the forum called
IMPORTANT READ BEFORE POSTING!!![/urlh7cuuoo4]
But since that might be too easy for people, here are the magical places where people find what they search for
[url=http://www.google.nl/#hl=en&source=hp&q=Error+for+wireless+request+%22Set+Mode&aq=f&aqi=g7g-m1&aql=&oq=&gs_rfai=&fp=495eb8d09f23167h7cuuoo4]GOOGLE[/urlh7cuuoo4]
[url=http://www.bing.com/search?q=Error+for+wireless+request+%22Set+Mode&go=&form=QBLH&filt=allh7cuuoo4]BING[/urlh7cuuoo4]

nan

23-08-2010 16:15:11

well, thanks for a kick in right direction!

originally i've set up hostapd as in "AP-mode_Howto" but it failed, so i've tried to set master mode manually. and at that time something clicked inside my brain and i've spent 6 hours trying to solve the wrong problem )

all i needed - change default driver (not mentioned in FAQ directly, but found in "rt2x00 master mode HOWTO")
[code37hqajpe]# Driver interface type (hostap/wired/madwifi/prism54; default: hostap)
#driver=hostap
driver=nl80211[/code37hqajpe]

wrostek

07-09-2010 04:56:53

I finally have my WMP600N configured, and running in MASTER mode with hostapd. The only problem I have is that it seems to be running IPV6 instead of IPV4, so my dhcpd program is not working well with any clients that connect to it. Here is some info on my setup

I was running Ubuntu 10.04, however I have read in numerous posts that a 2.6.35 kernel would work better for rt2800pci. So I have upgraded my machine to a pre-release of Ubuntu 10.10 Maverick Meerkat. Kernel version is 2.6.35-19-generic.

I have installed hostapd v0.6.10, and have downloaded the latest compat-wireless package from http//wireless.kernel.org/download/com ... eless-2.6/ . I have downloaded the latest rt2860.bin firmware from http//www.ralinktech.com/support.php?s=2 .

I have blacklisted rt2860sta driver, and when I boot up, the system selects the rt2800pci and loads the firmware without any problem. The only issue I have is usually two messages when the rt2800pci module is loaded
[code1e27i54m]
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[/code1e27i54m]
I believe I get two messages because this card has a dual band, but the messages don't seem to indicate any serious problem. Hostap starts at boot, and attaches to my wlan0 interface ( ip 192.168.2.1 ). I then take my wireless device ( an iPhone 4 ) and attempt to connect to the AP. The AP authenticates my passkey, however then it stumbles when dhcpd should assign my iPhone its ip address and DNS info. I ran wireshark on my wlan0 interface, and it seems like the interface is using IPV6 addressing, instead of IPV4. Here is a sample capture
[code1e27i54m]
0.000000 Apple_7a:df:d2 -> Broadcast XID Basic Format; Type 1 LLC (Class I LLC); Window Size 0
0.004599 Apple_7a:df:d2 -> Cisco-Li_e3:3c:91 EAPOL Key
0.009641 Apple_7a:df:d2 -> Cisco-Li_e3:3c:91 EAPOL Key
0.052590 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x16b8c067
0.053907 fe80::7ec5:37ff:fe7a:dfd2 -> ff02::1:ff7a:dfd2 ICMPv6 Multicast listener report
0.744959 :: -> ff02::1:ff7a:dfd2 ICMPv6 Neighbor solicitation
1.623596 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x16b8c067
1.764173 fe80::7ec5:37ff:fe7a:dfd2 -> ff02::2 ICMPv6 Router solicitation
[/code1e27i54m]
My dhcpd.conf is configured for subnet 192.168.2.0, however wlan0 is soliciting itself as fe807ec537fffe7adfd2, which dhcpd has no ip range available for, so my iPhone doesn't get properly configured. My question is what is causing my wlan0 to solicit itself with an IPv6 address ? Why wouldn't it use 192.168.2.1 instead of fe807ec537fffe7adfd2 ? Is it an issue with rt2800pci, hostapd or dhcp3-server ? I have gone so far as to disable all ipv6 from my linux box by editing the following files
/etc/sysctl.conf
[code1e27i54m]
#disable ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
[/code1e27i54m]
/etc/modprobe.d/networkdrivers.conf
[code1e27i54m]
alias net-pf-10 off
alias Ipv6 off
[/code1e27i54m]

This seems to disable IPv6 from everywhere, but from wireshark, or tcpdump on wlan0, I can still see it is using ipv6 addressing.

For some further info this is what my config files look like

/etc/network/interfaces
[code1e27i54m]
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.2.1
network 192.168.2.0
netmask 255.255.255.0
broadcast 192.168.2.255
[/code1e27i54m]

/etc/hostapd/hostapd.conf
[code1e27i54m]
##### hostapd configuration file ##############################################
interface=wlan0

driver=nl80211

logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

ctrl_interface_group=0

ssid=LiNuX_g0dZ

country_code=CA

ieee80211d=0

hw_mode=g

channel=3

beacon_int=100

dtim_period=2

max_num_sta=255

rts_threshold=2347

fragm_threshold=2346

macaddr_acl=0

auth_algs=1

ignore_broadcast_ssid=0

wme_enabled=1

wme_ac_bk_cwmin=4
wme_ac_bk_cwmax=10
wme_ac_bk_aifs=7
wme_ac_bk_txop_limit=0
wme_ac_bk_acm=0

wme_ac_be_aifs=3
wme_ac_be_cwmin=4
wme_ac_be_cwmax=10
wme_ac_be_txop_limit=0
wme_ac_be_acm=0

wme_ac_vi_aifs=2
wme_ac_vi_cwmin=3
wme_ac_vi_cwmax=4
wme_ac_vi_txop_limit=94
wme_ac_vi_acm=0

wme_ac_vo_aifs=2
wme_ac_vo_cwmin=2
wme_ac_vo_cwmax=3
wme_ac_vo_txop_limit=47
wme_ac_vo_acm=0


ieee80211n=1
ht_capab=[SMPS-STATIC][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC]


eapol_key_index_workaround=0

eap_server=0

own_ip_addr=127.0.0.1

wpa=2

wpa_passphrase=victoria

wpa_key_mgmt=WPA-PSK

wpa_pairwise=TKIP
rsn_pairwise=CCMP

[/code1e27i54m]
/etc/dhcp3/dhcpd.conf
[code1e27i54m]
log-facility local7;
max-lease-time 691200;

# wlan0 wirless network
subnet 192.168.2.0 netmask 255.255.255.0 {
authoritative;
option domain-name-servers 216.254.141.2, 209.90.160.220;
option routers 192.168.2.1;
range 192.168.2.3 192.168.2.10;
option broadcast-address 192.168.2.255;
option subnet-mask 255.255.255.0;
}
#eth0 wired network
subnet 192.168.0.0 netmask 255.255.255.0 {
authoritative;
option domain-name-servers 216.254.141.2, 209.90.160.220;
option routers 192.168.0.1;
range 192.168.0.4 192.168.0.10;
option broadcast-address 192.168.0.255;
option subnet-mask 255.255.255.0;
}
[/code1e27i54m]

ifconfig
[code1e27i54m]
eth0 Link encap:Ethernet HWaddr e0:cb:4e:54:c0:00
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:36438 (36.4 KB)
Interrupt:49 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:19:5b:68:89:6b
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:57231 errors:0 dropped:0 overruns:0 frame:0
TX packets:47845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15932918 (15.9 MB) TX bytes:7583390 (7.5 MB)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:17013 errors:0 dropped:0 overruns:0 frame:0
TX packets:17013 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2408687 (2.4 MB) TX bytes:2408687 (2.4 MB)

mon.wlan0 Link encap:UNSPEC HWaddr 00-25-9C-E3-3C-91-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2340 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:215880 (215.8 KB) TX bytes:0 (0.0 B)

ppp0 Link encap:Point-to-Point Protocol
inet addr:173.206.233.27 P-t-P:173.206.232.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:50190 errors:0 dropped:0 overruns:0 frame:0
TX packets:46754 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:14177012 (14.1 MB) TX bytes:6297902 (6.2 MB)

wlan0 Link encap:Ethernet HWaddr 00:25:9c:e3:3c:91
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3267 errors:0 dropped:0 overruns:0 frame:0
TX packets:3101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:554702 (554.7 KB) TX bytes:589075 (589.0 KB)
[/code1e27i54m]
iwconfig
[code1e27i54m]
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

ppp0 no wireless extensions.

wlan0 IEEE 802.11abgn Mode:Master Frequency:2.412 GHz Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

mon.wlan0 IEEE 802.11abgn Mode:Monitor Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
[/code1e27i54m]

nan

07-09-2010 14:47:48

[quote1bou6d30]I can still see it is using ipv6 addressing.[/quote1bou6d30]
last iphone will try to use ipv6 by default. also, where is a bug.
from google http//www.klammeraffe.org/~brandy/iOS4WLAN.html + discussions.apple.com

i use dnsmasq as dhcp server.

wrostek

12-09-2010 18:52:21

Just an update, After the post from NAN, I decided to try to connect to my AP from another Linux box I have ( instead of the iPhone ). I was able to connect, and was assigned an IPv4 address. So I attempted again with the iPhone and it worked!. I'm not sure why the iPhone wasn't getting the proper IP address at first. My setup has been running 3 or 4 days now, and its rock solid lol .

The only problem I face now is when I go into hostapd and try to set the option ieee80211n=1 , hostapd and the rt2800pci driver crash. I believe this is because rt2800pci does not support 80211n mode yet. Anyone have any idea when this may be coming?

IvD

12-09-2010 22:55:57

The only problem I face now is when I go into hostapd and try to set the option ieee80211n=1 , hostapd and the rt2800pci driver crash. I believe this is because rt2800pci does not support 80211n mode yet. Anyone have any idea when this may be coming?[/quote2n0miznj]

Practically all 11n features which the device supports have been implemented in the driver. And even if they are not, they should never cause the driver to crash. So could you give some more details about this issue?

wrostek

10-10-2010 20:10:03

I have been trying some different configurations, and waiting for Ubuntu 10.10 to be released to see if it was a problem in the beta, but I still cant get it to work in 802.11n.

To recap my problem, I am trying to get my WMP600N to work in 802.11n mode as an AP. So far, I have it working flawlessly in 802.11g, but when I add the option ieee80211n=1 to hostapd.conf, hostapd wont start.

Here is my info

I am using driver rt2800pci. I have tried to download and compile the latest compat-wireless package, but it still wont work, so I decided to stick with the version that ubuntu 10.10 provides linux-backports-modules-wireless-2.6.35-22-generic
[code1g70h0tu]
filename: /lib/modules/2.6.35-22-generic/kernel/drivers/net/wireless/rt2x00/rt2800pci.ko
license: GPL
firmware: rt2860.bin
description: Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 2F80455F839A36244226CB5
[/code1g70h0tu]

I am using the latest RT2860_Firmware_V26 from the ralink site for the firmware. ( rt2860.bin )

I have tried using various hostapd versions, but I cant get any of them working in n mode. I noticed that hostapd v0.6.10, which comes default in Ubuntu 10.10, rejects all authentication requests, I'm not sure why. I have settled settled on hostapd v0.7.3, which I downloaded and compiled. I can authenticate to it, but it seems to only work in g mode.

My hostapd.conf looks like this
[code1g70h0tu]
interface=wlan0
bridge=br0
driver=nl80211
ssid=LiNuX_b0x
hw_mode=g
channel=1
#wmm_enabled=1
#ieee80211n=1
ht_capab=[SMPS-STATIC][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC123]
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=xxxxx
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
[/code1g70h0tu]

Notice that ieee80211n=1 is commented out. This brings the device up perfectly, but only in g mode. As soon as a uncomment that line, to try N mode, hostapd refuses to start. I get the following error


[code1g70h0tu]
/usr/sbin/hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Opening raw packet socket for ifindex 248
BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=10 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=10 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=10 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=11 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=11 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=11 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=12 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=12 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=12 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=12 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=12 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=10 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=10 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=10 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=11 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=11 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=11 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=12 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=12 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=12 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=12 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=12 dBm
RATE[0] rate=10 flags=0x2
RATE[1] rate=20 flags=0x6
RATE[2] rate=55 flags=0x6
RATE[3] rate=110 flags=0x6
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
Passive scanning not supported
Mode: IEEE 802.11g Channel: 1 Frequency: 2412 MHz
Could not set channel for kernel driver
wlan0: Unable to setup interface.
[/code1g70h0tu]

Can anyone offer some suggestions?

wrostek

19-10-2010 01:55:41

I got the AP working in wireless N mode. I grabbed another recent copy of compat-wireless ( compat-wireless-2010-10-17 )
and compiled it, along with a bleeding edge hostapd ( hostapd v0.8.x ) and it finally brought up my WMP600N in wireless N AP mode
in Ubuntu 10.10! 8)

[code18vyf73s]
mon.wlan0 IEEE 802.11abgn Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
[/code18vyf73s]

Now my next problem, I have a Gentoo linux box, using an Asus N13-USB usb adapter. I'm trying to get it working
in wireless N mode to connect to my new AP!

I believe it should work with rt2800usb. But when I load the module, it detects it, downloads the firmware ( RT2870.bin ), and then
I get these errors... roll

[code18vyf73s]
Oct 17 21:00:54 betty kernel: [ 304.564605] phy1 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'.
Oct 17 21:00:54 betty kernel: [ 304.564621] rt2800usb 2-1:1.0: firmware: requesting rt2870.bin
Oct 17 21:00:54 betty kernel: [ 304.580720] phy1 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.22.
Oct 17 21:01:05 betty kernel: [ 315.398491] phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
Oct 17 21:01:05 betty kernel: [ 315.428475] phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
Oct 17 21:01:05 betty kernel: [ 315.458469] phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
Oct 17 21:01:05 betty kernel: [ 315.488462] phy1 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
Oct 17 21:01:05 betty kernel: [ 315.518646] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Oct 17 21:01:30 betty kernel: [ 340.284143] ohci_hcd 0000:00:02.3: urb dee4bf80 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.284153] ohci_hcd 0000:00:02.3: urb dfbd6a80 path 1 ep0out 5ec20000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.285141] ohci_hcd 0000:00:02.3: urb dee4b300 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.286143] ohci_hcd 0000:00:02.3: urb dee4bc00 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.287141] ohci_hcd 0000:00:02.3: urb dee4be00 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.287151] ohci_hcd 0000:00:02.3: urb dfbd6a80 path 1 ep0out 5ec20000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.287418] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1328 with error -62.
Oct 17 21:01:30 betty kernel: [ 340.288141] ohci_hcd 0000:00:02.3: urb dee4ba80 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.289143] ohci_hcd 0000:00:02.3: urb df98d500 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.290141] ohci_hcd 0000:00:02.3: urb df98d480 path 1 ep1in 5e160000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.392120] ohci_hcd 0000:00:02.3: urb dfbd6a80 path 1 ep0in 5ec20000 cc 5 --> status -62
Oct 17 21:01:30 betty kernel: [ 340.392151] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -62.
Oct 17 21:01:30 betty kernel: [ 340.392261] phy1 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xdfbcfda8
Oct 17 21:01:30 betty kernel: [ 340.395120] ohci_hcd 0000:00:02.3: urb dfbd6a80 path 1 ep0in 5ec20000 cc 5 --> status -62
[/code18vyf73s]

A large amount of errors like that, and ultimately it wont start. Not sure what is the cause.. I have heard some people say this is related to ACPI in the bios, and it should be disabled. I tried to do that, but it didnt seem to help. Other people have mentioned ensuring that the wireless card should be 'iwconfig power off' , I have added that to my /etc/conf.d/net but still no dice. Any Suggestions?

Mony

29-10-2010 06:21:56

Just want to thank everyone working on the driver. I've been using a version which was working rock stable but didnt had N support for a while, and i've checked the last compat-wireless and there it was! I'm running rt2860 pci card in master mode (+ N) and works perfect! Tested with 1x2 intel 5100 as client - 14-15 MB/s stable download. Thanks again guys! D

@wrostek
as far as i know rt28xxusb is still WIP

MatejB

04-11-2010 11:27:55

I was wondering why the Kconfig in the latest linux tree still says that the rt2800pci driver is non-functional at the moment. I tested the driver for few months and it works flawlessly.

xek2

26-11-2010 20:42:44

Dear friends, I have problems setting WMP600N in master mode @ 5 Ghz band.

I'm using wrostek's config (at the top of this page), and I compiled latest hostapd & compat-wireless.

I succeded doing it with channels 1, 3 etc., but when I change channel setting to 40, 140, 149, 160 etc. in hostapd.conf, it says

[code7mto46wr]
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 4
nl80211: New interface mon.wlan0 created: ifindex=6
nl80211: Add own interface ifindex 6
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=CA
nl80211: 2402-2472 @ 40 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5250-5330 @ 40 MHz
nl80211: 5490-5710 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=27 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=27 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=38 freq=5190 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=46 freq=5230 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=151 freq=5755 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=159 freq=5795 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=15 dBm
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=15 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=27 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=27 dBm
wlan0: IEEE 802.11 Configured channel (149) not found from the channel list of current mode (1) IEEE 802.11g
wlan0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
Flushing old station entries
Deauthenticate all stations
rmdir[ctrl_interface]: No such file or directory
nl80211: Remove interface ifindex=6
netlink: Operstate: linkmode=0, operstate=6[/code7mto46wr]

I don't clearly understand how to enable mode 2.

xek2

26-11-2010 22:01:36

Somehow I managed to bring it up and working on 5 ghz.
I copied original hostap.conf, changed country to US and it works @ 802.11n & 5 Ghz!

Not so stable as I expected, but works.

helmut

28-11-2010 01:39:24

Not so stable as I expected, but works.[/quote3fc3srnb]

Could you please elaborate? Which instabilities are you experiencing?

C00LM4N

28-11-2010 13:07:01

Hi all. Having a problem with 802.11n and WPA/2, rt2860pci.
compat-wireless-2.6.37
hostapd & wpa_supplicant 0.8.x
lastest gentoo kernel 2.6.35

If I disable .n mode in hostapd everything works fine with any encryption type (in .g mode).
But when I enable WPA/2 in .n mode clients are deauthed every 10 minutes.
As I understand rekeying happens every 10 minutes by default, even if the corresponding lines in hostapd.conf are coommented out, just like that
[code7guxcziz]# Time interval for rekeying GTK (broadcast/multicast encryption keys) in
# seconds. (dot11RSNAConfigGroupRekeyTime)
#wpa_group_rekey=600

# Maximum lifetime for PTK in seconds. This can be used to enforce rekeying of
# PTK to mitigate some attacks against TKIP deficiencies.
#wpa_ptk_rekey=600
[/code7guxcziz]

hostapd log in time of deauth
[code7guxcziz]wlan0: WPA rekeying GTK
WPA: group state machine entering state SETKEYS (VLAN-ID 0)
GMK - hexdump(len=32): [REMOVED]
GTK - hexdump(len=16): [REMOVED]
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:16:eb:0b:8c:d2 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
wpa_group_setkeys: GKeyDoneStations=1
IEEE 802.1X: 00:16:eb:0b:8c:d2 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:16:eb:0b:8c:d2 WPA: EAPOL-Key timeout
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:16:eb:0b:8c:d2 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
IEEE 802.1X: 00:16:eb:0b:8c:d2 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:16:eb:0b:8c:d2 WPA: EAPOL-Key timeout
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:16:eb:0b:8c:d2 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
IEEE 802.1X: 00:16:eb:0b:8c:d2 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:16:eb:0b:8c:d2 WPA: EAPOL-Key timeout
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:16:eb:0b:8c:d2 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
IEEE 802.1X: 00:16:eb:0b:8c:d2 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:16:eb:0b:8c:d2 WPA: EAPOL-Key timeout
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state REKEYNEGOTIATING
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state KEYERROR
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
wpa_driver_nl80211_set_key: ifindex=16 alg=3 addr=(nil) key_idx=2 set_tx=1 seq_len=0 key_len=16
WPA: 00:16:eb:0b:8c:d2 WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:16:eb:0b:8c:d2 reason 2
WPA: 00:16:eb:0b:8c:d2 WPA_PTK_GROUP entering state IDLE
WPA: 00:16:eb:0b:8c:d2 WPA_PTK entering state DISCONNECTED
WPA: 00:16:eb:0b:8c:d2 WPA_PTK entering state INITIALIZE
wpa_driver_nl80211_set_key: ifindex=16 alg=0 addr=0x8e94c18 key_idx=0 set_tx=1 seq_len=0 key_len=0
addr=00:16:eb:0b:8c:d2
wlan0: STA 00:16:eb:0b:8c:d2 IEEE 802.1X: unauthorizing port
wlan0: STA 00:16:eb:0b:8c:d2 IEEE 802.11: deauthenticated due to local deauth request[/code7guxcziz]

Before I upgraded wpa_supplicant to 0.8.x I had an unstable connection in .n mode using WPA/2 - very high pings, slow speed (about 1MB/s and slower), etc. After updating - 19-20MB/s and everything good, except this deauth problem.
Is it driver or wpa_supplicant bug?

xek2

30-11-2010 23:57:54

Not so stable as I expected, but works.[/quote34nii0yy]

Could you please elaborate? Which instabilities are you experiencing?[/quote34nii0yy]

Sorry, had no emails that somebody answered, now i see it, now I'll try to make ameds.

First of all being lauched first time after boot hosapd starts with exactly same error

[code34nii0yy]
root@servant:/etc/hostapd# ./hostapd.sh | less
rmdir[ctrl_interface]: No such file or directory
Configuration file: /etc/hostapd/my.conf
ctrl_interface_group=0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 4
nl80211: Add own interface ifindex 5
nl80211: New interface mon.wlan0 created: ifindex=6
nl80211: Add own interface ifindex 6
nl80211: Adding interface wlan0 into bridge br0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz
nl80211: 2457-2482 @ 20 MHz
nl80211: 2474-2494 @ 20 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
wlan0: IEEE 802.11 Configured channel (40) not found from the channel list of current mode (2) IEEE 802.11a
wlan0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
Flushing old station entries
Deauthenticate all stations
nl80211: Remove interface ifindex=6
netlink: Operstate: linkmode=0, operstate=6
[/code34nii0yy]


This can be fixed I believe. Maybe this is because wlan0 is down at that moment. (It's configured in a bridge with eth0).


Second problem is that sometimes it crashes, partly hanging the whole system (especially all network parts like ifconfig/iwconfig). But it only happens when I change smth in the system (I mean launching different programs, changing ifconfig params). When the server it just working as access point it works okay. I'll investigate that.

Nevertheless a huge work has been done and I'm happy putting my WMP600N back to work since last year, when Ralink's rt2860ap driver became incompatible with newer versions of linux. Btw, I have them, they are a bit outdated, but if somebody needs them, I can share them.

helmut

01-12-2010 09:23:06


[code23y26b5b]
root@servant:/etc/hostapd# ./hostapd.sh | less
...
nl80211: Regulatory information - country=00
...
[/code23y26b5b]
This can be fixed I believe. Maybe this is because wlan0 is down at that moment. (It's configured in a bridge with eth0).
[/quote23y26b5b]

Please try to add a "country_code=XX" to your hostapd.conf where XX is the country code of your country. Not sure if that helps though ...


Second problem is that sometimes it crashes, partly hanging the whole system (especially all network parts like ifconfig/iwconfig). But it only happens when I change smth in the system (I mean launching different programs, changing ifconfig params). When the server it just working as access point it works okay. I'll investigate that.
[/quote23y26b5b]

Hmm, not nice, if you can get a call trace from the kernel (maybe via netconsole) we might be able to fix this.

Helmut

xek2

03-12-2010 13:21:53

country_code=US is already in config file, but it always starts being lauched second time, but not first.
Don't know why, but first lauch always shows this
[quote22hcfeq9]nl80211 Regulatory information - country=00[/quote22hcfeq9]


Concerning the hanging problem sorry, It never hang during this week. I take my words back, after I stoppepd playing with hostapd.conf it works okay. Great work.

helmut

05-12-2010 11:32:07

country_code=US is already in config file, but it always starts being lauched second time, but not first.
Don't know why, but first lauch always shows this
[quote1tl2ee5k]nl80211 Regulatory information - country=00[/quote1tl2ee5k]
[/quote1tl2ee5k]
Strange, could you please check which regulatory domain is set prior to starting hostapd?
[code1tl2ee5k]iw reg get[/code1tl2ee5k]
Do things improve when you set the regulatory domain before starting hostapd?
[code1tl2ee5k]iw reg set US[/code1tl2ee5k]

xek2

06-12-2010 21:36:04

[code25shiv22]root@servant:~# iw reg get
country 00:
(2402 - 2472 @ 40), (3, 20)
(2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
(2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
(5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
(5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS[/code25shiv22]


after I launch hostapd
[code25shiv22]root@servant:/etc/hostapd# iw reg get
country US:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 20), DFS
(5490 - 5600 @ 40), (3, 20), DFS
(5650 - 5710 @ 40), (3, 20), DFS
(5735 - 5835 @ 40), (3, 30)[/code25shiv22]

helmut

07-12-2010 06:41:54

[code1ueaoo9b]root@servant:~# iw reg get
country 00:
(2402 - 2472 @ 40), (3, 20)
(2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
(2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
(5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
(5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS[/code1ueaoo9b]


after I launch hostapd
[code1ueaoo9b]root@servant:/etc/hostapd# iw reg get
country US:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 20), DFS
(5490 - 5600 @ 40), (3, 20), DFS
(5650 - 5710 @ 40), (3, 20), DFS
(5735 - 5835 @ 40), (3, 30)[/code1ueaoo9b][/quote1ueaoo9b]

Thanks, this is clearly a hostapd bug. hostapd sets the regulatory domain but before the reg domain is set up correctly within the kernel it already creates the channel list based on the previous reg domain. Using
[code1ueaoo9b]iw reg set US[/code1ueaoo9b] before starting up hostapd should work around this issue.

Helmut

xek2

07-12-2010 11:21:51

Ok, I'll add iw reg set US, before hostapd, no problem.
Thanks

ash

09-12-2010 01:33:05

Are there any bugfixes in the pipeline for rt2800pci?

I've been using the compat-wireless version for some time now and there are a few quirks still.

For one I have to manually change the timeout for initialization [1][/url1t3zm7ht] and also it often
takes multiples unloads/loads to make hostapd work at all. It seems to be particularly
picky about eeprom_93cx6 and only if I also unload that one as well it might
work on the next try. If I dont unload eeprom_93cx6 it its basically guaranteed to not work
the second try either.

Sometimes it would not bring up mon.wlan0, sometimes it will bring up mon.wlan0 but
not do anything and sometimes it will bring up everything correctly but the IRQ process
will take up a lot of cpu time making even the shell on a multi-cpu box very sluggish.

Manually unloading and reloading all modules associated with rt2800pci will fix it at
some point.

Posting reset to the phy does not help.

Latest Firmware from the ralinktech website (26 from march iirc)

Driver version used
[code1t3zm7ht]
filename: /lib/modules/2.6.34.7-0.5-xen/updates/drivers/net/wireless/rt2x00/rt2800pci.ko
license: GPL
firmware: rt2860.bin
description: Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 9F64E7029DA63951A0E1346
alias: pci:v00001A3Bd00001059sv*sd*bc*sc*i*
alias: pci:v00001432d00007768sv*sd*bc*sc*i*
alias: pci:v00001432d00007758sv*sd*bc*sc*i*
alias: pci:v00001432d00007748sv*sd*bc*sc*i*
alias: pci:v00001432d00007738sv*sd*bc*sc*i*
alias: pci:v00001432d00007728sv*sd*bc*sc*i*
alias: pci:v00001432d00007727sv*sd*bc*sc*i*
alias: pci:v00001432d00007708sv*sd*bc*sc*i*
alias: pci:v00001814d00000781sv*sd*bc*sc*i*
alias: pci:v00001814d00000701sv*sd*bc*sc*i*
alias: pci:v00001814d00000681sv*sd*bc*sc*i*
alias: pci:v00001814d00000601sv*sd*bc*sc*i*
depends: rt2x00lib,rt2800lib,rt2x00pci,eeprom_93cx6
vermagic: 2.6.34.7-0.5-xen SMP mod_unload modversions Xen
parm: nohwcrypt:Disable hardware encryption. (bool)[/code1t3zm7ht]

Error Message
[code1t3zm7ht]
kernel: [353955.667258] rt2800pci 0000:0b:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
kernel: [353955.675082] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
kernel: [353955.676628] Registered led device: rt2800pci-phy2::radio
kernel: [353955.676648] Registered led device: rt2800pci-phy2::assoc
kernel: [353955.676666] Registered led device: rt2800pci-phy2::quality
ifup: wlan0 device: RaLink RT2800 802.11n PCI
ifup-wireless: wlan0 warning: WPA configured, but is untested
ifup-wireless: wlan0 warning: with this device
ifup-wireless: wlan0 starting wpa_supplicant
kernel: [353955.980713] rt2800pci 0000:0b:00.0: firmware: requesting rt2860.bin
kernel: [353956.024252] phy2 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
kernel: [353956.072020] phy2 -> rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
kernel: [353956.072025] phy2 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
kernel: [353956.108100] phy2 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
kernel: [353956.156017] phy2 -> rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
kernel: [353956.156022] phy2 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
kernel: [353956.197575] phy2 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
kernel: [353956.244018] phy2 -> rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
kernel: [353956.244023] phy2 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).
ifup: Cannot enable interface wlan0.
ifup-route: interface wlan0 is not up[/code1t3zm7ht]

jay.slovak

10-01-2011 16:49:56

Hi,

I have been using the driver for several months and it's been working ok (its not great, but works). I have been upgrading to latest builds every now and then. But the driver has stopped working for me since I upgraded from compat-wireless-2010-11-05. I have reverted to this version and I try the new versions to see if my issue got fixed. I have tested several versions of hostapd (0.6 from squeeze, 0.7.3 from sid and even compiled 0.8.x).

I am using the 802.11n in 5GHz mode on WMP600n, under Debian Squeeze 32bit 2.6.32-5-686. The problem is that in the new versions of the driver, the 5GHz channels are disabled, and I think its caused by the regulatory country being "00"
[code1pekbs4j]
[root@kevin /usr/local/bin]# iw list
~~~
Frequencies:
* 5180 MHz [36] (15.0 dBm) (passive scanning, no IBSS)
* 5190 MHz [38] (15.0 dBm) (passive scanning, no IBSS)
* 5200 MHz [40] (15.0 dBm) (passive scanning, no IBSS)
* 5220 MHz [44] (15.0 dBm) (passive scanning, no IBSS)
* 5230 MHz [46] (15.0 dBm) (passive scanning, no IBSS)
* 5240 MHz [48] (15.0 dBm) (passive scanning, no IBSS)
* 5260 MHz [52] (disabled)
* 5270 MHz [54] (disabled)
* 5280 MHz [56] (disabled)
* 5300 MHz [60] (disabled)
* 5310 MHz [62] (disabled)
* 5320 MHz [64] (disabled)
* 5500 MHz [100] (disabled)
* 5510 MHz [102] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5550 MHz [110] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5590 MHz [118] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5630 MHz [126] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5670 MHz [134] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5745 MHz [149] (15.0 dBm) (passive scanning, no IBSS)
* 5755 MHz [151] (15.0 dBm) (passive scanning, no IBSS)
* 5765 MHz [153] (15.0 dBm) (passive scanning, no IBSS)
* 5785 MHz [157] (15.0 dBm) (passive scanning, no IBSS)
* 5795 MHz [159] (15.0 dBm) (passive scanning, no IBSS)
* 5805 MHz [161] (15.0 dBm) (passive scanning, no IBSS)
* 5825 MHz [165] (15.0 dBm) (passive scanning, no IBSS)
* 5835 MHz [167] (disabled)
* 5845 MHz [169] (disabled)
* 5855 MHz [171] (disabled)
* 5865 MHz [173] (disabled)
* 5920 MHz [184] (disabled)
* 5940 MHz [188] (disabled)
* 5960 MHz [192] (disabled)
* 5980 MHz [196] (disabled)
* 6040 MHz [208] (disabled)
* 6060 MHz [212] (disabled)
* 6080 MHz [216] (disabled)

[root@kevin ~]# iw reg get
country 00:
(2402 - 2472 @ 40), (6, 20)
(2457 - 2482 @ 20), (6, 20), PASSIVE-SCAN, NO-IBSS
(2474 - 2494 @ 20), (6, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
(5170 - 5250 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS
(5735 - 5835 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS

[/code1pekbs4j]

I have read the forum and tried what the people have been suggesting, like to set the regulatory country manually before hostapd starts, and then start hostapd
[code1pekbs4j]
[root@kevin /usr/local/bin]# iw reg set US
[root@kevin /usr/local/bin]# iw reg get
country 00:
(2402 - 2472 @ 40), (6, 20)
(2457 - 2482 @ 20), (6, 20), PASSIVE-SCAN, NO-IBSS
(2474 - 2494 @ 20), (6, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
(5170 - 5250 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS
(5735 - 5835 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS
[/code1pekbs4j]

I have even added a modprobe rule that forces the regulatory country
[code1pekbs4j]
[root@kevin /home]# cat /etc/modprobe.d/cfg80211.conf
options cfg80211 ieee80211_regdom=EU
[/code1pekbs4j]

[code1pekbs4j]
[root@kevin /home]# grep -v ^$ /etc/hostapd/hostapd.conf | grep -v '#'
interface=wlan0
bridge=br0
driver=nl80211
logger_syslog=-1
logger_syslog_level=3
logger_stdout=-1
logger_stdout_level=1
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=****
country_code=US
ieee80211d=0
hw_mode=a
channel=52
beacon_int=100
dtim_period=2
max_num_sta=255
rts_threshold=2347
fragm_threshold=2346
macaddr_acl=0
auth_algs=3
ignore_broadcast_ssid=0
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
ieee80211n=1
ht_capab=[LDPC][HT40-][HT40+][SMPS-STATIC][SHORT-GI-40][TX-STBC][RX-STBC12][DSSS_CCK-40][PSMP]
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1
wpa=2
wpa_passphrase=****
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
wpa_group_rekey=600
wpa_gmk_rekey=86400
[/code1pekbs4j]

I have tried to put in my country ID, EU, or even US, nothing works. If I try to set it manually. I get one line the syslog that says it is changing it, but that is a lie...

So, do you have any suggestions?

wims

14-01-2011 01:30:39

can somebody move all the hostap posts to another topic, i dont really want to read page after page about hostap when i try to find new info about my usb stick

eugeneblack

15-01-2011 13:17:33

Git comments [code3r0d0m9x]rt2x00: Fix radio off hang issue for PCIE interface
rt2x00: Fix and fine-tune rf registers for RT3070/RT3071/RT3090
[/code3r0d0m9x] solved [code3r0d0m9x]kernel: [353956.156017] phy2 -> rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
kernel: [353956.156022] phy2 -> rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5).[/code3r0d0m9x] problem for me. Kernel 2.6.37 (x86_64), compat-wireless-2011-01-09 with manually added patches from git.
lspci -k
[code3r0d0m9x]43:00.0 Network controller: RaLink RT3090 Wireless 802.11n 1T/1R PCIe
Subsystem: Hewlett-Packard Company Device 1453
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
[/code3r0d0m9x]
Great job! Thanks! )

C00LM4N

16-01-2011 16:43:04

After many times trying different settings and hostapd/wpa_supplicant verisons I still can't make my rt2860 card working stable in AP mode with 802.11n support. Latest kernel, compat-wireless nad hostapd. Even tried svn snapshots )
[codeezr0r458]
02:04.0 Network controller: RaLink Unknown device 0601
Subsystem: RaLink Unknown device 2860
Flags: bus master, slow devsel, latency 32, IRQ 16
Memory at fe6e0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
[/codeezr0r458]
First issue is deauth when group rekeying happens. If I disable group rekeying that error doesn't appear.
Second is connection freezes (for 5-10 seconds in any time, but it's often happens while network is being heavy loaded). I think it's driver-relevant, cos hostapd shows nothing in debug output in these moments.
And third - system totally stalls (only hard reset helps) after some rt2800pci module loadings/unloadings when trying to do "ifconfig wlan0 up" with driver module error output in main console. This trouble also often occurs if I start/stop hostapd without reloading driver modules.

If I switch to .g mode all works perfect with any versions of kernel/compat/hostapd

Also, "iwconfig wlan0" results in driver crash.

[codeezr0r458]ussr ~ # modprobe rt2800pci
ussr ~ # iwconfig wlan0
Killed[/codeezr0r458]

C00LM4N

07-04-2011 15:23:29

Deauth problem gone away. Don't exactly know what helped...

For now only connection freezes remains. I updated kernel, compat-wireless, hostapd and wpa supplicant. As I said above there is no debug output from hostapd when freeze happens. It often happens when I'm downloading huge amount of data, such as setup or video file. My notebook (client) transfers packets but don't receive it, just like the rt2x00 driver or NIC itself stalls.
Don't developers read this thread? No answers...