rt2x00.serialmonkey.com

Hi,

I hope somebody here can help me.

I was running Ubuntu 7.10 and used the driver from http://homepages.tu-darmstadt.de/~p_larbig/wlan/ -> rt2570-k2wrlz-1.6.1.tar.bz2

After the upgrade my wireless connection was gone.

I figured out that the driver above is not suited for the kernel I have now (2.6.24-16).

So I tried the driver CVS hourly tarball: rt2570-CVS

It compiled all right, and after startup I get a wlan0 interface. (Before I got a rausb0 interface. - strange)

I blacklisted the following drivers in /etc/modprobe.d/blacklist:
blacklist rt2500usb
blacklist rt2x00lib
blacklist rt73usb

I tried with the same config I had in /etc/network/interfaces (except changing rausb0 into wlan0):
auto wlan0
iface wlan0 inet static
address 172.31.31.72
netmask 255.255.255.240
network 172.16.16.64
gateway 172.16.16.70
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 mode Managed
pre-up iwpriv wlan0 auth 3
pre-up iwpriv wlan0 enc 3
pre-up iwconfig wlan0 essid stayoff
pre-up iwpriv wlan0 wpapsk cfc922b44bc10ec36b47f6db6bddc27eed73f6dde1b1d24a0d2a3cccdb005b24
pre-up iwconfig wlan0 essid stayoff
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid stayoff

After a reboot I see that in ifconfig I have the correct IP address, but iwconfig output does not seem normal:
iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 RT2500USB WLAN ESSID:"stayoff" Nickname:""
Mode:Managed Frequency=2.412 GHz Bit Rate=11 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level:-120 dBm Noise level:-85 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Obviously I am doing something wrong, but I can't find what it is.

My knowledge of Linux isn't that great either...

Some more output:
modinfo rt2570
filename: /lib/modules/2.6.24-16-generic/extra/rt2570.ko
license: GPL
author: http://rt2x00.serialmonkey.com
description: Ralink RT2570 usb 802.11g WLAN driver 1.0.0 - CVS 2008042510
srcversion: 23E05740A72BC0642A3BC9B
alias: usb:v5A57p0260d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0EB0p9020d*dc*dsc*dp*ic*isc*ip*
alias: usb:v114Bp0110d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0707pEE13d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0681p3C06d*dc*dsc*dp*ic*isc*ip*
alias: usb:v148Fp9020d*dc*dsc*dp*ic*isc*ip*
alias: usb:v148Fp2573d*dc*dsc*dp*ic*isc*ip*
alias: usb:v148Fp2570d*dc*dsc*dp*ic*isc*ip*
alias: usb:v148Fp1706d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DB0p6869d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DB0p6865d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DB0p6861d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0411p0097d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0411p008Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0411p0067d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0411p0066d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0411p005Ed*dc*dsc*dp*ic*isc*ip*
alias: usb:v06F8pE000d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1044p8007d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1044p8001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p3C00d*dc*dsc*dp*ic*isc*ip*
alias: usb:v14B2p3C02d*dc*dsc*dp*ic*isc*ip*
alias: usb:v13B1p001Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v13B1p0011d*dc*dsc*dp*ic*isc*ip*
alias: usb:v13B1p000Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp705Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp7051d*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp7050d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0B05p1707d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0B05p1706d*dc*dsc*dp*ic*isc*ip*
depends: usbcore
vermagic: 2.6.24-16-generic SMP mod_unload 586
parm: debug:Debug mask: n selects filter, 0 for none (int)
parm: ifname:Network device name (default rausb%d) (charp)


lsmod |grep rt
rt2570 191296 0
parport_pc 36260 1
parport 37832 3 ppdev,lp,parport_pc
agpgart 34760 2 nvidia,intel_agp
iTCO_vendor_support 4868 1 iTCO_wdt
usbcore 146028 12 ati_remote,usb_storage,hci_usb,libusual,lirc_atiusb,rt2570,usblp,gspca,usbhid,ehci_hcd,uhci_hcd


Any help or pointers in the right direction will be appreciated..

My alternative is to go out and buy a new pci wireless network card that hopefully is natively supported..

But since it worked before, I am sure I am doing something wrong..

Thx

Hi,

This morning with a clear head I did some more troubleshooting.

I think the driver is working, given this output:

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:58:04:FB:76
Mode:Managed
ESSID:"wifi17_5"
Encryption key:on
Channel:1
Cell 02 - Address: 00:12:17:C7:59:F7
Mode:Managed
ESSID:"stayoff"
Encryption key:on
Channel:3
Cell 03 - Address: 00:00:C5:C4:4B:A1
Mode:Managed
ESSID:"THUIS"
Encryption key:on
Channel:6
Cell 04 - Address: 00:12:BF:07:83:06
Mode:Managed
ESSID:"Kuypers"
Encryption key:on
Channel:6

But still can't get no connection.

When I do:

sudo ifup wlan0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported


So I guess I have a problem in /etc/network/interfaces. Something that worked with the old driver, but not with the new one (though I never tried the command above in the old environment).

For reference, here the contents of /etc/network/interfaces again:

cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The wireless network interface
auto wlan0
iface wlan0 inet static
address 172.16.16.72
netmask 255.255.255.240
network 172.16.16.64
gateway 172.16.16.70
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 mode Managed
pre-up iwpriv wlan0 auth 3
pre-up iwpriv wlan0 enc 3
pre-up iwconfig wlan0 essid stayoff
pre-up iwpriv wlan0 wpapsk
sddc922b33dd10ec36b47dddb6b5cc27eed73fdddde1b1d24a0d663adadb005bgg
pre-up iwconfig wlan0 essid stayoff
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid stayoff



So I will look some more into that. If in the mean time somebody has an idea or some pointers, it will be appreciated..

Thx

After removing the following from /etc/network/interfaces wireless works again:

#wpa-driver wext
#wpa-key-mgmt WPA-PSK
#wpa-proto WPA
#wpa-ssid stayoff

Thx for supplying this driver

Legacy drivers don't support wpa_supplicant, which means the WPA commands fail. You either need to use RUtilt or the iwpriv commands to configure your WPA

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com