Just so everyone knows--in Jaunty, the ralink drivers are compiled in--so things like this will no longer be needed......I'm on the current testing Jaunty & worked with the kernel team to get the drivers included.....

Just so everyone knows--in Jaunty, the ralink drivers are compiled in--so things like this will no longer be needed......I'm on the current testing Jaunty & worked with the kernel team to get the drivers included.....

Great, too bad they don't work. At least not with WPA/WPA2. I just upgraded from Intrepid to Jaunty and although I can "see" wireless networks, the connection fails.

*sigh*

It's always RALink and something is always broken. I'm to the point where I'll go out of my way to buy anything from anybody else (even Broadcom's proprietary crap that at least WORKS .. without needing 2 years of continuous screwing around).

Sorry, my frustration at YetAgain<tm> having to dig up a solution to a problem that was fixed, then wasn't, then was (for some), then wasn't .. ad nauseum is peaking out.

Great, too bad they don't work. At least not with WPA/WPA2. I just upgraded from Intrepid to Jaunty and although I can "see" wireless networks, the connection fails.

*sigh*

It's always RALink and something is always broken. I'm to the point where I'll go out of my way to buy anything from anybody else (even Broadcom's proprietary crap that at least WORKS .. without needing 2 years of continuous screwing around).

Sorry, my frustration at YetAgain<tm> having to dig up a solution to a problem that was fixed, then wasn't, then was (for some), then wasn't .. ad nauseum is peaking out.

Well--I'm using the driver in Jaunty & it works very well...I did make a /etc/Wireless/RT2860 with a modified .dat in it & I use WPA2.

The .dat is the one that came stock with the driver & I did as recommended---add the bit in /etc & edited the .dat for what I wanted---the info you need is in the Driver Info.tar I posted--I'll post the mod .dat if you want also....it's for N networks only, but it only takes a bit of modifying to work with B & G too...

If you've followed the last year's saga on launchpad you'll notice that the dat file should not be needed. And what ever happened to "It just works" .. I can't see your average Joe Blow screwing around with a cryptic config file.

FYI I nuked the kernel module on one of my broken machines and replaced it with Adam McDaniel's 1.7.1.1 DKMS module and WPA/WPA2 work without the dat just like they did before some (expletive deleted) decided to ship a broken-yet-again one. So it SHOULDN'T be needed if somebody upstream would actually leave the fixes in the code and/or regresssion test before shipping his latest cool idea.

Sorry, but this driver has over a year of screwing around behind it, and I've lost count of the times somebody has "upgraded" it and left out a fix or re-broken something. Somebody should be really ashamed that this junk is what got shipped when there was a working version.

This is a tutorial for getting Ralink's RT2760/RT2790/RT2860/RT2890-based (m)PCI(e) cards running on Intrepid with the latest Linux drivers provided on Ralink's website. You will need a wired connection to download the pertinent files.

You are looking for the "RT2860PCI/mPCI/PCIe/CB(RT2760/RT2790/RT2860/RT2890)" package. Download it and save it to your home directory.

Start a terminal and install the build-essential and linux-headers packages (if you don't have them already):

Code:

sudo aptitude install linux-headers-`uname -r` build-essential

Now, in your home folder untar the Ralink package:

Code:

tar -xvjf 2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2

Edit the 2008_0918_RT2860_Linux_STA_v1.8.0.0/os/linux/config.mk file to allow network-manager to manage the card:

ok i have a few questions, as i am new to ubuntu, and already feel over my head, i have gotten this far but it opened a new window that is blank, called [*config.mk , what should i do to this window? i have tried to put the codes down with edits to the newest driver name, but nothing seems to work right.