You are not logged in.
Pages: 1
Commands like
rfkill block bluetooth
are not persisting on shutdown or suspend.
Is there a way to block wifi/bluetooth persistently?
Offline
Blacklist the module.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
udev rule?
Offline
Disable and mask?
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
Indeed, options like these are on the table, but I was looking to see a "clean" solution.
At least I wanna learn what's the culprit that's re-enabling rfkill.
I have a hunch that rfkill makes changes to /sys/ which is a vfs residing in RAM. If my guess is correct, then non-persistence on shutdown makes sense, but not persisting even when suspending to RAM?
Offline
There's no "re-enabling", it's a transient state and the device/firmware defaults to "on".
but not persisting even when suspending to RAM?
Look at/post the system journal covering this and cc. if you've a parallel windows installation, see the 3rd link below.
Offline
Pages: 1