You are not logged in.
Pages: 1
I have a Rosewill RNX-N300X wireless card installed, which lspci tells me has a Ralink RT2800 chipset. It will usually work fine for a while after startup and then randomly fail. Wicd will suddenly show "no networks available."
dmesg output when this happens:
[ 13.630345] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 13.650445] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 19.070393] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 19.070578] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 19.071208] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.476979] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 22.497091] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 22.539475] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 22.539655] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 22.540355] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.606980] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 22.627089] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.110238] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 1)
[ 26.310025] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 2)
[ 26.510042] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 3)
[ 26.710040] wlan0: authentication with 94:44:52:1e:7c:a7 timed out
[ 65.266906] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 65.287115] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 65.328156] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 65.328336] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 65.328937] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 69.063578] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 69.083758] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 70.460248] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 70.480427] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 70.511619] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 70.511799] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 70.512423] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 70.570303] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 70.590416] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 72.830319] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 1)
[ 72.831739] wlan0: authenticated
[ 72.831830] wlan0: associate with 94:44:52:1e:7c:a7 (try 1)
[ 72.835546] wlan0: RX AssocResp from 94:44:52:1e:7c:a7 (capab=0x411 status=0 aid=1)
[ 72.835550] wlan0: associated
[ 72.843623] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 72.935054] Intel AES-NI instructions are not detected.
[ 72.972037] padlock_aes: VIA PadLock not detected.
[ 83.416696] wlan0: no IPv6 routers present
[ 397.219743] chromium-sandbo (3439): /proc/3437/oom_adj is deprecated, please use /proc/3437/oom_score_adj instead.
[ 486.647199] wlan0: deauthenticated from 94:44:52:1e:7c:a7 (Reason: 3)
[ 486.750054] cfg80211: Calling CRDA for country: US
[ 487.210208] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 487.230382] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 487.268463] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 487.268643] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 487.269273] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 492.060202] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 492.080378] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 493.446869] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 493.467056] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 493.498139] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[ 493.498319] forcedeth 0000:00:07.0: eth0: no link during initialization
[ 493.498951] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 493.566871] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 493.587041] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 495.820292] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 1)
[ 496.020015] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 2)
[ 496.220003] wlan0: authenticate with 94:44:52:1e:7c:a7 (try 3)
[ 496.419998] wlan0: authentication with 94:44:52:1e:7c:a7 timed outOutput of iwlist scan:
lo Interface doesn't support scanning.
wlan0 Failed to read scan data : Network is down
eth0 Interface doesn't support scanning.If I try to run ifconfig wlan0 up, I get this error:
SIOCSIFFLAGS: Input/output errorIs this a driver issue? Is the hardware itself bad?
Thanks in advance.
Offline
According to : http://linux-wless.passys.nl/query_chip … set=Ralink , you need the RT2860 driver and firmware.
Read this: https://wiki.archlinux.org/index.php/Wi … and_rt2870
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
I feel stupid, but what do I do now? All the articles I can find about this basically say "kernel 3.0 eliminates the staging drivers" and little else. I suppose I need to download and compile the staging driver? I apologize for being such a noob, but I have no idea how to do this.
Offline
I hate to bump an old thread but I have this exact same issue.
The rt2800pci module drops connections all the time, sometimes I have to reboot because reloading the module doesn't even fix the wi-fi. It's bad. I get the same errors as you.
Did you ever get your issue resolved??
Offline
@aphexx, please post the wireless card section of the output of "sudo lspci -v".
Tim
Offline
@aphexx, please post the wireless card section of the output of "sudo lspci -v".
Tim
Sure:
04:01.0 Network controller: Ralink corp. RT2800 802.11n PCI
Subsystem: Linksys Device 0067
Flags: bus master, slow devsel, latency 32, IRQ 19
Memory at fddf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Kernel driver in use: rt2800pci
Offline
There is a AUR package named rt2860 that _may_ work with your card. your wifi interface will be 'ra0'. notice the _may_ in the first sentence, your box might kernel panic when connecting to the WAP.
I have filed a bug report on it: https://bugzilla.kernel.org/show_bug.cgi?id=42745
(In my situation it only happens once i resume from suspend2ram)
Last edited by Illuna (2012-02-08 15:41:40)
Offline
There is a AUR package named rt2860 that _may_ work with your card. your wifi interface will be 'ra0'. notice the _may_ in the first sentence, your box might kernel panic when connecting to the WAP.
I have filed a bug report on it: https://bugzilla.kernel.org/show_bug.cgi?id=42745
(In my situation it only happens once i resume from suspend2ram)
Thanks! This seems to be working amazingly so far. I haven't had any issues for a couple of hours!
I'll report back here if anything goes awry, but so far my wifi speeds seem faster (no more lagging flash content), and wicd now reports signal strength (it didn't before..)
Offline
Well...something went awry -__-
The rt2860sta was like a dream at first. A few days of nonstop internet....no connection drops, just worked perfectly....
Then something happened. I have no idea what changed, but I get a kernel panic the second it tries to connect to a network. I've tried everything I could think of to no avail. So I went back to the toooootal pile of shit rt2800pci and I'm back to reconnecting (maybe..if I'm lucky) every 5 minutes or so. Not sure what to do at this point.
Offline
What you could do is try and work out what is causing your kernel panic.
First up look in /var/log/kernel.log and find the errors that prompt the kernel panic and Google and ask here if you can't find anything.
Do you have an older kernel in your cache that you could reinstall? (check the arch wiki for downgrading packages).
I use an Asus wireless dongle (with a Ralink chipset) that used to keep dropping the connection. I stopped using Networkmanager, then tried and wicd and the problem was much worse with wicd. I started using netcfg (check the Arch wiki). Now my connection is rock solid. Maybe try that?
Last edited by Bazzaah (2012-02-16 12:57:43)
Offline
Pages: 1