rt73 (daily snapshot) unstable WPA connection with 2.6.27

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

gar73

07-01-2009 22:58:10

Hello to everyone and happy new year to you!

I have just upgraded my laptop (now running a 2.6.27-gentoo-r7 kernel) and I am not able anymore to connect my AP using WPA[2]PSK / TKIP|AES.

I took the freshly released CVS snapshot (2009010709), compiled it and tested itbut it fails to connect.

I use the following commands for my test
[code2lfzjsnq]#!/bin/bash

SSID="MY_SSID"
WPAPSK="MY_KEY"

# Cleaning

ifconfig wlan0 down

if [ -f /var/run/dhcpcd-wlan0.pid ] ; then
kill `cat /var/run/dhcpcd-wlan0.pid`
fi

if [ -f /var/lib/dhcpcd/dhcpcd-wlan0.lease ] ; then
rm -f /var/lib/dhcpcd/dhcpcd-wlan0.lease
fi

# Module

rmmod rt73
modprobe rt73 debug=31

# Test

iwpriv wlan0 set Channel=12
iwpriv wlan0 set AuthMode=WPAPSK # or WPA2PSK
iwpriv wlan0 set EncrypType=AES # or TKIP
iwpriv wlan0 set WPAPSK="$WPAPSK"

iwconfig wlan0 essid "$SSID"
iwconfig wlan0 mode managed

ifconfig wlan0 up
[/code2lfzjsnq]

Whatever the WPAPSK/WPA2PSK or TKIP/AES couple I use, I have the same symptoms (seeing the leds) the card seems to connect the AP (the link led lights on), then, few seconds after, it goes down. dhcpcd has never received any IP address during the time the link seems to be up.

You'll find the logs as attachment. Using 2.6.26, the card was properly working (with another old CVS snapshot). Would you have any idea of my problem ?

Best regards,

Georges

Vern

08-01-2009 21:13:44

Hi gar73,

Do you happen to remember the date of the CVS snapshot that worked with 2.6.26?

Thanks,

PS. Any chance of regression testing the failing CVS on 2.6.26?

Thanks,

gar73

09-01-2009 11:02:04

Hi Vern,

Because of this problem, I retried to make my internal iwl4965 working and managed to do it. So that I am happier than when using my external RT73 USB stick. Meaning I won't use any more my RT73. Anyway, many thanks for your help purposal. You saved me in the passed and retried to know, that's very fair from you!

Best regards,

G.

gar73

09-01-2009 11:03:25

Hi gar73,
Do you happen to remember the date of the CVS snapshot that worked with 2.6.26?
Thanks,
PS. Any chance of regression testing the failing CVS on 2.6.26?
Thanks,[/quote2wbsbey1]

Whatever my future use of the RT73 module, if you need some tests for the rt73 testing, let me know!

Vern

10-01-2009 02:23:57

Hi gar73,

I guess you're the same guy as gar2500 (imagine my surprise. I really gotta clean some of this stuff out).

OK. Do you happen to remember the date of the CVS snapshot that worked with 2.6.26?

Thanks,

gar73

10-01-2009 10:36:54

Hi Vern,

Hi gar73, I guess you're the same guy as gar2500 (imagine my surprise. I really gotta clean some of this stuff out).[/quotemilu9v16]

You're right ) I was unable to use my old nickname coz I lost the password and was lazy to reforge the corresponding email address. So I updated my nick to the current chipset )

OK. Do you happen to remember the date of the CVS snapshot that worked with 2.6.26?[/quotemilu9v16]

The last one I used (and that was working) was rt73-cvs-2008121606.

Let me know if you want some testing )

Georges

PS Vern, should I add that I also tested the old cvs snapshot (rt73-cvs-2008121606) with the new kernel ? )

Vern

10-01-2009 17:45:43

The last one I used (and that was working) was rt73-cvs-2008121606.[/quote2ico9b48]Strange. The latest CVS commit is 1 December - 11 days previous. I would have thought that and the failing tarball would be identical. Maybe somehow a corrupted copy? Could you download the latest tarball and try that?

[quote2ico9b48]PS Vern, should I add that I also tested the old cvs snapshot (rt73-cvs-2008121606) with the new kernel ?[/quote2ico9b48]And did it work?

Thanks,

gar73

10-01-2009 20:14:43


PS Vern, should I add that I also tested the old cvs snapshot (rt73-cvs-2008121606) with the new kernel ?[/quote1g3lules]

And did it work?[/quote1g3lules]

Nope it did'nt ) I feel like the problem is linked to 2.2.27 and not to the driver release. Did you have a look at the logs I previously sent?

Georges

hexa

13-01-2009 03:17:01

I am having the exact same problem, on a complete different system, kernel and arch.

I am on ARM, kernel 2.6.20.4 and it happened on rt73-cvs-2008111819 and rt73-cvs-2009011214

The only part where our systems are similar, is in the device itself.

I have this D-Link DWL-G122 H/W Ver C1 F/W Ver 3.00 (so it says in the back label)
and the idVendor and idProduct are the same as yours.

idVendor = 0x7d1, idProduct = 0x3c03

I could get it working with WEP 128bits, but not with WPA (tkip or aes). Same behavior.

Later.