Announcement

Collapse
No announcement yet.

bluetooth works in live environment but not after installation

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    bluetooth works in live environment but not after installation

    hello there,

    for some reason bluetooth doesn't work on my PC (please see details below):

    application launcher > Bluetooth > Devices - KDE Control Module > "no bluetooth adapters have been found".

    Bluetooth did work when I tested Kubuntu 16.04 (before installing it). I wonder if it has something to do with any system update that followed...

    any idea? thanks.


    ------
    info about my system:

    - DISTRIB_RELEASE=16.04;
    - sorry "Alt+F2 then type dolphin then click on Help > About KDE" doesn't give any useful info about KDE...(that I can see..);
    - ~$ apt-cache show grub | grep ersion
    Version: 0.97-29ubuntu68
    Description-en_GB: GRand Unified Bootloader (Legacy version);

    -
    Asus ZenBook UX301LA
    -
    ~$ lscpu
    Architecture: x86_64
    CPU op-mode(s): 32-bit, 64-bit
    Byte Order: Little Endian
    CPU(s): 4
    On-line CPU(s) list: 0-3
    Thread(s) per core: 2
    Core(s) per socket: 2
    Socket(s): 1
    NUMA node(s): 1
    Vendor ID: GenuineIntel
    CPU family: 6
    Model: 69
    Model name: Intel(R) Core(TM) i5-4200U CPU @ 1.60G
    Stepping: 1
    CPU MHz: 1098.429
    CPU max MHz: 2600.0000
    CPU min MHz: 800.0000
    BogoMIPS: 4588.98
    Virtualisation: VT-x
    L1d cache: 32K
    L1i cache: 32K
    L2 cache: 256K
    L3 cache: 3072K
    NUMA node0 CPU(s): 0-3
    Flags: fpu vme de pse tsc msr pae mce cx8 api
    pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscal
    tant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonsto
    ni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma
    sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rd
    adow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2
    veopt dtherm ida arat pln pts


    ~$ lspci | grep aphic
    00:02.0 VGA compatible controller: Intel Corporation Haswell-
    troller (rev 09)

    #2
    What is the output from the following commands?
    Code:
    dmesg | grep -i blue
    and
    Code:
    dmesg | grep -i firmware
    If you're sitting wondering,
    Which Batman is the best,
    There's only one true answer my friend,
    It's Adam Bloody West!

    Comment


      #3
      ~$ dmesg | grep -i blue
      [ 4.160976] Bluetooth: Core ver 2.21
      [ 4.160995] Bluetooth: HCI device and connection manager initialized
      [ 4.161000] Bluetooth: HCI socket layer initialized
      [ 4.161003] Bluetooth: L2CAP socket layer initialized
      [ 4.161010] Bluetooth: SCO socket layer initialized
      [ 4.195635] Bluetooth: hci0: read Intel version: 370710018002030d00
      [ 4.212322] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
      [ 4.436652] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19)
      [ 6.343645] Bluetooth: hci0 command 0xfc8e tx timeout
      [ 6.343666] Bluetooth: hci0 sending frame failed (-19)
      [ 6.742689] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [ 6.742693] Bluetooth: BNEP filters: protocol multicast
      [ 6.742696] Bluetooth: BNEP socket layer initialized
      [ 8.347734] Bluetooth: hci0 command 0xfc11 tx timeout
      [ 14.436085] Bluetooth: hci0 exiting Intel manufacturer mode failed (-110)


      ~$ dmesg | grep -i firmware
      [ 1.869006] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x671f07)
      [ 4.212322] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
      [ 4.219456] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
      [ 4.224351] iwlwifi 0000:02:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm

      Comment


        #4
        As the next step run
        Code:
        rfkill list
        which should give output like
        Code:
        $ rfkill list
        0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no
        1: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no
        If bluetooth shows Soft blocked: yes then run
        Code:
        sudo rfkill unblock bluetooth
        If you're sitting wondering,
        Which Batman is the best,
        There's only one true answer my friend,
        It's Adam Bloody West!

        Comment


          #5
          it shows "no" (as far as I can see):

          ~$ rfkill list
          1: asus-wlan: Wireless LAN
          Soft blocked: no
          Hard blocked: no
          2: asus-bluetooth: Bluetooth
          Soft blocked: no
          Hard blocked: no
          3: phy0: Wireless LAN
          Soft blocked: no
          Hard blocked: no


          shall I run the last command anyway?

          Comment


            #6
            No, it won't do anything as it's already unblocked. So the next step is to have a look at
            Code:
            lsmod | grep -i bt
            and
            Code:
            hcitool dev
            which will check if the appropriate kenel modules are loaded.
            If you're sitting wondering,
            Which Batman is the best,
            There's only one true answer my friend,
            It's Adam Bloody West!

            Comment


              #7
              here you go:

              ~$ lsmod | grep -i bt
              btusb 45056 0
              btrtl 16384 1 btusb
              btbcm 16384 1 btusb
              btintel 16384 1 btusb
              bluetooth 520192 9 bnep,btbcm,btrtl,btusb,b


              ~$ hcitool dev
              Devices:



              Comment


                #8
                So that last command shows that the device is not being seen. I'm nearing the raggedy edge of my bluetooth knowledge here but just for giggles try restarting bluetooth. I think on 16.04 that would be
                Code:
                sudo systemctl restart bluetooth
                Also, is this a built in or plug in device?
                If you're sitting wondering,
                Which Batman is the best,
                There's only one true answer my friend,
                It's Adam Bloody West!

                Comment


                  #9
                  the last command didn't do anything, I'm afraid.
                  It's a built-in device - I had a look inside the Asus and it doesn't look like it can easily be removed without having to cut and soldier back wires.
                  I still find it funny that it used to work till very recently - in fact it stopped after installing Kubuntu. Not saying that it has anything to do with this, but it did work during the Kubuntu test/pre-install phase...

                  Comment


                    #10
                    I'm almost out of ideas here. As it works in the live environment, it may worth booting to that and looking at the output of the same commands to see if there are any differences (I would expect hcitool dev to be different!)

                    Hopefully someone with more knowledge will pay this thread a visit.
                    If you're sitting wondering,
                    Which Batman is the best,
                    There's only one true answer my friend,
                    It's Adam Bloody West!

                    Comment


                      #11
                      I re-booted and run the same commands - I can't see any difference (also hcitool dev looks the same).
                      as you said it'd be great if anyone could offer their view. I'd much appreciate it.
                      thanks in any case for your help.

                      Comment


                        #12
                        Originally posted by cadvanlei View Post
                        I re-booted and run the same commands - I can't see any difference (also hcitool dev looks the same).
                        as you said it'd be great if anyone could offer their view. I'd much appreciate it.
                        thanks in any case for your help.
                        Rebooting to a live environment?
                        If you're sitting wondering,
                        Which Batman is the best,
                        There's only one true answer my friend,
                        It's Adam Bloody West!

                        Comment


                          #13
                          OK, I|m now in a live environment. I can confirm that Bluetooth works flawlessly.

                          here is the output for the commands you gave me earlier:

                          ~$ dmesg | grep -i blue
                          [ 15.584314] Bluetooth: Core ver 2.21
                          [ 15.584334] Bluetooth: HCI device and connection manager initialized
                          [ 15.584338] Bluetooth: HCI socket layer initialized
                          [ 15.584341] Bluetooth: L2CAP socket layer initialized
                          [ 15.584348] Bluetooth: SCO socket layer initialized
                          [ 15.670771] Bluetooth: hci0: read Intel version: 370710018002030d55
                          [ 15.670775] Bluetooth: hci0: Intel device is already patched. patch num: 55
                          [ 16.767639] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                          [ 16.767642] Bluetooth: BNEP filters: protocol multicast
                          [ 16.767645] Bluetooth: BNEP socket layer initialized
                          [ 26.514264] Bluetooth: RFCOMM TTY layer initialized
                          [ 26.514274] Bluetooth: RFCOMM socket layer initialized
                          [ 26.514280] Bluetooth: RFCOMM ver 1.11

                          ~$ dmesg | grep -i firmware
                          [ 0.177451] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
                          [ 8.777644] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x671f07)
                          [ 15.686180] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
                          [ 15.770593] iwlwifi 0000:02:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm

                          ~$ rfkill list
                          0: hci0: Bluetooth
                          Soft blocked: no
                          Hard blocked: no
                          1: asus-wlan: Wireless LAN
                          Soft blocked: no
                          Hard blocked: no
                          2: phy0: Wireless LAN
                          Soft blocked: no
                          Hard blocked: no

                          ~$ lsmod | grep -i bt
                          btusb 45056 0
                          btrtl 16384 1 btusb
                          btbcm 16384 1 btusb
                          btintel 16384 1 btusb
                          bluetooth 520192 39 bnep,btbcm,btrtl,btusb,rfcomm,btintel

                          ~$ hcitool dev
                          Devices:
                          hci0 5C:51:4F:7B:4A:FC

                          i can see some differences, i wish i knew what they mean really

                          Comment


                            #14
                            It looks related to firmware (the dmesg output) so there are one or three last things to try, then I really am out of ideas

                            1. Reboot to your normal (not live) environment and run sudo apt install linux-firmware and reboot. If you get a message about it already being the latest version, go to step 2.

                            2. Run sudo apt install linux-firmware-nonfree and reboot. If you get a message about it already being the latest version, don't bother rebooting.

                            3. Run sudo apt-install intel-microcode and reboot

                            If any of these installs gets it working then stop; don't risk breaking it again
                            If you're sitting wondering,
                            Which Batman is the best,
                            There's only one true answer my friend,
                            It's Adam Bloody West!

                            Comment


                              #15


                              it's already the latest version:

                              ~$ sudo apt install linux-firmware
                              [sudo] password for weword:
                              Reading package lists... Done
                              Building dependency tree
                              Reading state information... Done
                              linux-firmware is already the newest version (1.157).
                              linux-firmware set to manually installed.
                              0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.



                              got troubles with the second, though...:

                              ~$ sudo apt-get install linux-firmware-nonfree
                              Reading package lists... Done
                              Building dependency tree
                              Reading state information... Done
                              E: Unable to locate package linux-firmware-nonfree

                              Comment

                              Working...
                              X