Low data rates with Ralink RT2500 PCI WLAN card

Bug #154524 reported by Tamas Varga
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

After upgrading from Feisty to Gutsy my network connection seemed to be very slow. After some measurements, I realized, that my yesterday at least 10 Mbps WLAN connection speed is reduced to about 500- 600 kbps. I made measurements with my girlfriend's computer, and it worked well, so I do think that the problem is located within the rt2x00 drivers.

Revision history for this message
Tamas Varga (tompika-deactivatedaccount) wrote :

I made some additional measurements:
If I generate downstream traffic with the maximal reachable bandwidth, and I simultaneously ping my router, I see, that the round trip time of ping is increased by a factor greater than a hundred.

Here's a snippet of ping output:

64 bytes from 10.0.0.1: icmp_seq=58 ttl=255 time=206 ms
64 bytes from 10.0.0.1: icmp_seq=59 ttl=255 time=171 ms
64 bytes from 10.0.0.1: icmp_seq=60 ttl=255 time=142 ms
64 bytes from 10.0.0.1: icmp_seq=61 ttl=255 time=156 ms
64 bytes from 10.0.0.1: icmp_seq=62 ttl=255 time=531 ms
64 bytes from 10.0.0.1: icmp_seq=63 ttl=255 time=147 ms
64 bytes from 10.0.0.1: icmp_seq=64 ttl=255 time=264 ms
64 bytes from 10.0.0.1: icmp_seq=65 ttl=255 time=281 ms
64 bytes from 10.0.0.1: icmp_seq=66 ttl=255 time=175 ms
64 bytes from 10.0.0.1: icmp_seq=67 ttl=255 time=493 ms
64 bytes from 10.0.0.1: icmp_seq=68 ttl=255 time=315 ms
64 bytes from 10.0.0.1: icmp_seq=69 ttl=255 time=2.16 ms
64 bytes from 10.0.0.1: icmp_seq=70 ttl=255 time=1.14 ms
64 bytes from 10.0.0.1: icmp_seq=71 ttl=255 time=1.06 ms
64 bytes from 10.0.0.1: icmp_seq=72 ttl=255 time=1.60 ms
64 bytes from 10.0.0.1: icmp_seq=73 ttl=255 time=2.16 ms
64 bytes from 10.0.0.1: icmp_seq=74 ttl=255 time=1.52 ms
64 bytes from 10.0.0.1: icmp_seq=75 ttl=255 time=2.81 ms
64 bytes from 10.0.0.1: icmp_seq=76 ttl=255 time=2.27 ms
64 bytes from 10.0.0.1: icmp_seq=77 ttl=255 time=1.56 ms

If I generate upstream traffic (which is not slower than with the former Ubuntu-shipped driver, rt2500), there's only a slight difference in ping times (e.g.: 1- 2 ms => 2- 4 ms).

Revision history for this message
TomLottermann (tomlottermann) wrote :

I can report some other bugs too:
My LAN connection breaks after a certain time. and I also have the low bandwidth.

Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

I confirm this too. Driver works correctly even with WPA2, but performance goes down from 1 MB/s in the first minutes to around 90Kb/s.

This is really annoying.

Revision history for this message
Tamas Varga (tompika-deactivatedaccount) wrote :

I wanted to bring you some details from /sys but I came across another annoying bug: I cannot set 802.11b mode with my card, so I just can't connect to my router in my home city. When I travel back to university, I'm going to send some more information.

So till then just another bug: no speed setting possilibity. No success with iwconfig ra0 rate 11M or NetworkManager. Default setting is 802.11g, so I cannot connect.

Revision history for this message
Tamas Varga (tompika-deactivatedaccount) wrote :

Using ndiswrapper is a workaround. I'm sure i'm using it till the native driver will have been fixed.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.