Linux WiFi: operation not possible due to RF-kill
2011-12-20 18:26
696 查看
Some people have been experiencing WiFi problems with Ubuntu 10.10 since an update that happend just before Christmas 2010. The problem seems to be a bug in a kernel module, which prevents the
rfkill's soft and hard block from syncing correctly.
In practice that means you can press your laptop's WiFi button as often as you want, it doesn't change anything. Your wireless adapter will always appear as disabled. If you try to start the wireless interface manually you get the following error message:
sk@ubuntu:~# sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill
If you do a rfkill list all you should get an output similar to this:
sk@ubuntu:~$ sudo rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
Depending on the state of your WiFi button the Hard blocked will either be
yes or no. Press the WiFi button and run
rfkill list all again to make sure the value for
Hard blocked changes.
The actual problem is, that the Soft blocked value is always set to
yes, because for some reason the syncing between the hardware block and the software block doesn't work as supposed. To override this behavior, you can just run
rfkill unblock wifi and it should work again. Double check by entering
rfkill list all again and make sure it looks like this, with all values set to
no:
sk@ubuntu:~$ sudo rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
If you then run ifconfig wlan0 up (or enable the wireless via your desktop's network manager) you should be able to connect to a wireless network again without any further issues.
The configuration, which I've been using:
Compaq Presario CQ60
Atheros AR5001 Wireless Network Adapter
Ubuntu 10.10
I also read, that some people could fix it, by turning off the WiFi button during the boot process and then switch it on again, once the system is up and running. It seems that the system expects the hard block to be set to off. This is still a bug, but it
could explain why then the soft block didn't sync with the hard block any more.
rfkill's soft and hard block from syncing correctly.
In practice that means you can press your laptop's WiFi button as often as you want, it doesn't change anything. Your wireless adapter will always appear as disabled. If you try to start the wireless interface manually you get the following error message:
sk@ubuntu:~# sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill
If you do a rfkill list all you should get an output similar to this:
sk@ubuntu:~$ sudo rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
Depending on the state of your WiFi button the Hard blocked will either be
yes or no. Press the WiFi button and run
rfkill list all again to make sure the value for
Hard blocked changes.
The actual problem is, that the Soft blocked value is always set to
yes, because for some reason the syncing between the hardware block and the software block doesn't work as supposed. To override this behavior, you can just run
rfkill unblock wifi and it should work again. Double check by entering
rfkill list all again and make sure it looks like this, with all values set to
no:
sk@ubuntu:~$ sudo rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
If you then run ifconfig wlan0 up (or enable the wireless via your desktop's network manager) you should be able to connect to a wireless network again without any further issues.
The configuration, which I've been using:
Compaq Presario CQ60
Atheros AR5001 Wireless Network Adapter
Ubuntu 10.10
I also read, that some people could fix it, by turning off the WiFi button during the boot process and then switch it on again, once the system is up and running. It seems that the system expects the hard block to be set to off. This is still a bug, but it
could explain why then the soft block didn't sync with the hard block any more.
相关文章推荐
- ubuntu WiFi: operation not possible due to RF-kill《转载》
- Can't init device hci0: Operation not possible due to RF-kill (132) 蓝牙不能启动错误
- linux无线遇到问题Operation not possible due to RF-kill
- operation not possible due to RF-kill
- Operation not possible due to RF-kill
- SIOCSIFFLAGS: Operation not possible due to RF-kill
- Operation not possible due to RF-kill
- operation not possible due to RF-kill
- RTNETLINK answers: Operation not possible due to RF-kill
- SIOCSIFFLAGS: Operation not possible due to RF-kill
- jquery crossdomain post plugin i changed bit test code suite for my env,due to the windows env is not familiar with github operation,i didn't forked form the original resposeritoy
- Operation is not valid due to the current state of the object.
- bug:"Operation is not valid due to the current state of the object."
- ORA-27125: unable to create shared memory segment Linux-x86_64 Error: 1: Operation not per
- GridView Postback后出错Operation is not valid due to the current state of the object.
- Operation is not valid due to the current state of the object.
- Linux安装apache源码包报错:mod_deflate has been requested but can not be built due to prerequisite failures
- Error occurred in deployment step 'Add Solution': Operation is not valid due to the current state of the object.
- linux启动报错:kernel panic - not attempted to kill init
- “Operation is not valid due to the current state of the object.”