rt2500 on Debian: no interface ra0 created

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


13-01-2009 00:43:08


I hope my problem is not resolved in an other topic. I did not found any and I am sorry if there is actually one s

So, I have got a MSI CB54G2 pcmcia card. Two years ago I had installed your great drivers without any problem (rt2500-1.1.0-b4).
This week end, I intended to perform the operation again (my kernel was then I started the same way than two years ago to compile the driver myself (rt2500-CVS) and then use [i2b4zgg0l]modprobe rt2500[/i2b4zgg0l]. But no wireless interface was created...
I continued my searches and I figured out that a Debian installation is available. So I used it but still no new network interface /

Finally, I learned that your driver is now part of the Linux kernel (congratulations!). So I decided to get the latest kernel (2.6.28) and try this way. But still impossible to get the ra0 interface... (or wlan0 or any wireless interface)

Here are the logs which appear when I insert my card in my laptop
[code2b4zgg0l]pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
rt2500pci 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
rt2500pci 0000:02:00.0: setting latency timer to 64
rt2x00pci -> rt2x00pci_alloc_reg: Error - Failed to allocate registers.
rt2500pci 0000:02:00.0: PCI INT A disabled
rt2500pci: probe of 0000:02:00.0 failed with error -12[/code2b4zgg0l]
(lspci shows my card [i2b4zgg0l]0200.0 Network controller RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)[/i2b4zgg0l])

The loaded modules are the following
[code2b4zgg0l]sthocs@freestyler:~$ lsmod
Module Size Used by
rt2500pci 14976 0
rt2x00pci 7552 1 rt2500pci
rt2x00lib 24576 2 rt2500pci,rt2x00pci
rfkill 10444 1 rt2x00lib
mac80211 131212 2 rt2x00pci,rt2x00lib
cfg80211 30224 2 rt2x00lib,mac80211
eeprom_93cx6 2176 1 rt2500pci[/code2b4zgg0l]
And here is my kernel configuration for rt2x00
# CONFIG_RT2400PCI is not set
# CONFIG_RT61PCI is not set
# CONFIG_RT2500USB is not set
# CONFIG_RT73USB is not set
I saw that some crypto modules are required but I don't think this is the problem here (however I have HW crypto and others compiled).

So that's it, I don't know why the interface is not created and I hope someone can help me. (

Thank you!


13-01-2009 07:43:41

The error returned in the log is quite serious, but not a driver problem. For some reason it cannot map the memory from the rt2500 device. Does this device work under windows, or on another machine?


13-01-2009 12:02:50

Does this device work under windows, or on another machine?[/quote3u45voth]
Hmm, you pointed the problem. I am afraid my computer starts to be old ?

Indeed, I've continued to perform some tests after my post, and under windows I get a Code 12 error
[quote3u45voth]This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system. (Code 12)[/quote3u45voth]

Under Linux I've lot of [i3u45voth]hdc lost interrupt[/i3u45voth] which appear in the logs during my session.
Also, an error occurs with [i3u45voth]cardmgr[/i3u45voth] during the boot. I've don't have the logs here, I will post it when I get home.

Since it's apparently not a driver problem, I know that you have no concern with my problem, however, do you have an idea of what is the problem ?
I will do some test with my cdrom device tonight.

Thanks for your answer.


13-01-2009 12:51:18

Well these issues are triggered by hardware problems, especially since Windows has similar issues it means it is OS independent.
You could try the card on another computer to see how it reacts there, if it worked on the other machine the cause is most likely the motherboard, if it is displaying the same issue on the other computer it is most likely the card itself.