BBPCSR register busy -- rt2x00 not working, Windows ok

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

bugfood

04-03-2009 19:11:16

Hello,

I am having a problem with my rt2500 mini-PCI card. I haven't had occasion to use wireless in about a year, and I can't get it to work any more. I used to use the closed-source rt2500 drivers, but I had tested the rt2x00 drivers not long after they entered the main kernel source, and I remember they worked before (though not as well, at the time).

Right now I can't get any of the Linux drivers to work. I have an installation of Windows 2000 on the same machine, though, and the RaLink drivers I installed appear to work fine. Based on that, I don't think this is a hardware problem, but I can't be sure.

I still have an old 2.6.23 and 2.6.24 kernel installed, from about that time; when I load the closed-source driver, the interface ends up with a MAC address of FFFFFFFFFFFF and ifconfig can't bring up the interface. The same thing happens when I compile the drivers from rt2500-cvs-2009022820 on my current 2.6.28 kernel.

I'd like to use the open-source drivers and forget about the closed-source ones, but I wanted to mention all I have tried at this point in case it's pertinent.

As for the rt2x00 drivers, here's a detailed account of what is happening.

The rt2500pci driver appears to load ok
-------------------------------------------------------------------
rt2500pci 0000020a.0 enabling device (0000 -> 0002)
ACPI PCI Interrupt Link [LNKH] enabled at IRQ 10
rt2500pci 0000020a.0 PCI INT A -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
phy0 Selected rate control algorithm 'pid'
-------------------------------------------------------------------

The wlan0 and wmaster0 interfaces look ok
-------------------------------------------------------------------
wlan0 Link encapEthernet HWaddr fe0196d5bde6
BROADCAST MULTICAST MTU1500 Metric1
RX packets0 errors0 dropped0 overruns0 frame0
TX packets0 errors0 dropped0 overruns0 carrier0
collisions0 txqueuelen1000
RX bytes0 (0.0 B) TX bytes0 (0.0 B)

wmaster0 Link encapUNSPEC HWaddr FE-01-96-D5-BD-E6-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU0 Metric1
RX packets0 errors0 dropped0 overruns0 frame0
TX packets0 errors0 dropped0 overruns0 carrier0
collisions0 txqueuelen1000
RX bytes0 (0.0 B) TX bytes0 (0.0 B)
-------------------------------------------------------------------

Iwconfig finds wireless extensions
-------------------------------------------------------------------
wlan0 IEEE 802.11bg ESSID""
ModeManaged Frequency2.412 GHz Access Point Not-Associated
Tx-Power=0 dBm
Retry min limit7 RTS throff Fragment thr=2352 B
Encryption keyoff
Power Managementoff
Link Quality0 Signal level0 Noise level0
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0
-------------------------------------------------------------------

I can put the interface into monitor mode, and it looks ok, except that dmesg outputs lots of errors like this (full log attached)
-------------------------------------------------------------------
phy0 -> rt2500pci_bbp_read Error - BBPCSR register busy. Read failed.
phy0 -> rt2500pci_bbp_write Error - BBPCSR register busy. Write failed.
phy0 -> rt2500pci_bbp_write Error - BBPCSR register busy. Write failed.
phy0 -> rt2500pci_bbp_write Error - BBPCSR register busy. Write failed.
-------------------------------------------------------------------

When I run kismet or airodump-ng to try to find local base stations, neither program can find any and I get lots more messages like that from dmesg.

The hardware is an MSI RT2500 mini-PCI card, with PCI ID 18140201. Here's the full lspci information
-------------------------------------------------------------------
020a.0 Network controller RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
Subsystem Micro-Star International Co., Ltd. Unknown 802.11g mini-PCI Adapter
Control I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency 64, Cache Line Size 128 bytes
Interrupt pin A routed to IRQ 10
Region 0 Memory at fce04000 (32-bit, non-prefetchable)
Capabilities [40] Power Management version 7
Flags PMEClk+ DSI+ D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status D3 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use rt2500pci
Kernel modules rt2500pci
-------------------------------------------------------------------

I'm running Debian Sid on a 2.6.28 kernel. I also tested 2.6.26 and rt2x00 a git kernel from yesterday. The git kernel had slightly different problems, but I don't want to clutter up this report with what might be unrelated information. I'd be happy to provide that information if you request, though. I'll have Internet access about once a day.


Thanks,
Corey

IvD

04-03-2009 19:21:20

Could you enable debugfs and use the script http//kernel.org/pub/linux/kernel/peop ... regdump.sh
to make a dump of all registers?

Please note that CONFIG_DEBUGFS, CONFIG_MAC80211_DEBUGFS and CONFIG_RT2X00LIB_DEBUGFS must be enabled.
After that debugfs must be mounted (i.e. mount -t debugfs debugfs /sys/kernel/debug)

Thanks.

bugfood

05-03-2009 18:13:53

Sure. Sorry I didn't see the sticky, or I would have sent a dump already. I'll work on that today and send it in when I get Internet access tomorrow.

Thanks for your help.

bugfood

06-03-2009 18:24:22

Ok, here's the register dump on 2.6.28.7. This is from a cold boot and before putting the interface into monitor mode. The registers remain the same for

- going to monitor mode
- bringing the interface up

When I start scanning for access points with airodump-ng, the dev_flags change from 0x00000a03 to 0x00000a2f. I'm going to attach a diff.

Thanks again.

bugfood

08-03-2009 17:58:48

Have you had a chance to look at this? I don't mean to be pushy, but it would be nice to know if I need to order a new card or if this can be resolved.

Thanks.

IvD

08-03-2009 18:02:54

No sorry, I have very limited time to work on the drivers lately. So don't expect a lot of progress. (

bugfood

09-03-2009 02:30:04

That's all right; I understand how it is...

Thanks for your help if/when you have a chance.