On Wed 07 Dec 2022 at 02:27:18 (-0600), d...@sherohman.org wrote: > Just replying here in case it helps others in the future. I've managed > to resolve my problem by disabling Bluetooth in the BIOS/UEFI config. > > On Tue, Dec 06, 2022 at 08:50:24AM -0600, David Wright wrote: > > On Tue 06 Dec 2022 at 14:25:02 (-0000), Curt wrote: > > > > I have twenty bluetooth modules in > > /lib/modules/5.10.0-19-amd64/kernel/drivers/bluetooth/ > > > > $ grep 'Reading Intel version' > > /lib/modules/5.10.0-19-amd64/kernel/drivers/bluetooth/* > > grep: /lib/modules/5.10.0-19-amd64/kernel/drivers/bluetooth/btintel.ko: > > binary file matches > > grep: /lib/modules/5.10.0-19-amd64/kernel/drivers/bluetooth/hci_uart.ko: > > binary file matches > > $ > > I have identical results here. Thanks for the tip on finding where > those kinds of messages come from - I'm sure it will be useful for > troubleshooting future problems. > > > > I have /etc/bluetooth/main.conf and /etc/default/bluetooth (but maybe > > > you don't). > > > > > > If you do, though, have one or both of those files, for the former: > > > > > > AutoEnable=false > > > > > > and the latter > > > > > > BLUETOOTH_ENABLED=0 > > I don't have either of those on the system in question: > > $ ls /etc/bluetooth > ls: cannot access '/etc/bluetooth': No such file or directory > $ ls /etc/default/bluetooth > ls: cannot access '/etc/default/bluetooth': No such file or directory > > Strange that it was trying to load bluetooth modules when so much of the > bluetooth ecosystem doesn't seem to be installed, but, *shrug*.
If you don't have the file, then you won't have read the warning about the default: $ head -n 5 /etc/default/bluetooth # Defaults for bluez # start bluetooth on boot? # compatibility note: if this variable is _not_ found bluetooth will start BLUETOOTH_ENABLED=1 $ Read as bluetooth will attempt to start. Cheers, David.
