Bluetooth is not running in Kali Linux

Bluetooth failure in Kali Linux usually stems from the Bluetooth service being stopped, missing firmware files, or kernel modules not loading correctly. The most effective fix involves verifying the status of the bluetooth systemd service, ensuring the necessary packages are installed, and restarting the daemon to reinitialize the hardware adapter.

Verify Service Status and Enable Boot Start

The first step in troubleshooting is determining whether the system recognizes the Bluetooth service as active. Kali Linux uses systemd to manage background services, and if the service is inactive or disabled, the operating system will not attempt to communicate with the Bluetooth hardware. You can check the current state by running the following command in your terminal:

systemctl status bluetooth

If the output indicates that the service is inactive (dead), you need to start it immediately. Use the start command to bring the service online for the current session:

sudo systemctl start bluetooth

However, starting the service alone does not guarantee it will survive a reboot. To ensure Bluetooth runs automatically every time you log in, you must enable the service at boot. This prevents the issue from recurring after a simple restart:

sudo systemctl enable bluetooth

After enabling the service, verify that the status has changed to active (running). If the service starts successfully but your devices still do not appear, proceed to the next section to check for package dependencies. For users who have successfully paired devices before, see our guide on How to Connect Bluetooth Permanently in Linux to ensure persistent connections are configured correctly.

Install Required Packages and Firmware

Kali Linux is a specialized distribution focused on security auditing, which means it often comes with a minimal set of default packages compared to desktop-oriented distributions like Ubuntu or Fedora. It is highly likely that the core Bluetooth utilities and specific firmware files required by your hardware vendor are missing from the installation. First, ensure that the base Bluetooth packages are installed. Open a terminal and run the update command followed by the install command:

sudo apt update
sudo apt install bluez blueman

The bluez package provides the core Bluetooth protocol stack, while blueman offers a graphical user interface for managing adapters and devices. If your system reports that these packages are already at their newest version, the issue may lie with missing firmware. Many Bluetooth adapters require proprietary firmware blobs to function. You can search for available firmware packages using the following command:

apt-cache search firmware-bluetooth

Install any relevant firmware packages listed in the results. For example, if you have a Broadcom or Realtek adapter, specific firmware packages might be available in the non-free repository. Ensure your sources list includes the contrib and non-free components if they are not already present. After installing any missing firmware, restart the Bluetooth service again to allow the system to load the new files.

Check Kernel Modules and Hardware Detection

Sometimes the software stack is correct, but the kernel has not loaded the appropriate driver module for the Bluetooth chip. This often happens after a kernel update or if the module was explicitly blacklisted. You can check which modules are currently loaded by searching for Bluetooth-related keywords:

lsmod | grep bluetooth

Look for modules such as btrtl, btusb, or btintel. If these modules are missing, you may need to load them manually. For USB Bluetooth adapters, the btusb module is typically responsible for communication:

sudo modprobe btusb

To make this change permanent across reboots, you should add the module name to the /etc/modules file or create a configuration file in /etc/modules-load.d/. Additionally, verify that the hardware is physically detected by the system using the dmesg command:

dmesg | grep -i blue

This command filters the kernel ring buffer for messages containing "blue". Look for lines indicating that the firmware was loaded successfully or any error messages regarding failed initialization. If you see errors related to permissions or device access, ensure your user account is part of the bluetooth group:

sudo usermod -aG bluetooth $USER

You will need to log out and log back in for this group change to take effect.

Restart the Daemon and Test Connectivity

Once you have verified the service status, installed necessary packages, and confirmed kernel modules are active, the final step is to force a clean restart of the Bluetooth daemon. This clears any cached states or temporary errors that may have accumulated during previous failed attempts. Run the following commands to stop, wait, and then start the service:

sudo systemctl stop bluetooth
sudo systemctl start bluetooth

Alternatively, you can use the restart command for a cleaner operation:

sudo systemctl restart bluetooth

After the service is running, open the Blueman manager or the system settings menu to scan for nearby devices. If your mouse, keyboard, or headphones appear in the list, the issue is resolved. If the adapter still does not show up, check the physical switch on your laptop or external dongle to ensure it is not disabled via hardware keys. For further assistance with other common Kali Linux issues, you might find our article on Keyboard not working on Kali Linux: Troubleshooting Guide helpful, as input device conflicts can sometimes interfere with peripheral management.

Frequently Asked Questions

Why does my Bluetooth adapter show as "Not Connected" even when enabled?

This often occurs when the bluetooth service is running but the specific device driver has crashed or failed to initialize. Restarting the service with sudo systemctl restart bluetooth forces the system to re-negotiate the connection with the hardware. If the problem persists, check dmesg for firmware loading errors.

Can I use Bluetooth without the Blueman graphical interface?

Yes, you can control Bluetooth entirely from the command line using bluetoothctl. This tool allows you to power on the adapter, scan for devices, pair, and trust them without needing a GUI. It is particularly useful on headless servers or when the desktop environment fails to load properly.

What should I do if the Bluetooth service fails to start?

Check the detailed logs using journalctl -xeu bluetooth.service to identify the specific error causing the failure. Common causes include missing configuration files in /etc/bluetooth/ or permission issues with the socket file. Ensuring all required packages like bluez are correctly installed usually resolves startup failures.

Does Kali Linux support Bluetooth 5.0 and higher?

Yes, modern versions of the BlueZ stack included in Kali Linux fully support Bluetooth 5.0 and newer standards. However, you must ensure that your kernel is updated to a version that includes drivers for your specific hardware chipset. Older kernels may lack support for newer Bluetooth features like long-range mode or faster data rates.

How do I remove a stubborn paired device that won't connect?

Use the bluetoothctl tool to remove the device from the local cache. Enter the interactive shell, then use the remove [MAC_ADDRESS] command. After removing it, turn off and on the adapter power to clear any residual connection states. This forces the system to treat the device as new during the next pairing attempt.