Comment 4 for bug 762987

Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

Hi FERNmann,

On Wed, Jun 1, 2011 at 3:11 PM, FERNmann <email address hidden> wrote:
> OK, I've blacklisted rt2870sta und unblacklisted the other ones but that
> doesn't work, NetworkManager shows "firmware missing" like described
> above.
What do the logs say about that?
dmesg | grep rt2
grep rt2 /var/log/syslog
grep -i firmware /var/log/syslog

> With lsusb, I found out something interesting. lsusb says:
>
> Bus 001 Device 003: ID 07d1:3c0a D-Link System DWA-140 RangeBooster N
> Adapter(rev.B2) [Ralink RT2870]
>
> Hm, on the one hand, it seems to be a RT2870 based one like it's written
> in the output, but one the other hand its ID is 07d1:3c0a which
> indicates that it's RT3070 based. lsusb also says it's "rev.B2" (the
> RT3070-based version of the DWA 140). I've checked out the original box
> from D-Link. Here it says "H/W Ver.: B2".

I think the simplest explanation is that the info on
http://wiki.ubuntuusers.de/WLAN/Karten/D-Link is wrong.
http://wiki.debian.org/rt2870sta has this to say about DWA-140:
USB: 07D1:3C09 D-Link System DWA-140 RangeBooster N Adapter(rev.B1)
[Ralink RT2870]
USB: 07D1:3C0A D-Link System DWA-140 RangeBooster N Adapter(rev.B2)
[Ralink RT2870]
which is in sync with what lsusb and the box say.

> I guess my stick has a RT3070 chipset which also explains why the
> rt2800usb driver does not work. The root of the problem is that the
> stick isn't correctly identifying so the wrong driver is loaded or there
> is a bug in one of the subsystems (libusb, udev etc.)

Again, from the source (see my previous comment):
for module rt2800usb:
Supported chips: RT2770, RT2870 & RT3070, RT3071 & RT3072
So no matter whether it is 2870 based or 3070 based (I do believe
lsusb when it says it is RT2870) it still is supposed to work with
rt2800usb and that is the module that needs debugging if it does not
work. Everything else (drivers from the staging directory or from
Ralink's website) is a workaround.