LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 03-28-2017, 04:19 PM   #1
signsanssignified
LQ Newbie
 
Registered: Mar 2017
Posts: 2

Rep: Reputation: Disabled
SIOCSIFFLAGS: Operation not possible due to RF-kill


Hello, all--

I'm running Ubuntu 16.04 on a dual boot Dell Inspiron 1535. I started setting up a VPN on my laptop a week ago, then aborted the effort, and my wifi has been down since then (I'm able to get online via my iPhone's Personal Hotspot feature). I've since uninstalled OpenVPN.

I've determined that the driver ath9k is off, but I cannot figure out how to turn it back on. I've been following instructions on various threads here & on Ask Ubuntu, using various commands to try to diagnose the problem. Tonight I ran ifconfig -a to see what my putative connections look like. Here's what I got:

Quote:
enp0s20u2c4i2 Link encap:Ethernet HWaddr 56:4e:90:d9:5f:57
inet addr:172.20.10.3 Bcast:172.20.10.15 Mask:255.255.255.240
inet6 addr: 2600:1017:b416:cf8f:b1e7:b5e4:f0c5:e3b3/64 Scope:Global
inet6 addr: 2600:1017:b416:cf8f:489c:6bb9:6dd:edfd/64 Scope:Global
inet6 addr: fe80::3bc6:73d3:9706:67a2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:295 errors:0 dropped:1 overruns:0 frame:0
TX packets:440 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:64168 (64.1 KB) TX bytes:66145 (66.1 KB)

eth0 Link encap:Ethernet HWaddr 74:86:7a:5a:41:6e
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:414 errors:0 dropped:0 overruns:0 frame:0
TX packets:414 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:33865 (33.8 KB) TX bytes:33865 (33.8 KB)

wlan0 Link encap:Ethernet HWaddr 34:23:87:5f:63:85
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
I then tried this:

sudo ifconfig wlan0 up

which yielded this message:

Quote:
SIOCSIFFLAGS: Operation not possible due to RF-kill
I'd run rfkill list last night, yielding this output:

Quote:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
I don't know how to unblock my wireless LAN.

Please advise.

Thanks.
 
Old 03-29-2017, 03:47 PM   #2
serafean
Member
 
Registered: Mar 2006
Location: Czech Republic
Distribution: Gentoo, Chakra
Posts: 997
Blog Entries: 15

Rep: Reputation: 136Reputation: 136
Your wireless card is disabled by a hardware switch. You can't do anything about it from linux.
There should be a hardware switch somewhere on your machine (sometimes it is Fn + F7, sometimes a dedicated button...). Flip that and you should be good.
Also maybe check that it isn't disabled in the BIOS/UEFI configuration.
 
1 members found this post helpful.
Old 03-29-2017, 08:32 PM   #3
signsanssignified
LQ Newbie
 
Registered: Mar 2017
Posts: 2

Original Poster
Rep: Reputation: Disabled
Thank you, Serafean! That did the trick! It was Fn-F2.

I'm really grateful to you--I've been banging away at this for a few days, to no avail (obviously). What a relief...
 
Old 03-31-2017, 06:30 PM   #4
padeen
Member
 
Registered: Sep 2009
Location: Perth, W.A.
Distribution: Slackware, Debian, Gentoo, FreeBSD, OpenBSD
Posts: 208

Rep: Reputation: 41
'rfkill list' shows all devices affected by the switch and whether it's a hard kill or soft kill. Hard kill is the hardware switch, soft kill is software so root should be able to change the state.

Also, I find that dual-booting Windows can frequently leave the switch in hard kill for the subsequent boot to Linux, and that, after changing the hard kill switch, it can take several boots for it to stick permanently. YMMV. (Dell Inspiron)
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How to kill a process in Linux - kill, killall, pkill, xkill LXer Syndicated Linux News 0 04-02-2013 12:01 PM
"Operation not possible to due rf-kill" with command: ifconfig wlan0 up Quon Linux - Networking 5 04-03-2012 01:58 PM
SIOCSIFFLAGS: Operation not permitted SIOCSIFFLAGS: Operation not permitted sushan1982 Linux - Wireless Networking 1 01-01-2012 08:04 PM
wifi on iwl3945 driver in Lenny - mysterious SIOCSIFFLAGS and HW RF Kill switch slawek Debian 4 08-26-2009 11:28 AM
Error USB-HUC on booting due in mdk10 due to mx700 Boudewijn Mandriva 4 10-09-2004 08:36 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 06:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration