Arch Linux

vexxor

Member

Registered: 2008-07-17

Posts: 45

[SOLVED] rt2800pci and new kernels

Hello,

Recently after a kernel upgrade I was greeted with strange problems when starting my system. I use KDM and it would let me type in my password and the it would seemingly freeze. When I switched to the console as I thought it was a KDM problem at the time, other commands like ping or even sudo would also freeze up the current shell.

I looked around and found output similar to this from dmesg (this is the output I got today while testing the most recent kernel):

phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
ADDRCONF(NETDEV_UP): wlan0: link is not ready
r8169 0000:05:04.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
ADDRCONF(NETDEV_UP): wlan0: link is not ready
r8169 0000:05:04.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0x05100000
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
ADDRCONF(NETDEV_UP): wlan0: link is not ready

After disabling wireless and hooking up with a cable, everything seemed to be OK. I tried downgrading the kernel (and nvidia as a dependency), and things went back to normal. Currently I'm running: 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 21:22:26 CEST 2010 x86_64. The problem doesn't seem to exist on this build. I have tried the most recent kernel and my PC keeps locking up. I have also looked around on google and the forums here and have not been able to find anything I can make sense of.

Anyone else have this problem? Anyone know any remedies?

Last edited by vexxor (2010-12-13 11:12:19)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [SOLVED] rt2800pci and new kernels

No direct experience with that hardware, but you should be aware that there are two drivers for rt28xx devices, the official ones from the rt2x00 family (rt2800pci in this case) and the staging ones originally provided by Ralink (rt2860sta/rt2870sta depending on the chipset). Udev module autoloading may be loading both drivers, which would then cause conflicts. Blacklisting the one you don't want might help.

vexxor

Member

Registered: 2008-07-17

Posts: 45

Re: [SOLVED] rt2800pci and new kernels

I wasn't using auto loading. But experimenting with my modules array revealed that if I switched to: rt2860sta, everything seems to work OK. Thanks for the information, without it I would still be lost.

Is this something that will be changing again soon, or will I be able to use this module from now on?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [SOLVED] rt2800pci and new kernels

Staging modules are temporary, by definition. They do not conform to required kernel coding standards, but they are there because they provide functionality that has not yet been merged into the corresponding official modules. In due course, the rt2x00 drivers will support everything that the staging drivers do, at which time the staging drivers will become obsolete, and you will change over to rt2800pci.

vexxor

Member

Registered: 2008-07-17

Posts: 45

Re: [SOLVED] rt2800pci and new kernels

OK. Thank you very much for the explanation. Marking as solved.