linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo Van Doorn <ivdoorn@gmail.com>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: Steev Klimaszewski <steev@genesi-usa.com>,
	Jett Chen <jett_chen@ralinktech.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Questions about rt2800usb
Date: Fri, 8 Apr 2011 11:42:07 +0200	[thread overview]
Message-ID: <BANLkTi=kkBReSDHcCqyTkbHsAgDLiy7okg@mail.gmail.com> (raw)
In-Reply-To: <179432.26955.qm@web161615.mail.bf1.yahoo.com>

Hi,

On Fri, Apr 8, 2011 at 11:32 AM, Walter Goldens
<goldenstranger@yahoo.com> wrote:
>> > Here's my vote against removing the rt2870sta from
>> staging. Some longstanding issues with latency and duplicate
>> packets (rt307x) are persistent with rt2800usb, whereas
>> rt2870sta works fine.
>> >
>> > my two cents
>> >
>> > Walter
>>
>> Personally, I've had the opposite (since the patch to
>> disable power
>> management on rt2800usb.)  rt2870sta hasn't been
>> noticeably more
>> stable, and in fact, I tend to see div0 bugs quite often
>> when using
>> it.  That said, I'm using Azurewave rt3070s.
>
> My vote went against only because of this:
> (rt3070 - 148f:3070)
>
> Ping gateway with staging:
>
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=4.34 ms
> 64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=4.70 ms
> 64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1.61 ms
> 64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=1.68 ms
> 64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=1.33 ms
> 64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=6.57 ms
> 64 bytes from 192.168.1.1: icmp_req=7 ttl=64 time=4.45 ms
> ^C
> --- 192.168.1.1 ping statistics ---
> 7 packets transmitted, 7 received, 0% packet loss, time 6009ms
>
>
> Now pinging gateway with rt2800usb:
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=647 ms
> 64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1590 ms
> 64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=583 ms
> 64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=29.2 ms
> 64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=1674 ms
> 64 bytes from 192.168.1.1: icmp_req=7 ttl=64 time=667 ms
> 64 bytes from 192.168.1.1: icmp_req=7 ttl=64 time=668 ms (DUP!)
> 64 bytes from 192.168.1.1: icmp_req=8 ttl=64 time=1645 ms
> 64 bytes from 192.168.1.1: icmp_req=9 ttl=64 time=637 ms
> 64 bytes from 192.168.1.1: icmp_req=10 ttl=64 time=1.38 ms
> ^C
> --- 192.168.1.1 ping statistics ---
> 10 packets transmitted, 9 received, +1 duplicates, 10% packet loss, time 9032ms
> rtt min/avg/max/mdev = 1.384/814.547/1674.284/588.666 ms, pipe 2
>
>
> Steev, you mentioned there was a fix? Could you please point which patch resolves this?
>
> I'll be glad to drop the staging driver if rt2800usb does not lag anymore.

Try:

iwconfig wlan0 power off

to disable powersaving.

Ivo

  reply	other threads:[~2011-04-08  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 21:49 Questions about rt2800usb Larry Finger
2011-04-07 22:19 ` Walter Goldens
2011-04-07 23:03   ` Steev Klimaszewski
2011-04-08  9:32     ` Walter Goldens
2011-04-08  9:42       ` Ivo Van Doorn [this message]
2011-04-08  9:54         ` Walter Goldens
2011-04-08 12:21           ` Walter Goldens
2011-04-08 12:41             ` Helmut Schaa
2011-04-08 16:31               ` Walter Goldens
2011-04-08  6:50 ` Helmut Schaa
2011-04-08  7:42 ` Ivo Van Doorn
  -- strict thread matches above, loose matches on Subject: below --
2011-04-10 16:55 Xose Vazquez Perez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=kkBReSDHcCqyTkbHsAgDLiy7okg@mail.gmail.com' \
    --to=ivdoorn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=goldenstranger@yahoo.com \
    --cc=jett_chen@ralinktech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=steev@genesi-usa.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).