Bluetooth not working with xHCI (USB 3.0) on Intel 7260 chipset in Asus UX301LA












4















I can't make my laptop's onboard bluetooth to work correctly and permanently without disabling xHCI from BIOS.



Bluetooth is always shown as disabled after booting the computer. When trying to enable it from the bluetooth settings (click on bluetooth icon-> select "bluetooth settings") I get this from dmesg:



[  948.641625] usb 1-4: USB disconnect, device number 2
[ 948.912013] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ 949.041299] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[ 949.041305] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 949.055380] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 949.057370] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 949.233672] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated


I can see the bluetooth "switch" become on and back off immediately, at the same time the above dmseg messages appear.



My system:




  • Laptop Asus UX301LA

  • wireless and bluetooth interface is based on Intel 7260 chipset.

  • Ubuntu 14.10 with latest updates

  • (kernel 3.16.0-31-generic at the moment, and regularly updated)


What other tried and discovered



Here is a very complete thread which documents a long investigation by the author, and everything that has been tried so far by him.



What is causing my Intel 7260 bluetooth device to disconnect when I unblock it with rfkill?



And this is a bug report on the subject:



https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124



What I have already tried:



Following comment #7 I can get bluetooth to temporarily work along with xHCI. But this is VERY hacky and does not survives reboots, nor resists basic use of the laptop (like switching wifi on and off).



I have tried setting the option asus_nb_wmi wapf=X to 0,1,2,3, or 4 (in the file /etc/modprobe.d/asus_nb_wmi.conf) seeing no change in the behavior.



I also tried blacklisting btusb, since it might be loading too early (as suggested by Jeremy31: echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf). You can see here a snip from my dmesg.




  • Up to second 90, the computer had just booted up. Bluetooth settings shows that bluetooth is disabled.

  • At second 90, I click on the "switch" to enable bluetooth. The switch stays on, but bluetooth is obviously still not working (because we blacklisted it).

  • At second 99, I click on the switch to disable it.

  • Then on seconds 111, 118, 123 and 126, I repeat the last 2 steps, and get the same result.

  • On second 145 I ran sudo modprobe btusb to load btusb module again.

  • Finally, on second 157 I click on the switch again to enable bluetooth, but this time, it comes immediately back off.


So....



There could be a fix already released in newer versions of the kernel, which I don't know how to install nor try. If so, I am more than happy to try.



I would like to find a way to solve this problem definitely, in a way that survives reboots, and allows me to enable and disable bluetooth with the keyboard Fn buttons.



Thank you.










share|improve this question

























  • Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

    – Jeremy31
    Mar 26 '15 at 21:09











  • I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

    – chronos00
    Mar 29 '15 at 17:12











  • You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

    – Jeremy31
    Mar 29 '15 at 17:17











  • Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

    – chronos00
    Mar 29 '15 at 18:12











  • uname -a and I will help you with a new kernel

    – Jeremy31
    Mar 29 '15 at 18:38
















4















I can't make my laptop's onboard bluetooth to work correctly and permanently without disabling xHCI from BIOS.



Bluetooth is always shown as disabled after booting the computer. When trying to enable it from the bluetooth settings (click on bluetooth icon-> select "bluetooth settings") I get this from dmesg:



[  948.641625] usb 1-4: USB disconnect, device number 2
[ 948.912013] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ 949.041299] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[ 949.041305] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 949.055380] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 949.057370] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 949.233672] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated


I can see the bluetooth "switch" become on and back off immediately, at the same time the above dmseg messages appear.



My system:




  • Laptop Asus UX301LA

  • wireless and bluetooth interface is based on Intel 7260 chipset.

  • Ubuntu 14.10 with latest updates

  • (kernel 3.16.0-31-generic at the moment, and regularly updated)


What other tried and discovered



Here is a very complete thread which documents a long investigation by the author, and everything that has been tried so far by him.



What is causing my Intel 7260 bluetooth device to disconnect when I unblock it with rfkill?



And this is a bug report on the subject:



https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124



What I have already tried:



Following comment #7 I can get bluetooth to temporarily work along with xHCI. But this is VERY hacky and does not survives reboots, nor resists basic use of the laptop (like switching wifi on and off).



I have tried setting the option asus_nb_wmi wapf=X to 0,1,2,3, or 4 (in the file /etc/modprobe.d/asus_nb_wmi.conf) seeing no change in the behavior.



I also tried blacklisting btusb, since it might be loading too early (as suggested by Jeremy31: echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf). You can see here a snip from my dmesg.




  • Up to second 90, the computer had just booted up. Bluetooth settings shows that bluetooth is disabled.

  • At second 90, I click on the "switch" to enable bluetooth. The switch stays on, but bluetooth is obviously still not working (because we blacklisted it).

  • At second 99, I click on the switch to disable it.

  • Then on seconds 111, 118, 123 and 126, I repeat the last 2 steps, and get the same result.

  • On second 145 I ran sudo modprobe btusb to load btusb module again.

  • Finally, on second 157 I click on the switch again to enable bluetooth, but this time, it comes immediately back off.


So....



There could be a fix already released in newer versions of the kernel, which I don't know how to install nor try. If so, I am more than happy to try.



I would like to find a way to solve this problem definitely, in a way that survives reboots, and allows me to enable and disable bluetooth with the keyboard Fn buttons.



Thank you.










share|improve this question

























  • Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

    – Jeremy31
    Mar 26 '15 at 21:09











  • I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

    – chronos00
    Mar 29 '15 at 17:12











  • You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

    – Jeremy31
    Mar 29 '15 at 17:17











  • Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

    – chronos00
    Mar 29 '15 at 18:12











  • uname -a and I will help you with a new kernel

    – Jeremy31
    Mar 29 '15 at 18:38














4












4








4


2






I can't make my laptop's onboard bluetooth to work correctly and permanently without disabling xHCI from BIOS.



Bluetooth is always shown as disabled after booting the computer. When trying to enable it from the bluetooth settings (click on bluetooth icon-> select "bluetooth settings") I get this from dmesg:



[  948.641625] usb 1-4: USB disconnect, device number 2
[ 948.912013] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ 949.041299] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[ 949.041305] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 949.055380] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 949.057370] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 949.233672] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated


I can see the bluetooth "switch" become on and back off immediately, at the same time the above dmseg messages appear.



My system:




  • Laptop Asus UX301LA

  • wireless and bluetooth interface is based on Intel 7260 chipset.

  • Ubuntu 14.10 with latest updates

  • (kernel 3.16.0-31-generic at the moment, and regularly updated)


What other tried and discovered



Here is a very complete thread which documents a long investigation by the author, and everything that has been tried so far by him.



What is causing my Intel 7260 bluetooth device to disconnect when I unblock it with rfkill?



And this is a bug report on the subject:



https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124



What I have already tried:



Following comment #7 I can get bluetooth to temporarily work along with xHCI. But this is VERY hacky and does not survives reboots, nor resists basic use of the laptop (like switching wifi on and off).



I have tried setting the option asus_nb_wmi wapf=X to 0,1,2,3, or 4 (in the file /etc/modprobe.d/asus_nb_wmi.conf) seeing no change in the behavior.



I also tried blacklisting btusb, since it might be loading too early (as suggested by Jeremy31: echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf). You can see here a snip from my dmesg.




  • Up to second 90, the computer had just booted up. Bluetooth settings shows that bluetooth is disabled.

  • At second 90, I click on the "switch" to enable bluetooth. The switch stays on, but bluetooth is obviously still not working (because we blacklisted it).

  • At second 99, I click on the switch to disable it.

  • Then on seconds 111, 118, 123 and 126, I repeat the last 2 steps, and get the same result.

  • On second 145 I ran sudo modprobe btusb to load btusb module again.

  • Finally, on second 157 I click on the switch again to enable bluetooth, but this time, it comes immediately back off.


So....



There could be a fix already released in newer versions of the kernel, which I don't know how to install nor try. If so, I am more than happy to try.



I would like to find a way to solve this problem definitely, in a way that survives reboots, and allows me to enable and disable bluetooth with the keyboard Fn buttons.



Thank you.










share|improve this question
















I can't make my laptop's onboard bluetooth to work correctly and permanently without disabling xHCI from BIOS.



Bluetooth is always shown as disabled after booting the computer. When trying to enable it from the bluetooth settings (click on bluetooth icon-> select "bluetooth settings") I get this from dmesg:



[  948.641625] usb 1-4: USB disconnect, device number 2
[ 948.912013] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ 949.041299] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[ 949.041305] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 949.055380] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 949.057370] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 949.233672] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated


I can see the bluetooth "switch" become on and back off immediately, at the same time the above dmseg messages appear.



My system:




  • Laptop Asus UX301LA

  • wireless and bluetooth interface is based on Intel 7260 chipset.

  • Ubuntu 14.10 with latest updates

  • (kernel 3.16.0-31-generic at the moment, and regularly updated)


What other tried and discovered



Here is a very complete thread which documents a long investigation by the author, and everything that has been tried so far by him.



What is causing my Intel 7260 bluetooth device to disconnect when I unblock it with rfkill?



And this is a bug report on the subject:



https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124



What I have already tried:



Following comment #7 I can get bluetooth to temporarily work along with xHCI. But this is VERY hacky and does not survives reboots, nor resists basic use of the laptop (like switching wifi on and off).



I have tried setting the option asus_nb_wmi wapf=X to 0,1,2,3, or 4 (in the file /etc/modprobe.d/asus_nb_wmi.conf) seeing no change in the behavior.



I also tried blacklisting btusb, since it might be loading too early (as suggested by Jeremy31: echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf). You can see here a snip from my dmesg.




  • Up to second 90, the computer had just booted up. Bluetooth settings shows that bluetooth is disabled.

  • At second 90, I click on the "switch" to enable bluetooth. The switch stays on, but bluetooth is obviously still not working (because we blacklisted it).

  • At second 99, I click on the switch to disable it.

  • Then on seconds 111, 118, 123 and 126, I repeat the last 2 steps, and get the same result.

  • On second 145 I ran sudo modprobe btusb to load btusb module again.

  • Finally, on second 157 I click on the switch again to enable bluetooth, but this time, it comes immediately back off.


So....



There could be a fix already released in newer versions of the kernel, which I don't know how to install nor try. If so, I am more than happy to try.



I would like to find a way to solve this problem definitely, in a way that survives reboots, and allows me to enable and disable bluetooth with the keyboard Fn buttons.



Thank you.







14.10 bluetooth asus intel intel-wireless






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 29 '15 at 18:09







chronos00

















asked Mar 26 '15 at 16:08









chronos00chronos00

329314




329314













  • Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

    – Jeremy31
    Mar 26 '15 at 21:09











  • I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

    – chronos00
    Mar 29 '15 at 17:12











  • You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

    – Jeremy31
    Mar 29 '15 at 17:17











  • Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

    – chronos00
    Mar 29 '15 at 18:12











  • uname -a and I will help you with a new kernel

    – Jeremy31
    Mar 29 '15 at 18:38



















  • Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

    – Jeremy31
    Mar 26 '15 at 21:09











  • I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

    – chronos00
    Mar 29 '15 at 17:12











  • You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

    – Jeremy31
    Mar 29 '15 at 17:17











  • Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

    – chronos00
    Mar 29 '15 at 18:12











  • uname -a and I will help you with a new kernel

    – Jeremy31
    Mar 29 '15 at 18:38

















Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

– Jeremy31
Mar 26 '15 at 21:09





Have you tried loading the asus_nb_wmi module with a wapf parameter, echo "options asus_nb_wmi wapf=X" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf using 0, 1, 2, 3, or 4 in place of X and rebooting?

– Jeremy31
Mar 26 '15 at 21:09













I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

– chronos00
Mar 29 '15 at 17:12





I had forgot to mention in my original post that I had already tried the asus_nb_wmi wapf=X options. After reading your comment, I tried them all once again, just to be sure, and the behavior is still the same. In the first place, I don't have the file /etc/modprobe.d/asus_nb_wmi.conf, but I guess that is normal, and I just used your command to create an empty file with your proposed option. In second place, I don't see ANY difference at all, across reboots, after trying the different options. I will update my question's description to show this attemps.

– chronos00
Mar 29 '15 at 17:12













You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

– Jeremy31
Mar 29 '15 at 17:17





You might try blacklisting btusb with echo "blastlist btusb" | sudo tee /etc/modprobe.d/btusb.conf reboot and then sudo modprobe btusb to see if it is trying to load firmware to the bluetooth device too early and causing issues, if not you can remove the blacklist with sudo rm /etc/modprobe.d/btusb.conf

– Jeremy31
Mar 29 '15 at 17:17













Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

– chronos00
Mar 29 '15 at 18:12





Thank you for your promt reply Jeremy31. I tried your suggestions and posted the results in my question, as they were too long to post as a comment here.

– chronos00
Mar 29 '15 at 18:12













uname -a and I will help you with a new kernel

– Jeremy31
Mar 29 '15 at 18:38





uname -a and I will help you with a new kernel

– Jeremy31
Mar 29 '15 at 18:38










2 Answers
2






active

oldest

votes


















1














I solved this problem on my Asus Zenbook UX301L by replacing the Intel 7260 wifi/BT adaptor with an Intel 7265 wifi/BT adaptor. The problem immediately vanished. The only problem was getting the back off the UX301L. Not easy.






share|improve this answer































    0





    +50









    I had this error before but it was solved with some configurations in bios if you can just have a try!



    In USB configuration Enable



    Leagacy USB support
    USB 3.0 support
    XHCI Hand-off
    EHCI Hand-off


    and in SOUTH or NORTH bridge there will be option chipset go into it and.



    make XHCI mode Enable



    make USB2 Link Power Management Disbale



    make USB 2.0 (EHCI) Support Disable






    share|improve this answer
























    • I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

      – chronos00
      Apr 21 '15 at 16:07













    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f601618%2fbluetooth-not-working-with-xhci-usb-3-0-on-intel-7260-chipset-in-asus-ux301la%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I solved this problem on my Asus Zenbook UX301L by replacing the Intel 7260 wifi/BT adaptor with an Intel 7265 wifi/BT adaptor. The problem immediately vanished. The only problem was getting the back off the UX301L. Not easy.






    share|improve this answer




























      1














      I solved this problem on my Asus Zenbook UX301L by replacing the Intel 7260 wifi/BT adaptor with an Intel 7265 wifi/BT adaptor. The problem immediately vanished. The only problem was getting the back off the UX301L. Not easy.






      share|improve this answer


























        1












        1








        1







        I solved this problem on my Asus Zenbook UX301L by replacing the Intel 7260 wifi/BT adaptor with an Intel 7265 wifi/BT adaptor. The problem immediately vanished. The only problem was getting the back off the UX301L. Not easy.






        share|improve this answer













        I solved this problem on my Asus Zenbook UX301L by replacing the Intel 7260 wifi/BT adaptor with an Intel 7265 wifi/BT adaptor. The problem immediately vanished. The only problem was getting the back off the UX301L. Not easy.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 14 '16 at 17:38









        user594707user594707

        691156




        691156

























            0





            +50









            I had this error before but it was solved with some configurations in bios if you can just have a try!



            In USB configuration Enable



            Leagacy USB support
            USB 3.0 support
            XHCI Hand-off
            EHCI Hand-off


            and in SOUTH or NORTH bridge there will be option chipset go into it and.



            make XHCI mode Enable



            make USB2 Link Power Management Disbale



            make USB 2.0 (EHCI) Support Disable






            share|improve this answer
























            • I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

              – chronos00
              Apr 21 '15 at 16:07


















            0





            +50









            I had this error before but it was solved with some configurations in bios if you can just have a try!



            In USB configuration Enable



            Leagacy USB support
            USB 3.0 support
            XHCI Hand-off
            EHCI Hand-off


            and in SOUTH or NORTH bridge there will be option chipset go into it and.



            make XHCI mode Enable



            make USB2 Link Power Management Disbale



            make USB 2.0 (EHCI) Support Disable






            share|improve this answer
























            • I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

              – chronos00
              Apr 21 '15 at 16:07
















            0





            +50







            0





            +50



            0




            +50





            I had this error before but it was solved with some configurations in bios if you can just have a try!



            In USB configuration Enable



            Leagacy USB support
            USB 3.0 support
            XHCI Hand-off
            EHCI Hand-off


            and in SOUTH or NORTH bridge there will be option chipset go into it and.



            make XHCI mode Enable



            make USB2 Link Power Management Disbale



            make USB 2.0 (EHCI) Support Disable






            share|improve this answer













            I had this error before but it was solved with some configurations in bios if you can just have a try!



            In USB configuration Enable



            Leagacy USB support
            USB 3.0 support
            XHCI Hand-off
            EHCI Hand-off


            and in SOUTH or NORTH bridge there will be option chipset go into it and.



            make XHCI mode Enable



            make USB2 Link Power Management Disbale



            make USB 2.0 (EHCI) Support Disable







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 16 '15 at 16:07









            Tohid TamboliTohid Tamboli

            79946




            79946













            • I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

              – chronos00
              Apr 21 '15 at 16:07





















            • I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

              – chronos00
              Apr 21 '15 at 16:07



















            I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

            – chronos00
            Apr 21 '15 at 16:07







            I appreciate the effort, but these configurations are not available in the BIOS of Asus UX301 laptop. I only have 2 options about USB config, and I tried every possible combination of them, but none worked. Any other thing I could try from the module point of view?

            – chronos00
            Apr 21 '15 at 16:07




















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f601618%2fbluetooth-not-working-with-xhci-usb-3-0-on-intel-7260-chipset-in-asus-ux301la%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

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅