rt2500pci: Failed to initialize device on kernel 2.6.27

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

cherry314159

10-10-2008 18:17:25

The relevant messages from dmesg

[quote28z9c5z6]
cfg80211 Calling CRDA to update world regulatory domain
PCI enabling device 0000000e.0 (0140 -> 0142)
phy0 Selected rate control algorithm 'pid'
phy0 Failed to initialize wep -2
phy0 -> rt2x00lib_probe_dev Error - Failed to initialize hw.
rt2500pci probe of 0000000e.0 failed with error -2
[/quote28z9c5z6]

Seems that 2.6.27 is a step backwards. Anyone else had success with 2.6.27?

IvD

11-10-2008 08:14:33

Use the search button to find the exact modules which must be loaded before mac80211/rt2x00/.

cherry314159

11-10-2008 11:16:47

I searched the forum and checked out the wiki README but I'm unable to find the list of required modules. Looks like it fails to find some crypto module. These are loaded before the wireless modules. I'm using a similar configuration that I used in 2.6.26.5 that worked. Here's the output of lsmod

[quote1afp0v0h]
root@OpenWrt/# lsmod
Module Size Used by Not tainted
spi_gpio 2144 0
spi_bitbang 2496 1 spi_gpio
spi_ks8995 2176 0
nf_nat_tftp 448 0
nf_conntrack_tftp 2440 1 nf_nat_tftp
nf_nat_irc 768 0
nf_conntrack_irc 2644 1 nf_nat_irc
nf_nat_ftp 1184 0
nf_conntrack_ftp 4512 1 nf_nat_ftp
ipt_MASQUERADE 1024 2
iptable_nat 2376 1
nf_nat 8918 5 nf_nat_tftp,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,iptable_nat
xt_state 800 6
nf_conntrack_ipv4 7212 9 iptable_nat,nf_nat
nf_conntrack 32860 11 nf_nat_tftp,nf_conntrack_tftp,nf_nat_irc,nf_conntrack_irc,nf_nat_ftp,nf_conntrack_ftp,ipt_MASQUERADE,iptable_nat,nf_nat,xt_state,nf_conntrack_ipv4
ipt_REJECT 1504 2
xt_TCPMSS 1792 1
ipt_LOG 3904 0
xt_multiport 1856 0
xt_mac 672 0
xt_limit 960 1
iptable_mangle 1120 0
iptable_filter 928 1
ip_tables 7216 3 iptable_nat,iptable_mangle,iptable_filter
xt_tcpudp 1760 3
x_tables 6724 11 ipt_MASQUERADE,iptable_nat,xt_state,ipt_REJECT,xt_TCPMSS,ipt_LOG,xt_multiport,xt_mac,xt_limit,ip_tables,xt_tcpudp
sit 7044 0
tunnel4 1416 1 sit
tun 6852 0
ppp_async 5632 0
ppp_generic 12596 1 ppp_async
slhc 3776 1 ppp_generic
crc_ccitt 960 1 ppp_async
rt2500pci 12832 0
rt2x00pci 2624 1 rt2500pci
rt2x00lib 15136 2 rt2500pci,rt2x00pci
mac80211 100810 2 rt2x00pci,rt2x00lib
cfg80211 16904 2 rt2x00lib,mac80211
ipv6 183684 22 sit
eeprom_93cx6 1024 1 rt2500pci
crc_itu_t 960 0
ixp4xx_crypto 10604 0
des_generic 16288 1 ixp4xx_crypto
authenc 3136 0
arc4 800 0
aes_generic 32680 0
aead 3232 2 ixp4xx_crypto,authenc
deflate 1184 0
ecb 1184 0
cbc 1728 0
crypto_blkcipher 9380 4 ixp4xx_crypto,authenc,ecb,cbc
crypto_hash 2368 1 authenc
crypto_algapi 6816 10 ixp4xx_crypto,des_generic,authenc,arc4,aes_generic,aead,deflate,ecb,cbc,crypto_blkcipher
root@OpenWrt/#
[/quote1afp0v0h]

a-slack

11-10-2008 17:31:58

The relevant messages from dmesg

[quote35j7y7ux]
cfg80211 Calling CRDA to update world regulatory domain
PCI enabling device 0000000e.0 (0140 -> 0142)
phy0 Selected rate control algorithm 'pid'
phy0 Failed to initialize wep -2
phy0 -> rt2x00lib_probe_dev Error - Failed to initialize hw.
rt2500pci probe of 0000000e.0 failed with error -2
[/quote35j7y7ux]

Seems that 2.6.27 is a step backwards. Anyone else had success with 2.6.27?[/quote35j7y7ux]
I think you are playing with compat-wireless modules because that regulatory domain message only appears in rt2x00 git, wireless-testing git or compat-wireless.

I have a rt2500pci working on kernel 2.6.27 and works well.
[code35j7y7ux]# uname -a
Linux picapiedra 2.6.27-1-586 #1 Fri Oct 10 21:12:20 CEST 2008 i586 GNU/Linux


# lspci | grep -i net
00:0a.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)


# lsmod
aes_i586 7424 2
aes_generic 28552 1 aes_i586
arc4 1568 2
ecb 2432 2
crypto_blkcipher 14404 1 ecb
cryptomgr 2432 0
rt2500pci 15104 0
rt2x00pci 5888 1 rt2500pci
rt2x00lib 28576 2 rt2500pci,rt2x00pci
led_class 3268 1 rt2x00lib
eeprom_93cx6 1696 1 rt2500pci
mac80211 190740 2 rt2x00pci,rt2x00lib
cfg80211 22152 2 rt2x00lib,mac80211
...


# modinfo rt2500pci
filename: /lib/modules/2.6.27-1-586/kernel/drivers/net/wireless/rt2x00/rt2500pci.ko
license: GPL
description: Ralink RT2500 PCI & PCMCIA Wireless LAN driver.
version: 2.1.8
author: http://rt2x00.serialmonkey.com
srcversion: 8A2D79D2F9BCB71EE9923B1
alias: pci:v00001814d00000201sv*sd*bc*sc*i*
depends: rt2x00lib,rt2x00pci,eeprom_93cx6
vermagic: 2.6.27-1-586 mod_unload 586MMX


# iwconfig
lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"WLAN"
Mode:Managed Frequency:2.422 GHz Access Point: 00:13:F7:XX:XX:XX
Bit Rate=54 Mb/s Tx-Power=18 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:5295-8050-E407-1419-ABE4-9D7D-CDAC-B7F4 [3] Security mode:open
Power Management:off
Link Quality=75/100 Signal level:-66 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 00:80:5a:XX:XX:XX
inet addr:192.168.100.3 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9487 errors:0 dropped:0 overruns:0 frame:0
TX packets:6270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10372745 (9.8 MiB) TX bytes:750380 (732.7 KiB)

wmaster0 Link encap:UNSPEC HWaddr 00-80-5A-XX-XX-XX-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)[/code35j7y7ux]

cherry314159

11-10-2008 19:40:44


...
I think you are playing with compat-wireless modules because that regulatory domain message only appears in rt2x00 git, wireless-testing git or compat-wireless.
...
[/quote30gcexxz]

You are right that what I've copy-pasted was from compat-wireless. I've tried first the stock 2.6.27 and then the compat-wireless; both failed to initialized. Seems that the crypto modules aren't loaded correctly. I'll investigate some more. It's very encouraging to know that someone does have it working.

AdamBaker

11-10-2008 22:18:12

There have been a few posts suggesting that some of the crypto modules need to be in kernel, not loaded as modules in order to work properly. I've not tested it personally and don't know why it would be the case but more than one person has claimed it has fixed things.