[rt2x00-users] Indirect register access failed

Antonio Quartulli ordex at ritirata.org
Sun Jun 20 11:25:52 UTC 2010


On Sun, Jun 20, 2010 at 12:54:27PM +0200, Helmut Schaa wrote:
> Am Freitag 18 Juni 2010 schrieb Antonio Quartulli:
> > On Fri, Jun 18, 2010 at 10:29:12PM +0200, Helmut Schaa wrote:
> > > Am Freitag 18 Juni 2010 schrieb Antonio Quartulli:
> > > > Hi Helmut, hi all, sorry for the large delay..
> > > 
> > > No Problem ;)
> > > 
> > > > I tried a few minutes ago the last wireless-testing (.35-rc3-wl) kernel 
> > > > and the rt2800pci was able to come up even without your patch, but at 
> > > > this point it was not able to associate to any AP. Any request got time out..
> > > 
> > > Ok, that's good. What's the output of dmesg during association?
> > > 
> > 
> > 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
> 
> Ok, might be something in mac80211 as well. Or maybe even with your AP ;)
> 
> If this 100% reproducible? Of does it work sometimes?
100% reproducible, I also tried to change AP and the result was the
same.

Then i retried with my working driver version on 2.6.33 and everything
started working again.

> 
> Helmut

-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara



More information about the users mailing list