Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
#ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill
and
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
-----------------------------------------------------------------------
i use Archlinux
(#rfkill unblock all) can not solv this problem.
Hard blocked is still "yes"
and the wireless is enable in BIOS
-----------------------------------------------------------------------
my wireless card is LINK 5100
it worked great before 'pacman -Syu'
Same thing here with my Atheros. The hard block only occurs when suspending to disk (hibernation) and "rfkill unblock all" don't release it. It started with kernel 2.6.36. Suspending to ram goes without problem. I had two options to bring wireless up again: rebooting or removing the modules and blacklisting rfkill before probing ath5k again, but I loose acer_wmi functionality.
Same thing here with my Atheros. The hard block only occurs when suspending to disk (hibernation) and "rfkill unblock all" don't release it. It started with kernel 2.6.36. Suspending to ram goes without problem. I had two options to bring wireless up again: rebooting or removing the modules and blacklisting rfkill before probing ath5k again, but I loose acer_wmi functionality.
I was wrong about the kernel. First time I saw this error was shortly after I had 2.6.36 compiled. Playing recently with ConsoleKit I lost permission to manage power functions when starting KDE by console. Sent the system a "few" times to memory/disk and all came clean. The bug goes away... Sorry for misleading.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.