Hi! not wanting to discourage the users in anyway, let me make things clear.
No Ralink card will work with any of the available drivers in AP (master) mode. Work is under way to achieve this, but only for 2.6 kernels. In fact all wireless cards from Ralink are currently scheduled for inclusion in the kernel, perhaps only with 2.6.21 or later releases. As for the available drivers, I would go for the one supplied by my team @ http://rt2x00.serialmonkey.com, if in doubt use the CVS version. Note that I do not say it will not work!!!! Just don't expect miracles. One other thing, don't forget to place the FIRMWARE files in the expected folder... Hope this statment would clarify things. Luis Correia > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Mats Erik Andersson > Sent: Monday, November 27, 2006 3:37 PM > To: [email protected] > Cc: [EMAIL PROTECTED] > Subject: [leaf-user] First try at Ralink driver rt61 > > > Fellow Bering-users, > > encouraged by an answer from Cédric Schieli, I went ahead to > bye myself two Ralink wireless cards CWP-854. > Unfortunately, they turned out not to react to the driver > rt2500.o present with Bering-uC 3.0, and this was due to the > fact that Ralink has as of late changed the chip set in their > economically priced cards. The new driver module is named rt61. > > Well, I fetched the source code for rt61 at > > http://www.ralink.com.tw/supp-1.htm > > and installed the buildtool for Bering-uClibc that so > benevolently is available to us all. After a little hacking > at the makefile for rt61 I managed, to my surprise, compile > the module at the first try. > (The test compilation for my Debian on a laptop was > elementary.) Then Bering nicely rewarded a simple 'insmod > rt61' by creating the desired interface ra0. > > Now, I must confess to being essentially illitterate in > matters concerning wireless cards, so I hope someone could > take the effort upon him to give me some pointers into > documents and procedures for testing and > > verifying wireless components, from the software point of > view. Of course, I would not object to someone else building > this driver for us all. I only hope that that person would > share his testing procedures with us; for my own edification at least! > > The source code rt61-sta-1.1.0.0 was released Nov. 22., so > Bering would be one of the first distributions to have it > going if we do take a go at it. This source code for rt61 > also includes code for wpa_supplicant support. > > Let me finally point out that Ralink has code release > 1.4.6.6 for rt2500, dated Oct. 12th, which is a good deal > more recent than version 1.1.0-beta4 that goes with rt2500 of > Bering-uClibc. Anyone feeling inspired? > > Regards > Mats E Andersson > > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to > share your opinions on IT & business topics through brief > surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge > &CID=DEVDEV > -------------------------------------------------------------- > ---------- > leaf-user mailing list: [email protected] > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
