[rt2x00-users] Indirect register access failed

Helmut Schaa helmut.schaa at googlemail.com
Fri Jul 2 15:45:25 AEST 2010


Am Donnerstag 01 Juli 2010 schrieb Antonio Quartulli:
> On lun, giu 21, 2010 at 11:51:05 +0200, Antonio Quartulli wrote:
> > > > > > > > The classic time out error:
> > > > > > > > 
> > > > > > > > Jun 18 21:54:57 eagle3 kernel: [   96.206662] phy0: device no longeridle - scanning
> > > > > > > > Jun 18 21:54:58 eagle3 kernel: [   97.161141] wlan0: direct probe to 00:22:3f:03:81:dd (try 1)
> > > > > > > > Jun 18 21:54:58 eagle3 kernel: [   97.361146] wlan0: direct probe to 00:22:3f:03:81:dd (try 2)
> > > > > > > > Jun 18 21:54:58 eagle3 kernel: [   97.561100] wlan0: direct probe to 00:22:3f:03:81:dd (try 3)
> > > > > > > > Jun 18 21:54:59 eagle3 kernel: [   97.761324] wlan0: direct probe to 00:22:3f:03:81:dd timed out
> > > > > > > > Jun 18 21:54:59 eagle3 kernel: [   97.766249] phy0: device now idle
> > > > > 
> > > > > First possibility: the probe requests are not sent out at all
> > > > > Second possibility: the probe requests are sent out but not received by the AP
> > > > > 
> > > > > One way to find that out would be to sniff the wireless traffic with a second
> > > > > wireless card and check if the rt2800 card sends out probe requests and if
> > > > > the AP answers them. Do you think you can do that?
> > > > 
> Hi all!
> Sorry for writing only once aweek but in this period I'm a bit in
> trouble with the university exams :P

No problem, good luck ;)

> About the card, I did some other tests (with the actual version of
> wireless-testing) and as result I got that: the first time i was not
> able to associate to the AP and i reported the same timeout as before.
> Then i turned on wireshark and magically the device has associated, but
> in wireshark i saw A LOT of retransmission by the AP!
> I tried to use some application, like dhcp for first and then a simple
> ping and I got that every packet (dhcp offer, echo reply) is sent many
> many time..

Hmm, indeed there is a huge number of retries. That would explain why you've
got such a lousy performance and association problems.

Did you again capture the traffic with the same wireless card you've used for
the association?

Because it seems as if the ralink card doesn't ack the frames sent by the AP
or the ACKs are not received by the AP. Although the ralink card perfectly
receives the frames sent by the AP (as they show up in the frame capture).

Could you please check if there are ACKs being sent out by the device?

Helmut




More information about the users mailing list