You are not logged in.

#1 2024-02-17 02:17:17

avidseeker
Member
Registered: 2022-09-06
Posts: 62
Website

Permanent rfkill

Commands like

rfkill block bluetooth

are not persisting on shutdown or suspend.

Is there a way to block wifi/bluetooth persistently?

Offline

#2 2024-02-17 02:41:29

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,261
Website

Re: Permanent rfkill

Blacklist the module.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2024-02-17 08:33:52

seth
Member
Registered: 2012-09-03
Posts: 57,369

Offline

#4 2024-02-17 13:52:28

merlock
Member
Registered: 2018-10-30
Posts: 249

Re: Permanent rfkill

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

#5 2024-02-18 08:21:02

avidseeker
Member
Registered: 2022-09-06
Posts: 62
Website

Re: Permanent rfkill

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

#6 2024-02-18 09:31:08

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Permanent rfkill

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

Board footer

Powered by FluxBB