Symptoms & scope
- Wi-Fi is disabled and scanning is unavailable.
- A radio appears in rfkill even though no wireless connection activates.
Relevant environment
Wi-Fi devices exposed through the kernel rfkill interface; laptops may provide a hardware switch, firmware setting or platform hotkey.
Possible causes
These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.
- A soft block can come from airplane mode or software radio policy.
- A hard block can be reported by hardware or platform firmware and cannot be cleared solely by software unblocking.
Diagnose safely
Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.
Check 1
List radio types and their soft/hard block states without changing them; match the Wireless LAN device rather than Bluetooth.
rfkill listInterpret the result: Soft blocked: yes permits a software unblock attempt. Hard blocked: yes requires the physical/platform path even if the soft block is cleared.
Check 2
Read NetworkManager’s Wi-Fi software radio policy; do not append on or off to this diagnostic command.
nmcli radio wifiInterpret the result: Disabled confirms NetworkManager’s radio policy is off, but enabled does not override a hard block. No rfkill WLAN entry can instead indicate absent driver/device enumeration.
Evidence-guided next steps
Clear the confirmed software block
If the WLAN device is only soft-blocked, turn airplane mode off and enable Wi-Fi in the desktop or with nmcli radio wifi on. Re-read rfkill and try the existing connection only after the soft block clears.
Precautions: This enables Wi-Fi transmissions and may reconnect saved profiles automatically. Check the intended network and do not unblock every radio indiscriminately.
Recovery / rollback: Return Wi-Fi to its previous disabled state if the radio must remain off; retain the saved profile for a later controlled connection.
Did this solution help you?
Resolve the physical or firmware block
If hard blocked remains yes, inspect the laptop’s radio switch, documented hotkey and firmware radio setting. If the state appeared after dual boot, perform a complete shutdown before retesting and follow the machine vendor’s platform guidance.
Precautions: Save work before shutdown and record firmware changes. A driver reinstall cannot by itself bypass a genuine hardware block.
Recovery / rollback: Restore the previous firmware setting or switch position if necessary; use Ethernet or another approved connection while platform diagnosis continues.
Did this solution help you?
References & review
This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.
- Linux kernel: rfkill hard and soft blocks (project or distribution documentation)
- util-linux: rfkill(8) (project or distribution documentation)
- NetworkManager: nmcli queries, profiles and checkpoints (project or distribution documentation)