USB 3.1 hub shown as USB 2.0












1















My problem is the following. My system is detecting my USB 3.1 Gen1 hub (onboard hub).



First, I confirmed that my motherboard does indeed have support for USB 3.1. I have an Asus H97-PRO which has obviously the H97 chipset which does have support for USB 3.1 Gen1. You can find listed in the Asus the following 6 x USB 3.1 Gen 1 port(s) (4 at back panel, blue, 2 at mid-board). So, my board does have support for USB 3.1 Gen1`.



If I do lsusb, I get two USB 2.0 hubs. I have one USB 2.0 hub and one USB 3.1 Gen1 hub.



Bus 002 Device 004: ID 04d9:a070 Holtek Semiconductor, Inc. 
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


If I do lsusb -t. I get the two hubs with a speed of 480M as expected.



/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M


Using one of my development boards, which has USB 3.0, I can confirm that when connected to a USB 3.1 port, it is forced to run on USB 2.0.



I have already ran update-usbids, update-pciids and added iommu=soft to GRUB_CMDLINE_LINUX_DEFAULT in the grub configuration.



I've ran out of ideas. Thanks in advance for everyone who tries to help.










share|improve this question


















  • 1





    Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

    – Stephen Kitt
    Oct 20 '17 at 19:37











  • I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

    – FFY00
    Oct 20 '17 at 19:44
















1















My problem is the following. My system is detecting my USB 3.1 Gen1 hub (onboard hub).



First, I confirmed that my motherboard does indeed have support for USB 3.1. I have an Asus H97-PRO which has obviously the H97 chipset which does have support for USB 3.1 Gen1. You can find listed in the Asus the following 6 x USB 3.1 Gen 1 port(s) (4 at back panel, blue, 2 at mid-board). So, my board does have support for USB 3.1 Gen1`.



If I do lsusb, I get two USB 2.0 hubs. I have one USB 2.0 hub and one USB 3.1 Gen1 hub.



Bus 002 Device 004: ID 04d9:a070 Holtek Semiconductor, Inc. 
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


If I do lsusb -t. I get the two hubs with a speed of 480M as expected.



/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M


Using one of my development boards, which has USB 3.0, I can confirm that when connected to a USB 3.1 port, it is forced to run on USB 2.0.



I have already ran update-usbids, update-pciids and added iommu=soft to GRUB_CMDLINE_LINUX_DEFAULT in the grub configuration.



I've ran out of ideas. Thanks in advance for everyone who tries to help.










share|improve this question


















  • 1





    Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

    – Stephen Kitt
    Oct 20 '17 at 19:37











  • I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

    – FFY00
    Oct 20 '17 at 19:44














1












1








1


1






My problem is the following. My system is detecting my USB 3.1 Gen1 hub (onboard hub).



First, I confirmed that my motherboard does indeed have support for USB 3.1. I have an Asus H97-PRO which has obviously the H97 chipset which does have support for USB 3.1 Gen1. You can find listed in the Asus the following 6 x USB 3.1 Gen 1 port(s) (4 at back panel, blue, 2 at mid-board). So, my board does have support for USB 3.1 Gen1`.



If I do lsusb, I get two USB 2.0 hubs. I have one USB 2.0 hub and one USB 3.1 Gen1 hub.



Bus 002 Device 004: ID 04d9:a070 Holtek Semiconductor, Inc. 
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


If I do lsusb -t. I get the two hubs with a speed of 480M as expected.



/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M


Using one of my development boards, which has USB 3.0, I can confirm that when connected to a USB 3.1 port, it is forced to run on USB 2.0.



I have already ran update-usbids, update-pciids and added iommu=soft to GRUB_CMDLINE_LINUX_DEFAULT in the grub configuration.



I've ran out of ideas. Thanks in advance for everyone who tries to help.










share|improve this question














My problem is the following. My system is detecting my USB 3.1 Gen1 hub (onboard hub).



First, I confirmed that my motherboard does indeed have support for USB 3.1. I have an Asus H97-PRO which has obviously the H97 chipset which does have support for USB 3.1 Gen1. You can find listed in the Asus the following 6 x USB 3.1 Gen 1 port(s) (4 at back panel, blue, 2 at mid-board). So, my board does have support for USB 3.1 Gen1`.



If I do lsusb, I get two USB 2.0 hubs. I have one USB 2.0 hub and one USB 3.1 Gen1 hub.



Bus 002 Device 004: ID 04d9:a070 Holtek Semiconductor, Inc. 
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


If I do lsusb -t. I get the two hubs with a speed of 480M as expected.



/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M


Using one of my development boards, which has USB 3.0, I can confirm that when connected to a USB 3.1 port, it is forced to run on USB 2.0.



I have already ran update-usbids, update-pciids and added iommu=soft to GRUB_CMDLINE_LINUX_DEFAULT in the grub configuration.



I've ran out of ideas. Thanks in advance for everyone who tries to help.







drivers usb hardware usb-device hardware-compatibility






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 20 '17 at 19:34









FFY00FFY00

265




265








  • 1





    Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

    – Stephen Kitt
    Oct 20 '17 at 19:37











  • I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

    – FFY00
    Oct 20 '17 at 19:44














  • 1





    Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

    – Stephen Kitt
    Oct 20 '17 at 19:37











  • I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

    – FFY00
    Oct 20 '17 at 19:44








1




1





Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

– Stephen Kitt
Oct 20 '17 at 19:37





Before anyone else asks, the lsusb -t output does indeed confirm that the kernel only sees USB 2 ports: USB 3 ports would appear as Class=root_hub, Driver=xhci_hcd/6p, 5000M (with a varying number of ports of course, the important part here is “5000M”).

– Stephen Kitt
Oct 20 '17 at 19:37













I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

– FFY00
Oct 20 '17 at 19:44





I just answered the question. For some reason the motherboard didn't came with XHCI enabled by default which I took for granted. Guess we can't trust in the manufacturers.

– FFY00
Oct 20 '17 at 19:44










2 Answers
2






active

oldest

votes


















2














Okay, for some reason my motherboard doesn't come with the XHCI support enabled by default. So if anyone is experiencing a similar issue just go and check if XHCI is enabled in the bios.






share|improve this answer

































    0














    Setting the xHCI to disabled allows the dual boot to function correctly.
    On dual-Boot between Window 10 and Linux Ubuntu 18.04 , the xHCI Controller bypasses the legacy usb ports (loads no legacy usb ports).
    As a result usb 3 port act as usb 2 port.






    share|improve this answer








    New contributor




    Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      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%2f399421%2fusb-3-1-hub-shown-as-usb-2-0%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









      2














      Okay, for some reason my motherboard doesn't come with the XHCI support enabled by default. So if anyone is experiencing a similar issue just go and check if XHCI is enabled in the bios.






      share|improve this answer






























        2














        Okay, for some reason my motherboard doesn't come with the XHCI support enabled by default. So if anyone is experiencing a similar issue just go and check if XHCI is enabled in the bios.






        share|improve this answer




























          2












          2








          2







          Okay, for some reason my motherboard doesn't come with the XHCI support enabled by default. So if anyone is experiencing a similar issue just go and check if XHCI is enabled in the bios.






          share|improve this answer















          Okay, for some reason my motherboard doesn't come with the XHCI support enabled by default. So if anyone is experiencing a similar issue just go and check if XHCI is enabled in the bios.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 22 '17 at 18:34

























          answered Oct 20 '17 at 19:42









          FFY00FFY00

          265




          265

























              0














              Setting the xHCI to disabled allows the dual boot to function correctly.
              On dual-Boot between Window 10 and Linux Ubuntu 18.04 , the xHCI Controller bypasses the legacy usb ports (loads no legacy usb ports).
              As a result usb 3 port act as usb 2 port.






              share|improve this answer








              New contributor




              Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                Setting the xHCI to disabled allows the dual boot to function correctly.
                On dual-Boot between Window 10 and Linux Ubuntu 18.04 , the xHCI Controller bypasses the legacy usb ports (loads no legacy usb ports).
                As a result usb 3 port act as usb 2 port.






                share|improve this answer








                New contributor




                Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  Setting the xHCI to disabled allows the dual boot to function correctly.
                  On dual-Boot between Window 10 and Linux Ubuntu 18.04 , the xHCI Controller bypasses the legacy usb ports (loads no legacy usb ports).
                  As a result usb 3 port act as usb 2 port.






                  share|improve this answer








                  New contributor




                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  Setting the xHCI to disabled allows the dual boot to function correctly.
                  On dual-Boot between Window 10 and Linux Ubuntu 18.04 , the xHCI Controller bypasses the legacy usb ports (loads no legacy usb ports).
                  As a result usb 3 port act as usb 2 port.







                  share|improve this answer








                  New contributor




                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 18 mins ago









                  Prakash KarkeePrakash Karkee

                  1




                  1




                  New contributor




                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Prakash Karkee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399421%2fusb-3-1-hub-shown-as-usb-2-0%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