DWL-122 rev A1 support

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4470

max2k

28-11-2007 10:56:46

Hallo,

I have this D-Link DWL-122 A1 usb stick. It's working fine with wlan-ng's prism2_usb driver in Debian 4.0r1. But this driver doesn't allow AP respectively Master mode. Hostap driver is not working with USB, so I thought I should stick with rt2xx drivers.
I installed the Debian package for rt2xx (cvs20060928), it compiles and installs (among others)

rt73usb.ko
rt2500pci.ko
rt2400pci.ko
rt61pci.ko
rt2500usb.ko
80211.ko
rate_control.ko
crt-itu-t.ko

The problem now is, that (after blacklisting the prism2_usb driver) nothing happens, when plugging the stick in. I guess, it should load automatically the correct driver.
Another problem is, which one would be the correct one? Most likely one of the drivers ending in usb, so something from rt73 and rt2500, right? But which one?
As far as I know, it is some kind of prism2/2.5 chipset, as it works (as client) very fine with prism2_usb driver from wlan-ng.


lsusb output
Bus 002 Device 008 ID 20013700 D-Link Corp. [hex] DWL-122 802.11b
Device Descriptor
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x2001 D-Link Corp. [hex]
idProduct 0x3700 DWL-122 802.11b
bcdDevice 1.32
iManufacturer 0
iProduct 0
iSerial 1 000000000000
bNumConfigurations 1
Configuration Descriptor
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Device Status 0x0000
(Bus Powered)

Another question would be, if I buy a new USB wireless card, which one should I buy, to have it working as a Access Point in Linux?


Thank you very much in advance,

Maximilian

IvD

28-11-2007 18:36:07

Correct me if I am mistaken, but are you really trying to use the Ralink drivers for a Prism device while deliberatly blocking the correct prism driver and then expect things to work?

Drivers are created for specific hardware, so drivers for chipset X will _not_ work on chipsets Y.

max2k

28-11-2007 18:52:37

Okay, so I also figured that one out ;)
I was confused because I read somewhere rt2x00 is good for DWL-122, but I assume this was for a different revision of that card.

As I need just some USB stick which is capable of Master mode (performance, .11G whatever doesn't matter), I guess I could just buy any ralink chipset and use the rt2x00 beta drivers for that?

Which one would you recommend? I found the Asus WL-167G having the ralink rt2500, would this work as an AP?


Thank you very much!

max

IvD

28-11-2007 18:56:04

At the moment rt2x00 has master mode disabled, this because we are working on stabilizing some of the simple features before working on the advanced features.

You might want to check the Broadcom drivers, I believe they do have a working driver for master mode

max2k

28-11-2007 19:40:04

are you aware of any broadcom based USB sticks?
I just know so far built-in for laptops respectively pcmcia...

But thanks for this info!

ps I just found out, that also the free broadcom drivers only support PCI/PCMCIA, same as hostap. therefore i already wanted to use rt2x00 drivers... btw, is it easy to reenable AP mode in the current rt2x00 code?

IvD

28-11-2007 20:49:27

Enabling the code is simple, just a matter of removing 3 lines of code.
The problem is that master mode is not working since the beacons are not being generated correctly. Because that is failing, master mode was disabled, when beaconing is properly debugged and tested, master mode will be enabled again.

max2k

29-11-2007 08:17:33

Okay, i see.
Was there a previous version of rt2x00, which had a working AP/Master mode?
Or how long will it most likely take, before it'll be enabled again?


Thanks!

IvD

29-11-2007 19:01:55


Was there a previous version of rt2x00, which had a working AP/Master mode?
[/quote1lbkl9xf]

At some points people reported success, but we never reached a point it was working for everybody and the status changed too often. So I am not even sure which version actually worked.


Or how long will it most likely take, before it'll be enabled again?[/quote1lbkl9xf]

No idea.

max2k

30-11-2007 08:54:06

Okay, I think I'll give it a try anyway, with a asus wl-167g and different versions of the rt2x00 drivers, which had still AP mode enabled...
because if it doesn't work with any USB wlan card, I have to get a different pc with pci/mini-pci/pcmcia...

Thank you very much!