rfkill soft block status persistence across reboots

29 April 2025, 16:13:03

Hi there, so there's a bunch of stuff online for people whose WiFi cards are softblocked upon boot and they want the card to be permanently unblocked. The solution suggested for those cases is to just run the rfkill unblock command on startup.

What I would like is for my wifi and bluetooth cards to neither be permanently blocked nor permanently unblocked, but for me to be able to toggle them, and for the state of them to persist across reboots. Currently, if I softblock them, they go back to being unblocked upon boot. I could run rfkill block upon startup automatically, but I don't want my wifi/bluetooth cards to always be blocked.

I suppose I could save the state during/immediately prior to shutdown, and run rfkill commands to restore this state upon startup. Is this the best or only way? It seems a bit janky to just do this via bash scripts.

Re: rfkill soft block status persistence across reboots

Reply #1 – 29 April 2025, 18:13:53

If your desktop environment can't do it for you (e.g. like KDE can with Bluetooth -> Configure -> On Login -> Restore Previous Status), setting up a script is the way.