Now you can install the package manually by running If the output is "i586" or "i686", download this oneĬopy the package from a USB to your linux machine, I would prefer the /tmp If this outputs "x86_64" you will need to download this package Out yourself by having a look at the output of Give dedicated advise on which rfkill package to install, you will have to find
You say you are running 13.2, fine, but that is not sufficient information to Idea what is behind all this "black magic" of Here in order for other users reading this thread in the future to get some Off"-command to the BIOS/UEFI that can not be understood/reverted by linux.īut this is all speculation withut further facts and I am writing this down There is a setting done by a (pre)installed Windows system, which (in mostĬases on shutdown) sends a non-documented/non-standard "switch radio In most cases, unblocking a hard block will work via a hardware switch, a keyĬombination or even worse by setting UEFI/BIOS parameters or even more worse Other rfkill devices present in the system which simulate a hard block, so theĬomplete output of rfkill list is importatnt. Likely be impossible, there are very few "exceptions" most of them depending on However, if you get a "Hard blocked: yes" unblocking with rfkill will most This could also be done without rfkill, but I think for some user new to linux, Unblocking soft locks via rfkill is quite easy Useful in order find out if the suspicion is true or not. Now let's block wifi by software (soft block)Īs you (and me also) suspect radio being turned off, this information would be If rfkill is installed, things become easier: Information as this type of block is done by a hardware switch and can not be
This means "not blocked by hardware switch", which would be a crucial Now let's have a look and split the command from my first answer into two single Yes, there is a rfkill sub directory in /sys/class (even two, but let's ignore Yes, by coincidence my wireless device is also driven by ath9k.
Let me show you the outputs on my system:Ġ2:00.0 Network controller : Qualcomm Atheros AR9285 Wireless NetworkĪdapter (PCI-Express) (rev 01) Subsystem: Askey Computer Corp.ĭevice Kernel driver in use: ath9k The program rfkill is a user space application to communicate with the rfkill Means to the best of my knowledge there must beĪ /sys/class/rfkill/rfkill$NUMBER (starting from 0) as the module cfg80211ĭepends on another kernel module called "rfkill" (which is not the program This driver is dependant on two other kernel modules mac80211 and cfg80211 which "ath9k" kernel module (aka "driver") as lspci shows a 9xxx-number for your Well, considering this, I suspect you mistyped at least the cat command in myĪs far as I can see, you have an atheros card, most likely powered by the