Ralink RT2870 based USB Wireless N adapters (Ubuntu)

Hardware Compatibility
61

You’ve clearly a lot of expertise in Linux on the other hand I’m good in website programming (that’s how I make money). Therefore I know that the 16 character is not exactly a limit in the chat but that limit is imposed by the login screen. The code defining the username box says:

If you change the number in maxlength=“16” in something different or if you delete that part all together then the limit is set to the new number resp. there’s no limit anymore.
Note: I can see it is a PHP page so if you look into the PHP source you´ll probably see something that differs a bit from what I’ve pasted.

Anyway, back on topic:

  • The new version of the driver didn’t work. Instead in dmesg there are even more warnings issued. The relevant part is:

[ 22.875013] usbcore: registered new interface driver rt2870
[ 22.880899] rt3070sta: Unknown symbol usb_register_driver (err 0)
[ 22.882060] rt3070sta: Unknown symbol usb_put_dev (err 0)
[ 22.882479] rt3070sta: Unknown symbol usb_get_dev (err 0)
[ 22.883212] rt3070sta: Unknown symbol usb_submit_urb (err 0)
[ 22.884355] rt3070sta: Unknown symbol usb_free_coherent (err 0)
[ 22.949400] rt3070sta: Unknown symbol usb_control_msg (err 0)
[ 22.950701] rt3070sta: Unknown symbol usb_deregister (err 0)
[ 22.996995] rt3070sta: Unknown symbol usb_kill_urb (err 0)
.
.
.
[ 25.126505] Registered led device: rt2800usb-phy0::radio
[ 25.126584] Registered led device: rt2800usb-phy0::assoc
[ 25.126653] Registered led device: rt2800usb-phy0::quality
[ 25.127891] usbcore: registered new interface driver rt2800usb
[ 25.298559] udev[374]: renamed network interface wlan0 to wlan1

So it seems to register first rt2870 and somewhat later rt2800usb and then it renames the interface name which already was the wrong one?!

That sequence of warnings led me to a new thought. Your driver contains a readme file that file talks about changing certain values in the rt2870.dat file, like setting the SSID and so on. Is it necessary to do that because you didn’t mention it anywhere in this thread.

B.T.W.: I’ve finally performed the actions you’ve asked for:

lsmod | grep rt2 gives:

rt2800usb 9580 0
rt2800lib 30847 1 rt2800usb
crc_ccitt 1351 1 rt2800lib
rt2x00usb 9736 1 rt2800usb
rt2x00lib 29556 3 rt2800usb,rt2800lib,rt2x00usb
led_class 2633 1 rt2x00lib
mac80211 235189 3 rt2800lib,rt2x00usb,rt2x00lib
cfg80211 142680 2 rt2x00lib,mac80211
rt2870sta 565472 0

lshw -C network gives as relevant part:

*-network DISABLED
description: Wireless interface
physical id: 1
bus info: usb@1:1
logical name: wlan1
serial: 00:1f:1f:87:e1:61
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=rt2800usb driverversion=2.6.35-30-generic-pae firmware=N/A link=yes multicast=yes wireless=IEEE 802.11bgn

And for no particular reason I’ve tried /etc/init.d/networking restart
That command replied something about not being able to start wpa_supplicant.

and from iwconfig I can’t find the file with the output but it talks about wlan1 not being associated too.

My 10.10 is an upgrade, not a fresh install. In the past I’ve started with Ubuntu 9.04.

62

I take it the wpasupplicant package is installed ? … do you use WPA/WPA2 encryption ?

can you send the contents of /etc/network/interfaces

and the output from

sudo rfkill list
*-network DISABLED

Maybe a stupid question, but I also take it networking IS enabled in network manager ?

configuration: broadcast=yes driver=rt2800usb [b]driverversion=2.6.35-30-generic-pae[/b]

are you back on the 2.6.35 kernel ? … if not, you might want to look at installing linux-backports-modules-compat-wireless
http://packages.ubuntu.com/maverick/i386/linux-backports-modules-compat-wireless-2.6.38-2.6.35-30-generic-pae/download
direct link:
http://security.ubuntu.com/ubuntu/pool/universe/l/linux-backports-modules-2.6.35/linux-backports-modules-compat-wireless-2.6.38-2.6.35-30-generic-pae_2.6.35-30.22_i386.deb

BTW, you should be able to log into chat by shortening your username to the first 16 characters q7icmfm1x0h609c6 and entering your password… this should be done “automagically” when you click on the “chat” link at the top of every page… at least it is for me, it just shortens mine to Mark_Greaves_(PC and adds underscores in the spaces :o

16 characters is enough, otherwise the chat window could become very messy :wink: … first thing I do after logging into chat is change my name to Mark (/nick Mark) anyway :wink:

If you still have problems with chat, I’ll pass it on to our resident programming guru (Mad Penguin)

63

@Mark Greaves

Sadly no connection. Below is the information you requested. I looked at my black listed drivers but could not see anything similar to the rtlink drivers. Also I ensured I was using the latest driver you supplied and with root permissions
sudo su
make && make install

Thanks again

user@user-Desktop:~$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 145f:013a Trust
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 148f:5370 Ralink Technology, Corp.
Bus 002 Device 003: ID 090c:1000 Feiya Technology Corp. Flash Drive
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 03f0:4117 Hewlett-Packard LaserJet 1018
Bus 001 Device 002: ID 04a9:2224 Canon, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@user-Desktop:~$ sudo lshw -C network
[sudo] password for user:
*-network
description: Ethernet interface
product: RTL8111/8168B PCI Express Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth1
version: 02
serial: …
size: 100Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=192.168.1.71 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:41 ioport:de00(size=256) memory:fdaff000-fdafffff memory:fdae0000-fdaeffff memory:fda00000-fda0ffff
user@user-Desktop:~$ iwconfig
lo no wireless extensions.

eth1 no wireless extensions.

user@user-Desktop:~$ nm-tool

NetworkManager Tool

State: connected

  • Device: eth1 [Auto eth1] ----------------------------------------------------
    Type: Wired
    Driver: r8169
    State: connected
    Default: yes
    HW Address: …

    Capabilities:
    Carrier Detect: yes
    Speed: 100 Mb/s

    Wired Properties
    Carrier: on

    IPv4 Settings:
    Address: …
    Prefix: 24 (255.255.255.0)
    Gateway: …

    DNS: …

user@user-Desktop:~$ lsmod
Module Size Used by
nls_iso8859_1 12617 1
nls_cp437 12751 1
vfat 17335 1
fat 55505 1 vfat
nls_utf8 12493 1
isofs 39571 1
vesafb 13449 1
binfmt_misc 13213 1
fglrx 2434640 51
snd_hda_codec_hdmi 27479 1
snd_seq_midi 13132 0
snd_rawmidi 25269 1 snd_seq_midi
gspca_pac207 13301 0
snd_hda_codec_realtek 255820 1
gspca_main 27894 1 gspca_pac207
snd_seq_midi_event 14475 1 snd_seq_midi
ppdev 12849 0
snd_hda_intel 24140 2
snd_hda_codec 90901 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13274 1 snd_hda_codec
snd_pcm 80244 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq 51291 2 snd_seq_midi,snd_seq_midi_event
usblp 17827 0
videodev 75143 1 gspca_main
parport_pc 32111 1
snd_seq_device 14110 3 snd_seq_midi,snd_rawmidi,snd_seq
rt2870sta 410104 0
snd_timer 28659 2 snd_pcm,snd_seq
psmouse 73312 0
snd 55295 14 snd_hda_codec_hdmi,snd_rawmidi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
k8temp 12872 0
serio_raw 12990 0
crc_ccitt 12595 1 rt2870sta
shpchp 32345 0
sp5100_tco 13456 0
i2c_piix4 13095 0
soundcore 12600 1 snd
snd_page_alloc 14073 2 snd_hda_intel,snd_pcm
lp 13349 0
parport 36746 3 ppdev,parport_pc,lp
usb_storage 43946 1
uas 17676 0
firewire_ohci 31504 0
ahci 21591 2
firewire_core 56138 1 firewire_ohci
floppy 60032 0
crc_itu_t 12627 1 firewire_core
r8169 42534 0
libahci 25548 1 ahci
pata_atiixp 12968 1

64

I’m sorry to hear that on jamesrl’s computer things are still not working either. There’s apparently a lot of work to do by the Ubuntu community to support wireless dongle decently.

In the meantime I’ve done an experiment on my own. Apart from the Ubuntu Server I own a laptop the runs on Ubuntu 11.04 (kernel 2.6.38-10) and I’ve a second WLAN usb stick that also identifies to be a 148f:3070. So I decided to find out what happened if the internal WLAN card was disabled and instead the WLAN usb stick inserted. Result: it connected immediately to the wireless network. So we can conclude that kernel 2.6.38 supports WLAN usb sticks that identify as 148f:3070. I noticed a few interesting things:

  • According to lsmod it does not use RT2870 or RT 3070 drivers at all but it takes RT2x00:
    rt2870sta 450556 0
    rt2800usb 18235 0
    rt2800lib 45181 1 rt2800usb
    crc_ccitt 12667 2 rt2870sta,rt2800lib
    rt2x00usb 20330 1 rt2800usb
    rt2x00lib 49235 3 rt2800usb,rt2800lib,rt2x00usb
    mac80211 294370 3 rt2800lib,rt2x00usb,rt2x00lib
    parport_pc 36959 0
    cfg80211 178528 3 rt2x00lib,mac80211,r8192se_pci
    parport 46458 3 parport_pc,ppdev,lp

  • Even more interesting: it appears that the name has changed. It is not ra0 any longer but it seems to be wlan0 or wlan1 whatever is available. See this:

wlan1 IEEE 802.11bgn ESSID:“p2zFsepJ6jmue_MLehec2jVahWCW-jJE”
Mode:Managed Frequency:2.462 GHz Access Point: 00:04:0E:D0:8C:55
Bit Rate=9 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=33/70 Signal level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:2 Missed beacon:0

And this is confirmed by the output of lshw -C network:

*-network
description: Wireless interface
physical id: 4
bus info: usb@2:2.3
logical name: wlan1
serial: 00:06:4f:82:39:1c
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=rt2800usb driverversion=2.6.38-10-generic firmware=0.29 ip=10.0.0.12 link=yes multicast=yes wireless=IEEE 802.11bgn

So I’ve redefined my target. From the experiment I know that it should be definitely possible to get that adapter active in the new Ubuntu kernel and now I don’t longer care about how to achieve this. If there’s a nice driver package to do it that would be nice, but if I have to copy certain files between my laptop and my server I’ll take that too as a viable option. Right now I’m interested in if we can identify why it does work in Ubuntu Desktop version but not in Ubuntu Server version.

And we’ve few open questions:

You asked if networking is enabled in network manager. Well that question is not relevant because there’s no network manager. My server runs (of course) the Ubuntu Server version which has no desktop.
You asked if I was back on 2.6.35. It depends on how you see it. Currently there are multiple kernels on my server because I was hoping to find one in which the USB stick would work. I supposed the standard Maverick 2.6.35 kernel would be better so I did the tests on that one. But since that dongle on my laptop appears to work in 2.6.38 I’ll rather like to continue with that kernel now.
You asked for /etc/network/interfaces. I can give you that:

auto ra0
iface ra0 inet static
address 10.0.0.19
netmask 255.255.255.0
gateway 10.0.0.140
wpa-driver wext
wpa-ssid
wpa-ap-scan 2
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <I’d rather not publish the key online>

May be those ra0 items pose a problem now the interface name appears to be different?

A few supplemental observations:
My network is wpa/wpa2 mixed and it does not broadcast the ssid. Some fora state that will lead to problems. But in the old kernel 2.6.31 I can connect nevertheless.

You asked if wpasupplicant was installed. apt reports it’s installed and it is the newest version, so that’s a yes.

65

@ q7icmfm1x0h609c6xiok

Erm… yes ra0 will be a problem in /etc/network/interfaces because according to this post:
http://linuxforums.org.uk/hardware-compatibility/ralink-rt2870-based-usb-wireless-n-adapters-(ubuntu)/msg59151/#msg59151

*-network DISABLED description: Wireless interface physical id: 1 bus info: usb@1:1 logical name: wlan1 serial: 00:1f:1f:87:e1:61 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rt2800usb driverversion=2.6.35-30-generic-pae firmware=N/A link=yes multicast=yes wireless=IEEE 802.11bgn

The wireless connetcions logical name is wlan1,

so you need to change both instances of ra0 to wlan1 and then:

sudo ifup wlan1

Sorry I didn’t realise we were working on a server ::slight_smile:

jamesrl’s problem is different because his card doesn’t seem to be being recognised at all… probably a device ID issue… need to think on that one a bit.

66

@Mark:
Sorry, but it didn’t work.
For some weird reason in 2.6.35-30 the logical name has changed again and now it is once again ra0, so it should work but it doesn’t.
On 2.6.35-28 the logical name is now wlan0 while a few days ago starting the 2.6.35-28 kernel resulted in a freeze.
Well, I can live with whatever name the interface has but now I can bring up wlan0 but it won’t associate. May be something is wrong with my /etc/network/interfaces.
In this kernel and in a 2.6.38 kernel the led on the stick starts blinking like crazy but the stick can’t associate.
My modemrouter registers in its log that it sees the connection attempts of the server but it refuses them (it does not log why). Is it possible that the encoded wpa-psk key in /etc/network/interfaces has to be adjusted according to the new situation and that the modemrouter refuses it because it is wrong? In the old 2.6.31 I still have network connectivity so in that case the wpa-psk key is not wrong.

I think I’ve messed up somehow certain things with blacklisting or whatever. I’m completely lost now and I think we need to repeat some steps.
Even better would be to completely remove the obsolete kernels including the drivers you’ve provided and then reinstall one current kernel and work with that. I know that before I discovered this website I’ve done things with backports but I don’t know how to get rid of it.

67

@ q7icmfm1x0h609c6xiok

You can show a list of installed packages with:
dpkg --get-selections | less

or export them t a file in your home directory with:

cd ~
dpkg --get-selections >> paackag_list

or search for “backports” in the output with:

dpkg --get-selections | grep backports

are you still getting the wpa_supplicant error ?

It’s entirely possible the WPA key is wrong, but only you would know that :wink:

So lets find out if it IS just a WPA encryption problem… will it associate with an unsecured wireless access point ?
(ie. turn off wireless security in your modem/router for a test connection)

68

@ jamesrl

For some reason it’s loaded the rt2870sta module rather than rt5370sta… try running these 2 commands:

sudo modprobe -r rt2870sta

then:

sudo modprobe rt5370sta

then post the output from:

lsmod | grep rt

and:

sudo lshw -C network
69

Thanks. I actually rebuilt my machine last night, and tried your driver and all seems OK now. Soz didn’t get round to updating forum.

Thanks again for all your help.

70

@ jamesrl

At least you’re up and running, thanks for the update :slight_smile:

71

Nice, that it works for jamesrl!

@mark:
I’ve tried dpkg --get-selections and it detected 3 different backports. So like I said I’ve messed up things.
Furthermore there are several packages indicated as deinstalled (but the configuration files are seemingly still present). So currently I’m in the process of cleaning up things.

I’m still not convinced about that wpa_supplicant thingy. I’ve found an interesting webpage which describes that the security settings in /etc/network/interfaces can be included in /etc/wpa/wpa_supplicant.conf.
I’ll try it and if it works with my currently working 2.6.31 kernel we’ll know for sure that wpa_supplicant is working.
And I’ve found an article claiming that Ralink wireless usb adapters simply do work with stock drivers but this article follows an approach using udev rules.
I’ll report back to you soon.

72

All right, I’m back again.

With the 2.6.31 kernel (with connectivity) the result of ps -A | grep wpa_supplicant is:
3332 ? 00:00:00 wpa_supplicant
So wpa_supplicant seems to be running.

I’ve made a new version of /etc/network/interfaces and now it’s like this:

auto ra0
iface ra0 inet static
address 10.0.0.19
netmask 255.255.255.0
gateway 10.0.0.140
wpa-conf /etc/wpa_supplicant.conf
wpa-ap-scan 2

and my /etc/wpa_supplicant.conf looks like:

ctrl_interface=/var/run/wpa_supplicant
network={
ssid=
psk=
key_mgmt=WPA-PSK
proto=RSN WPA
pairwise=CCMP TKIP
group=CCMP TKIP

I was too lazy to reboot :wink:
so I did sudo /etc/init.d/networking restart
and I got the message:
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with returncode 1

So it seems that there’s indeed something wrong with wpasupplicant.

B.T.W.: if I remove RSN from the proto statement in the original 2.6.31 network interfaces configuration in order to force a WPA2 connection the network connectivity breaks. If I put it back everything works.

73

What is the verbose (-v) output from ifdown and ifup ?

sudo ifdown -v ra0

and

sudo ifup -v ra0

Hopefully this will give us an idea where WPA is failing.

74

Those commands did not produce any useful results but in the daemon log I noticed wpa_supplicant parsing errors.
In the end I discovered that wpa_supplicant wants my SSID in between quotes. So my old 2.6.31`kernel is now running with wpa_supplicant.
After that success I decided to proceed but that resulted in disaster. I lost all network connectivity including the 2.6.31 kernel. I took me about 3 hours to repair the damage.
It seems that after a series of many changes the USB stick gets somehow confused, locks up and ignores all changes as instructed by the driver. The only way to make it work again is unplug it and replug after 1 minute.

During the session I noticed that the driver tries to read the contents of the file /etc/Wireless/RT2870STA/RT2870STA.dat and it ignores what wpa_supplicant instructs. The only way to make the driver to ignore that file is to remove or rename it.
Furthermore I found that kernel 2.6.38-9 still hangs so that one won’t work I guess.
Kernel 2.6.35-30 and the experimental kernel 2.6.38-02063808 produces these two errors:

  • WPA: unsupported CCMP Group Cipher key length 32 (32).
  • RSN: failed to configure GTK.
    Kernel 2.6.35-28 is not able to connect and times out each attempt.

And in the logs I’ve found an error that I can’t link to a specific kernel right now. It says: Failed to disable WPA in the driver.

75

With all this swapping of kernels, are you recompiling the driver each time ?

I think your last idea of picking a kernel and then trying to get it to work would probably be the better idea… the default kernel is probably the one you should go with unless there is a specific reason not to… AFAIK these drivers should work with any (recent) kernel they are compiled for.

My suggestion would be to go back to the default kernel (whatever that is, I’ve forgotten which Ubuntu version you are running), recompile/install the drivers, then try to sort out the configs.

Swapping kernels seems fairly pointless, the drivers are loaded as a module, so are not part of the kernel.

76

Recompiling each time? Well, actually no I didn’t. I assumed that compiling it once for each kernel was good enough. Besides as far as I know the RT3070 driver is used by none of the tested kernels they all go for RT2870.
Currently I use Ubuntu Server Maverick so the default kernel would be 2.6.35-30, so I´ll continue with that one.
I think this weekend I don’t have much time for testing purposes so I probably won’t do anything until monday.

77

Well, I’ve resumed testing again. In the process I’ve caused a major connectivity breakdown. No kernel could establish a connection not even the so far always working 2.6.31 kernel.
It took me 6 hours to repair things. So far I’ve found out that:

  • rt2800lib and rt2800usb need to be blacklisted otherwise no connection will be established in any circumstances.
  • It does not matter if rt2x00lib and rt2x00usb are not blacklisted.
    And there’s something that was not necessary before: I need to blacklist rt3070sta otherwise the connection will not come up automatically (however it can be brought up by ifup, but I want it to come up automatically).
    I expect to do some further testing with kernel 2.6.35 in order to make that one work.
    May be something has changed so I would like to ask you again which driver do you recommend?
    Do we have a working mode that involves NO touching of /etc/network/interfaces and the wpa_supplicant stuff? Wpa_supplicant is working in the old kernel so I like to keep it that way.
    I´m a bit worried about the /etc/Wireless/RT2870STA/RT2870STA.dat file. For some reason I have to remove it otherwise no connection will be established. I’ve tried to fill it in with appropriate values but these are probably not appropriate enough because it’s not working. Removing that file obviously causes messages in the log that the file can’t be opened so it seems that it should be used somehow.
78

can you attach these 4 files:
/etc/Wireless/RT2870STA/RT2870STA.dat
/etc/network/interfaces
/etc/wpa_supplicant.conf
/etc/resolv.conf

The driver I’d go with is:
http://dl.dropbox.com/u/11876059/2011_0407_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.2_DPO.tar.bz2
which is the latest driver that is supposed to support your card (148f:3070)

Writing a small script to bring the connection up automatically at starttup will be fairly easy.
or just adding
ifdown ra0
ifup ra0
to /etc/rc.local
should also run those 2 commands at startup
but let’s just get it working first.

You also NEED to test it with an unsecured network as well, to check if it is JUST a WPA issue.

79

/etc/Wireless/RT2870STA/RT2870STA.dat:
#The word of “Default” must not be removed
Default
CountryRegion=5
CountryRegionABand=7
CountryCode=NL
ChannelGeography=1
SSID=“here the SSID”
NetworkType=Infra
WirelessMode=9
Channel=0
BeaconPeriod=100
TxPower=100
BGProtection=0
TxPreamble=0
RTSThreshold=2347
FragThreshold=2346
TxBurst=1
PktAggregate=0
WmmCapable=1
AckPolicy=0;0;0;0
AuthMode=WPA
EncrypType=NONE
WPAPSK=
DefaultKeyID=1
Key1Type=0
Key1Str=
Key2Type=0
Key2Str=
Key3Type=0
Key3Str=
Key4Type=0
Key4Str=
PSMode=CAM
AutoRoaming=0
RoamThreshold=70
APSDCapable=0
APSDAC=0;0;0;0
HT_RDG=1
HT_EXTCHA=0
HT_OpMode=0
HT_MpduDensity=4
HT_BW=1
HT_BADecline=0
HT_AutoBA=1
HT_AMSDU=0
HT_BAWinSize=64
HT_GI=1
HT_MCS=33
HT_MIMOPSMode=3
HT_DisallowTKIP=1
HT_STBC=0
EthConvertMode=
EthCloneMac=
IEEE80211H=0
TGnWifiTest=0
WirelessEvent=0
MeshId=MESH
MeshAutoLink=1
MeshAuthMode=OPEN
MeshEncrypType=NONE
MeshWPAKEY=
MeshDefaultkey=1
MeshWEPKEY=
CarrierDetect=0
AntDiversity=0
BeaconLostTime=4
FtSupport=0
Wapiifname=ra0
WapiPsk=
WapiPskType=
WapiUserCertPath=
WapiAsCertPath=
PSP_XLINK_MODE=0
WscManufacturer=
WscModelName=
WscDeviceName=
WscModelNumber=
WscSerialNumber=
RadioOn=1

/etc/network/interfaces & /etc/wpa_supplicant.conf:
These are already in the post of July 06, 2011, 09:56:29 pm

/etc/resolv.conf:
nameserver 10.0.0.19
nameserver 208.67.222.222
nameserver 208.67.220.220

The server runs its own DNS and queries the servers from OpenDNS when necessary.

80

What does:

wpa_supplicant -Dwext -ira0 -c /etc/wpa_supplicant.conf -dd

output ?

Have you tested the connection WITHOUT security yet ? … we need to know if it is a driver issue, or a wpa_supplicant issue.

[EDIT]

IF this is just a wpa_supplicant issue… which you can only be 100% sure of by trying it with an unsecured AP…

After reading on a few sites that people seemed to be having more luck with -
HAS_WPA_SUPPLICANT=y
and
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n
set in config.mk before compiling and installing… you might want to give that a try.

then test the wpa_supplicant with:

wpa_supplicant -Dralink -ira0 -c /etc/wpa_supplicant.conf -dd

See last but one posting here:
http://forum.sabayon.org/viewtopic.php?t=19032