Dlink DWL-G122 Rev. C1 and rt73_usb

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

brotk

02-12-2007 11:37:40

Hello everyone, and thanks for your effort. I really appreciate your work, and i thought maybe i could help a bit.

I recently bought a new wifi stick, and i saw on a homepage that the dlink dwl-g122 has good support, so i bought it. This wasnt quite true, but i discovered your project and so installed the 2.6.24-rc3 kernel.

This is what i get when i plug the stick in
[code1w3upt4f]usb 1-2.2: new high speed USB device using ehci_hcd and address 5
usb 1-2.2: configuration #1 chosen from 1 choice
usb 1-3: new high speed USB device using ehci_hcd and address 6
usb 1-3: configuration #1 chosen from 1 choice
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - NIC: 0xffef
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - Led: 0xe000
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET BG: 0x0000
phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0002, rev: 0002573a.
phy0: Selected rate control algorithm 'simple'
usbcore: registered new interface driver rt73usb
[/code1w3upt4f]

I have only managed to get connected to an unsecured wlan network, and i will try to show what i have to do to get connected.

first i have to get the wifi0 interface up with "ifconig wlan0 up", which shows the following
[code1w3upt4f]phy0 -> rt73usb_init_bbp: Debug - Start initialization from EEPROM...
phy0 -> rt73usb_init_bbp: Debug - ...End initialization from EEPROM.
ADDRCONF(NETDEV_UP): wlan0: link is not ready[/code1w3upt4f]

Then i start wpa_supplicant, which connects to the not encrypted network "brotnet"
[code1w3upt4f]brotkastn brot # wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Trying to associate with SSID 'brotnet'
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - Associated with 00:1b:fc:6b:7d:9f
CTRL-EVENT-CONNECTED - Connection to 00:1b:fc:6b:7d:9f completed (auth) [id=0 id_str=][/code1w3upt4f]

and dmesg says the following

[code1w3upt4f]phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 2 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 3 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 4 - CWmin: 4, CWmax: 10, Aifs: 2.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:1b:fc:6b:7d:9f
wlan0: RX authentication from 00:1b:fc:6b:7d:9f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:1b:fc:6b:7d:9f
wlan0: RX AssocResp from 00:1b:fc:6b:7d:9f (capab=0x401 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:1b:fc:6b:7d:9f)
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 2 - CWmin: 4, CWmax: 10, Aifs: 3.
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 3 - CWmin: 4, CWmax: 10, Aifs: 7.
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 3, CWmax: 4, Aifs: 2.
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 2, CWmax: 3, Aifs: 2.
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
[/code1w3upt4f]

And i am connected. The connection is a bit unstable
[code1w3upt4f]--- 192.168.1.1 ping statistics ---
100 packets transmitted, 61 received, +3 errors, 39% packet loss, time 99062ms
rtt min/avg/max/mdev = 0.798/1.877/4.364/0.800 ms, pipe 3
[/code1w3upt4f]

So in my opinion this is very good for an experimental beta driver D

The only problems i have is that it wont work with any encryption and the stability of the connection, but that will get better as the driver gets more stable, right ?

I hope i could help, and thanks again to the devs.

brot

pepposole

21-12-2007 12:29:22

i have the same dongle....



but different problem

dmesg seems ok

[listt7eb9iuo]phy0 -> rt73usb_validate_eeprom EEPROM recovery - NIC 0xffef
phy0 -> rt73usb_validate_eeprom EEPROM recovery - Led 0xe000
phy0 -> rt73usb_validate_eeprom EEPROM recovery - RSSI OFFSET BG 0x0000
phy0 -> rt2x00_set_chip Info - Chipset detected - rt 1300, rf 0002, rev 0002573a.
phy0 Selected rate control algorithm 'simple'
usbcore registered new interface driver rt73usb
[/listut7eb9iuo]


iwconfig too... even if i don't know what WMASTER0 and SIT0 means

[listt7eb9iuo]wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ModeMonitor Frequency2.412 GHz Tx-Power=27 dBm
Retry min limit7 RTS throff Fragment thr=2346 B
Encryption keyoff
Link Quality0 Signal level0 Noise level0
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0

sit0 no wireless extensions.
[/listut7eb9iuo]


airmon-ng show something not good (


[listt7eb9iuo][root@pcdvdn ~]# airmon-ng


Interface Chipset Driver

eth1 Centrino b/g ipw2200
wlan0 Unknown Unknown (MONITOR MODE NOT SUPPORTED)
[/listut7eb9iuo]


any idea?

AdamBaker

21-12-2007 20:25:08

Most likely airmon-ng is not aware of the mac80211 restriction that you must down the interface before switching to monitor mode. if you do

ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up

before starting airmon-ng that may help.

sit0 is a special interface for creating tunnels and wmaster0 is a special interface that is used for some mac80211 control functions.

pepposole

22-12-2007 09:24:12

Most likely airmon-ng is not aware of the mac80211 restriction that you must down the interface before switching to monitor mode. if you do

ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up

before starting airmon-ng that may help.

sit0 is a special interface for creating tunnels and wmaster0 is a special interface that is used for some mac80211 control functions.[/quote3pw02soa]



do you think it's a good thing get driver unknown and chipset unkwnon???

with rt73 legacy, i got driver = rt73 and chipset = rt73


i got another problem....

my DWL 122 don't catch BEACONS from some AP =(


and sometime system freeze.... do you think it's because i got an active centrino in the same pc???

AdamBaker

22-12-2007 16:22:36

I'm not sure driver and chipset unknown being reported by airmon-ng is anything to worry about. It only needs to understand the driver and chipset to know how to enable monitor mode. With the generic mac80211 radiotap monitor mode it shouldn't need to know about drivers and chipsets.

The missing beacon packets could be down to incorrect antenna or sensitivity settings - that is an area that is still being worked on in the driver. It is also possible that there are bugs in monitor mode support, I suspect that rt73usb is sometimes dropping packets when I use it with wireshark whereas rt61pci seems more reliable.

The crash is concerning. Are you able to get it to crash while you have the console selected (with ctrl-alt-f1) and if so do you see a crash dump? If so could you capture that dump (ideally with a serial console but a photo of the screen will help if you can't set up a serial console).

brotk

22-12-2007 16:35:28

someone knows if wpa works with the driver included in 2.6.24-rc4 ? I cant get my wlan-stick to connect to the encrypted ap here.

pepposole

23-12-2007 09:50:35

I'm not sure driver and chipset unknown being reported by airmon-ng is anything to worry about. It only needs to understand the driver and chipset to know how to enable monitor mode. With the generic mac80211 radiotap monitor mode it shouldn't need to know about drivers and chipsets.

The missing beacon packets could be down to incorrect antenna or sensitivity settings - that is an area that is still being worked on in the driver. It is also possible that there are bugs in monitor mode support, I suspect that rt73usb is sometimes dropping packets when I use it with wireshark whereas rt61pci seems more reliable.

The crash is concerning. Are you able to get it to crash while you have the console selected (with ctrl-alt-f1) and if so do you see a crash dump? If so could you capture that dump (ideally with a serial console but a photo of the screen will help if you can't set up a serial console).[/quote2uq45jqd]


thank you so much...


one last thing that might help you...


with rt73 "only" drivers, i catch perfectly all beacons....


i'll check new drivers releases every day ;)