[SOLVED] SIOCSIFFLAGS: Operation not possible due to RF-kill

carebearboy · 2011-07-03 22:28:32

Each time I start KDE (installed base package - minimal install) I need to run this command to get wireless running:

rfkill unblock 0 && rfkill unblock 1 && rfkill unblock 2 && rfkill unblock 3 && ifconfig wlan0 up

Running without rfkill unblock results in:

[root@Spaghettios user]# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill

driver - ath9k

I have a feeling it may be something to do with my config file as I'm new, so I'm posting it.

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Toronto"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
#MOD_AUTOLOAD="yes" #depreciated as of june                ###### ****EDIT *** heard this was obsolete
#MOD_BLACKLIST=() #deprecated as of june
MODULES=(!ath5k ath9k)      ######## ***EDIT **** added ath9k which is my driver

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="Spaghettios"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"  ## this was added back
wlan0="dhcp" ## new add
INTERFACES=(eth0 wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)                                   #### ****EDIT **** does this need to be blacklisted as it is?

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
eth0="dhcp"  ## this was added back
wlan0="dhcp" ## new add
INTERFACES=(eth0 wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#

DAEMONS=(syslog-ng dbus alsa ntfs networkmanager crond) #network was replaced by networkmanager



# DAEMONS=(syslog-ng dbus alsa ntfs network wicd crond)
# Gaves depreciated warning + rfkill warning (SIOCSIFFLAGS: Operation not possible due to RF-kill) and fails to load wicd daemon

I've spent hours on archwiki reading up on the following sections:

- networkmanager
- network
- rc.conf
- kde

I'm thinking I likely missed a step somehow. Any ideas?

Last edited by carebearboy (2011-07-04 04:10:46)

anrxc · 2011-07-04 01:21:53

Add interfaces here /etc/conf.d/rfkill and enable rfkill in rc.conf DAEMONS.

carebearboy · 2011-07-04 03:12:24

anrxc wrote:

Add interfaces here /etc/conf.d/rfkill and enable rfkill in rc.conf DAEMONS.

Thanks for that advice! Now the wlan0 is no longer blocked.

Here's what I entered as a reference for anyone that wants to know:

This file can be kept as is. Just make sure that RFKILL_UNBLOCK="all" is uncommented (no "#" infront of it):

#
# /etc/conf.d/rfkill
# Configuration for the rfkill startup script
#

# List of devices to block on startup (space-separated)
# RFKILL_BLOCK=""

# List of devices to unblock on startup (space-separated)
RFKILL_UNBLOCK="all"

# Supported device names are: all, wifi, bluetooth, umb, wimax, wwan, gps and specific devic$
# See "rfkill list" for available devices
# Examples:
#
# Block all bluetooth devices:
# RFKILL_BLOCK="bluetooth"
#
# Unblock the phy0 wifi device and all wwan devices:
# RFKILL_UNBLOCK="phy0 wwan"

Here's where I put the 'rfkill' command in /etc/rc.conf:

DAEMONS=(syslog-ng dbus alsa ntfs rfkill networkmanager crond)

Now it's 50% solved!

I noticed that when booting into the kde desktop the network manager does not automatically make a connection to a wireless network. The wireless works but I have to click the icon and choose the network each time once logged in. In my network system settings I have it checked to "Connect Automatically".

* edit *

I've read the Networkmanager Wiki page again and followed the instructions on how to "Automatically connect on boot" and still no luck. There is talk about a nm-system-settings and nm-applet of which I wasn't able to find in the repos.

Any help would be great!

* 2nd edit *

Fixed it!

System Settings -> Network Settings -> Network Manager -> Wireless -> Check "System Connection"

I've never had to check that one before, but it worked!

Last edited by carebearboy (2011-07-04 04:09:36)

Arch Linux

#1 2011-07-03 22:28:32

[SOLVED] SIOCSIFFLAGS: Operation not possible due to RF-kill

#2 2011-07-04 01:21:53

Re: [SOLVED] SIOCSIFFLAGS: Operation not possible due to RF-kill

#3 2011-07-04 03:12:24

Re: [SOLVED] SIOCSIFFLAGS: Operation not possible due to RF-kill

Board footer