Ifconfig Wlan0 Up Siocsifflags Input/output Error
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more rtnetlink answers input/output error about Stack Overflow the company Business Learn more about hiring developers or posting ads
Ubuntu Wifi Device Not Ready
with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “Could not set interface wlan0 flags (UP): Input/output error” RT3290 up vote 1 down vote favorite 1 I've encountered a very puzzling issue with my WiFi card on Ubuntu. After reboot it's always disabled and there is no way to bring it back other than suspending or shutting down the laptop. Status according to Network Manager is "device not ready". This occurs consistently. Some background on my system: The laptop is HP 350 G1. The WLAN card is the infamous Ralink RT3290. (If I knew how much trouble I would have with it I would never have bought it). Ubuntu is the latest LTS 16.04, recently upgraded. Kernel is 4.4.9-040409-generic (was 4.4.0-22-generic before upgrading from mainline - no difference wrt WiFi). Before upgrading the distro, I was using a version of the rt3290sta/2.6.0.0 driver (compiled from source and loaded via DKMS) which performed mostly fine, but it doesn't work with the newer kernels and it seems abandoned anyway. So now I had to revert to rt2800 and have this problem since. This seems to be a very old but recurring issue. I read through all threads I could find, but so far no luck. Fortunately it's not critical for me because I rarely reboot, but it's still annoying and vexing at the least. Below are outputs of some commands that could be of interest (this is the state after reboot): lshw -c network says the interface is disabled: # lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:01:00.0 logical name: eth0 version: 10 serial: c4:34:6b:05:5f:ff size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Linux will not activate wireless after device has been re-enabled up vote 3 down vote favorite 1 Using a Eee 900A netbook by Asus. http://askubuntu.com/questions/770488/could-not-set-interface-wlan0-flags-up-input-output-error-rt3290 By pressing Fn + F2, I can disable or enable the wireless chip on the netbook, a blue LED indicates the status. I've been able to connect to wireless networks just fine with this netbook. However, if the wireless chip ever becomes disabled, I have to reboot to get my network connection back. This generally happens when suspending. For some reason the LED will be off and I have to hit Fn + F2 for it to light up again. However, after doing http://superuser.com/questions/139156/linux-will-not-activate-wireless-after-device-has-been-re-enabled so, Linux will not reconnect to the network. It simply changes the wireless status from "wireless is disabled" to "device not ready". Even worse, I've recently had issues with the chip being enabled at boot, thus making it nearly impossible to get connected. I've searched around on-line but haven't found much of anything useful on this. This happens on all kinds of different distros including Ubuntu 9.10 Netbook, EeeBuntu 4 beta, Jolicloud and Ubuntu 10.04 Netbook. Edit I noticed this question is getting a lot of views. To give a quick update, I never did resolve this issue with the given distro's. However, I'm currently running Ubuntu 10.10 netbook edition and this issue has gone away. linux drivers wireless-networking netbook network-adapter share|improve this question edited Jan 20 '12 at 20:50 asked May 8 '10 at 23:06 Matt Molnar 18317 What kernel versions are those distros? You could try to install a Vanilla Kernel, maybe this is a bug which has already been fixed. –Bobby Jun 8 '10 at 10:24 Current installed distro is Ubuntu 10.04 Netbook Edition with kernel 2.6.32-21-generic. I tried installing a new kernel like you said using the instructions here wiki.ubuntu.com/KernelTeam/GitKernelBuild but I ran out of disk space. :sigh: –Matt Molnar Jun 9 '10 at 3:33 add a comment| 5 Answers 5 active oldest votes up vote 1 down vote I can confirm that WICD (in Ubuntu community repos: add community/universe repos in sources then apt-get install wicd) does re
people Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Expired Medium Unassigned Edit You https://bugs.launchpad.net/bugs/1132360 need to log in to change this bug's status. Affecting: https://bbs.archlinux.org/viewtopic.php?id=128723 linux (Ubuntu) Filed here by: Kenny Strawn When: 2013-02-24 Completed: 2013-10-04 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) input/output error Project (Find…) Status Importance Expired Medium Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description The device in question: a Linksys WMP600N (both the device ID and subsystem ID ifconfig wlan0 up in the title). And the kernel: 3.8.0-7-generic, the very kernel that the latest commenter on Bug 1128840 said would fix the problem. --- ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3130 F.... pulseaudio CasperVersion: 1.330 DistroRelease: Ubuntu 13.04 LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: System manufacturer System Product Name MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=
2010-10-03 Posts: 11 Wifi randomly fails 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 req