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-bluetooth.conf file in > /lib/modprobe.d/ and containing > > blacklist btusb > > or whichever modules (one per line), before removing it/them.
Does that require a reboot to take effect? Based on the redhat kb article at https://access.redhat.com/solutions/41278 I've now tried root@fubar:# modprobe -r btusb root@fubar:# echo "blacklist btusb" >> /etc/modprobe.d/local-dontload.conf root@fubar:# echo "install btusb /bin/false" >> /etc/modprobe.d/local-dontload.conf root@fubar:# cat /etc/modprobe.d/local-dontload.conf blacklist btusb install btusb /bin/false root@fubar:# modprobe -r btusb ...and the same log messages are continuing to appear. -- Dave Sherohman
