On 02/27/2011 03:06 PM, kog13 wrote:
> 2434.113087] No probe response from AP 00:25:9c:6a:41:76 after 500ms, disconnecting.
>
> I’m pretty sure it’s the line about the probe disconnecting that points
> to the problem, but I have no idea what’s causing it.
>
> Any ideas?
Yes, that is what is causing the disconnect. The MAC layer is probing the AP and
is getting no response. The problem may be in the driver, the AP, or an
incompatibility between them. Usually, one must set up wireshark and capture the
traffic on the air. It is best if done from a second computer.
The workaround is probably to “/sbin/modprobe -rv rt2870 && /sbin/modprobe -v
rt2870”.
That driver is in the staging directory, which means the quality is unknown. The
problem is likely in the driver, but you might have trouble getting anyone to
fix it.
According to hardware information, there are two drivers loaded: rt2870sta and rt2800usb. Reloading rt2800usb fixes the connection problem, but again, only for a little bit. It looks like the rt2800usb module loads the rt2870 module; I guess both of them are needed for it to work.
I’m going to look into getting the driver directly from Ralink and compiling it.
On 02/27/2011 06:36 PM, kog13 wrote:
>
> No luck. Compiling it from source makes it work even less than the one
> that comes with the kernel.
>
> Is there any hope for this driver, then?
I do not know.
What is the USB Id for the device as shown by ‘lsusb’?
On 02/27/2011 11:06 PM, kog13 wrote:
>
>
> Code:
> --------------------
> Bus 002 Device 003: ID 07d1:3c09 D-Link System DWA-140 802.11n Adapter [ralink rt2870]
> --------------------
As you saw in the loaded driver list, there are two drivers that claim this
device. You should blacklist rt2870sta as it comes from staging. Driver
rt2800usb has undergone much more rigorous review and testing.