Getting DWA-110 support with if_rum

Jonathan Lee spamtrap at tczyhatczsche.eu
Thu Aug 14 21:07:51 UTC 2008


%uname -a
FreeBSD johnny.mnemoni.ca 7.0-STABLE
FreeBSD 7.0-STABLE #5: Sun Aug 10 15:26:30 EEST 2008
root at johnny.mnemoni.ca:/usr/obj/usr/src/sys/JOHNNY  i386


I've noticed D-LINK's DWA-111 (a USB wireless LAN adapter, product ID
0x3c06) having been added to /usr/src/sys/dev/usb/usbdevs list, and the
same ID added to if_rum.c.

Then, I have a DWA-110, with prod. ID 0x3c07. I have opened its
case, there's a RT2571WF chip inside. According to 'man rum',
that's what if_rum supports.

Suspect DWA-110 to be a close relative of DWA-111, though might be
horribly wrong.

I added the DWA-110 ID to if_rum.c (and recompiled). The device is
recognized and shown in ifconfig.

There are some errors upon inserting the device:


Aug 12 11:00:36 johnny kernel: wpi0: timeout resetting Tx ring 1
Aug 12 11:00:36 johnny kernel: wpi0: timeout resetting Tx ring 3
Aug 12 11:00:36 johnny kernel: wpi0: timeout resetting Tx ring 4


(Using the Perforce (development) version of the driver.)

And also one warning in /var/log/messages:


Aug 14 22:49:26 johnny kernel: rum0: <Ralink 802.11 bg WLAN, class 0/0, rev 2.00/0.01, addr 3> on uhub4
Aug 14 22:49:26 johnny kernel: rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528
Aug 14 22:49:27 johnny kernel: rum0: WARNING: using obsoleted IFF_NEEDSGIANT flag


The issue is, the device doesn't see any networks. 'ifconfig scan'
shows no output (hangs until CTRL+С is pressed). (Actually, wlandebug
says that scanning is started as soon as the device is brought to the
'up' state.)

'wlandebug +debug
+scan' shows no errors.

dmesg repeats the following over and over:


...
rum0: scan_next: chan   8g ->   9g [active, dwell min 20 max 200]
rum0: scan_next: chan   9g ->  10g [active, dwell min 20 max 200]
rum0: scan_next: chan  10g ->  12g [active, dwell min 20 max 200]
rum0: scan_next: chan  12g ->  14g [active, dwell min 20 max 200]
rum0: sta_pick_bss: no scan candidate
rum0: scan_next: done, restart [ticks 20994469, dwell min 20 scanend 2168334612]
rum0: scan_next: chan  14g ->   1g [active, dwell min 20 max 200]
rum0: scan_next: chan   1g ->   6g [active, dwell min 20 max 200]
rum0: scan_next: chan   6g ->  11g [active, dwell min 20 max 200]
rum0: scan_next: chan  11g ->   7g [active, dwell min 20 max 200]
rum0: scan_next: chan   7g ->  13g [active, dwell min 20 max 200]
rum0: scan_next: chan  13g ->   2g [active, dwell min 20 max 200]
rum0: scan_next: chan   2g ->   3g [active, dwell min 20 max 200]
rum0: scan_next: chan   3g ->   4g [active, dwell min 20 max 200]
rum0: scan_next: chan   4g ->   5g [active, dwell min 20 max 200]
rum0: scan_next: chan   5g ->   8g [active, dwell min 20 max 200]
rum0: scan_next: chan   8g ->   9g [active, dwell min 20 max 200]
rum0: scan_next: chan   9g ->  10g [active, dwell min 20 max 200]
rum0: scan_next: chan  10g ->  12g [active, dwell min 20 max 200]
rum0: scan_next: chan  12g ->  14g [active, dwell min 20 max 200]
rum0: sta_pick_bss: no scan candidate
rum0: scan_next: done, restart [ticks 20997281, dwell min 20 scanend 2168334612]
rum0: scan_next: chan  14g ->   1g [active, dwell min 20 max 200]
rum0: scan_next: chan   1g ->   6g [active, dwell min 20 max 200]
rum0: scan_next: chan   6g ->  11g [active, dwell min 20 max 200]
...


I've also tried specifying the SSID of a network, explicitly setting
the channel, etc..


So, the QUESTIONS are:

1) Are there any documents/threads/messages about getting DWA-111, the
already-added device, configured? Who actually owns the device and
reported it as working? Contacts?

2) Any advice on my DWA-110? Something I'm missing?

3) Other logs needed? Additional wlandebug output?


More information about the freebsd-drivers mailing list