rt2x00 Driver Support in Kernel 2.6.26.5

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

ManuelSahm

16-09-2008 12:59:06

Hello,

I have downloaded the latest tarball of rt2570usb and rt73usb. I have compiled the drivers an started them.

They works much better than the drivers which are inside the Kernel 2.6.26.5.

Could I load the rt73.ko and the rt2570.ko the same time ?
When will the latest bugfixes, which are included in the latest tarballs, be inside the official kernel release ?

I have problems since Kernel 2.6.26...?

Thank you

IvD

16-09-2008 18:14:09


Could I load the rt73.ko and the rt2570.ko the same time ?
[/quote2edtzoak]

rt2570.ko and rt73.ko can be loaded at the same time as long as you don't have hardware that attempts to use both drivers.


When will the latest bugfixes, which are included in the latest tarballs, be inside the official kernel release ?
[/quote2edtzoak]

As you might have read on numerous locations the legacy drivers are _not_ the rt2x00 drivers and thus there is no such thing as a bugfix from legacy going to rt2x00.

ManuelSahm

17-09-2008 06:24:53

[quote3hxdx5so]The rt2x00 driver is currently in the kernel tree marked as experimental. Please report all problems here first for discussion before they are promoted into SourceForge's Bug Tracker.[/quote3hxdx5so]

I thought this drivers are inside the kernel tree ?
In Kernel 2.6.26.5 there are bugs.

My question was when they will be fixed.

Thanks
Manuel

IvD

17-09-2008 07:37:10

Then you should recheck my replies to your topics, because I already asked you to test something since you didn't use the correct commands to enable the device...

ManuelSahm

17-09-2008 08:18:01

I have tested the command
[codevhnsrx1q]
iwconfig wlan0 ap auto
[/codevhnsrx1q]

but the stick doesn´t connect to my AccessPoint...

IvD

17-09-2008 11:59:31

In my reply in the other topic I said to use the BSSID address of the AP you want to connect with, using 'auto' is not correct.

ManuelSahm

17-09-2008 13:51:57

Ok, I have tested the command with the BSSId, but without success

[code3g6z8sft]iwconfig wlan0 essid obidsahm
ifconfig wlan0 192.168.10.10
ADDRCONF(NETDEV_UP): wlan0: link is not ready
iwconfig wlan0 ap 00:16:01:F4:7E:E9
phy1 -> rt2x00mac_conf_tx: Onfo - Configured TX queue 0 - CWmin: 4, CWmax: 10, Aifs: 2.
phy1 -> rt2x00mac_conf_tx: Onfo - Configured TX queue 1 - CWmin: 4, CWmax: 10, Aifs: 2.
[/code3g6z8sft]

I have an accesspoint without encryption and ssid enabled ssid = obidsahm
ip is 192.168.10.1
Kernel 2.6.26.5
Wireless Tool 0.29

Thanks for help

IvD

17-09-2008 14:00:12

What is the output of 'dmesg' after the 'iwconfig wlan0 ap <bssid>' command?

ManuelSahm

17-09-2008 14:06:39

This is the output from dmesg, from the point I inserted my wlan stick

[codehssbxv8z]usb 1-1:1.0: uevent
usb 1-1: uevent
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0002
at91_ohci at91_ohci: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS
hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
at91_ohci at91_ohci: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS
usb 1-1: new full speed USB device using at91_ohci and address 4
at91_ohci at91_ohci: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS
usb 1-1: default language 0x0409
usb 1-1: uevent
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
usb 1-1:1.0: uevent
rt2500usb 1-1:1.0: usb_probe_interface
rt2500usb 1-1:1.0: usb_probe_interface - got id
phy2 -> rt2500usb_validate_eeprom: EEPROM recovery - NIC: 0xfff0
phy2 -> rt2x00_set_chip: Info - Chipset detected - rt: 1201, rf: 0005, rev: 00000005.
phy2: Selected rate control algorithm 'pid'
Registered led device: rt2500usb-phy2:radio
drivers/usb/core/inode.c: creating file '004'
usb 1-1: New USB device found, idVendor=1044, idProduct=8007
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: 802.11g WLAN + Pen Drive
usb 1-1: Manufacturer: Ralink
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0002
phy2: HW CONFIG: freq=2412
ADDRCONF(NETDEV_UP): wlan0: link is not ready
phy2: HW CONFIG: freq=2412
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2417
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2422
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2427
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2432
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2437
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2442
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2447
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2452
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2457
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2462
phy2: TX to low-level driver (len=50) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:1a:4d:3e:19:2e A3=ff:ff:ff:ff:ff:ff
phy2: HW CONFIG: freq=2412
phy2: HW CONFIG: freq=2412
phy2 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 4, CWmax: 10, Aifs: 2.
phy2 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 10, Aifs: 2.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: authenticate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: authenticate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: authentication with AP 00:16:01:f4:7e:e9 timed out
phy2: HW CONFIG: freq=2412
phy2 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 4, CWmax: 10, Aifs: 2.
phy2 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 10, Aifs: 2.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: RX authentication from 00:16:01:f4:7e:e9 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=54) FC=0x0000 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: authentication frame received from 00:16:01:f4:7e:e9, but not in authenticate state - ignored
wlan0: associate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=54) FC=0x0000 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: associate with AP 00:16:01:f4:7e:e9
phy2: TX to low-level driver (len=54) FC=0x0000 DUR=0x013a A1=00:16:01:f4:7e:e9 A2=00:1a:4d:3e:19:2e A3=00:16:01:f4:7e:e9
wlan0: association with AP 00:16:01:f4:7e:e9 timed out
~ #[/codehssbxv8z]

IvD

17-09-2008 14:19:01

You might want to repeat the 'ap' command a few times untill dmesg indicates the association succeeded,
the logs do indicate it is at least trying to authenticate but the association step fails.

ManuelSahm

17-09-2008 14:48:43

It doesn´t work, I´m sorry.

With the rt2570usb driver it works.... but not with this one included in the kernel 2.6.26.5.

Any ideas ?

dj_def

24-09-2008 15:49:23

That's a driver bug, it will never authenticate with this kernel (and I think that it's so with all 2.6.26.x kernels).
I hope developers understood there is a problem.
With debian lenny I get an authentication only after the system boot at the first try.
Then it will never reauthenticate again until reboot.