Conversation
`dietpi-config` uses `/etc/modprobe.d/dietpi-disable_bluetooth.conf` as flag about whether Bluetooth is enabled or not. Since v10.5 we do not create it anymore on all systems, so that Bluetooth in those cases kept showing as enabled, hence could not be actually enabled anymore either. This commit re-adds `/etc/modprobe.d/dietpi-disable_bluetooth.conf` in every case, it might just remain empty. It is no elegant solution, but works, until we have a better idea how to detect whether Bluetooth is enabled or not, like the `bluez` package, or service. Or use rfkill, to block Bluetooth on a lower level, no matter which adapter/driver is loaded (almost, `sprdbt_tty` on Allwinner does not support rfkill).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dietpi-configuses/etc/modprobe.d/dietpi-disable_bluetooth.confas flag about whether Bluetooth is enabled or not. Since v10.5 we do not create it anymore on all systems, so that Bluetooth in those cases kept showing as enabled, hence could not be actually enabled anymore either.This commit re-adds
/etc/modprobe.d/dietpi-disable_bluetooth.confin every case, it might just remain empty. It is no elegant solution, but works, until we have a better idea how to detect whether Bluetooth is enabled or not, like thebluezpackage, or service. Or use rfkill, to block Bluetooth on a lower level, no matter which adapter/driver is loaded (almost,sprdbt_ttyon Allwinner does not support rfkill).