[Maverick][2.6.35] RT2860 (ralink) broken with rt2800pci

I forget to say that it worked fine before (<= 2.6.31).

And also I don't know if it's related but now if I shutdown (not reboot) the computer and restart it later, it seems that this wireless card is disabled and I can't enable it with:
  $ sudo ifconfig wlan0 up
The output says that the device is busy. This is what I've from 'dmesg'
   [ 43.762591] phy0 -> rt2800pci_load_firmware: Error - PBF system register not ready.
   [ 43.763112] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xbdfcfb7b

I can't enable it at startup because the related option on the BIOS setup has only two possibilities: "Disabled" and the "same status just before the shutdown".

Hi Matthieu,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I confirm, it doesn't work with the latest daily build.
Firstly, I can't enable the WiFi card:
  [ 124.570044] phy1 -> rt2800pci_load_firmware: Error - PBF system register not ready.
  [ 124.570565] phy1 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xbdfcfb7b
  [ 128.642576] phy1 -> rt2800pci_load_firmware: Error - PBF system register not ready.
  [ 128.643099] phy1 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xbdfcfb7b
  [ 135.403250] phy1 -> rt2800pci_load_firmware: Error - PBF system register not ready.
  [ 135.403773] phy1 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xbdfcfb7b

  $ LANG=C && sudo ifconfig wlan0 up
    SIOCSIFFLAGS: Device or resource busy

Secondly, after having rebooted and enable the WiFi card from another OS (really annoying ^^), I can't connect to a secured wireless network. I join the output of 'dmesg'

Hello,

Just to say that I have the same problem with the version 2.6.35-7: this version of the kernel can't enable my Ralink wireless card and after having enable it with an older version and reboot the computer, it fails to connect to secured wireless networks:
    [ 118.573082] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
    [ 118.573608] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
    [ 118.574124] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
    [ 118.594600] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
    [ 118.686301] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 122.462568] wlan0: direct probe to 00:14:c1:1f:db:08 (try 1)
    [ 122.662584] wlan0: direct probe to 00:14:c1:1f:db:08 (try 2)
    [ 122.862564] wlan0: direct probe to 00:14:c1:1f:db:08 (try 3)
    [ 123.062635] wlan0: direct probe to 00:14:c1:1f:db:08 timed out

After having compiled the latest version of Ralink drivers (version 2.3.0.0 => http://eng.ralinktech.com.tw/support.php?s=2 ) I still have the problem.
I join the output of 'dmesg'.

Thank you for your help!

Hello,

I confirm that this problem is not fixed with the version 2.6.35-10. So I'm no longer able to enable my Ralink Wireless card if it's not activated at startup. And after having enabled it from an older kernel version and reboot the computer, it fails to connect to secured wireless networks.
I've added the dmesg output.

Thank you

Hello,

I still have the same problem with the latest linux version (available on Maverick repositories)

After having mounted my Ralink Wireless card from another kernel, this is what I have (it still the same I think)
   [ 103.143058] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
   [ 103.143669] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
   [ 103.144187] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
   [ 103.164735] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
   [ 103.273048] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
   [ 103.274290] ADDRCONF(NETDEV_UP): wlan0: link is not ready

It seems that this bug affects 6 other people but I don't know if their errors are exactly the same.

But before it worked! :) ... So... it's just a regression ;)

Thank you

Maybe it can help you:
 # lspci -vv
 0a:00.0 Network controller: RaLink RT2860
 Subsystem: RaLink Device 2790
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=64K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
   ClockPM- Surprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
 Kernel driver in use: rt2800pci
 Kernel modules: rt2860sta, rt2800pci

And after having powered off the computer:
 $ LANG=C && sudo ifconfig wlan0 up
  SIOCSIFFLAGS: Device or resource busy
 # lspci -vv
  0a:00.0 Network controller: RaLink RT2860
 Subsystem: RaLink Device 2790
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=64K]
 Capabilities: <access denied>
 Kernel driver in use: rt2800pci
 Kernel modules: rt2860sta, rt2800pci

Just to note that there is a new version of Ralink drivers on their website (v. 2.4.0.0) => http://eng.ralinktech.com.tw/support.php?s=2

But I don't know if it can help... This is the release note:
 [2.4.0.0]
  1. Fix Adhoc issue.
  2. Fix issue: Correct RSSI, SNR, Noise calculation
  3. Fix issue: STA cannot connect to OPEN-WEP AP if WpaSupplicant set
  4. Add an ATE command for AUTOALC.
  5. Add an ATE command for interpacket GAP.
  6. Add an ATE command for ATE payload pattern.

PS: the tarball with the new version of Ralink drivers is in fact a tar.gz and not a tar.bz2...

After reading your last comment I tried the 2.4.0.0 driver you mention. It works well as a client in an ad hoc WEP network while the stock maverick rt2860sta always fails. (Both fail as clients in an ad hoc WPA network, but that has never ever worked.)
I have not yet tried infrastructure mode, where the stock rt2860sta has worked well.

PS: thanks for the heads up about this stupid tar.bz2 thing

I tried something more in the KISS idea today: download the daily-live amd64 and did this:

ifconfig wlan0 down
lsmod | grep rt
rmmod rt2800pci
rmmod rt2860sta
rmmod rt2800lib
rmmod rt2x00usb
rmmod rt2x00pci
rmmod rt2x00lib
modprobe rt2860sta
ifconfig wlan0 up

and then I could connect to my WPA protected wireless network, still in the live image. Will try the installed system later.

adding:

blacklist rt2800pci
blacklist rt2800lib
blacklist rt2x00usb
blacklist rt2x00pci
blacklist rt2x00lib

to /etc/modprobe.d/blacklist.conf, than reboot. This works for me.

@Bruno: Many thanks for this **Workaround**
It works for me too.

I hope that a final solution will be found before Maverick release :)

Workaround did not work for me. But I kept the blacklisted modules
blacklisted. After the kernel upgrade to 2.6.35-21-generic the ndiswrapper
solution seems to work again.

Regards,
Charles

2010/9/15 Matthieu Baerts <email address hidden>

> @Bruno: Many thanks for this **Workaround**
> It works for me too.
>
> I hope that a final solution will be found before Maverick release :)
>
> --
> [Maverick][2.6.35] RT2860 (ralink) support seems to be broken (it fails to
> connect to secured wireless networks)
> https://bugs.launchpad.net/bugs/594866
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Hello,
>
> With the new kernel release available on Ubuntu Maverick (2.6.35-x) I'm not
> able to be connected to a secured wireless network. I already had this kind
> of bug on Lucid (bug #496093) but the connexion worked after two or three
> time and I had the problem only with one router.
>
> Don't hesitate to tell me something to do if it's needed ;)
>
> Thank you!
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-2.6.35-3-generic 2.6.35-3.4
> Regression: Yes
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.35-3.4-generic 2.6.35-rc3
> Uname: Linux 2.6.35-3-generic x86_64
> NonfreeKernelModules: nvidia
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: mbaerts 2774 F.... pulseaudio
> CRDA:
> country DE:
> (2400 - 2483 @ 40), (N/A, 20)
> (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
> (5470 - 5725 @ 40), (N/A, 26), NO-OUTDOOR, DFS
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xfa200000 irq 48'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,17c02026,00100001'
> Controls : 36
> Simple ctrls : 21
> Date: Tue Jun 15 23:46:41 2010
> HibernationDevice: RESUME=UUID=feb4bf5c-a5b0-417a-b9c6-26fe24c479e7
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> MachineType: MEDION WIM2180
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-3-generic
> root=UUID=c11e30c7-48fb-4c4e-8f3e-0c506b8c9885 ro quiet
> ProcEnviron:
> LANG=fr_BE.utf8
> SHELL=/bin/bash
> RelatedPackageVersions: linux-firmware 1.36
> SourcePackage: linux
> StagingDrivers: rt2860sta
> Title: [STAGING]
> dmi.bios.date: 12/18/2009
> dmi.bios.vendor: Phoenix Technologies LTD
> dmi.bios.version: V1.0K
> dmi.board.name: WIM2180
> dmi.board.vendor: MEDION
> dmi.board.version: Not Applicable
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: MEDION
> dmi.chassis.version: A2040
> dmi.modalias:
> dmi:bvnPhoenixTechnologiesLTD:bvrV1.0K:bd12/18/2009:svnMEDION:pnWIM2180:pvr20:rvnMEDION:rnWIM2180:rvrNotApplicable:cvnMEDION:ct10:cvrA2040:
> dmi.product.name: WIM2180
> dmi.product.version: 20
> dmi.sys.vendor: MEDION
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/594866/+subscribe
>

I can confirm problems with RT2860 in the 2.6.35-21-generic too.

I've had problem like it ever since Ubuntu 10.04 related to the kernel. (Bug filed)
I have been running on a RC kernel which seemed to fix any problems.
Previously I had problems connecting to WPA2 Personal and possibly others too.
With 2.6.35-21-generic WPA2 Personal seems to work however.
But nevertheless problems resurface when I try to connect to WPA2 Enterprise with TTLS+PAP. (The global EDUROAM network here)

I'm able to connect to the network but the connection is spotty at best.
When the connection is not falling out, I'm simply not able to communicate on it - no DNS or data.
If I'm really lucky I manage punching a hole through just long enough to load a webpage, but then loose the data connection again.

I'm running on a standard EEE PC 1000H.

I just booted in 2.6.32-25-generic and see instant improvement.
None of the problem seen in 2.6.35-21-generic or 2.6.35-20-generic are present.

I did however notice the following error while booting 2.6.35-21-generic:

[ 35.357754] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware

Could the problem be that the kernel for some reason fails to recognise the hardware correctly and loads the wrong driver ?

Anyways, an easy work-around (as I used in Lucid too) seems simply to download another kernel and run off of that.
As mentioned I'm successfully using http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.32-25-generic_2.6.32-25.43_i386.deb

@Bruno #14 -- thanks for that, works like a charm on my MSI U230 (Ralink RT3090) running Maverick and kernels 2.6.35-22-generic and 2.6.35-19-generic.

-19 throws a load of "PBF system register not ready" errors in dmesg, -22 doesn't seem to do that but won't associate with the access point. After rebooting from -22 (with the default modules loaded), the BIOS reports a HyperTransport Sync Flood error. Blacklist the modules and it works great.

@Bruno #14 -- That workaround works for me. I'm running the Maverick beta with kernel 2.6.35-22-generic on an MSI GT 735 with an RT2860. Before the fix I was unable to connect to my WPA2 network.

I've installed the ubuntu 10.10 final release, and I can confirm that this bug still happening.
The Bruno's solution help me to get on line using my wireless / wpa,
however this workaround sometimes crash my network interface.

uname -a
Linux HP-TouchSmart 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux

lshw -C network
  *-network
       description: Wireless interface
       product: RT2860
       vendor: RaLink
       physical id: 0
       bus info: pci@0000:05:00.0
       logical name: wlan0
       version: 00
       serial: 00:22:5f:7f:2d:a8
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rt2860 ip=192.168.1.2 latency=0 multicast=yes wireless=Ralink STA
       resources: irq:16 memory:f9ff0000-f9ffffff

Thanks Bruno (#14). This worked for me with 10.10 on an Eeepc 1001HA. Everything had worked well with Lucid UNE but on installing Maverick I had limited network connectivity and couldn't shutdown, hibernate or suspend without freezing. Any attempts to disable networking also caused the machine to freeze. Blacklisting the various modules as per your post has got wireless working and I'm able to shutdown gracefully.

I can confirm this bug for Maverick on eeepc 1000H. Workaround from Bruno (#14, thanks!) works perfectly.

Unfortunately Bruno's fix did not work for me. I have an MSI CR700 laptop. I played around with blacklisting and un-blacklisting the modules Bruno mentioned but it seems my system requires rt2800pci. If I blacklist rt2800pci then the system shuts down properly but I cannot connect to a WPA2 wireless router, if I blacklist the others and leave rt2800pci enabled I can connect but not shut down.

Any ideas why this would be?

Chris, may I suggest you file a new report for your shut down issue. It is a symptom that was not reported by the original reporter and we should anyway really try to start separating the many interesting ways those drivers fail.

Wolfgang, I would be happy to submit a new report but I wouldn't know where to start and as I'm not very technically minded I don't know if I'd be able to help much in solving the problem. I can follow instructions but wouldn't know where to start resolving an error such as this.

Just open a terminal (Applications>Accessories>Terminal) and type ubuntu-bug linux . It should do all the rest. It will collect relevant information. You do not have to do anything else.

Wolfgang, I have submitted the new bug as you requested, hopefully I have done it correctly. Some of the questions Ubuntu threw up weren't exactly easy to understand for a newbie like me so I took my best guess. Hopefully this will be of help to others as well.

It can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/662288

I did a few tests on a WPA2 router:

Results:
2.6.36rc8 64bit self-compiled ralink: works (this is the only driver that can also do ad hoc mode with good speed)

64 bit live:
rt2800pci: wlan unavailable (syslog shows an error loading firmware ...PBF)
rt2860sta works; connects immediately (nominal 54 Mb/s)

32 bit live:
rt2800pci: works fine (nominal 54 Mb/s; really seen: 800kiB/s)
rt2860sta works fine; same speed (nominal and real);

Notes:
on maverick rt2800pci is the default module for this hardware; rt2860 is available and can be used instead (via modprobe);
(all systems maverick; all live systems final maverick; rt2860sta stock maverick unless mentioned otherwise; wlan hardware: rt2860 on an Acer Extensa 5630Z)

Wolfgang: for you it doesn't work in 64bit mode, but for me it doesn't in 32bit as well, so please change the title back...

Frank, could you please verify that it is a RaLink RT2860 [1814:0781] (output of lspci -vvnn) that fails (with the rt2800pci) for you on 32 bit. A different hardware than the original report could be the reason you have different symptoms.

If it is a different hardware, would you please file a separate bug report for this. If it is the same hardware we should investigate further to find what causes the different symptoms.

Best regards

I have the same problem.

[ 10.934914] rt2800pci 0000:04:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 11.035987] phy0: Selected rate control algorithm 'minstrel'
[ 11.036475] Registered led device: rt2800pci-phy0::radio
[ 11.036488] Registered led device: rt2800pci-phy0::assoc
[ 11.036501] Registered led device: rt2800pci-phy0::quality

[ 11.932183] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 11.990860] ADDRCONF(NETDEV_UP): wlan0: link is not ready

My card is d-link dwa 525 and has ralink RT2860 chip.

lspci -vv

04:06.0 Network controller: RaLink Device 3060
 Subsystem: D-Link System Inc Device 3c04
 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: 32 (500ns min, 1000ns max), Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 21
 Region 0: Memory at fb100000 (32-bit, non-prefetchable) [size=64K]
 Capabilities: [40] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: rt2800pci
 Kernel modules: rt2800pci

Simão, your problem looks quite a bit different:

>04:06.0 Network controller: RaLink Device 3060
...
>Kernel modules: rt2800pci

in contrast to my hardware:
lspci -k|grep -i --after-context=3 network
03:00.0 Network controller: RaLink RT2860
 Subsystem: Foxconn International, Inc. Device e002
 Kernel driver in use: rt2860
 Kernel modules: rt2860sta, rt2800pci

Which means the rt2860sta does not offer itself for your RaLink Device 3060. Which means the standard workaround (switching to the rt2860sta module) most people here are using will not work for you.

>Error - MCU request failed, no response from hardware
Afair I have seen that one in my syslog when rt2800pci worked, so I think that error is no show stopper.

Also I do not see:
"Error - PBF system register not ready."
which seems to be the core of this bug here.

I think it would be best if you made a new bug report (with "ubuntu-bug linux") after a fresh cold start and connection attempt. Maybe someone can then see from your logs where this fails for you.

Bruno thanks for your workaround! Now my Compaq/HP netbook (CQ10-400CA ) will actually shutdown/reboot - plus it now connects with wpa2 at 54mbps... still won't connect with "n" but this is much better than the 1-2Mbps it was getting before even while showing 100% signal strength!

lspci -vv shows:

02:00.0 Network controller: RaLink RT3090 Wireless 802.11n 1T/1R PCIe
    Subsystem: RaLink RT3090 Wireless 802.11n 1T/1R PCIe
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 17
    Region 0: Memory at 52000000 (32-bit, non-prefetchable) [size=64K]
    Capabilities: <access denied>
    Kernel driver in use: rt2860
    Kernel modules: rt2860sta, rt2800pci

Just tried to improve the bug report a bit by adding the workaround (thanks to Bruno Lambert) in the description. I made a hopefully user friendly howto (as a launchpad question). It might be a good idea if someone checked it for errors.

The description now says "Sometimes the new rt2800pci does not work as well as the rt2860sta."

Agreed, but isn't "does not work as well" understating the situation? rt2800pci is marked experimental.

See line 66 and following on the Kconfig for the driver:

http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=blob;f=drivers/net/wireless/rt2x00/Kconfig;h=eea1ef2f502bd3c926599b2308901277e35250ef;hb=d75c265c3e4edf33049e0b70ff2de6830308d94e

In the 'config RT2800PCI" stanza, it says, 'This driver is non-functional at the moment and is intended for developers. When compiled as a module, this driver will be called "rt2800pci.ko".'

(If I'm operating git correctly, that link refers to a tag of the 2.6.35 kernel release.)

Point is, perhaps the solution is to simply turn off this config option when configuring the kernel.

Lol, yes I saw those dire warnings too. They seem on the other hand to be overstating the situation a bit. It functions well for some hardware. I write this here on lucid with a 2.6.33 kernel and compat-wireless-2.6.36-rc5-2-s. It works very well so far. Others have had mixed experiences - like working well but freezing on shutdown (bug #662288). For others it has not worked at all, like for me with maverick 64 bit (bug #659143).
What the developers need is good bug reports from everyone. One bug report per person (or computer). With ubuntu-bug linux, so that relevant information is documented. If possible, after the bug happens. Those bugs are often very hardware specific. They will have to fix those one by one.

See also:
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs

Hello,

I still have a bug with my ralink wireless card but now on Ubuntu Natty 11.04 with a new kernel (2.6.37-2). The workaround no longer works :-/
Please can you confirm this bug #673440 ?

@Logan
The indications of non-functional support have been removed for this driver:
http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=commit;h=9fd847137d116558bdd404da2f5bd3f20adce4e1

So it is officially supposed to work now. :-)

Hi Matthieu,
I have been able to git bisect and patch this "PBF system register not ready." bug.

More info in comment 16 of bug 659143.

I have a Sony Vaio VPCM11M1E and was having problems with Maverick hanging on shutdown.
I had to power off to reboot.

Then the link above on how to blacklist the PCI drive in favour of the STA driver fixed the problem.
I'll try re-enabling when a new kernel update comes through.

IMHO the best solution right now for natty is to switch back to rt2860sta for this card by default, until rt2800pci is tested and confirmed to work at least as well, for both the 64-bit and 32-bit cases.

Something like this patch:

Index: mainline/drivers/net/wireless/rt2x00/rt2800pci.c
===================================================================
--- mainline.orig/drivers/net/wireless/rt2x00/rt2800pci.c
2011-05-03 14:54:48.168173002 +0300
+++ mainline/drivers/net/wireless/rt2x00/rt2800pci.c 2011-05-03
14:54:57.378172995 +0300
@@ -1108,7 +1108,6 @@
       { PCI_DEVICE(0x1814, 0x0601), PCI_DEVICE_DATA(&rt2800pci_ops) },
       { PCI_DEVICE(0x1814, 0x0681), PCI_DEVICE_DATA(&rt2800pci_ops) },
       { PCI_DEVICE(0x1814, 0x0701), PCI_DEVICE_DATA(&rt2800pci_ops) },
- { PCI_DEVICE(0x1814, 0x0781), PCI_DEVICE_DATA(&rt2800pci_ops) },
       { PCI_DEVICE(0x1814, 0x3090), PCI_DEVICE_DATA(&rt2800pci_ops) },
       { PCI_DEVICE(0x1814, 0x3091), PCI_DEVICE_DATA(&rt2800pci_ops) },
       { PCI_DEVICE(0x1814, 0x3092), PCI_DEVICE_DATA(&rt2800pci_ops) },