Making a USB Bluetooth Adapter Work on Linux Instead of Internal Bluetooth

To use a USB Bluetooth adapter on Linux instead of the internal Intel AX210 chip, you must disable the internal device via kernel module blacklisting or hardware switch. This prevents conflicts and allows your Realtek USB dongle to become the primary interface for audio and peripherals.

Many MiniPCs and modern laptops come equipped with high-performance Wi-Fi and Bluetooth cards, such as the Intel AX210. While these are excellent for connectivity, users often prefer external USB adapters for specific reasons: better range, compatibility with older drivers, or simply because the internal antenna is poorly positioned. However, Linux typically auto-detects both devices upon boot. If both are active, they can conflict over the radio frequency spectrum or cause confusion in system settings like PulseAudio or PipeWire, which may fail to route audio correctly if multiple Bluetooth controllers are present. The goal is to make the system ignore the internal Intel Bluetooth controller entirely and recognize only the plugged-in Realtek USB adapter. There are two primary methods to achieve this: temporarily disabling the driver at runtime, or permanently blacklisting the kernel module. The permanent method is generally preferred for desktop setups where the internal card is not needed.

Identifying Your Devices

Before making changes, you need to confirm that Linux sees both devices. Open a terminal and run the following command:

lsusb

Look for entries mentioning "Realtek" or "Bluetooth." You should also check the kernel messages to see how the internal Intel device is being handled:

dmesg | grep -i bluetooth

You might see references to btintel, which is the kernel driver for Intel Bluetooth chips. Confirming the presence of both devices ensures you are targeting the correct hardware.

Method 1: Permanent Blacklisting (Recommended)

Blacklisting prevents the kernel from loading the driver for the internal Bluetooth chip during boot. For the Intel AX210, the relevant module is usually btintel. However, caution is required. On some systems, the Bluetooth functionality is tightly coupled with the Wi-Fi subsystem. Disabling btintel might occasionally affect Wi-Fi stability if the firmware loading process is shared. In most standard configurations, however, disabling the Bluetooth driver does not break Wi-Fi data transmission. To blacklist the module, create or edit a configuration file in the /etc/modprobe.d/ directory. 1. Create a new file named blacklist-btintel.conf:

sudo nano /etc/modprobe.d/blacklist-btintel.conf

2. Add the following line to the file:

blacklist btintel

3. Save the file and exit the editor. After saving, you must update your initial ramfs so the change takes effect on the next boot. The command varies by distribution: For Debian, Ubuntu, and Mint:

sudo update-initramfs -u

For Arch Linux and Manjaro:

sudo mkinitcpio -P

For Fedora and RHEL-based systems:

sudo dracut --force

Reboot your system. Upon restart, the internal Intel Bluetooth should no longer appear in lsusb or system settings. Your Realtek USB adapter should now be detected and available for pairing.

Method 2: Runtime Disable (Temporary Fix)

If you want to test the setup without rebooting or fear breaking your Wi-Fi, you can unload the module temporarily. Run the following commands:

sudo modprobe -r btintel

This removes the driver from memory. Check lsusb again; the internal device should disappear. If everything works with your USB adapter, you can proceed with the permanent blacklisting method above. If you experience issues, you can reload the module with sudo modprobe btintel.

Troubleshooting USB Adapter Detection

Sometimes, after disabling the internal Bluetooth, the USB adapter might still not work immediately. This can happen if the USB port is in a low-power state or if the driver needs a fresh start. 1. Check Kernel Messages: Run dmesg | tail -n 20 after plugging in the USB adapter. Look for errors related to rtw_btcoex or other Realtek-specific drivers. Many Realtek USB Bluetooth dongles share firmware with Wi-Fi chips and require specific firmware files in /lib/firmware/rtl_bt/. 2. Install Missing Firmware: If the adapter is detected but shows as "unconfigured," you may need to install the linux-firmware package or specific Realtek firmware packages provided by your distribution's repository. 3. Service Restart: Restart the Bluetooth service to ensure it picks up the new primary controller:

sudo systemctl restart bluetooth

Why Not Just Unplug It?

While physically unplugging the internal antenna is possible, it is invasive and voids warranties. Software blacklisting is non-destructive and reversible. Always remember that if you ever need to re-enable the internal Bluetooth (for example, if the USB adapter fails), you simply delete the blacklist file and reboot. Xmodmap Freezes KDE During Peripheral Connection discusses similar issues where peripheral detection causes system instability, highlighting the importance of ensuring drivers are stable before relying on them for critical functions like audio routing.

Frequently Asked Questions

Will blacklisting btintel break my Wi-Fi?

In most cases, no. The Intel AX210 handles Wi-Fi and Bluetooth through separate logical interfaces, even if they share physical components. However, on some rare firmware implementations, disabling the Bluetooth driver might prevent proper initialization of the entire card. Test your Wi-Fi connection after applying the blacklist before committing to the change.

How do I re-enable the internal Bluetooth?

To revert the changes, remove or comment out the line blacklist btintel in /etc/modprobe.d/blacklist-btintel.conf. Then, run the appropriate update command for your distribution (like update-initramfs -u) and reboot your system. The internal chip will return to normal operation.

My Realtek USB adapter is detected but won't pair devices.

This is often a firmware issue. Realtek adapters frequently require specific binary blobs located in /lib/firmware/rtl_bt/. Ensure your linux-firmware package is up to date. You can also check dmesg for error messages indicating missing firmware files when the adapter is plugged in.

Can I use both Bluetooth adapters simultaneously?

Technically yes, but it is highly discouraged. Operating two Bluetooth radios close together can cause significant interference, leading to dropped connections and poor audio quality. System daemons like BlueZ may also get confused about which controller to use for audio profiles, resulting in silent output or failed pairings.

What if my USB adapter uses a different chipset like CSR?

The blacklisting method remains the same regardless of the USB adapter's chipset. You only blacklist the *internal* Intel driver (btintel). The USB adapter will load its own generic or specific drivers automatically. Ensure the necessary firmware for your USB device is installed, but the removal of the Intel driver is independent of the USB hardware type.