Bluetooth show ON but its OFF ?

[z3huti]

In dietpi-config in advanced options, bluetooth show ON but packages for it not even installed.
If I try to set it to OFF, I see

[  OK  ] DietPi-Set_hardware | Desired setting in /boot/firmware/config.txt was already set: dtoverlay=disable-bt
[ INFO ] DietPi-Set_hardware | APT purge bluez bluez-firmware pi-bluetooth sprd-bluetooth, please wait...
[ INFO ] DietPi-Set_hardware | None of the packages are currently installed. Aborting...
[  OK  ] DietPi-Set_hardware | APT purge bluez bluez-firmware pi-bluetooth sprd-bluetooth
[  OK  ] bluetooth (disable) | Completed

after that it still show ON in advanced options, after reboot too

could it be that after turning wifi on and then off, bluetooth in menu show on ?

[MichaIng]

Thanks, it is a regression from v10.5 indeed: The kernel module blacklist file we use as flag whether Bluetooth is disabled or not, is not created on every system anymore.

So we need to find a different flag.

That it is shown as "On" while it is actually all disabled is visual-only. But the bigger problem is that it cannot be enabled anymore for that reason. Workaround is using the CLI:

/boot/dietpi/func/dietpi-set_hardware bluetooth enable

Or one can manually create the flag file as dummy:

sudo touch /etc/modprobe.d/dietpi-disable_bluetooth.conf

[MichaIng]

Done in #8225 for next release. Not the cleanest way, to have an empty modprobe config, but simple. I think mod-term, we should use rfkill, to block Bluetooth reliably for (almost) all drivers on a lower level, and can use the rfkill soft-block as flag then. Same for WiFi.