When I use gnome network manager it indicates that wireless is disabled by hardware switch while it is not. Even in windows I can not turn on my wireless!
I just tried this:
The output was something like this:
Then I have run this command:
and all is fine now :) Have fun :) I hope it will help you :)
To explicitly check your wireless is turn off by hardware switch or not, you can use
Then you can use this command to unblock every blocked component there:
I think this is just a new manifestation of an old problem that affects Vaio laptops. I have one too, ran into the same problem with 12.04 (beta 2), and had success using the same solution I used with Ubuntu 11.*:
Let me know if that works for you. I think Ubuntu gets confused by having both "sony-wifi" and "acer-wireless" (which you can see in the previous answers "sudo rfkill list all"), and the rmmod will clear the "acer-wireless" option.
A more permanent version of this solution, suggested on this thread http://ubuntuforums.org/archive/index.php/t-1859633.html, is to just blacklist it by adding
and then restarting your system.
Check your BIOS settings. In my laptop's BIOS, there is an option of shutting down Wireless, Bluetooth and other networking interfaces.
The other problem might be that there is a physical problem with your Wireless hardware
The other case might be that your hardware is blacklisted. Check if the module is blacklisted in
if it is not present in this, check other blacklist files in
Additionally please check that in
This thread came up tops in search but was not marked SOLVED so I'll post what worked for me.
Most driver and configuration bugs have been worked out, hence methods to remove or override stubborn hardware locks don't work and lead only to frustration.
The first step should be to locate the wifi/wlan switch and toggle it. It may be a function key, slider switch or other. If unsure of its location, head to the mfr's website and search the manual.
Those who, like me, leave WIFI on all the time are most susceptible to this trouble. We don't use the switch so we're not mindful of it.
After wasting hours searching and trying many suggestions like others here, I finally reviewed the documentation and found the tiny switch that had been accidentally toggled. Toggled it back and everything started working again.
protected by Community♦ Jul 19 '12 at 6:24
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?