Ralink RT3290 WiFi Chipset Fails To Come Up (JESSIE)

[Alula]

I'm running a HP Envy 17 laptop with a Ralink RT3290 WiFi card on Debian jessie. I'm using rt2800pci driver as I can't get rt3290sta to compile.

The WiFi card worked (except it wouldn't recover from suspend) until I ran a large aptitude full-upgrade yesterday and rebooted. Now, it doesn't come up at boot and will not come up when I attempt to do bring it up manually.

Kernel version:

Code: Select all

alula@sweetiebelle:~$ uname -ar
Linux sweetiebelle 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux

lshw output:

Code: Select all

  *-network DISABLED      
       description: Wireless interface
       product: RT3290 Wireless 802.11n 1T/1R PCIe
       vendor: Ralink corp.
       physical id: 0
       bus info: pci@0000:07:00.0
       logical name: wlan0
       version: 00
       serial: 9c:d2:1e:42:48:d5
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rt2800pci driverversion=3.13-1-amd64 firmware=0.37 latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
       resources: irq:18 memory:d3610000-d361ffff

lspci output:

Code: Select all

alula@sweetiebelle:~$ lspci -nnk | grep -iA2 net
07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter [103c:18ec]
Kernel driver in use: rt2800pci
--
0f:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Hewlett-Packard Company Device [103c:1968]
Kernel driver in use: r8169

iwconfig output:

Code: Select all

alula@sweetiebelle:~$ sudo iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

ifconfig output:

Code: Select all

alula@sweetiebelle:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr fc:15:b4:fc:ac:82
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::fe15:b4ff:fefc:ac82/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33749 errors:0 dropped:0 overruns:0 frame:0
TX packets:26867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33047156 (31.5 MiB) TX bytes:2806273 (2.6 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:41 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4604 (4.4 KiB) TX bytes:4604 (4.4 KiB)

Output when I try to manually bring the interface up:

Code: Select all

alula@sweetiebelle:~$ sudo ip link set wlan0 up
RTNETLINK answers: Input/output error
alula@sweetiebelle:~$ dmesg | tail -f
[ 2858.299716] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2859.901306] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2859.901311] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[ 2861.518943] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2863.120553] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2863.120557] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[ 2864.738172] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2866.339737] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 2866.339742] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[ 2867.957399] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]

I've been Googling this for an hour or so and tried reinstalling firmware, rmmod/reboot/modprobe and nothing thus far has worked. I believe the kernel updated in my major upgrade yesterday so thinking this may be a regression.

Any ideas & help appreciated.

[Alula]

I plugged in my Cisco WiFi USB dongle, and the PCI WiFi randomly works again...

Sometimes I just give up. ><

[black level]

hi,

i have the same problem every time that restart the system.
you manage to resolve this problem? my distro is openSUSE.

[GarryRicketson]

This is "
Debian User Forums
and this thread is 2 years old, did you notice ? 2014-04-06 09:54
I do not know anything about opensuse, and do not have any interest, and
I don't know that a solution that works on Debian would be of any use.
But if it was Debian , this has all the instructions, :

https://wiki.debian.org/rt2800pci

You would be better off asking them, at:
https://forums.opensuse.org/forum.php

Did you try doing any searches ?
Ralink RT3290 WiFi Chipset Fails To Come Up on Opensuse

https://forums.opensuse.org/showthread.php/509167

[black level]

This is "
Debian User Forums
and this thread is 2 years old, did you notice ? 2014-04-06 09:54
I do not know anything about opensuse, and do not have any interest, and
I don't know that a solution that works on Debian would be of any use.
But if it was Debian , this has all the instructions, :

https://wiki.debian.org/rt2800pci

You would be better off asking them, at:
https://forums.opensuse.org/forum.php

Did you try doing any searches ?
Ralink RT3290 WiFi Chipset Fails To Come Up on Opensuse

https://forums.opensuse.org/showthread.php/509167

if you do not know no answer

easy

[tomazzi]

if you do not know no answer

easy

1. Normally I wouldn't even try to respond to a post like this one...
2. I'm bored -> ( )
3. If you're not able to understand what is the difference between OpenSUSE and Debian and what are the consequences, then I'm going to give You a hint:

The hint:
Show some respect to yourself and don't make yourself looking like a moron.

Regards.

[black level]

if you do not know no answer

easy

1. Normally I wouldn't even try to respond to a post like this one...
2. I'm bored -> ( )
3. If you're not able to understand what is the difference between OpenSUSE and Debian and what are the consequences, then I'm going to give You a hint:

The hint:
Show some respect to yourself and don't make yourself looking like a moron.

Regards.

The ignorance leads to the insults, if the problem is the same the solution can be similar.
bye

Thank you
newbies

[tomazzi]

Thank you
newbies

Don't speak for others.
Being newbie is not an excuse for beeing lazy.
There are few solutions for Your problem on the OpenSUSE forums - I've just checked this.

The ignorance leads to the insults, if the problem is the same the solution can be similar.

Obviously, You are not interested in the art of logical thinking.
1. The problem is not the same unless You can prove it.
2. Solution is very unlikely to be similar, because Debian and OpenSuse are just two completely different operating systems.

bye, bye...