rt2500usb (ASUS WL-167g)

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

zeekoe

28-10-2007 17:18:25

After I got rt2x00 to compile[/url2ztwskrn], I now must get it to work. First, some version and debugging info

[code2ztwskrn]root@zeekoe:/usr/src/rt2x00# cg-status
Heads:
>master db0d1a7b3854~ rt2x00: Release rt2x00 2.0.12
R origin db0d1a7b3854~ rt2x00: Release rt2x00 2.0.12

? commando
? conf.vars
? debian/
? stamp-arch-conf
? stamp-configure
? stamp-configure-arch
? stamp-configure-indep
? stamp-indep-conf
? stamp-kernel-headers
? stamp-kernel-image
M arch/x86/kernel/crash.c
M scripts/package/Makefile[/code2ztwskrn]

[code2ztwskrn][ 497.478455] phy1 -> rt2500usb_validate_eeprom: EEPROM recovery - NIC: 0xfff0
[ 497.478816] phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 1201, rf: 0005, rev: 00000005.
[ 497.478897] PM: Adding info for No Bus:phy1
[ 497.484803] PM: Adding info for No Bus:wmaster0
[ 497.486420] phy1: Selected rate control algorithm 'simple'
[ 497.486574] PM: Adding info for No Bus:wlan0
[ 497.489405] usbcore: registered new interface driver rt2500usb
[ 497.705207] phy1 -> rt2500usb_init_bbp: Debug - Start initialization from EEPROM...
[ 497.705231] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x11, value: 0x33.
[ 497.706333] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x15, value: 0x18.
[ 497.706894] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x16, value: 0x18.
[ 497.707580] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x3e, value: 0x00.
[ 497.708021] phy1 -> rt2500usb_init_bbp: Debug - ...End initialization from EEPROM.
[ 497.717337] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 274.179970] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 274.179992] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 274.179995] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 7 - CWmin: 5, CWmax: 10, Aifs: 2.
[ 723.840943] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 741.227344] eth0: no IPv6 routers present
[ 1177.482049] phy1 -> rt2500usb_init_bbp: Debug - Start initialization from EEPROM...
[ 1177.482069] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x11, value: 0x33.
[ 1177.483174] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x15, value: 0x18.
[ 1177.483675] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x16, value: 0x18.
[ 1177.484304] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x3e, value: 0x00.
[ 1177.484926] phy1 -> rt2500usb_init_bbp: Debug - ...End initialization from EEPROM.
[ 1177.494060] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 829.262657] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 829.262672] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 829.262676] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 7 - CWmin: 5, CWmax: 10, Aifs: 2.
[ 829.278052] wlan0: Initial auth_alg=0
[ 829.278069] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 829.480922] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 829.685406] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 829.888695] wlan0: authentication with AP 00:01:e3:c5:f0:ee timed out
[/code2ztwskrn]

I then used the commands
[code2ztwskrn]ifconfig wlan0 down
ifconfig wlan0 up
iwconfig wlan0 essid {my-ssid}
iwconfig wlan0 key {my-wep-key}
iwconfig wlan0 ap auto [note: the docs said that I had to fill in my ssid here, but iwconfig fails on that. On 'auto', iwconfig says it associates]
dhclient wlan0[/code2ztwskrn]
giving the following
[code2ztwskrn][ 2391.189530] phy1 -> rt2500usb_init_bbp: Debug - Start initialization from EEPROM...
[ 2391.189545] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x11, value: 0x33.
[ 2391.195313] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x15, value: 0x18.
[ 2391.197038] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x16, value: 0x18.
[ 2391.203826] phy1 -> rt2500usb_init_bbp: Debug - BBP: 0x3e, value: 0x00.
[ 2391.204363] phy1 -> rt2500usb_init_bbp: Debug - ...End initialization from EEPROM.
[ 2391.242536] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2391.248308] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 2391.248321] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 4, CWmax: 10, Aifs: 2.
[ 2391.248324] phy1 -> rt2x00mac_conf_tx: Info - Configured TX ring 7 - CWmin: 5, CWmax: 10, Aifs: 2.
[ 2391.275147] wlan0: Initial auth_alg=0
[ 2391.275163] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 2391.275210] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 2391.354595] wlan0: Initial auth_alg=0
[ 2391.354611] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 2391.552423] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 2391.752016] wlan0: authenticate with AP 00:01:e3:c5:f0:ee
[ 2391.955881] wlan0: authentication with AP 00:01:e3:c5:f0:ee timed out[/code2ztwskrn]
The output of iwconfig
[code2ztwskrn]wlan0 IEEE 802.11g ESSID:"{my-ssid}"
Mode:Managed Frequency:2.412 GHz Access Point: {my-ssid-mac}
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:{my-wep-key}
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0[/code2ztwskrn]
So that looks quite right. But it doesn't authenticate. I couldn't find any clear solution for that, does someone have an idea what it could be on my case?
Note, my access point doesn't support disabling encryption. Also, MAC filtering is on, but my MAC is in there and it has worked before with the rt2570 driver (though that one disabled my keyboard on plug-out in previous kernels).

Oh, and relevant sections of ifconfig
[code2ztwskrn]wlan0 Link encap:Ethernet HWaddr {my-mac}
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0:ava Link encap:Ethernet HWaddr {my-mac}
inet addr:169.254.6.172 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

wmaster0 Link encap:UNSPEC HWaddr {my-mac}-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[/code2ztwskrn]
dhclient times out, btw.

AdamBaker

28-10-2007 22:06:05

This looks like similar symptoms to those described by ben in the thread at
http//rt2x00.serialmonkey.com/phpBB2/v ... e4a7c814e5

If you have another wireless card that could be used to sniff the auth sequence with wireshark that would be informative.

Another test that may be worthwhile is to check if it works with WEP disabled.

zeekoe

28-10-2007 22:48:35

Thanks for the reply.
I do have another card (PCMCIA), a Realtek 8180L. But the driver for that is not in the kernel tree, and ndiswrapper doesn't seem to work with 2.6.24 yet, and the native driver doesn't seem to that new either. Then there's an Atheros USB thingy, but that one is not supported at all...
Hmm, I might try it from a windows computer. But I don't think I can do that in the next two weeks or so. Unfortunately my router doesn't give me the option to disable encryption (just tried disabling MAC filter to be 100% sure, but that didn't help). Setting from Open to Shared did not help. I can try WPA though, but don't think that'll help... so this auth thing _is_ related to WEP?
Does it help that the normal rt2570usb driver did work well?

AdamBaker

28-10-2007 23:28:47

Knowing that the legacy driver works is good news - it suggests there may be a setup problem with rt2500usb. Comparison register dumps between the 2 would be helpful to track that down.

Windows drivers (either on windows or with ndiswrapper) are no use for trying to capture these messages, you need a driver that supports monitor mode.

The message isn't directly related to WEP to the extent it also exists in open networks but the content is crypto system dependent. There have been a couple of instances recently of failures with encrypted messages but it hasn't mattered in that case whether it was WEP or WPA.