How can I debug why my built-in bluetooth is not working?












6














I would like to see bluetooth devices over my computer. I have a Asus x79 Deluxe which supports Bluetooth 4.0. It would be nice if that worked under Linux.



I have installed the following packages:




  • bluez-utils

  • libopenobex1


I have blueman installed and clicked on "turn bluetooth on". After that, when I click on devices it does not see any. When I click on "Adapters" I get an empty popup.



What is the problem and how can I further investigate it / solve it?



My System



$ uname -a
Linux pc09 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/issue
Linux Mint 17 Qiana n l

$ lspci | grep -i blu
$ lsusb | grep -i blu
$ lshw | grep -i blu
$ lsmod | grep -i blu
bluetooth 391136 10 bnep,rfcomm
$ hciconfig --all


$ dmesg | grep -i blue
[ 3.746659] Bluetooth: Core ver 2.17
[ 3.746667] Bluetooth: HCI device and connection manager initialized
[ 3.746672] Bluetooth: HCI socket layer initialized
[ 3.746673] Bluetooth: L2CAP socket layer initialized
[ 3.746675] Bluetooth: SCO socket layer initialized
[ 3.796894] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.796898] Bluetooth: BNEP filters: protocol multicast
[ 3.796904] Bluetooth: BNEP socket layer initialized
[ 3.797018] Bluetooth: RFCOMM TTY layer initialized
[ 3.797021] Bluetooth: RFCOMM socket layer initialized
[ 3.797024] Bluetooth: RFCOMM ver 1.11

$ sudo hcitool scan
Device is not available: No such device

$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no


I am not sure, but I think the WLAN chipset BCM4352 is also the part that handles bluetooth.










share|improve this question
















bumped to the homepage by Community 27 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    6














    I would like to see bluetooth devices over my computer. I have a Asus x79 Deluxe which supports Bluetooth 4.0. It would be nice if that worked under Linux.



    I have installed the following packages:




    • bluez-utils

    • libopenobex1


    I have blueman installed and clicked on "turn bluetooth on". After that, when I click on devices it does not see any. When I click on "Adapters" I get an empty popup.



    What is the problem and how can I further investigate it / solve it?



    My System



    $ uname -a
    Linux pc09 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    $ cat /etc/issue
    Linux Mint 17 Qiana n l

    $ lspci | grep -i blu
    $ lsusb | grep -i blu
    $ lshw | grep -i blu
    $ lsmod | grep -i blu
    bluetooth 391136 10 bnep,rfcomm
    $ hciconfig --all


    $ dmesg | grep -i blue
    [ 3.746659] Bluetooth: Core ver 2.17
    [ 3.746667] Bluetooth: HCI device and connection manager initialized
    [ 3.746672] Bluetooth: HCI socket layer initialized
    [ 3.746673] Bluetooth: L2CAP socket layer initialized
    [ 3.746675] Bluetooth: SCO socket layer initialized
    [ 3.796894] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 3.796898] Bluetooth: BNEP filters: protocol multicast
    [ 3.796904] Bluetooth: BNEP socket layer initialized
    [ 3.797018] Bluetooth: RFCOMM TTY layer initialized
    [ 3.797021] Bluetooth: RFCOMM socket layer initialized
    [ 3.797024] Bluetooth: RFCOMM ver 1.11

    $ sudo hcitool scan
    Device is not available: No such device

    $ rfkill list
    0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    1: brcmwl-0: Wireless LAN
    Soft blocked: no
    Hard blocked: no


    I am not sure, but I think the WLAN chipset BCM4352 is also the part that handles bluetooth.










    share|improve this question
















    bumped to the homepage by Community 27 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      6












      6








      6







      I would like to see bluetooth devices over my computer. I have a Asus x79 Deluxe which supports Bluetooth 4.0. It would be nice if that worked under Linux.



      I have installed the following packages:




      • bluez-utils

      • libopenobex1


      I have blueman installed and clicked on "turn bluetooth on". After that, when I click on devices it does not see any. When I click on "Adapters" I get an empty popup.



      What is the problem and how can I further investigate it / solve it?



      My System



      $ uname -a
      Linux pc09 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

      $ cat /etc/issue
      Linux Mint 17 Qiana n l

      $ lspci | grep -i blu
      $ lsusb | grep -i blu
      $ lshw | grep -i blu
      $ lsmod | grep -i blu
      bluetooth 391136 10 bnep,rfcomm
      $ hciconfig --all


      $ dmesg | grep -i blue
      [ 3.746659] Bluetooth: Core ver 2.17
      [ 3.746667] Bluetooth: HCI device and connection manager initialized
      [ 3.746672] Bluetooth: HCI socket layer initialized
      [ 3.746673] Bluetooth: L2CAP socket layer initialized
      [ 3.746675] Bluetooth: SCO socket layer initialized
      [ 3.796894] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [ 3.796898] Bluetooth: BNEP filters: protocol multicast
      [ 3.796904] Bluetooth: BNEP socket layer initialized
      [ 3.797018] Bluetooth: RFCOMM TTY layer initialized
      [ 3.797021] Bluetooth: RFCOMM socket layer initialized
      [ 3.797024] Bluetooth: RFCOMM ver 1.11

      $ sudo hcitool scan
      Device is not available: No such device

      $ rfkill list
      0: phy0: Wireless LAN
      Soft blocked: no
      Hard blocked: no
      1: brcmwl-0: Wireless LAN
      Soft blocked: no
      Hard blocked: no


      I am not sure, but I think the WLAN chipset BCM4352 is also the part that handles bluetooth.










      share|improve this question















      I would like to see bluetooth devices over my computer. I have a Asus x79 Deluxe which supports Bluetooth 4.0. It would be nice if that worked under Linux.



      I have installed the following packages:




      • bluez-utils

      • libopenobex1


      I have blueman installed and clicked on "turn bluetooth on". After that, when I click on devices it does not see any. When I click on "Adapters" I get an empty popup.



      What is the problem and how can I further investigate it / solve it?



      My System



      $ uname -a
      Linux pc09 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

      $ cat /etc/issue
      Linux Mint 17 Qiana n l

      $ lspci | grep -i blu
      $ lsusb | grep -i blu
      $ lshw | grep -i blu
      $ lsmod | grep -i blu
      bluetooth 391136 10 bnep,rfcomm
      $ hciconfig --all


      $ dmesg | grep -i blue
      [ 3.746659] Bluetooth: Core ver 2.17
      [ 3.746667] Bluetooth: HCI device and connection manager initialized
      [ 3.746672] Bluetooth: HCI socket layer initialized
      [ 3.746673] Bluetooth: L2CAP socket layer initialized
      [ 3.746675] Bluetooth: SCO socket layer initialized
      [ 3.796894] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [ 3.796898] Bluetooth: BNEP filters: protocol multicast
      [ 3.796904] Bluetooth: BNEP socket layer initialized
      [ 3.797018] Bluetooth: RFCOMM TTY layer initialized
      [ 3.797021] Bluetooth: RFCOMM socket layer initialized
      [ 3.797024] Bluetooth: RFCOMM ver 1.11

      $ sudo hcitool scan
      Device is not available: No such device

      $ rfkill list
      0: phy0: Wireless LAN
      Soft blocked: no
      Hard blocked: no
      1: brcmwl-0: Wireless LAN
      Soft blocked: no
      Hard blocked: no


      I am not sure, but I think the WLAN chipset BCM4352 is also the part that handles bluetooth.







      bluetooth






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 25 '14 at 12:02

























      asked Sep 25 '14 at 11:49









      Martin Thoma

      1,14731942




      1,14731942





      bumped to the homepage by Community 27 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 27 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I am afraid BCM4352 is not supported by current Linux kernel's b43 driver. I would suggest trying Dell's or Broadcom's proprietary drivers instead, see also this answer for same problem on an older version of Ubuntu.



          If they provide a .deb package for Ubuntu 14, you'll likely be able to see the device with blueman and use it.



          NOTE: it will affect your wifi functionality as well






          share|improve this answer



















          • 1




            I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
            – Martin Thoma
            Sep 26 '14 at 13:30












          • And what does "PHY" mean on that page (in the table header row).
            – Martin Thoma
            Sep 26 '14 at 13:37










          • "PHY" is the radio chipset, see also the Wikipedia page
            – Deim0s
            Sep 26 '14 at 13:43










          • "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
            – Deim0s
            Sep 26 '14 at 13:45











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f157462%2fhow-can-i-debug-why-my-built-in-bluetooth-is-not-working%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          I am afraid BCM4352 is not supported by current Linux kernel's b43 driver. I would suggest trying Dell's or Broadcom's proprietary drivers instead, see also this answer for same problem on an older version of Ubuntu.



          If they provide a .deb package for Ubuntu 14, you'll likely be able to see the device with blueman and use it.



          NOTE: it will affect your wifi functionality as well






          share|improve this answer



















          • 1




            I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
            – Martin Thoma
            Sep 26 '14 at 13:30












          • And what does "PHY" mean on that page (in the table header row).
            – Martin Thoma
            Sep 26 '14 at 13:37










          • "PHY" is the radio chipset, see also the Wikipedia page
            – Deim0s
            Sep 26 '14 at 13:43










          • "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
            – Deim0s
            Sep 26 '14 at 13:45
















          0














          I am afraid BCM4352 is not supported by current Linux kernel's b43 driver. I would suggest trying Dell's or Broadcom's proprietary drivers instead, see also this answer for same problem on an older version of Ubuntu.



          If they provide a .deb package for Ubuntu 14, you'll likely be able to see the device with blueman and use it.



          NOTE: it will affect your wifi functionality as well






          share|improve this answer



















          • 1




            I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
            – Martin Thoma
            Sep 26 '14 at 13:30












          • And what does "PHY" mean on that page (in the table header row).
            – Martin Thoma
            Sep 26 '14 at 13:37










          • "PHY" is the radio chipset, see also the Wikipedia page
            – Deim0s
            Sep 26 '14 at 13:43










          • "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
            – Deim0s
            Sep 26 '14 at 13:45














          0












          0








          0






          I am afraid BCM4352 is not supported by current Linux kernel's b43 driver. I would suggest trying Dell's or Broadcom's proprietary drivers instead, see also this answer for same problem on an older version of Ubuntu.



          If they provide a .deb package for Ubuntu 14, you'll likely be able to see the device with blueman and use it.



          NOTE: it will affect your wifi functionality as well






          share|improve this answer














          I am afraid BCM4352 is not supported by current Linux kernel's b43 driver. I would suggest trying Dell's or Broadcom's proprietary drivers instead, see also this answer for same problem on an older version of Ubuntu.



          If they provide a .deb package for Ubuntu 14, you'll likely be able to see the device with blueman and use it.



          NOTE: it will affect your wifi functionality as well







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:22









          Community

          1




          1










          answered Sep 26 '14 at 13:22









          Deim0s

          535410




          535410








          • 1




            I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
            – Martin Thoma
            Sep 26 '14 at 13:30












          • And what does "PHY" mean on that page (in the table header row).
            – Martin Thoma
            Sep 26 '14 at 13:37










          • "PHY" is the radio chipset, see also the Wikipedia page
            – Deim0s
            Sep 26 '14 at 13:43










          • "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
            – Deim0s
            Sep 26 '14 at 13:45














          • 1




            I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
            – Martin Thoma
            Sep 26 '14 at 13:30












          • And what does "PHY" mean on that page (in the table header row).
            – Martin Thoma
            Sep 26 '14 at 13:37










          • "PHY" is the radio chipset, see also the Wikipedia page
            – Deim0s
            Sep 26 '14 at 13:43










          • "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
            – Deim0s
            Sep 26 '14 at 13:45








          1




          1




          I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
          – Martin Thoma
          Sep 26 '14 at 13:30






          I have seen that page. However, I have enabled a proprietary driver and WLAN seems to work. What does the wl in the column "alternative" mean?
          – Martin Thoma
          Sep 26 '14 at 13:30














          And what does "PHY" mean on that page (in the table header row).
          – Martin Thoma
          Sep 26 '14 at 13:37




          And what does "PHY" mean on that page (in the table header row).
          – Martin Thoma
          Sep 26 '14 at 13:37












          "PHY" is the radio chipset, see also the Wikipedia page
          – Deim0s
          Sep 26 '14 at 13:43




          "PHY" is the radio chipset, see also the Wikipedia page
          – Deim0s
          Sep 26 '14 at 13:43












          "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
          – Deim0s
          Sep 26 '14 at 13:45




          "wl" is just another wireless driver in Linux, but is not alternative to yours as you can see from that table, there's no point in trying it. You say that you have enabled a proprietary driver, but this is not what I said in the answer. You need to use the one provided by vendor (Dell/Broadcom/Asus...), if there's any available. Your chipset is not yet supported natively. So yes, it will be difficult to make it work.
          – Deim0s
          Sep 26 '14 at 13:45


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f157462%2fhow-can-i-debug-why-my-built-in-bluetooth-is-not-working%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt