Arch Linux

esph

Member

Registered: 2014-03-22

Posts: 1

Wireless card hardware failure or something else?

I've been using Arch quite merrily on my desktop for 1.5 years, but just recently my wireless card failed to work correctly after a reboot.

Here is the output lspci shows for the card:

04:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
	Subsystem: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at f7d00000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-00-4d-1e-fb-2a-02-48
	Kernel driver in use: rt2800pci
	Kernel modules: rt2800pci

Here is the output of netcfg when the card fails to work:

:: home2 up Successfully initialized wpa_supplicant
Could not set interface wlan0 flags (UP): Input/output error
nl80211: Could not set interface 'wlan0' UP
Could not set interface wlan0 flags (UP): Input/output error
WEXT: Could not set interface 'wlan0' UP
wlan0: Failed to initialize driver interface
wpa_supplicant did not start, possible configuration error
[fail]

(ip and ifconfig similarly fail to set the card up)

And here is a relevant section of dmesg output:

[   26.981666] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[   26.989624] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[   28.336325] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[   29.670269] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[   29.670322] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[   31.017556] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[   32.351500] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[   32.351553] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  127.605994] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
[  127.609564] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
[  127.609646] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[  133.882799] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[  133.882829] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[  135.228923] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  136.562879] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  136.564000] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  137.913502] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  139.247449] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  139.248509] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  145.739959] fglrx_pci 0000:01:00.0: irq 47 for MSI/MSI-X
[  145.740550] <6>[fglrx] Firegl kernel thread PID: 480
[  145.740690] <6>[fglrx] Firegl kernel thread PID: 481
[  145.740889] <6>[fglrx] Firegl kernel thread PID: 482
[  145.740970] <6>[fglrx] IRQ 47 Enabled
[  145.750661] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000 
[  145.750663] <6>[fglrx] Reserved FB block: Unshared offset:f878000, size:4000 
[  145.750664] <6>[fglrx] Reserved FB block: Unshared offset:f87c000, size:484000 
[  145.750665] <6>[fglrx] Reserved FB block: Unshared offset:7ffef000, size:11000 
[  173.163088] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  174.497033] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  174.497038] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  327.003969] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
[  327.007543] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 0005 detected
[  327.007618] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[  335.902246] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[  335.902269] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[  337.248728] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  338.582670] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  338.582676] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  339.929962] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  341.263914] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  341.263920] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  621.399725] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  622.733664] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  622.733670] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  624.080967] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  625.414895] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  625.414901] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  703.834386] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  705.168333] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  705.168339] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  712.758502] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  714.092443] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  714.092449] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  739.097308] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  740.431256] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  740.431263] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[  835.981975] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  837.315927] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[  837.315933] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)

(The "rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy" messages appear when I try to use the card with netcfg or ip or whatever.)

If you want to see the earlier bits of my dmesg output, here is a complete log: http://sprunge.us/gWOJ. It's from a different boot, but the error messages at the end are the same.

Anyway, when this first happened, I googled around after the errors in hope of finding someone else with the same problem (not much luck there), and also looked up my wireless card in the wiki. I ended up trying out the rt3090-dkms driver from the AUR as suggested here (and yes, I followed all the directions). The rt3090 driver actually allowed me to set the card up manually, and I could send and receive pings, but if I tried to use the connection for something more interesting like loading a webpage, it caused the whole system to crash.

After a while of messing around with this stuff, I found out that occasionally the card works perfectly fine after a reboot (using the standard rt2800 drivers -- I uninstalled the rt3090 one). I can't find anything that's particularly different from one reboot to the next, but the card seems to work after about 35% of reboots. The irregularity of it all has me wondering if it's a hardware problem. Is there an easy way to know if it's a hardware problem or not? I'm pretty much stuck, so any insights on this issue are greatly appreciated

hal

Member

Registered: 2012-06-13

Posts: 3

Re: Wireless card hardware failure or something else?

I've been having the same problem for about 2 months. Same dmesg output and get the following output trying to pull the card up:

>$ ip link set wlan0 up
RTNETLINK answers: Input/output error

Wasn't able to get the rt3090-dkms package to compile (it is flagged outdated right now) and have resorted to a second usb card for the time being. esph: have you continued to have issues? I haven't found anyone else with this particular issue.

Last edited by hal (2014-09-04 20:19:56)

hal

Member

Registered: 2012-06-13

Posts: 3

Re: Wireless card hardware failure or something else?

Here is some module info.

>$ modinfo rt2800pci
filename:       /lib/modules/3.16.1-1-ARCH/kernel/drivers/net/wireless/rt2x00/rt2800pci.ko.gz
license:        GPL
firmware:       rt2860.bin
description:    Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
version:        2.3.0
author:         http://rt2x00.serialmonkey.com
srcversion:     F8D3E83728CFFB1CC77557E
alias:          pci:v00001814d0000539Fsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Bsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Asv*sd*bc*sc*i*
alias:          pci:v00001814d00005392sv*sd*bc*sc*i*
alias:          pci:v00001814d00005390sv*sd*bc*sc*i*
alias:          pci:v00001814d00005362sv*sd*bc*sc*i*
alias:          pci:v00001814d00005360sv*sd*bc*sc*i*
alias:          pci:v00001814d0000359Fsv*sd*bc*sc*i*
alias:          pci:v00001814d00003593sv*sd*bc*sc*i*
alias:          pci:v00001814d00003592sv*sd*bc*sc*i*
alias:          pci:v00001814d00003562sv*sd*bc*sc*i*
alias:          pci:v00001814d00003062sv*sd*bc*sc*i*
alias:          pci:v00001814d00003060sv*sd*bc*sc*i*
alias:          pci:v00001432d00007722sv*sd*bc*sc*i*
alias:          pci:v00001432d00007711sv*sd*bc*sc*i*
alias:          pci:v00001814d00003390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003290sv*sd*bc*sc*i*
alias:          pci:v00001A3Bd00001059sv*sd*bc*sc*i*
alias:          pci:v00001462d0000891Asv*sd*bc*sc*i*
alias:          pci:v00001432d00007768sv*sd*bc*sc*i*
alias:          pci:v00001432d00007758sv*sd*bc*sc*i*
alias:          pci:v00001432d00007748sv*sd*bc*sc*i*
alias:          pci:v00001432d00007738sv*sd*bc*sc*i*
alias:          pci:v00001432d00007728sv*sd*bc*sc*i*
alias:          pci:v00001432d00007727sv*sd*bc*sc*i*
alias:          pci:v00001432d00007708sv*sd*bc*sc*i*
alias:          pci:v00001814d00003092sv*sd*bc*sc*i*
alias:          pci:v00001814d00003091sv*sd*bc*sc*i*
alias:          pci:v00001814d00003090sv*sd*bc*sc*i*
alias:          pci:v00001814d00000781sv*sd*bc*sc*i*
alias:          pci:v00001814d00000701sv*sd*bc*sc*i*
alias:          pci:v00001814d00000681sv*sd*bc*sc*i*
alias:          pci:v00001814d00000601sv*sd*bc*sc*i*
depends:        rt2x00lib,rt2800lib,rt2800mmio,rt2x00mmio,rt2x00pci,eeprom_93cx6
intree:         Y
vermagic:       3.16.1-1-ARCH SMP preempt mod_unload modversions 
parm:           nohwcrypt:Disable hardware encryption. (bool)

Also possibly relevant: at the same time my wireless card starting giving me issues, my SD card reader module stopped loading. It seems the driver was renamed from rt5139 to rtsx_usb_sdmmc in Linux 3.16. I now have to load it manually on boot. I doubt the problem is directly related, but maybe it is indicative of a general module issue?

>$ lsusb -v
...
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x0129 RTS5129 Card Reader Controller
  bcdDevice           39.60
  iManufacturer           1 Generic
  iProduct                2 USB2.0-CRW
  iSerial                 3 20100201396000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 CARD READER
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      6 
      bInterfaceProtocol     80 
      iInterface              5 Bulk-In, Bulk-Out, Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0003  1x 3 bytes
        bInterval              10
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)
...

Pse

Member

Registered: 2008-03-15

Posts: 413

Re: Wireless card hardware failure or something else?

Have you tried reseating the card in the PCI slot?

What happens if you temporarily switch to the LTS kernel?

xangelux

Member

Registered: 2010-05-29

Posts: 73

Re: Wireless card hardware failure or something else?

I have the same problem, is there a solution to get this working or to know what is happening

solamour

Member

Registered: 2011-09-14

Posts: 5

Re: Wireless card hardware failure or something else?

I have pretty much the same problem. Oddly, when the system boots from the complete shutdown state, the WiFi works; it stops working (with a similar error message) when I reboot the system. I'd also be interested in a possible solution.
__
sol

keivan

Member

Registered: 2011-07-17

Posts: 3

Re: Wireless card hardware failure or something else?

I have the same problem also. Asus laptop N56J. In addition to above scenarios, enabling laptop-mode-tools also produces the same dmesg log and failure.

nomorewindows

Member

Registered: 2010-04-03

Posts: 3,370

Re: Wireless card hardware failure or something else?

Has wlan0 become something like wlp???

---

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

betseg

Member

From: Turkey

Registered: 2015-04-25

Posts: 182

Re: Wireless card hardware failure or something else?

I have the same problem.

sesese9

Member

From: California, United States

Registered: 2015-04-01

Posts: 75

Website

Re: Wireless card hardware failure or something else?

I have the same problem.

Please no zombie threads... Make a new thread for your problem because this topic is 3.16 and not 4.x
Thx!

---

Just trying to figure things out in this world

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,804

Re: Wireless card hardware failure or something else?

A year and a half later and the OP has only one post.   I am going to close this thread.  If someone needs to pick this topic up, feel free to start a new thread and, if appropriate, link back to this one.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way