p.s. i was working initially with some thinking from this forum:
http://rt2x00.serialmonkey.com/phpBB/search.php?keywords=backports&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search
read through the forums. one of the lead dev guys comments well.

On Sun, Dec 21, 2008 at 9:24 AM, <email address hidden> <email address hidden>wrote:

> yeah, 64 b could be the diff. i am on 32 b ubuntu.
>
> On Sat, Dec 20, 2008 at 11:01 PM, Stuart Bishop <
> <email address hidden>> wrote:
>
>> joshyg6 - Any other thoughts on how you managed to use the -backports
>> module? Many of us see nothing but unknown symbol errors (Bug #306087).
>>
>> I'm running 64 bit - could that make a difference?
>>
>> --
>> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must
>> restart driver
>> https://bugs.launchpad.net/bugs/283759
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in The rt2x00 Project: New
>> Status in Ubuntu: Fix Released
>> Status in Fedora: Confirmed
>> Status in Mandriva Linux: In Progress
>>
>> Bug description:
>> I may have something.. So I blacklisted the recompiled/newly installed
>> legacy rt73 drivers, and i went back to using the rt73usb included initially
>> with intrepid. i was using the Internet as normal, and then it crapped out,
>> and these are the tail logs..
>>
>> Quote:
>> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971]
>> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
>> (LODGER)
>> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943]
>> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
>> ((none))
>> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557]
>> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
>> (LODGER)
>>
>> ****** Connection seemed to crap out around this point!!!********
>>
>> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high
>> speed USB device using ehci_hcd and address 4
>> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / &&
>> run-parts --report /etc/cron.hourly)
>> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 ->
>> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
>> non-full queue 2.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to
>> http://rt2x00.serialmonkey.com.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 ->
>> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
>> non-full queue 2.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to
>> http://rt2x00.serialmonkey.com.
>>
>> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo
>> modprobe -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig
>> wlan0 up. Then I reselect the proper network from the NetworkManager drop
>> down, and then it connects and I have internet again! ****************
>>
>>
>> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no
>> longer relevant for mDNS.
>> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group
>> on interface wlan0.IPv4 with address 192.168.0.100.
>> Oct 15 08:28:48 jupiter2 dhclient: receive_packet failed on wlan0: Network
>> is down
>> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Withdrawing address record
>> for 192.168.0.100 on wlan0.
>> Oct 15 08:28:51 jupiter2 NetworkManager: <debug> [1224073731.029387]
>> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
>> ((none))
>> Oct 15 08:28:55 jupiter2 kernel: [ 6003.929519] usbcore: deregistering
>> interface driver rt73usb
>> Oct 15 08:28:55 jupiter2 nm-system-settings: SCPlugin-Ifupdown: devices
>> removed (udi: /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0)
>> Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): now unmanaged
>> Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 8 -> 1
>> Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): deactivating
>> device.
>> Oct 15 08:28:55 jupiter2 NetworkManager: <info> wlan0: canceled DHCP
>> transaction, dhcp client pid 8501
>> Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module
>> rt73
>> Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module
>> rt73
>> Oct 15 08:28:55 jupiter2 NetworkManager:
>> nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0'
>> failed
>> Oct 15 08:28:55 jupiter2 NetworkManager:
>> nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0'
>> failed
>> Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module
>> rt73
>> Oct 15 08:28:55 jupiter2 last message repeated 2 times
>> Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): cleaning up...
>> Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module
>> rt73
>> Oct 15 08:28:55 jupiter2 nm-dispatcher.action: Error in get_property:
>> Method "Get" with signature "ss" on interface
>> "org.freedesktop.DBus.Properties" doesn't exist
>> Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module
>> rt73
>> Oct 15 08:28:55 jupiter2 last message repeated 13 times
>> Oct 15 08:29:10 jupiter2 kernel: [ 6019.060139] phy0: Selected rate
>> control algorithm 'pid'
>> Oct 15 08:29:10 jupiter2 kernel: [ 6019.060438] Registered led device:
>> rt73usb-phy0:radio
>> Oct 15 08:29:10 jupiter2 kernel: [ 6019.060452] Registered led device:
>> rt73usb-phy0:assoc
>> Oct 15 08:29:10 jupiter2 kernel: [ 6019.060464] Registered led device:
>> rt73usb-phy0:quality
>> Oct 15 08:29:10 jupiter2 kernel: [ 6019.061014] usbcore: registered new
>> interface driver rt73usb
>> Oct 15 08:29:10 jupiter2 nm-system-settings: SCPlugin-Ifupdown: devices
>> added (udi: /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0, iface:
>> wlan0)
>> Oct 15 08:29:10 jupiter2 NetworkManager: <info> wlan0: driver is
>> 'rt73usb'.
>> Oct 15 08:29:10 jupiter2 NetworkManager: <info> wlan0: driver supports
>> SSID scans (scan_capa 0x01).
>> Oct 15 08:29:10 jupiter2 NetworkManager: <info> Found new 802.11 WiFi
>> device 'wlan0'.
>> Oct 15 08:29:10 jupiter2 NetworkManager: <info> (wlan0): exported as
>> /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0
>> Oct 15 08:29:13 jupiter2 kernel: [ 6022.272165] firmware: requesting
>> rt73.bin
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 1 -> 2
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): preparing device.
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): deactivating
>> device.
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 2 -> 3
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> interface state change: 1 -> 2.
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0)
>> starting connection 'Auto LODGER'
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 3 -> 4
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 4 -> 5
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation
>> (wlan0/wireless): access point 'Auto LODGER' has security, but secrets are
>> required.
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 5 -> 6
>> Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.884609] wlan0: authenticate with
>> AP 00:16:b6:2e:13:f8
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.886242] wlan0: authenticated
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.886247] wlan0: associate with AP
>> 00:16:b6:2e:13:f8
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.888496] wlan0: RX AssocResp from
>> 00:16:b6:2e:13:f8 (capab=0x401 status=0 aid=4)
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.888501] wlan0: associated
>> Oct 15 08:29:15 jupiter2 kernel: [ 6023.889065] wlan0: disassociating by
>> local choice (reason=3)
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 1 -> 4
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 4 -> 0
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 6 -> 4
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 4 -> 5
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation
>> (wlan0/wireless): connection 'Auto LODGER' has security, and secrets exist.
>> No new secrets needed.
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'ssid' value
>> 'LODGER'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'scan_ssid'
>> value '1'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'bssid'
>> value '00:0f:3d:39:10:96'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'key_mgmt'
>> value 'NONE'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'auth_alg'
>> value 'SHARED'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'wep_key0'
>> value '<omitted>'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added
>> 'wep_tx_keyidx' value '0'
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: set interface
>> ap_scan to 1
>> Oct 15 08:29:19 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 0 -> 2
>> Oct 15 08:29:20 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 2 -> 3
>> Oct 15 08:29:21 jupiter2 kernel: [ 6030.477636] wlan0: authenticate with
>> AP 00:0f:3d:39:10:96
>> Oct 15 08:29:21 jupiter2 kernel: [ 6030.484519] wlan0: authenticated
>> Oct 15 08:29:21 jupiter2 kernel: [ 6030.484523] wlan0: associate with AP
>> 00:0f:3d:39:10:96
>> Oct 15 08:29:21 jupiter2 kernel: [ 6030.486778] wlan0: RX AssocResp from
>> 00:0f:3d:39:10:96 (capab=0x431 status=0 aid=1)
>> Oct 15 08:29:21 jupiter2 kernel: [ 6030.486782] wlan0: associated
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 3 -> 4
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): supplicant
>> connection state change: 4 -> 7
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation
>> (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to
>> wireless network 'LODGER'.
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3
>> of 5 (IP Configure Start) scheduled.
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3
>> of 5 (IP Configure Start) started...
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 5 -> 7
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0)
>> Beginning DHCP transaction.
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> dhclient started with pid
>> 10598
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3
>> of 5 (IP Configure Start) complete.
>> Oct 15 08:29:21 jupiter2 dhclient: Internet Systems Consortium DHCP Client
>> V3.1.1
>> Oct 15 08:29:21 jupiter2 dhclient: Copyright 2004-2008 Internet Systems
>> Consortium.
>> Oct 15 08:29:21 jupiter2 dhclient: All rights reserved.
>> Oct 15 08:29:21 jupiter2 dhclient: For info, please visit
>> http://www.isc.org/sw/dhcp/
>> Oct 15 08:29:21 jupiter2 dhclient:
>> Oct 15 08:29:21 jupiter2 dhclient: wmaster0: unknown hardware address type
>> 801
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> DHCP: device wlan0 state
>> changed normal exit -> preinit
>> Oct 15 08:29:21 jupiter2 dhclient: wmaster0: unknown hardware address type
>> 801
>> Oct 15 08:29:21 jupiter2 dhclient: Listening on
>> LPF/wlan0/00:16:44:7c:a0:e2
>> Oct 15 08:29:21 jupiter2 dhclient: Sending on LPF/wlan0/00:16:44:7c:a0:e2
>> Oct 15 08:29:21 jupiter2 dhclient: Sending on Socket/fallback
>> Oct 15 08:29:21 jupiter2 dhclient: DHCPDISCOVER on wlan0 to
>> 255.255.255.255 port 67 interval 5
>> Oct 15 08:29:21 jupiter2 dhclient: DHCPOFFER of 192.168.0.100 from
>> 192.168.0.1
>> Oct 15 08:29:21 jupiter2 dhclient: DHCPREQUEST of 192.168.0.100 on wlan0
>> to 255.255.255.255 port 67
>> Oct 15 08:29:21 jupiter2 dhclient: DHCPACK of 192.168.0.100 from
>> 192.168.0.1
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> DHCP: device wlan0 state
>> changed preinit -> bound
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4
>> of 5 (IP Configure Get) scheduled...
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4
>> of 5 (IP Configure Get) started...
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> address 192.168.0.100
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> prefix 24 (255.255.255.0)
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> gateway 192.168.0.1
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> nameserver '192.168.0.1'
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5
>> of 5 (IP Configure Commit) scheduled...
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4
>> of 5 (IP Configure Get) complete.
>> Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5
>> of 5 (IP Configure Commit) started...
>> Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: Joining mDNS multicast group
>> on interface wlan0.IPv4 with address 192.168.0.100.
>> Oct 15 08:29:21 jupiter2 dhclient: bound to 192.168.0.100 -- renewal in
>> 290345 seconds.
>> Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: New relevant interface
>> wlan0.IPv4 for mDNS.
>> Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: Registering new address
>> record for 192.168.0.100 on wlan0.IPv4.
>> Oct 15 08:29:22 jupiter2 NetworkManager: <info> (wlan0): device state
>> change: 7 -> 8
>> Oct 15 08:29:22 jupiter2 NetworkManager: <info> Policy set (wlan0) as
>> default device for routing and DNS.
>> Oct 15 08:29:22 jupiter2 NetworkManager: <info> Activation (wlan0)
>> successful, device activated.
>> Oct 15 08:29:22 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5
>> of 5 (IP Configure Commit) complete.
>> Oct 15 08:29:22 jupiter2 ntpd[8629]: ntpd exiting on signal 15
>> Oct 15 08:29:23 jupiter2 ntpdate[10687]: adjust time server 91.189.94.4
>> offset -0.006663 sec
>> Oct 15 08:29:23 jupiter2 ntpd[10721]: ntpd 4.2.4p4@1.1520-o Wed Aug 20
>> 17:03:52 UTC 2008 (1)
>> Oct 15 08:29:23 jupiter2 ntpd[10722]: precision = 1.000 usec
>>
>> What do you all think? Does this shed more late anywhere!!???
>>
>
>