Announcement

Collapse
No announcement yet.

Bluetooth issues on Kubuntu 26.04

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bluetooth issues on Kubuntu 26.04

    Hello everyone,

    A bit of background: just recently made the decision to switch from Windows 11 to Linux, and I settled on Kubuntu. I installed Kubuntu 26.04 on my recently purchased laptop. It feels very modern, snappy, and a joy to use as a complete Linux beginner. Installation was straightforward except for one small but important issue. Bluetooth does not seem to be working properly, if at all, prompting me to make my first post on this forum. Although I can see the bluetooth option, whenever I hit the switch to turn it on, it still says disabled. In the bluetooth configuration tool, there is no difference between the enabled and disabled state as the panel simply displays "disabled".

    Here is the inxi output:
    Code:
    System:
      Host: afloresrLIN Kernel: 7.0.0-15-generic arch: x86_64 bits: 64
      Desktop: KDE Plasma v: 6.6.4 Distro: Kubuntu 26.04 LTS (Resolute Raccoon)
    Machine:
      Type: Laptop System: LENOVO product: 21QA0036US v: ThinkPad X9-14 Gen 1
        serial: <superuser required>
      Mobo: LENOVO model: 21QA0036US v: SDK0T76576 WIN
        serial: <superuser required> Firmware: UEFI vendor: LENOVO
        v: N4DET39W (1.22 ) date: 02/11/2026
    Battery:
      ID-1: BAT0 charge: 30.3 Wh (54.6%) condition: 55.5/55.1 Wh (100.7%)
        volts: 11.68 min: 11.7
    CPU:
      Info: 8-core model: Intel Core Ultra 7 268V bits: 64 type: MCP cache:
        L2: 14 MiB
      Speed (MHz): avg: 1108 min/max: 400/5000:4900:3700 cores: 1: 1108 2: 1108
        3: 1108 4: 1108 5: 1108 6: 1108 7: 1108 8: 1108
    Graphics:
      Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] driver: xe
        v: kernel
      Display: wayland server: Xwayland v: 24.1.10 compositor: kwin_wayland
        driver: gpu: xe resolution: 2880x1800~120Hz
      API: EGL v: 1.5 drivers: iris,swrast
        platforms: gbm,wayland,x11,surfaceless,device
      API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.3-1ubuntu1
        renderer: Mesa Intel Graphics (LNL)
      API: Vulkan v: 1.4.341 drivers: intel,llvmpipe surfaces: N/A
      Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
        de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
        xdpyinfo, xprop, xrandr
    Audio:
      Device-1: Intel Lunar Lake IPU driver: N/A
      Device-2: Intel Lunar Lake-M HD Audio driver: sof-audio-pci-intel-lnl
      API: ALSA v: k7.0.0-15-generic status: kernel-api
      Server-1: PipeWire v: 1.6.2 status: active
    Network:
      Device-1: Intel BE201 320MHz driver: iwlwifi
      IF: wlp0s20f3 state: up mac: 80:13:16:1f:24:3a
    Bluetooth:
      Device-1: Intel driver: btintel_pcie
      Report: hciconfig ID: hci0 rfk-id: 1 state: down
        bt-service: enabled,running rfk-block: hardware: no software: yes
        address: 00:00:00:00:00:00
    Drives:
      Local Storage: total: 953.87 GiB used: 12.63 GiB (1.3%)
      ID-1: /dev/nvme0n1 vendor: Samsung model: MZAL81T0HFLB-00BLL
        size: 953.87 GiB
    Partition:
      ID-1: / size: 334.38 GiB used: 12.62 GiB (3.8%) fs: ext4 dev: /dev/nvme0n1p6
      ID-2: /boot/efi size: 1022 MiB used: 8.1 MiB (0.8%) fs: vfat
        dev: /dev/nvme0n1p5
    Swap:
      ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) file: /swapfile
    Sensors:
      System Temperatures: cpu: 40.0 C mobo: N/A
      Fan Speeds (rpm): fan-1: 0 fan-2: 0
    Info:
      Memory: total: 32 GiB note: est. available: 30.87 GiB used: 4.74 GiB (15.4%)
      Processes: 425 Uptime: 6h 13m Shell: Bash inxi: 3.3.40
    
    ​
    I also found similar post, but on older Ubuntu support forms. One user requested info from the command
    Code:
     sudo dmesg | grep -i bluetooth
    which is quite long:
    Code:
    [    2.831725] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
    [    2.915741] Bluetooth: Core ver 2.22
    [    2.924668] NET: Registered PF_BLUETOOTH protocol family
    [    2.924675] Bluetooth: HCI device and connection manager initialized
    [    2.924681] Bluetooth: HCI socket layer initialized
    [    2.924683] Bluetooth: L2CAP socket layer initialized
    [    2.924692] Bluetooth: SCO socket layer initialized
    [    3.131283] Bluetooth: hci0: Device revision is 0
    [    3.131286] Bluetooth: hci0: Secure boot is enabled
    [    3.131287] Bluetooth: hci0: OTP lock is disabled
    [    3.131288] Bluetooth: hci0: API lock is enabled
    [    3.131288] Bluetooth: hci0: Debug lock is disabled
    [    3.131289] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
    [    3.131290] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
    [    3.131837] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi
    [    3.131840] Bluetooth: hci0: Boot Address: 0x30098800
    [    3.131840] Bluetooth: hci0: Firmware Version: 107-8.26
    [    3.191602] Bluetooth: hci0: Waiting for firmware download to complete
    [    3.191606] Bluetooth: hci0: Firmware loaded in 58366 usecs
    [    3.193842] Bluetooth: hci0: Waiting for device to boot
    [    3.193873] Bluetooth: hci0: Device booted in 2208 usecs
    [    3.193874] Bluetooth: hci0: Waiting for device transition to d0
    [    3.193875] Bluetooth: hci0: Device moved to D0 in 0 usecs
    [    3.194165] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b
    [    3.196522] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi
    [    3.196531] Bluetooth: hci0: Boot Address: 0x10000800
    [    3.196533] Bluetooth: hci0: Firmware Version: 107-8.26
    [    3.219792] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.363859] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.379643] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.390905] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.400159] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.449742] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.449883] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.453865] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.454150] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.457536] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.457673] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.763998] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.764503] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.797153] Bluetooth: hci0: Waiting for firmware download to complete
    [    3.797156] Bluetooth: hci0: Firmware loaded in 586554 usecs
    [    3.832880] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    3.832913] Bluetooth: hci0: Controller in error state
    [    4.709061] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [    4.709069] Bluetooth: BNEP filters: protocol multicast
    [    4.709074] Bluetooth: BNEP socket layer initialized
    [    6.850639] Bluetooth: hci0: Timeout (3000 ms)  on alive interrupt, alive context: intel_reset1
    [    6.850660] Bluetooth: hci0: Failed to send frame (-62)
    [    6.850661] Bluetooth: hci0: sending frame failed (-62)
    [    6.850680] Bluetooth: hci0: Failed to send Intel Reset command
    [    6.850691] Bluetooth: hci0: Intel Soft Reset failed (-62)
    [    6.850696] Bluetooth: hci0: Firmware download retry count: 1
    [    6.889198] Bluetooth: hci0: Device revision is 0
    [    6.889205] Bluetooth: hci0: Secure boot is enabled
    [    6.889207] Bluetooth: hci0: OTP lock is disabled
    [    6.889208] Bluetooth: hci0: API lock is enabled
    [    6.889208] Bluetooth: hci0: Debug lock is disabled
    [    6.889209] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
    [    6.889211] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
    [    6.889541] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi
    [    6.889544] Bluetooth: hci0: Boot Address: 0x30098800
    [    6.889545] Bluetooth: hci0: Firmware Version: 107-8.26
    [    6.944220] Bluetooth: hci0: Waiting for firmware download to complete
    [    6.944241] Bluetooth: hci0: Firmware loaded in 53416 usecs
    [    6.946563] Bluetooth: hci0: Waiting for device to boot
    [    6.946566] Bluetooth: hci0: Device booted in 2248 usecs
    [    6.946569] Bluetooth: hci0: Waiting for device transition to d0
    [    6.946570] Bluetooth: hci0: Device moved to D0 in 1 usecs
    [    6.947150] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b
    [    6.951402] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi
    [    6.951425] Bluetooth: hci0: Boot Address: 0x10000800
    [    6.951429] Bluetooth: hci0: Firmware Version: 107-8.26
    [    6.964659] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    6.964785] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    6.992169] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.051268] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.051435] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.434444] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.434612] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.539240] Bluetooth: hci0: Waiting for firmware download to complete
    [    7.539253] Bluetooth: hci0: Firmware loaded in 574065 usecs
    [    7.575058] Bluetooth: hci0: Received gp1 mailbox interrupt
    [    7.575089] Bluetooth: hci0: Controller in error state
    [   10.562724] Bluetooth: hci0: Timeout (3000 ms)  on alive interrupt, alive context: intel_reset1
    [   10.562736] Bluetooth: hci0: Failed to send frame (-62)
    [   10.562738] Bluetooth: hci0: sending frame failed (-62)
    [   10.562784] Bluetooth: hci0: Failed to send Intel Reset command
    [   10.562788] Bluetooth: hci0: Intel Soft Reset failed (-62)
    [   10.609016] Bluetooth: hci0: Received hw exception interrupt
    [   10.609050] Bluetooth: hci0: Received gp1 mailbox interrupt
    [   10.610174] Bluetooth: hci0: Unsupported cnvi 0x00000000
    [   10.611239] Bluetooth: hci0: Received gp1 mailbox interrupt
    [   10.611290] Bluetooth: hci0: Controller in error state
    [   11.066877] Bluetooth: hci0: Timeout (500 ms) on tx completion
    [   11.066934] Bluetooth: hci0: Failed to send frame (-62)
    [   11.066935] Bluetooth: hci0: sending frame failed (-62)
    [   11.066983] Bluetooth: hci0: Failed to read MSFT supported features (-62)​
    Any help is appreciated.

    #2
    Welcome to KFN.
    Originally posted by element18 View Post
    I installed Kubuntu 26.04 on my recently purchased laptop.
    What make/model? Is it 'new'? Does it have a wifi/Bluetooth switch on the laptop?
    Windows no longer obstruct my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Hello,

      It is a Lenovo ThinkPad X9-14 Gen 1. It is new, meaning purchased directly from Lenovo. As far as I am aware, it does not have a physical switch.

      Comment


        #4
        Often one of the first things I do (done best before buying a new PC) is to have a look at the database of linux-hardware.org
        There you can browse which computer components of certain computer models are supported in different Linux distrubutions and if special drivers might generally be needed (e.g. for WLAN chips).

        This should be your model if I am not mistaken:
        https://linux-hardware.org/?view=computers&type=Notebook&vendor=Lenovo&model= ThinkPad+X9-14+Gen+1+%28All%29

        Very new computers might need the absolute newest e.g. kernel or firmware versions (newer than those in *Ubuntu) and if you are unlucky some components might never work in Linux. (sorry, this is the reality, I know e.g. of certain ASUS laptops where this is the case - which does not mean that this has to be true in your case).

        And welcome to the forum.
        Last edited by Schwarzer Kater; Yesterday, 02:37 PM.
        Debian LXQt • Kubuntu • openSUSE KDE • Linux Mint • Windows • macOS
        Desktop: HP Elite SFF 805 G9 • Laptop: Apple MacBook Pro 13" • and others

        important things to do after installation (24/26.04)get rid of Snap script (20.04 +)
        install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04 +)

        Comment


          #5
          Yes, perhaps I should have done that. As of right now, I still have Windows 11 OS installed on the laptop, just in case I need it for something or decide to go back, but I wanted to try fully committing to using Kubuntu as my daily driver. In that case, is there anything I could do to try to fix this problem? Where could I get these kernel or firmware versions you speak of? I believe my Wifi/bluetooth adapter is an Intel BE201 according to system information?

          Comment


            #6
            At first you will have to determine if Bluetooth of the Intel BE201 is supported at all and if yes which kernel and/or firmware versions are required at minimum for the support or if there is additional software you will have to install.
            You will have to search the internet for this and I think the link(s) I posted can also help with the search.

            This way you can determine if the hardware will work with Linux at all, if it will work specifically with *Ubuntu or if you possibly will have to change your distribution to something different.
            Debian LXQt • Kubuntu • openSUSE KDE • Linux Mint • Windows • macOS
            Desktop: HP Elite SFF 805 G9 • Laptop: Apple MacBook Pro 13" • and others

            important things to do after installation (24/26.04)get rid of Snap script (20.04 +)
            install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04 +)

            Comment


              #7
              https://www.intel.com/content/www/us...downloads.html
              https://bugs.launchpad.net/ubuntu/+s...e/+bug/2075564
              may be this going to work for you . all the best and congrats for new laptop .
              Last edited by Trinity-108; Today, 12:53 AM.

              Comment


                #8
                AI Overview

                Bluetooth issues on the BE201 (Intel Wi-Fi 7) chipset in early 2026 Ubuntu/Kubuntu versions are likely due to a linux-firmware regression. Users on Lunar Lake processors may experience broken Bluetooth functionality with linux-firmware version 20250311.b69d4b74-2, which can often be resolved by reverting to an older firmware version, such as 20250210.5bc5868b-1. [1]
                This video shows how to troubleshoot and fix Bluetooth adapter issues on Linux:

                Fix Bluetooth Adapter Issues on Linux


                Known Issues & Troubleshooting
                • Regression in linux-firmware: The 2025-03-11 firmware update broke BE201 Bluetooth.
                • Fix by Reverting Firmware: Reverting to linux-firmware version 20250210.5bc5868b-1 restores functionality.
                • Check Kernel Detection: Run sudo dmesg | grep -i blue to see if the kernel detects the device.
                • Check Module Loading: Use lsusb to check if the controller appears on the USB bus.
                • Power Cycle: Perform a full shut down and turn off the power supply to drain power from the card, which can fix initialization issues. [1, 2, 3]

                Potential Workarounds

                If the device is not appearing, a cold boot (shutting down, waiting 30 seconds, and restarting) is recommended to reset the Bluetooth module, as simply rebooting often fails to reset the hardware.




















                Windows no longer obstruct my view.
                Using Kubuntu Linux since March 23, 2007.
                "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                Comment


                  #9
                  your lappy seems like extremely new hardware ,that the kernel hasn't caught up with yet
                  try installing these bluetooth tools
                  Code:
                  sudo apt install bluez bluez-tools
                  then run
                  Code:
                  sudo hciconfig hci0 up
                  and
                  Code:
                  sudo btmgmt power on
                  If it fails with timeout/reset errors again, that confirms the firmware issue.
                  another thing to check maybe is:
                  Code:
                  rfkill list
                  if it says Soft blocked: yes , then unblock it with
                  Code:
                  sudo rfkill unblock bluetooth
                  and restart bluetooth
                  Code:
                  sudo systemctl restart bluetooth
                  ʟɨռʊӼ ʄօʀ ʟɨʄɛ

                  Comment

                  Users Viewing This Topic

                  Collapse

                  There are 0 users viewing this topic.

                  Working...
                  X