Fn + flight mode key does a soft block instead of hard block for WiFi / Bluetooth

[baptx]

The problem you're addressing (if any)

I am using the NovaCustom NV41 Series laptop with Debian 12 and noticed the Fn + flight mode key just does a soft block and not hard block for WiFi / Bluetooth unlike my previous computers (it can be checked with the command "sudo rfkill").

Describe the solution you'd like

It should be possible to do a hard block for WiFi and Bluetooth. The Fn + flight mode key should only do a hard block / unblock and the soft block / unblock should only be changeable by the software settings, like it is done usually on laptops. This way, we can use both the hard and soft block for additional security in case one is unblocked by mistake.

Where is the value to a user, and who might that user be?

This could benefit users of the laptop I am using and maybe other laptops using Dasharo / coreboot. A hard block is preferred to a soft block since it cannot be enabled by a software (for example accidentally by the user or automatically without the user consent if the software's developers did not have this in mind). The benefit is to have a more reliable way to disable WiFi and Bluetooth when not needed (for example if we use an Ethernet cable), in order to avoid unnecessary battery usage or electrosmog.

Describe alternatives you've considered

For the moment, I use modprobe to blacklist modules (ath9k and btusb) instead of the hard block when I don't need WiFi and Bluetooth. Compared to the soft block, the modprobe solution has the advantage that a software cannot enable WiFi and Bluetooth without root privileges. But it would still be useful to have the hard block like there is usually on laptops (more reliable than soft block and no need to enter root password like with modprobe).

Additional context

No response

[mkopec]

Thanks for taking the time to add the request. There is the hardware capability for hardware rfkill by Wi-Fi and BT disable pins on the M.2 card, so the feature is feasible in theory.

Please also note that there is already an option for disabling the Wi-Fi / BT card completely in the UEFI setup menu, which cuts out the power to the M.2 module and disables the slot.

[baptx]

@mkopec Thanks for the information but disabling WiFi / Bluetooth in UEFI would have the disadvantage that we need to reboot if we want to use WiFi / Bluetooth later I guess. I forgot to mention, I am using the wireless card "Qualcomm Atheros QCNFA222 WiFi 802.11a/b/g/n + Bluetooth 4.0" which is blob-free for WiFi. Is it feasible to have the hard block with Fn + flight mode key for this card also?

[mkopec]

I think there's a very good chance it'll work, can't confirm 100% at the moment but it's a rather common feature on M.2 cards

[macpijan]

@BeataZdunczyk Shouldn't we analyze this feature more closely?