Ralink Drivers do not work out of the box on Ubuntu Gutsy Beta

Ok this is a serious problem and this problem has never been fixed.

I like many "thousands" of people cannot use our Belkin Wireless USB Dongle that uses the ralink chipset. Ubuntu Gutsy Beta still does not work. The problem is as follows...

When the os finishes booting, and you iwconfig it lists 2 wireless cards:
wmaster0
wlan0

before I blacklisted the modules and rebooted I was unable to scan at all.
I had to blacklist some modules:
blacklist rt73usb
blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib
blacklist rfkill
blacklist crc_itu_t
blacklist input_polldev

I go into network manager and try and connect and it seems to connect correctly "but it doesnt"

here is what network manager inputs into /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wireless-essid 2WIRE999
wireless-key mywifikeyivealwayshad

I even tried a static connection:
auto wlan0
iface wlan0 inet static
address 192.168.0.70
netmask 255.255.255.0
gateway 192.168.0.1
wireless-essid 2WIRE999
wireless-key mywifikeyivealwayshad

ok so I resorted to blacklist every Ubuntu Gutsy driver and compile, install my own from:
http://rt2x00.serialmonkey.com
I downloaded the latest cvs and compiled normally like I always have in Ubuntu Feisty, compile went fine, kernel module install went fine as well..

*note* if I didnt blacklist rt73usb or any others the system would completely lock up and not produce any logs
I modprobed the new rt73 driver and attempted to connect via wpa, and this produced a total system lock up.... more information below.

Here is more information I posted at the serialmonkey forum:
root@ion:~# uname -a
Linux ion 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

Ok I just upgraded from Ubuntu Feisty to Ubuntu Gutsy Gibbon, now I am unable to use WPA AES encryption, if I even attempt to connect with it, my system panics instantly with flashing caps/scroll lock. I am able to connect to wep perfectly with this driver, but as you know wep security is nonsecurity which id rather not get my internet stolen...

Here are the logs of the event, let me know what else is needed to figure out what the issue is to help fix it.

defcon

Here is the Gutsy modules I have blacklisted:
blacklist rt73usb
blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib
blacklist rfkill
blacklist crc_itu_t
blacklist input_polldev

Here is a grep'd lsmod for rt*
root@ion:~# lsmod | grep rt
rt73 214400 0
agpgart 35016 3 drm,intel_agp
parport_pc 37412 1
parport 37448 3 ppdev,lp,parport_pc
iTCO_vendor_support 4868 1 iTCO_wdt
usbcore 137864 5 rt73,usbhid,ehci_hcd,uhci_hcd

Here is my messages log:
Sep 27 13:47:46 ion kernel: [ 28.769487] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Sep 27 13:47:46 ion kernel: [ 28.769495] apm: disabled - APM is not SMP safe.
Sep 27 13:47:46 ion kernel: [ 28.983759] AppArmor: Registered secondary security module: capability.
Sep 27 13:47:46 ion kernel: [ 28.983767] Capability LSM initialized as secondary
Sep 27 13:47:47 ion dhcdbd: Started up.
Sep 27 13:47:47 ion kernel: [ 29.171768] Bluetooth: Core ver 2.11
Sep 27 13:47:47 ion kernel: [ 29.171944] NET: Registered protocol family 31
Sep 27 13:47:47 ion kernel: [ 29.171949] Bluetooth: HCI device and connection manager initialized
Sep 27 13:47:47 ion kernel: [ 29.171954] Bluetooth: HCI socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.190285] Bluetooth: L2CAP ver 2.8
Sep 27 13:47:47 ion kernel: [ 29.190292] Bluetooth: L2CAP socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248381] Bluetooth: RFCOMM socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248530] Bluetooth: RFCOMM TTY layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248535] Bluetooth: RFCOMM ver 1.8
Sep 27 13:47:48 ion kernel: [ 30.419827] [drm] Initialized drm 1.1.0 20060810
Sep 27 13:47:48 ion kernel: [ 30.426794] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
Sep 27 13:47:48 ion kernel: [ 30.429668] [drm] Initialized i915 1.6.0 20060119 on minor 0
Sep 27 13:47:58 ion kernel: [ 40.906457] NET: Registered protocol family 10
Sep 27 13:47:58 ion kernel: [ 40.906752] lo: Disabled Privacy Extensions
Sep 27 13:47:58 ion kernel: [ 40.906996] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:50:26 ion kernel: [ 188.777697] usbcore: deregistering interface driver rt2500usb
Sep 27 13:51:25 ion kernel: [ 247.787304] usbcore: deregistering interface driver rt73
Sep 27 13:51:25 ion kernel: [ 247.787495] <=== rtusb exit
Sep 27 13:52:51 ion kernel: [ 332.859548] rtusb init ====>
Sep 27 13:52:51 ion kernel: [ 332.949013] idVendor = 0x50d, idProduct = 0x705a
Sep 27 13:52:51 ion kernel: [ 333.029495] usbcore: registered new interface driver rt73
Sep 27 13:52:51 ion kernel: [ 333.029890] rt73 driver version - 1.0.3.6 CVS
Sep 27 13:52:51 ion kernel: [ 333.188206] ***rt73***: Interface goes up for the first time, activating permanent MAC
Sep 27 13:52:51 ion kernel: [ 333.188216] ***rt73***: Active MAC is: 00:17:3f:c5:bf:91.
Sep 27 13:55:20 ion kernel: [ 482.105645] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:55:49 ion kernel: [ 511.200312] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:55:51 ion kernel: [ 513.231185] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:55:52 ion kernel: [ 514.172295] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:55:56 ion kernel: [ 518.175510] rt73 driver version - 1.0.3.6 CVS
Sep 27 13:55:56 ion kernel: [ 518.333787] ***rt73***: net_device supplies MAC, activating this one
Sep 27 13:55:56 ion kernel: [ 518.333797] ***rt73***: Active MAC is: 00:17:3f:c5:bf:91.
Sep 27 13:55:57 ion kernel: [ 519.167342] rt73 driver version - 1.0.3.6 CVS
Sep 27 13:55:57 ion kernel: [ 519.326697] ***rt73***: net_device supplies MAC, activating this one
Sep 27 13:55:57 ion kernel: [ 519.326706] ***rt73***: Active MAC is: 00:17:3f:c5:bf:91.
Sep 27 13:56:38 ion kernel: [ 559.969475] rt73 driver version - 1.0.3.6 CVS
Sep 27 13:56:38 ion kernel: [ 560.127476] ***rt73***: net_device supplies MAC, activating this one
Sep 27 13:56:38 ion kernel: [ 560.127486] ***rt73***: Active MAC is: 00:17:3f:c5:bf:91.
Sep 27 13:56:52 ion kernel: [ 574.061991] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:57:06 ion kernel: [ 588.200135] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:57:06 ion kernel: [ 588.319084] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:58:40 ion syslogd 1.4.1#21ubuntu2: restart.

Well im truly dissapointed in Ubuntu Gutsy for not fixing this problem since Ubuntu has always had a problem with the ralink chipsets, I dont know anyone who has booted up a live cd with my card and everything worked perfectly.

No new linux user or semi new linux user or even advanced linux user can figure this out unless they program, this driver needs to be tested and fixed because it does not work at all, never has that is why people resort to serialmonkey, why dont we use there drivers?

I believe something is wrong with the kernel-source..

Thankyou
defcon