You are not logged in.
I have an issue with a new Ralink RT2870 wireless USB adapter I just bought. I am connecting to an AP successfully using netcfg and the net-auto-wireless daemon, and all is well with a strong connection. Then after about a minute things drop out. The error is clear in my dmesg:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with 00:1f:1f:b5:a9:31 (try 1)
wlan0: authenticated
wlan0: associate with 00:1f:1f:b5:a9:31 (try 1)
wlan0: RX AssocResp from 00:1f:1f:b5:a9:31 (capab=0x411 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
No probe response from AP 00:1f:1f:b5:a9:31 after 500ms, disconnecting.
cfg80211: Calling CRDA to update world regulatory domain
wlan0: authenticate with 00:1f:1f:b5:a9:31 (try 1)
wlan0: authenticate with 00:1f:1f:b5:a9:31 (try 2)
wlan0: authenticate with 00:1f:1f:b5:a9:31 (try 3)
wlan0: authentication with 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:21:29:e2:90:79 (try 1)
wlan0: direct probe to 00:21:29:e2:90:79 (try 2)
wlan0: direct probe to 00:21:29:e2:90:79 (try 3)
wlan0: direct probe to 00:21:29:e2:90:79 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed out
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 1)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 2)
wlan0: direct probe to 00:1f:1f:b5:a9:31 (try 3)
wlan0: direct probe to 00:1f:1f:b5:a9:31 timed outNote the two APs - I should be able to connect to at least one of them.
Is there a way to extend the 500ms timeout for the AP probe?
This is my iwconfig once the connection is successfully operational:
wlan0 IEEE 802.11bgn ESSID:"my_essid"
Mode:Managed Frequency:2.432 GHz Access Point: 00:1F:1F:B5:A9:31
Bit Rate=54 Mb/s Tx-Power=12 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=36 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0Then after the connection is dropped:
wlan0 IEEE 802.11bgn ESSID:"my_essid"
Mode:Managed Frequency:2.432 GHz Access Point: Not-Associated
Tx-Power=12 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:offAs you can see, power management is switched off. The weird thing is my signal shouldn't be that strong - none of my other wireless cards have anywhere near full signal (~30/70). I can reconnect to the network temporarily (until it fails again) by restarting net-auto-wireless.
Last edited by STM (2010-10-05 01:31:24)
New account: tjbp
Offline
Problem solved - blacklisted other RT* drivers in rc.conf:
MODULES=(!rt2800usb !rt2800lib !rt2*00usb !rt2*00lib)New account: tjbp
Offline