Re: Killing bluetooth dead

2022-12-07 Thread David Wright
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 20

Re: Killing bluetooth dead

2022-12-07 Thread dave
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 (-), Curt wrote: > > I have twenty bluetooth modules in

Re: Killing bluetooth dead

2022-12-06 Thread David Wright
On Tue 06 Dec 2022 at 14:25:02 (-), Curt wrote: > On 2022-12-06, d...@sherohman.org wrote: > > > > ...and the same log messages are continuing to appear. I have twenty bluetooth modules in /lib/modules/5.10.0-19-amd64/kernel/drivers/bluetooth/ $ grep 'Reading Intel version' /lib/modules/5.1

Re: Killing bluetooth dead

2022-12-06 Thread Curt
On 2022-12-06, d...@sherohman.org wrote: > > ...and the same log messages are continuing to appear. > 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 BLUETO

Re: Killing bluetooth dead

2022-12-06 Thread dave
On Mon, Dec 05, 2022 at 04:18:19PM -0600, David Wright wrote: > On Mon 05 Dec 2022 at 11:57:19 (-0500), Jeffrey Walton wrote: > > It may be easier to look in the BIOS/UEFI and see if there's a way to > > disable Bluetooth and Wifi. Then you don't have to worry about drivers > > loading for chips th

Re: Killing bluetooth dead

2022-12-06 Thread dave
On Mon, Dec 05, 2022 at 02:32:15PM -0500, Timothy M Butterworth wrote: > If you do not want Bluetooth to run you can simply disable it in systemd. > > sudo systemctl stop bluetooth.service > > sudo systemctl disable bluetooth.service That was actually the first thing I tried, I just forgot to

Re: Killing bluetooth dead

2022-12-06 Thread dave
On Mon, Dec 05, 2022 at 03:28:40PM +, Brad Rogers wrote: > On Mon, 5 Dec 2022 08:42:14 -0600 > d...@sherohman.org wrote: > > mentioning "blue", "tooth", or "bt" - there aren't any, so the obvious > > what about 'blue*'? Good thought, but the specific command I use to check for that sort of t

Re: Killing bluetooth dead

2022-12-06 Thread dave
On Mon, Dec 05, 2022 at 09:51:20AM -0600, David Wright wrote: > > - `rmmod btusb` - this has no apparent effect, probably because > > bluetooth.target loads the mod back in before I even have time to run > > `lsmod` and see if it's still there > > Then I would blacklist it. Create a blacklist-

Re: Killing bluetooth dead

2022-12-05 Thread David Wright
On Mon 05 Dec 2022 at 11:57:19 (-0500), Jeffrey Walton wrote: > On Mon, Dec 5, 2022 at 10:19 AM wrote: > > > > I've got a headless server which is endlessly spamming its logs multiple > > times per second with: > > > > --- > > Dec 5 15:22:33 fubar systemd[2097]: Reached target Bluetooth. > > Dec

Re: Killing bluetooth dead

2022-12-05 Thread Timothy M Butterworth
On Mon, Dec 5, 2022 at 12:05 PM Jeffrey Walton wrote: > On Mon, Dec 5, 2022 at 10:19 AM wrote: > > > > I've got a headless server which is endlessly spamming its logs multiple > > times per second with: > > > > --- > > Dec 5 15:22:33 fubar systemd[2097]: Reached target Bluetooth. > > Dec 5 15:

Re: Killing bluetooth dead

2022-12-05 Thread Jeffrey Walton
On Mon, Dec 5, 2022 at 10:19 AM wrote: > > I've got a headless server which is endlessly spamming its logs multiple > times per second with: > > --- > Dec 5 15:22:33 fubar systemd[2097]: Reached target Bluetooth. > Dec 5 15:22:33 fubar systemd[2093386]: Reached target Bluetooth. > Dec 5 15:22:3

Re: Killing bluetooth dead

2022-12-05 Thread Cindy Sue Causey
On 12/5/22, Brad Rogers wrote: > On Mon, 5 Dec 2022 08:42:14 -0600 > d...@sherohman.org wrote: > > Hello d...@sherohman.org, > >> mentioning "blue", "tooth", or "bt" - there aren't any, so the obvious > > what about 'blue*'? > > Found bluedevil, bluez and bluezobexd here, where 'blue' alone found

Re: Killing bluetooth dead

2022-12-05 Thread Ryan Nowakowski
On Mon, Dec 05, 2022 at 08:42:14AM -0600, d...@sherohman.org wrote: > How do I kill bluetooth dead and make this stop? You might try blacklisting the bluetooth kernel module.

Re: Killing bluetooth dead

2022-12-05 Thread David Wright
On Mon 05 Dec 2022 at 08:42:14 (-0600), d...@sherohman.org wrote: > I've got a headless server which is endlessly spamming its logs multiple > times per second with: > > --- > Dec 5 15:22:33 fubar systemd[2097]: Reached target Bluetooth. > Dec 5 15:22:33 fubar systemd[2093386]: Reached target Bl

Re: Killing bluetooth dead

2022-12-05 Thread Brad Rogers
On Mon, 5 Dec 2022 08:42:14 -0600 d...@sherohman.org wrote: Hello d...@sherohman.org, > mentioning "blue", "tooth", or "bt" - there aren't any, so the obvious what about 'blue*'? Found bluedevil, bluez and bluezobexd here, where 'blue' alone found nothing. -- Regards _ "Valid sig sep